>If instead you wait when there is a real fire, you can get the 15 teams actually fixing that one.
In this case, with Microsoft's really amazing revenue stream, a charismatic management team can distort reality for quite some time and convince the right people within the company that there is no fire.
>I personally can't accept shipping unreviewed code. It feels wrong. The product has to work, but the code must also be high-quality.
Sadly review isn't enough. I just today I found some code that I reviewed 2 months where the developer clearly used an agent to generate the code and I completely missed some really dumb garbage the agent put in. The agent took a simple function that returns an object with some data and turned it into a mess that required multiple mocks in the tests (also generated by the agent).
The dev is a junior and a clear example of what is to come, inexperienced people thinking coding is getting an agent to get something to pass CI.
Another key difference is that wood itself has built in visual transparency as to the goodness of the solution - as it is pretty easy to figure out that a cabinet is horrible (I do get that there are defects in wood joining techniques that can surface after some time due to moisture, etc - but still, lot of transparency out of the box). Software has no such transparency built in.
The advantage of hand coded solutions is that the author of the code has some sense of what the code really does and so is a proxy for transparency, vibe coded solutions not so much.
I mean, it is 2025 and still customers are the best detectors of bad software over all quality apparatus to date.
As in all things, it depends. For example if you have an iron clad exit plan after you land that promotion for "delivering" a steaming pile for someone else to debug, and you have no sense of shame, then by all means!
>swap every postgres insert query, with the corresponding mysql insert query.
If the data and relationships in those insert queries matter, at some unknown future date you may find yourself cursing your choice to use an LLM for this task. On the other hand you might not ever find out and just experience a faint sense of unease as to why your customers have quietly dropped your product.
This is why I still haven't pulled the trigger on home automation stuff. Bad enough keeping my laptop functioning, don't want that experience extending to the rest of my life!
>“Value to the company” means furthering the explicit plans of your company’s executives
If you are a software leader, work on discovering and filling customer needs. Filling those will boost both your success and the company's success.
Executives at most companies rarely do anything other than figure out how to get a bigger paycheck. They have no clue about, nor do they try to discover, customer needs; but they have and aggressively acquire a strong sense of their upchain's needs.
This means a software leader who does basic research on customer needs is the one-eyed in the kingdom of the blind at most companies.
In this case, with Microsoft's really amazing revenue stream, a charismatic management team can distort reality for quite some time and convince the right people within the company that there is no fire.