133,202 karma · joined December 12, 2010
Also, the increase in output is meaningless when the amount of customers doesn't scale in similar size.
Then there are the constraints of physics, there are so many humans in the planet that actually want to pay for a specific product, or consulting services.
If business can deliver the same product with a smaller team, great!
And yes this has been happening for a while, even if not everywhere.
In enterprise consulting, projects that would require a team of 20 devs on average, now have about 5.
Moving away from on-prem, managing own cloud infra to managed containers, to serverless, SaaS and iPaaS ready made products, and offshoring naturally.
All contributed to ever decreasing team sizes.
Now AI based tooling is added to that cocktail, reducing even further the team sizes.
The only folks doing well in the end, are the employees of AI companies, without moral issues contributing to the industry downfall, because the CEO themselves aren't the ones coding and pirating human culture.
Usually this was never an issue when becoming the one at the driving wheel, was due scaling up the ladder all the way from the bottom, or having the luck of being in the owners' family already.
Disgustes me as well, above all the layoffs only to give the money to the "poor" shareholders.
See how other economies are doing it.
Example,
https://docs.github.com/en/site-policy/other-site-policies/g...
However, like in any ISO languages, that only happens if enough people vote for it, and someone is willing to submit a paper in first place.
"The Power of Ten: Rules for Safety Critical Coding by Gerard Holzmann"
https://youtu.be/GRJtYwneG2Q?is=M0z7hnpQ78C8fLLP
At a moment he mentions a trick he played on JPL folks, his static analysis tool, instead of showing all the issues found, would only display the top 10, without telling them there were actually more than 10.
So they felt motivated to fix them, it were only 10 after all.
Naturally eventually they became aware of the trick.
Khronos and RISC-V now have locations outside US for a reason.
In some circles having the compiler dictate the way, and only true way, is seen as straightjacket programming.
It is hard to find, unless one knows the technical details.
WSL 1.0 was a Drawbrige picoprocess.
Your confusion is natural among those that aren't into Windows programming.
Here are the links for the related information,
https://www.microsoft.com/en-us/research/project/drawbridge
WSL 1.0 architecture,
https://learn.microsoft.com/en-gb/archive/blogs/wsl/pico-pro...
I am quite sure my MS-DOS C code is going to have some hard time being compiled on GCC 16.
Then they get irritated that not all C compiler vendors have the same language extensions or implementation defined behaviours they got used to rely on.