HACKER Q&A
📣 lexi-k

Is it time for "organic" coding?


Yesterday at work I was testing my library's changes with my college in their system.

As AI first engineers we just prompted Claude to make progress.

After 2 hours of integration lazyness of letting AI run the tests, make changes and fix bugs I just suddenly decided to make the final changes myself.

You know like move the code, fix the bug, rename the function, run formatter, but even write the commit message and push upstream.

Then I looked at my college funny and said - you will love my last change, it will finally work as it's an organic commit. And this got me thinking.

Is it already time for the term "organic" to be used in coding?

  👤 kathir05 Accepted Answer ✓
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
👤 Lazy_Player82
If our "organic" codes are valuable than Agent's, and there is someone who demands organic, I could say yes.
👤 GeoSys
I prefer artisan coding :)
👤 a1exnd3r
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.

👤 pancsta
Hybrid-coding, organic implies a complex cause-n-effect organism, not single a human with probabylistic search engine.