replyifuagree

>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.

> logging into MS Teams

I mean, this is one application nobody should ever log into!

>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.

The tech debt is accelerating exponentially!

Those people on the boeing flights would have appreciated a little more of the correct motivations.

Instead they got McDonnell Douglas'd

As it turns out the motivations matter way more than you might think.

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.

You want to pay me bank to rubber stamp bad code? Weird flex but alright!

3. ...

4. ...

5. Profit!

If your competition figures out a way to cut overhead by 10% and you don't, they win. This is the normal outcome between similar businesses

The only thing that will save RTO companies now is graft and corruption.

I'd love to. First you need to get Tim Cook to stop sabotaging mobile web.

>(Shown above: my earnings from this bug.)

I lol'd!

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.

yeah, adding "AI" to something like that really means add in random nonsensical failures

Yep, Tim Cook = Steve Ballmer