> So if you can sell those MT for $1-5, you're printing money.
The IF is doing a lot of heavy lifting there.
I understood the OP in the context of "human history has not produced sufficiently many tokens to be sent into the machines to make the return of investment possible mathematically".
Maybe the "token production" accelerates, and the need for so much compute realizes, who knows.
Less headcount usually means faster pace - less lines of comminication, less red tape etc.
Or at least that's what many C-level people believe to be true. "We need to move like a startup" is a common mantra repeated by executives, even megacorps like Amazon.
I guess it's true to some degree though, anecdotally as an IC at a tech company, I feel like I could move a lot faster if some people around me removed and replaced by an automation instead.
> I think politically, everyone would want airlines to have working IT-systems and they would probably want to pay $100 (rationally, closer to $1000) amortized over 50 years to pay for that, but apparently humanity is just too stupid to make it work.
Not stupid, just corrupt :)
If we did this, the money would get misappropriated or stolen - most likely completely legally through overpaid consulting fees.
So clearly we should pay someone to prevent that from happening.
> Are there really people out there who still reach for Meta-scale by default? Who start with microservices?
Anecdotally, the last three greenfield projects I was a part of, the Architects (distinct people in every case) began the project along the lines of "let us define the microservices to handle our domains".
Every one of those projects failed, in my opinion not primarily owing to bad technical decisions - but they surely didn't help either by making things harder to pivot, extend and change.
It kinda started with Clean Code. I remember some old colleagues walking around with the book in their hand and deleting ten year old comments in every commit they made: "You see, we don't need that anymore, because the code describes itself". It made a generation (generations?) of software developers think that all the architectural patterns were found now, we can finally do real engineering and just have to find the one that fits for the problem at hand! Everyone asked the SOLID principles during interviews, because that's how real engineers design! I think "cargo cult" was getting used at that time too to describe this phenomenon.
It was (is) bad. The worst part is they the majority of people pushing it haven’t even read Clean Code. They’ve read a blog post by a guy who read a blog post by a guy who skimmed the book.
reply