I dunno. The stock price will probably dead cat bounce, but this is the sort of thing that causes companies to spiral eventually.
They just made thousands of IT people physically visit machines to fix them. Then all the other IT people watched that happen globally. CTOs got angry emails from other C-levels and VPs. Real money was lost. Nobody is recommending this company for a while.
They aren't good. Also, diffusion models work well for the artists to spit out pixels. The artists assume the LLM generated code is the same quality and that the OP is a fool who won't do what they ask due to lack of skill or stubbornness.
It's messing up the dynamic where creatives come up with blue sky stuff and developers come to a compromise on a possible solution. Now you have this AI model hallucinating plausible, but fake solutions.
The model says what they want to hear because it is a chicken, not a pig in this scenario.
You might like "Software Architecture: The Hard Parts." Though you already describe some of the points of the book. There isn't a magic bullet and every decision to split something apart or which parts to combine has various trade-offs.
The book isn't perfect. The use of afferent and efferent terminology and some of the arbitrary methods to put numbers on decisions weren't ideal. Most of the concepts are sound. The fact that almost every decision has cost/benefit and real world implications for a living product was refreshing. That a monolith can't be cut over instantly with zero effort to a perfect system is absolutely true.
It's good food for thought for anyone considering slicing up a monolith, but maybe don't follow it to the letter.
They just made thousands of IT people physically visit machines to fix them. Then all the other IT people watched that happen globally. CTOs got angry emails from other C-levels and VPs. Real money was lost. Nobody is recommending this company for a while.
It may put a dent in Microsoft as splash damage.