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.
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.