Sort of, the one who, when left stranded on a desert island, would make a CPU out of sand, write software for it, including the entire TCP/IP stack, and email someone to come get them.
Yeah. Andy Tanenbaum described studying at MIT as "drinking from a fire hose". Do we have someone who both got their degree from MIT and worked at Bell Labs? That'd be an interesting combo.
What's the best path from zero to a fully legal status (visa first I imagine, but eventually citizenship) in the US for someone coming over from the Western Balkans (non-EU), with a bachelors degree in EE or CS and no prior work experience? Thanks for doing this.
The central point behind this type of books isn't so much to build an enterprise-grade production-ready thing, but rather to bridge the delta between zero and having a working thing of sufficiently large complexity, which inevitably exists for someone who had never been there before. Having that in mind, I think these books are very valuable.
Yeah. My favorite are books that guide you through implementing complex systems projects from scratch, like Nora Sandler's "Writing a C compiler", or Sy Brand's "Building a Debugger". I wish they produced A LOT more of them.
I'll admit that I'd used github copilot while I worked on one of my projects, and I couldn't help it but notice a rather significant cognitive decline whenever I set out to take over and start hammering out the code myself. I just can't allow cognitive declines.
I mean, it's not like I'm going to forget how to write code any time soon. I'm currently recovering from the n-th tough burnout, and I feel like I need a shift toward something new and meaningful. When it comes to job opportunities, from my perspective, knowing the entire stack (not in the webdev sense, but rather both hardware and software) makes you highly attractive on the market, in both worlds. So, while I genuinely can't predict what I'll end up doing 5 years from now, I do feel like it's time to familiarize myself with the other side of the entire stack.