2 ms·
> Isn't it more useful to think of code not as an asset but as a liability? Yes. I love to code and I love that metaphor. One day while browsing Reddit/TIFU, a
by bayindirh 3y ago
> Isn't it more useful to think of code not as an asset but as a liability?
Yes. I love to code and I love that metaphor. One day while browsing Reddit/TIFU, a post jumped at me: "TIFU by creating and releasing a Reddit plugin for Firefox/Chrome, because I'll have to maintain it for my whole life."
It's so funny, true and enlightening at the same time.
> most people use it as a synonym for "bad code"
For me, "tech debt" is the suboptimal solution you shoehorned in the last minute because you don't have any alternative course at that moment (time, brain fog, etc.), which can boil to bad code, in general.
Presence of code itself is not the technical debt itself.
- ruszki 3y agoAs I became senior, I realised that you always have that alternative course. It’s definitely a skill to avoid technical debt, even when you don’t have the knowledge at a given time. For example, if you code something in Spring and it seems that something is against the “Spring mindset”, then it’s almost 100% that you introduce technical debt. There was only one single time when Spring utterly broke its own methodologies, and it was needed for my day-to-day job (ie Spring Security with multiple providers). Looking after such cases is way more beneficial, than that one case when it took me a deep inspection of Spring to figure out, that there is really no nice solution. Nowadays it’s even easier with LLMs, they can help you point to the right direction, then it’s easy to validate with some search engines.