AI can catch some failure modes, especially common ones, but it doesn’t really have the context of how your system behaves in production — traffic, retries, data size, edge cases, etc.
That’s usually where things break.
So the real difference isn’t organic vs AI, it’s whether someone understands the system they’re shipping into.
If you know how to code a particular fix, be an Engineer first, AI assisted.
If you have no idea about codebase and less confidence, then become AI first engineer
Disagree on the second sentence - that attitude is how I'm seeing production systems break all over the place these days. "I don't know, so the AI output must be correct."
I see it as not having authority to deploy code to production without a human review. And that review cannot be done unless you understand the systems you are working on.
Believe me, I absolutely hear all the people saying you need to be all-in on AI coding. But I disagree because that doesn't resonate with what I'm seeing in the real world, which is breakage, outages, incidents, and pissed off customers.
It's been a decade coding for me. Strong in fundamentally and my mental model wired in and out in coding now. AI is making writing faster me. But not sure how would younger generation would navigate this clouded AI coding maze and down in 10 years make them resilient.
AI can catch some failure modes, especially common ones, but it doesn’t really have the context of how your system behaves in production — traffic, retries, data size, edge cases, etc.
That’s usually where things break.
So the real difference isn’t organic vs AI, it’s whether someone understands the system they’re shipping into.
Hybrid-coding, organic implies a complex cause-n-effect organism, not single a human with probabylistic search engine.
If you know how to code a particular fix, be an Engineer first, AI assisted. If you have no idea about codebase and less confidence, then become AI first engineer
Disagree on the second sentence - that attitude is how I'm seeing production systems break all over the place these days. "I don't know, so the AI output must be correct."
hymm. interesting perspective. curious to know where you see AI will fit in in our coding task?
I see it as not having authority to deploy code to production without a human review. And that review cannot be done unless you understand the systems you are working on.
Believe me, I absolutely hear all the people saying you need to be all-in on AI coding. But I disagree because that doesn't resonate with what I'm seeing in the real world, which is breakage, outages, incidents, and pissed off customers.
I am completely aligned with you.
I am all-in to support AI-assisted coding.
I totally disagree AI first coding.
It's been a decade coding for me. Strong in fundamentally and my mental model wired in and out in coding now. AI is making writing faster me. But not sure how would younger generation would navigate this clouded AI coding maze and down in 10 years make them resilient.
If our "organic" codes are valuable than Agent's, and there is someone who demands organic, I could say yes.
I prefer artisan coding :)
This is new term for me but I love it