2,647 karma · joined April 20, 2025
Yes, let's fix the foundation. It will make adding features easier once the debt is paid off. And we will probably learn how to do better in the future. It reminds me of settings compiler warning to be treated as errors. Once you do that, you have a ton of work to do. But if you are smart (not all devs are), you learn why the warnings are there and avoid these problems in the future.
I used to work at startup that did video encoding. We had tons of computer vision scientists that refused to learn decent C++ coding practices. Their stuff never worked right and they didn't really contribute much. We also had a few scientists who were decent coders and pretty much all progress came from them.
I see the same with some data scientists. They want to do pure data science and refuse to do the coding to actually get their data. So they have to be spoon fed all the time and their progress is super slow.
I used to do that but it's a dangerous game. If you don't make sure to still be very visible to management further up, you end up with a stalled career or being laid off.
"don't even bother to check it."
I have to admit it gets really exhausting to review the AI output. It comes in so fast and more and more it's quite good. So it's very tempting to get more relaxed about reviews. I guess in a sense manual coding gave you some mental downtime while writing code. With AI you don't get that anymore. It's always full speed.
Neither do Anthropic and OpenAI.
I highly doubt that New Mexico will get 25. Although it would be nice since I live in New Mexico.
It also took the industry quite a while to accept that server code needs to be secure even if that requires a lot of extra effort. AI will probably be the same.
I agree that with AI it's very tempting to throw together a bunch of code without any thought of the longer term. But a lot of people are acting as if all programmers are artisans that produce well written code following the highest standards. That is just not true.