This is my weekend project. I am building up my pattern recognition in machine learning. By that I mean see X problem, instantly think of Y solution. The primer markdown file is the artifact of that exploration.
read it from top to bottom or better have your favorite language model read it and then explore the space with a strong guided syllabus.
I personally think it is much more important to have strong statistical intuitions rather than intuitions about what neural networks are doing.
The latter isn’t wrong or useless. It’s simply not something a typical software engineer will need.
On the other hand, wiring up LLMs into an application is very popular and may be an engineer’s first experience with systems that are fundamentally chaotic. Knowing the difference between precision and recall and when you care about them will get you a lot more bang for your buck.
I would suggest the gateway drug into ML for most engineers is something like: we have a task and it can currently be done for X dollars. But maybe we can do it for a tenth of the price with a different API call. Or maybe there’s something on Huggingface that does the same thing for a fixed hourly cost, hundreds of times cheaper in practice.
Just read a good textbook instead of this LLM-written stuff. For example those by Murphy or Prince or Bishop. Or one of many YouTube lecture series from MIT or Stanford. There are many primer 101 tutorials and Medium posts. But if you actually want to learn instead of procrastinating, pick up a real textbook or work through a course.
my apologies it wasn't up to your standards. In fairness to me, that line is exactly what my effort was. I wasn't trying to "learn ML" I am trying to build a mental model that let's me decompose real problem into ML primitives.
It's unclear to me if you think the resource has no value or if it bother you that I wrote it using a coding agent.
I wrote the syllabus and worked through each section. Where my understanding was weak I explored the space, pulled in research, referred the model to other sources, and just generally tried to ground the topic in something I understood.
What resulted was something that helped a lot of subjects click together for me. Especially when to reach for a particular activation function and the section on gating.
This enter survey was motivated by an ML expirent I ran with assosicative memories that just failed horribly. So rather than post mortem that I set about understanding why it failed.
Anyhow, thank you for the feedback. I submitted this in good faith that it may help others.
Block pages that contain a construct that is commonly used by humans in human writing and has been for centuries because AI that trained on human writing also uses it?
Should we also block pages that contain no spelling errors or no grammatical errors?
Nice weekend project! Even though there are copious resources out there (textbooks, videos, etc.), those may not appeal to everyone. People have different preferred modalities for consuming information and there is always value in (correctly) reframing concepts in a way that can be better understood by people who don’t resonate with traditional textbooks and YouTube videos. I’m
glad you found a formulation that works for you, and judging by the number of upvotes, it resonated with others as well. At the very least, I’m sure that working on this improved your understanding as well!
Please stop trying to trick us into reading AI generated text.
"This isn't a textbook or a tutorial. It's a mental model — the abstractions you need to reason about ML systems the way you already reason about software systems."
It's not a trick bud. The github page shows my user name and Claude. The content is intended to be read by an AI agent and explored through a text interface. That is explicit in the readme and the primer itself.
If you think you can generate this artifact with a prompt then show me. This was 2 days of exploration and research.
11 comments
[ 3.8 ms ] story [ 33.3 ms ] threadread it from top to bottom or better have your favorite language model read it and then explore the space with a strong guided syllabus.
The latter isn’t wrong or useless. It’s simply not something a typical software engineer will need.
On the other hand, wiring up LLMs into an application is very popular and may be an engineer’s first experience with systems that are fundamentally chaotic. Knowing the difference between precision and recall and when you care about them will get you a lot more bang for your buck.
I would suggest the gateway drug into ML for most engineers is something like: we have a task and it can currently be done for X dollars. But maybe we can do it for a tenth of the price with a different API call. Or maybe there’s something on Huggingface that does the same thing for a fixed hourly cost, hundreds of times cheaper in practice.
It's unclear to me if you think the resource has no value or if it bother you that I wrote it using a coding agent.
I wrote the syllabus and worked through each section. Where my understanding was weak I explored the space, pulled in research, referred the model to other sources, and just generally tried to ground the topic in something I understood.
What resulted was something that helped a lot of subjects click together for me. Especially when to reach for a particular activation function and the section on gating.
This enter survey was motivated by an ML expirent I ran with assosicative memories that just failed horribly. So rather than post mortem that I set about understanding why it failed.
Anyhow, thank you for the feedback. I submitted this in good faith that it may help others.
Should we also block pages that contain no spelling errors or no grammatical errors?
"This isn't a textbook or a tutorial. It's a mental model — the abstractions you need to reason about ML systems the way you already reason about software systems."
If you think you can generate this artifact with a prompt then show me. This was 2 days of exploration and research.