The problem I encounter more frequently is: Advertised number is high %, then after considering all risks and terms and conditions it is sub average.

In principle I like it, what I don't like is that some companies will use the data only for their own benefit / dystopian nightmare mission.

Another comment here claims their license forbids that.

Interesting, is there something like this for azure

I was initially inspired by the https://instances.vantage.sh/, so, like them, I want to add other providers later. Like Azure and GCP.

It would also be interesting to have cross-provider comparison. I think it's doable. Thanks!

I think the more stressful part is the management expectation that things will speed up more, especially when you can generate plausible looking frontends relatively quickly. And if you have out of touch control-freak management without any technical experience, you waste more life time arguing with them.

Of course you also might exhaust yourself to some degree, as your own expectation might be that you can develop multiple things in parallel, while also having to review a lot of code where you might not have context, so in a way you have to hold more high level context in your brain state, what might be somewhat stressful. However, when you have been tech lead once, all of that is somewhat familiar.

For marketing purposes it is always too dangerous, not saying it is safe

Interesting that there is consumer protection in US. But aren't dark patterns like everywhere?

Spreadsheets.

Had the same thought, since it is kinda slow (only have 4 pyhsical/8 logical cores though). But I think vRAM might be a problem (8gb can work, if one has a rather recent gpu (here m1/2 might be interesting)).

Often ICs stay for 2 years in a company, start a project, but aren't happy with org/management/career progression and move to the next company before having to deal with the problems they have created. Eventually other developers who weren't assigned on this project now also need to maintain this project, without having the detailed knowledge of existing mechanisms and prevalent tech debt. Those developers did work on their own project and now need to care about both or even more projects.

The developers are basically invisible to upper management. PMs are the point of contact which translate between higher managment and the devs. Higher management often operates on such a high level, that they are disconnected from reality and work on a abstract level, basically using the inputs of the PMs. The PMs often also were never that technical, instead they realized soon that career progression is only possible in mgmt. This leads to the incentive to spawn new projects a PM can lead.

Eventually there are too many (poorly defined) projects with too few (original) developers. New developers are unhappy since they have to work with legacy code and the devs who are spread over multiple projects and still have some original knowledge, don't have enough time/incentive to properly take care about project development (plus, spent a lot of time in "agile" meetings for each project). Adding no career paths for devs (since the company only focuses on mgmt), this leads again to the starting point, where the ICs leave the company.

“There’s class warfare, all right, but it’s my class, the rich class, that’s making war, and we’re winning.”

― Warren Buffett