3 ms·
>don’t buy it. As software developers we learn technologies for breakfast. This is such a funny mantra. Okay learn how nuclear fission works. Or EUV lithograph
by mathisfun123 3y ago
>don’t buy it. As software developers we learn technologies for breakfast.
This is such a funny mantra. Okay learn how nuclear fission works. Or EUV lithography. Or power transmission across superconductors. All of these are extant, commercial, technologies (yes even the last one). Too much? How about something more pedestrian like overhead cams and electric fuel injection? Too far afield? Okay learn how DMA works on a GPU - not how to call `copy(host, device)` but what actually happens and more importantly why.
The truth is software developers learn APIs, not technologies (and not over breakfast either). Point being, it's not good to be haughty because if tomorrow you were out of a job and the only place hiring was the Ford motor plant I think you'd be just as fucked as the author of the post.
- somsak2 3y agoYou're just arguing semantics. And the example given can go the other way: if your Ford motor plant closes and the only places hiring are software shops, you'd also be "fucked".
- mathisfun123 3y ago> You're just arguing semantics I never have any clue what this retort means: when exactly are semantics (the meanings of things) not important? > Ford motor plant closes and the only places hiring are software shops, you'd also be "fucked". That's one hundred percent true but the difference is I don't see assembly plant workers going around claiming they learn technologies for breakfast (or lunch or dinner).
- johnnyanmac 3y ago>when exactly are semantics (the meanings of things) not important? arguing over meanings when we should understand the meanings tends to mean you're nitpicking instead of clarifying. There's clarification and then there's bike shedding.
- mtizim 3y agoAs software developers we learn software technologies for breakfast, not entire industrial processes...