I offer an alternative perspective. After a few years you become skilled to the point where you are not learning on the job. Also you start to dive into tech that is outside your job.
At this point the job is not there for growth. Its not needed for growth. Like a chef, you are there to make good dishes known by the patrons. Not change the menu every week.
Well seasoned engineers want stability and professionalism. They want consistent processes that cteate stable systems. Learning new tech for learnings sake is not growth. Its a headache.
But their readers dont understand correct methods. The readers dont see any difference between the current way and what you are suggesting. This is a uniquely hacker news read of the story.
The env should be known. If you cant control the env then you shouldnt be writing the script. If someone runs your script on a windows machine and it fails its not the script writers fault. There is a level of assumed resources.
Microservices and monoliths have never been about cog load. Its an implementatiom detail that solves scaling, deployment and team managment problems.
The cog load should be fairly similar weather you jave micro or monolith.
There are good and bad abstractions but in the end the cog load is a sum of the leaves and this never changes in the tree. In fact the cog load is better with bad abstraction , or no abstraction.
Hard coding is no cog load. Its in that file that function for that feature.
We are infinity in the making. You are living at the peek of this entity.
This has always been true but take some account for it and where it might go.
Fist it wa the mountain peaks, then it was the continents next stop the ends of the galaxy.
You are either an engineer tryig to make money or one trying to advance mankind. Weather it be a js lib, curing cancer or building a rocket. We all have our part.
Maybe relatively speaking we are meaningless now but in time we will define our place in the universe together. Just like the molecules in your body work together to make meaning from a blank file.
I see a lot of comments about the governments responsibility.
There are two main ideas to approach.
1. It is in the govs interest to protect this private entity for tax rev and ability to anex it in war time. (we need some extra oil and a landing strip , this place looks good, your airport/farm is now the militarys till the war is over)
2. A private entity is protected by the gov no matter how big or small. As long as it doesnt break the law. This position is not about calculating current value of this one entity but of the general value of portection. This airport foesnt function not only are these tax/tourist revs lost but maybe others.
Its not about building a culture to grow stars but to grow a place stars want to be.
Its mostly money and clarity , no politics.
I look at valve and think thats a good place to be an engineer. But they dont let any one in. Stars arent born or created. They are willed by the individual.
You put george washington carver in a field of peanuts he becomes a chemist. You put 40% of college students in fundies 1 and they drop out by the third week.
At this point the job is not there for growth. Its not needed for growth. Like a chef, you are there to make good dishes known by the patrons. Not change the menu every week.
Well seasoned engineers want stability and professionalism. They want consistent processes that cteate stable systems. Learning new tech for learnings sake is not growth. Its a headache.