I enjoyed reading this. It could be because I'm thinking of doing more of system/network programming (and learning Zig). I've spent the last 6 years in the JavaScript land and bored of yet-another-bundling or SPA-like pattern.
So there's hope that with consistency and patience, one could build expertise in a totally different area
I'm also interested in more low level or systems programming, though I am coming from a mostly backend/system integration background. I feel like a roadblock is that I am self taught, and though I have been doing software engineering professionally for 15 years and software as a job for 20, I still can't call myself an engineer legally. I certainly know I can do the work, but I worry about hiring being wary of a lack of credentials as a legal liability for lower level stuff.
I would love to hear people's stories of interesting jobs they've gotten without a degree in this space.
Depends on the use-case, but if your product is <14 month lifecycle App/shovel-ware, than go JS for the labor compatibility... Yet if you are hitting >40k concurrent users, the options winnow down fairly quickly.
The OTP offers a flat/simple architecture, and most people are puzzled the first time they see a Phoenix channels demonstration.
I think it is hilarious people assume 3NF or 4NF db schema can save them from bad design. Yet, many have tried to make SQL scale efficiently (with some obvious caveats) =3
So there's hope that with consistency and patience, one could build expertise in a totally different area