Comment by some_random
8 days ago
You can write cope like this all you want but it doesn't change the fact I can ship a feature in few days that previously would have taken me a few weeks.
8 days ago
You can write cope like this all you want but it doesn't change the fact I can ship a feature in few days that previously would have taken me a few weeks.
> I can
You can because, I guess, your project may have a small scope, few people working on it, no dependencies etc.
I cannot, because each line that I change has an effect in millions of other lines and hundreds of other people, and millions of users.
Different situation, different needs.
Wise words. Exactly what I would except from a millenium-old elf :P
> each line that I change has an effect in millions of other lines
That sounds like an architectural problem.
> That sounds like an architectural problem.
Each time a Linux system library changes a space, billions or trillions of lines of code around the world are affected by it. To encapsulate complexity does not mean to eliminate complexity.
I do not work at that level, but I work low enough in our system as to potentially affect much of it on each change.
If your changes only affect your own code is because is high level enough as to not have anything build over it.
Context matters.
It probably is, but show me a large AI assisted or vibe coded code base where this won’t be the case.
Shipping the happy path faster is easy. The part codegen hides is the month after, when teh weird edge cases start colliding and you're stuck reading a pile of code no one would have written on purpose.
That trade can still make sense for a throwaway MVP. Most people underestimate how fast the maintenance bill add up once the first non-obvious bug report lands.
I read that as you have never been debugging a production issue at 3am while losing data and/or revenue.
I don't. I did those things before AI so what's new?
The Googling you do to get an understanding of something you've never seen before can be done in a fraction of the time by AI.
A feature wasn't 10000 loc written by a AI before that no one except the AI with the context understands. If you review all that to understand it fully your productivity gain diminishes, the gain might not go away fully but it is much less when you can be woken up at 3am because of an incident and start reviewing everything.
2 replies →
AI helps in both, so not sure what your point is?
its like saying "don't write code because we will have to debug it later".
Well you aren't writing the code, the AI is and you are letting the AI debug that created it in the first place and it doesn't learn from the experience in the same way. Hopefully you understand the problem in such a degree that you can spec away the problem in the next iteration. I'm seeing that issue now, people just forget to learn what the issue is and keep repeating mistakes that are regurgitated from the training material.
Can you provide some examples?
THIS