Programmers of the past didn’t have to work 2 jobs to be able to buy a house and live comfortably, less alone spend most of their paycheck on inflated prices for gas, food, services, etc.
But hey we got AI and Amazon Prime now.
Not to mention the sense of pioneering something. Like I imagine calculating the Moon landing is something you’re happy to spend 80+ hours a week on, especially when basic needs are taken care of.
something you’re happy to spend 80+ hours a week on, especially when basic needs are taken care of.
Vs writing the same thing that already exists with a different front end, a bunch of times with different examples, because somebody who has more resources (not just more cash, but also time) decides visuals are more important than real functionality.
Part of the reason I don’t like ‘coding’ or developing software its because is so dreadful and feels overly stupid when an open source alternative works better than what you’d be able to make before the deadline.
I just rather be a CTO / SysAdmin and live happier.
Margaret Hamilton’s first job out of undergrad was working for Lorenz. She was incredibly accomplished with several stints in top labs, by the time of Apollo. It’s not like opportunities for trail blazing software fell out of the sky on shlubs who barely passed undergrad data structures and algorithms courses.
shlubs who barely passed undergrad data structures and algorithms courses.
And that’s the problem with most people getting into IT nowadays, they expect to go to an algorithms course or a development bootcamp and come out knowing everything to make a 6 figure salary, but don’t even try to learn what a software dependency is or how to fix their dev environment and expect GPT to shlub it up, when in reality many of these old school software programmers were self learning nerds who were just trying to solve (a) problem, and spent hours doing so.
don’t even try to learn what a software dependency
Everyone at my company keeps using the term “dependency hell” when referring to literally dependency management and order of operations with a modern package manager like NPM that tracks versions and dependencies.
They’ve literally never experienced working with dynamically linked libraries and they think it’s so hard because they have to understand a tree that exists in data form (e.g. package-lock.json) and can be easily visualized vs a tangled file system and LD_LIBRARY_PATH or Windows standard search order / HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\KnownDLLs.
These guys are living in the glory. I bet they don’t even know all the info they need is just in a fucking config file, in a damn manual somewhere or in the stupid docs that people doesn’t seem to bother reading anymore, or writing some decent ones.
Programmers of the past didn’t have to work 2 jobs to be able to buy a house and live comfortably, less alone spend most of their paycheck on inflated prices for gas, food, services, etc. But hey we got AI and Amazon Prime now.
Not to mention the sense of pioneering something. Like I imagine calculating the Moon landing is something you’re happy to spend 80+ hours a week on, especially when basic needs are taken care of.
Vs writing the same thing that already exists with a different front end, a bunch of times with different examples, because somebody who has more resources (not just more cash, but also time) decides visuals are more important than real functionality.
Part of the reason I don’t like ‘coding’ or developing software its because is so dreadful and feels overly stupid when an open source alternative works better than what you’d be able to make before the deadline.
I just rather be a CTO / SysAdmin and live happier.
Margaret Hamilton’s first job out of undergrad was working for Lorenz. She was incredibly accomplished with several stints in top labs, by the time of Apollo. It’s not like opportunities for trail blazing software fell out of the sky on shlubs who barely passed undergrad data structures and algorithms courses.
And that’s the problem with most people getting into IT nowadays, they expect to go to an algorithms course or a development bootcamp and come out knowing everything to make a 6 figure salary, but don’t even try to learn what a software dependency is or how to fix their dev environment and expect GPT to shlub it up, when in reality many of these old school software programmers were self learning nerds who were just trying to solve (a) problem, and spent hours doing so.
Everyone at my company keeps using the term “dependency hell” when referring to literally dependency management and order of operations with a modern package manager like NPM that tracks versions and dependencies.
They’ve literally never experienced working with dynamically linked libraries and they think it’s so hard because they have to understand a tree that exists in data form (e.g.
package-lock.json) and can be easily visualized vs a tangled file system andLD_LIBRARY_PATHor Windows standard search order /HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\KnownDLLs.It’s pathetic.
These guys are living in the glory. I bet they don’t even know all the info they need is just in a fucking config file, in a damn manual somewhere or in the stupid docs that people doesn’t seem to bother reading anymore, or writing some decent ones.