Post

The cost of introducing and paying off tech debt has changed very, very much and I don't even know most of us have the time and space to think about what it means Tech debt has been so central to the software craft for decades, and now... how much does it matter?

because people will suddenly start reading the code again in 12-18 months? seems unlikely those who are still reading the code already know, and the rest don't care 🤷‍♂️

0 reposts1 like

You can incur tech debt while reading the code, the two things are unrelated. All this means is you can experiment faster and take on tech debt in service of some goal because it’s easier (read: cheaper) to fix in the future.

no one said you can't incur tech debt while reading the code claiming the two are "unrelated" is (excuse be but) preposterous

Sure they are. Incurring tech debt happens whether or not you read the code, when it’s done consciously, the decision is made outside of reading the code entirely. Even detecting most classes of it doesn’t require reading the code, observability, complexity checking, etc. have existed for years

debt happens whether or not you read the code, I never claimed it doesn't I claim it happens *less* when you read the code, more when you don't again, if you haven't read the code, you don't know what you don't know, which means you can't even ask debt happens either way - but at different rates

claiming it's easier to fix in the future is also fairly moot, because you can't fix it if you don't know it's there, and you won't find (all of) it unless you read the code if your agent could find it, it wouldn't exist in the first place alas 😌

IME tech debt is usually taken on consciously, and agents properly applied tend to be able to spot it more reliably than humans. Whether you take on tech debt or not has changed with agents, because often they can do it “right” to begin with, but a) not always and b) taking on TD is still useful at