If you never LGTM’d when a colleague dropped a hefty PR on your lap, why would you do the same if it were a robot

I love using AI, but any feature it creates I test the hell out of it, i become the QA testers I hated and do all sort of ways to break the app, and after 100 or so hours, I have a bug free and fully working app, now will this app scale as I add more features that to be seen.

By taking responsibility of it, maybe by saying "Hey this is not a good idea", and if that doesn't work perhaps by switching jobs if that's an option?

The mental gymnastics developers are willing to go through just so they can avoid standing up for something is quite perplexing.

>How are you handling this?

easy, don't write code with LLMs. If my job forced me to do so I would quit.

I'm building a high level code explorer, like the CASE systems of a long time ago I suppose. I also built a facility called zork that lets me and an agent explore the code system together like a dungeon, taking notes as I go and if you want to take the metaphor too far, 'invoking spells' or rather commands like code references, call flow, data flow, exception flow, profiling, labelling design patterns and validating implementation, etc.

With zork I can also just start typing in a code file and leave instructions for the agent to fill in or fix parts of the code while I'm editing it. So I can lay out what I want the class shape to be and don't have to implement all the annoying little parts. This feels more like the GitHub Copilot days.

I honestly believe more of us will pair program with agents, not just yelling at a chat window.

if you have to maintain it, you will still have to get an understanding of it when it breaks.

not understanding the detail is quite similar to a coworker writing the code and another coworker approving and merging the changes.

At the end of the day it's really about developing a feel for it:

You will know intuitively if it's worth taking a closer look or if u can safely close your eyes and just commit it right away.

I usually know which meta questions are crucial to clarify with colleagues and where to check the code punctually.

Drink and pray.

An engineer from Meta not knowing what they're doing is exactly how I imagined engineers at Meta. Thank you for confirming it's an actual reality.

On the other hand, not even surprised anymore most people even try to provide serious answers to this. Welcome to the pure insanity.

Flat-out, you _need_ to understand the code you're merging. If you don't, ownership then lands on whatever AI agent you're using. Ultimately, you can't fire the AI agent in the same way you can fire the person at the driver seat when shit hits the fan and they've consistently caused incidents that force people to work late hours to resolve it.