rstagi

Thank you mate! Please share your feedback :)

Thank you for your thoughtful answer!

Just to be clear: I haven’t made up my mind yet either :) that’s why I asked a question and avoided delivering truths or anything

Everything you said are all doubts I have, and especially the “it works until it doesn’t” is my biggest fear.

I’m probably less afraid of the “once it stops you’re screwed” part, I have been working in places where taking up codebases and products full of tech debt and renewing them was the norm, so I believe in the worst case that’s still doable.

So I’m not saying it’s an easy and straightforward revolution, yet I’m not so negative about it :)

Fair point on the QA, I might have some strong take there but it’s a chapter I’d rather not open now, but I guess the point of my post is on the last sentence of yours: is looking at the code really necessary to prevent headaches?

I have started delegating chunks of code without looking, and many times when I do look for one reason or another (I still want to know the big picture!) they looked good to me. So my idea it’s just that it could work, but I’m still experimenting as most of us :)

“More bugs” is different from “a bunch of bugs”, and I agree on the support nightmare. My statement was implying that without looking at the code we might still be able to release something good quality that doesn’t fire back :)

Yes I meant delivering value ofc, and I love the framing you propose, so my question is: are we already at the point where we could go safely faster, if we didn’t look at the code?

Speeding up delivering value to the users seem a pretty good goal to me tbh

Great example! You usually don’t look both ways if you have a semaphor though, so maybe all we need is good semaphors. I hope the metaphor holds :)

Anyone else who tried and can share their experience?

neovim + claude code + open terminal is exactly my setup! But all the heavy lifting I used to do simply I’m not doing it anymore. I spend most of the time creating new worktrees and reviewing code, and I guess I’m just not interested about the implementation details that much (not that I don’t look at the code, but minor styling things I just ignore them right now) I’m transitioning to this new way of work btw, so I still haven’t made up my mind. That’s why I asked for someone else opinion here :)

I see a lot of valid points, so let me specify better: now that the way we write code drastically changed, did you change anything in your vim setup? Like plugins, habits, anything?

Right now I'm using TMUX with Claude Code and Vim side-by-side, but I mostly use vim to look at the code and make small changes, while I review the code changes directly on GitHub PRs.

And yes, I admit I look at the code less than before. For as much as I'd like to say it's untrue, I'm increasingly spending time in crafting skills to make sure they don't break the code, trusting the Coding Agent more and more, and consequently looking less at the code itself (which it doesn't mean I don't know how it works, I am in a sort of "reviewer mode" as a coworker writes it, with additional care and attention ofc).

So yeah I was wondering how did it change for you and if you think it still makes sense (it's my understanding that the agreement is "yes" apparently, with which I tend to agree!)

What you’re saying is super interesting, I’ve been using my setup for so long I might have missed some of the latest updates. I spend most of my time on TMUX with Claude Code and vim side by side btw, but I’m using it just to search some specific code and making small changes. I mostly review on GitHub PRs tbh

yeah I've been saying the same, AI has multiplied the blast radius

Maybe I don't use LinkedIn that much, but I saw it especially on X and Reddit... Just today I was on a Reddit post and saw so many AI sloppish comments from people trying to farm karma

Honestly same way I did before, checking periodically. There's a real challenge though: I'm getting less and less knowledgeable about the details of my own code, so it's hard to fact-check everything all the time.

Anyway, for now we're assisting to either outdated Docs (Coding Agents often don't even look at them), or to over-bloated ones (the slop is not just in the code). We should probably still find a balance between human readable docs (e.g. README.md) and LLM-tailored ones (e.g. llms.txt)

I think yes, I will keep using it for some analysis and documentation tasks, I think it's been really good at those. Also when I really wanna make sure about the quality of some piece of code, if not too large (otherwise I'll break it down first).

This is only feasible if you have a company and you can spend those money, I wouldn't if it was for personal use

"best" is a relative term, but in terms of technology we all use every day I would say either Linus Torvalds or Jeff Dean are up there among the best for sure

They're so easy to miss, but usually if you catch them immediately they issue the refund

I think we have roughly the same rate of people following the hype as in the past, but their spamming capabilities is like 10x because of AI. I believe it'll adjust by itself, but for now let's brace through it together

"MCP Inspector [...] never sees the traffic between your client and your server." This line resonates a lot, what you're building makes sense to me! I had built something similar to track these interactions and turn them into a benchmark, I'm gonna try this out.