undefined

points

[-]

The current AI tools extremely good at telling you about how an existing system works. You don't need that one super knowledgeable person anymore.

With the right MCPs or additional context you can have the tools go read PRs or the last 10 tickets that impacted the system and even go out and read cloud configuration or log files to tell you about problems.

The concept of a "bus factor" is a relic of the past.

by pigon10024 days ago|

parent|

[-]

I feel the same way. AI coding skills seem to sit somewhere between intermediate and advanced. Unless you’re working in a space where you’ve thought very deeply and developed your own solutions—those “gotcha, you didn’t know this” kinds of problems—it doesn’t really feel like AI falls short.

So far, I’ve been reading through almost 100% of the code AI writes because of the traps and edge cases it can introduce. But now, it feels less like “AI code is full of pitfalls” and more like we need to focus on how to use AI properly.

by raw_anon_11113 days ago|

prev|

[-]

Understanding the system and understanding the code is different. The “system” I just mentioned was “architected” by me just like I would have done in 2018 when I first started with AWS (but with 20 years of experience with coding).

I know what every module does (well Lambda in my case but I’m trying to be more generic), I know the abstractions, I know the business case, etc.

As a team lead/architect, even with other people writing code, I don’t know every line of code does. Claude code/Codex is just a junior/mid level developer to me