Red Rozenglass on Nostr: Feoh A funny coincidence, I was literally just watching some vids by ...
Feoh (nprofile…23qj) A funny coincidence, I was literally just watching some vids by https://www.youtube.com/@Asianometry about the quantum mechanics of microelectronics. It is not my area of specialty, but I also think it's not outrageous for a software developer to know the general ideas of their dependencies down to the base level of quantum physics.
Every engineering discipline does that, they go down to the bottom of physics when creating things, why should software engineers be any different? It is impossible if you're working in a disgusting swamp of over 10,000 dependency packages maintained by a million different people isolated from each other, so just don't do that. An engineer building a bridge doesn't introduce 10,000 materials that they need to factor into their calculations, instead, they cut out everything but the essentials. If you're working in an intentional, minimal, methodically engineered code-base, those things are not crazy.
I was contracted to debug a software issue once, an issue that perplexed two software developers before me. After days of digging and experiments, turned out to be a hardware-level electromagnetic interference issue corrupting data in-transfer. It's not rocket surgery. Physics exist. You can't just ignore it. It is completely feasible to at least read the general outline of the code of every dependency you use in a project, especially production ones, especially if you're selling to hospitals and schools and public infrastructure. All this cargo-culting, all the illusions people are telling themselves, are because they're lazy, privileged (complaining about the top 1% not knowing that they're the 1% with their $200K+ salaries), don't want to read, write, or think, and most importantly, they block their empathy behind those tech abstractions, to protect themselves from realizing that the slowness of their web app costs 10 million people 10 extra seconds each, per-day, and that amounts to 115 years of human life, per-year. Their stupid app is doing the equivalent of unnecessarily murdering 1.4 innocent people per year, and they feel nothing about it, sipping on their Starbucks, they say smugly: "Developer time is more expensive than machine time", as if to magically absolve themselves from their responsibility, or revel in their complacency in eroding the human soul, because for some reason, developers' souls are more expensive or something.
Aaaanyway, I'm just ranting by now. A decade of work in the industry got me here. But I'm still hopeful, otherwise I would have left a long time ago. I'm hopeful that people would take responsibility, that they would finally honor their craft, and know that behind every system they make are real human souls being shaped and moved. Or put more practically, that the people who see the errors of our ways, would out compete the sloppy masses in the market of ideas and production.
Or maybe, a man can dream ^-^
Every engineering discipline does that, they go down to the bottom of physics when creating things, why should software engineers be any different? It is impossible if you're working in a disgusting swamp of over 10,000 dependency packages maintained by a million different people isolated from each other, so just don't do that. An engineer building a bridge doesn't introduce 10,000 materials that they need to factor into their calculations, instead, they cut out everything but the essentials. If you're working in an intentional, minimal, methodically engineered code-base, those things are not crazy.
I was contracted to debug a software issue once, an issue that perplexed two software developers before me. After days of digging and experiments, turned out to be a hardware-level electromagnetic interference issue corrupting data in-transfer. It's not rocket surgery. Physics exist. You can't just ignore it. It is completely feasible to at least read the general outline of the code of every dependency you use in a project, especially production ones, especially if you're selling to hospitals and schools and public infrastructure. All this cargo-culting, all the illusions people are telling themselves, are because they're lazy, privileged (complaining about the top 1% not knowing that they're the 1% with their $200K+ salaries), don't want to read, write, or think, and most importantly, they block their empathy behind those tech abstractions, to protect themselves from realizing that the slowness of their web app costs 10 million people 10 extra seconds each, per-day, and that amounts to 115 years of human life, per-year. Their stupid app is doing the equivalent of unnecessarily murdering 1.4 innocent people per year, and they feel nothing about it, sipping on their Starbucks, they say smugly: "Developer time is more expensive than machine time", as if to magically absolve themselves from their responsibility, or revel in their complacency in eroding the human soul, because for some reason, developers' souls are more expensive or something.
Aaaanyway, I'm just ranting by now. A decade of work in the industry got me here. But I'm still hopeful, otherwise I would have left a long time ago. I'm hopeful that people would take responsibility, that they would finally honor their craft, and know that behind every system they make are real human souls being shaped and moved. Or put more practically, that the people who see the errors of our ways, would out compete the sloppy masses in the market of ideas and production.
Or maybe, a man can dream ^-^