Bro, if I don’t have to sit there for a half hour banging out code to map structure A on to structure B, I won’t. I’ll let someone else write it and spend 5 minutes to check that the code is clean and it works

Vibe coding is you not reviewing what the model outputs. I read every line, often give feedback and tell the model about patterns I want to use.

I probably write like 60-70% of the code myself.

I disagree about better code. Claude has been pretty bad at understanding external context and deriving why you’re doing something from the implementation. This can result in wonky structure that you need to fix, or at the very least tell Claude to redo over and over untill it looks clean and organized.

Honestly, never been on a team that stuck to TDD. As you test your stuff, and understand whatever libraries and apis you’re calling you modify your implementation as you go.

For public facing methods, especially ones called by customers, having pre agreed upon tests matter more but usually that’s at the integration test and system test level. I usually use AI for unit testing and read what was written. Tests end up being a lot of writing harnesses and setting up mocks that you delegate to the model and if there’s gaps or incorrect requirements, you change them.

I would never let the agent define the code structure. It doesn’t understand business processes or what might need to be extended or we’re instead about.

I’ve been doing software for a while, I know how to review code. I don’t vibe code, I let the model implement boilerplate and mapping functions while I do other stuff, like manual testing or talking with product. If done correctly, you can incorporate generative models into your workflows without fully handing over all control.

There’s an anecdote that comes up in software about people working on missile software not caring about memory leaks because it’s going to explode anyway before that becomes an issue.

Who cares about bugs in your software if it’s a hobby project that’s going to blow up anyway.

Also, including Claude doesn’t inherently mean vibe coded, it can be for writing tests, small components, or debugging.

Over the years I think I care less about some public apology or statement to accept that a creator has moved past old behavior (I assume you’re talking about the bridge, I don’t really follow PewDiePie).

We see too many fake apologies and if it’s been some time, apologizing just gives an opportunity for viewers to dogpile when someone is trying to move past something.

I think if it’s been a few years and he’s clearly shown to have grown past it, that’s enough for me. You never really know what a content creator’s private beliefs are just how they choose to use their public persona.

It’s a case of “we do these things not because they are easy, but because we thought they would be easy”

The admin wants to be these lofty world changing leaders and refuse to listen to people who tell them things are more complicated than they are. They don’t read about other countries or governments outside of their own propaganda so they are really that dumb and flying blind.