It reminds me of when everyone was trying to build their own frontend framework. Like "neat, I agree with this in concept, but I don't trust your code or you to maintain this project"
This feels right. It fits the "Assembly to C" style transition of abstraction in that we're going from "code to design of code."
A question I've been struggling with, however, is what are the artifacts that live at this level? Are they design docs? Are they standardized? If I read your design docs, will I understand the code or do I need to "decompile" (use a coding agent to explain) to get back to this level of abstract for me to edit it?
Definitely. IMO, plumbing is one of those trades that videos on YouTube seem to help a lot more than an LLM. Code and simple stuff an LLM is great, but anything more complex or getting into heavy installation not so much.
The phones are watches are primarily sold on annual leases through carriers. And no one is buying them for the chips, it's all camera and form factor.
The macs, on the other hand, can more easily swap between chips in manufacturing. And the form factor is pretty static. So Apple, in a race to have the best chip in the field at any given time, is just releasing them as soon as they're ready.
I agree the whole "m5 max > m6" is confusing, but I think they figure only the nerds who learn the specifics are going to care anyway.
As someone who teaches AI at a university, understanding the basics of how the LLM works is really invaluable to understanding where and how they'll be applied.
You're right that it's probably a little too in the weeds, but it's also a nice clear and fun objective that teaches you the basics. Like building a TODO list in JavaScript to learn webdev or a Gameboy emulator in C++ to learn how a CPU works.