Like a junior engineer, I find the models to be too ambitious and unable to steer themselves at a high level yet. What I’ve done to address this is prompting the model to break down its plans into more atomic steps. For whatever reason, they’re still lazy at planning.
Programming is human. Obviously there will be cultures (and cults) that spring up and die down all the time. I probably pissed off a few colleagues over the years by rejecting their arguments because they were “appeals to authority” that I did not recognize as authorities in the particular problems we were solving at the time. Hate cargo cult programming, but admit I fell into that trap often enough in my early years. Gotta start somewhere.
Oracle overcommitted on behalf of OpenAI, taking on debt to meet their obligations. Not that healthy companies are not also doing ridiculous layoffs, but in this case, Oracle does have to do some drastic things to get out of this tailspin.
I agree with this take for experienced and capable engineering teams. Three times over the last three years, I have told my senior engineers to skip code review, and nothing catastrophic happened, and recovery from bugs was rapid. Three times I have been told by engineering management to reimplement code review. Now that management is either gone or about to be gone.
Four years ago I was a reluctant maintainer of a Cloudflare workers setup. At the time, my thoughts were “Cloudflare is not my app, yet because of these workers, it’s performing business logic, which doesn’t feel right. I want Cloudflare to just be a dumb shield preventing DDOS attacks.”
Now that I’ve used it for a few years professionally, my opinions are much more nuanced and hard to put into words. Cloudflare’s products are mostly pretty good, and the cost savings are very attractive. You just have to be willing to work at their level.
I use Claude Code on a 900kloc Rails/JS monolith and it’s still pretty pleasant. However if it wasn’t already structured well, I could see that being a worse experience.
There’s really nothing in the article that speaks to savings due to “AI” per se, and the timeline really doesn’t work out. I suspect this is just another executive wanting to jump on claiming “we’re AI now!”