←back to thread

157 points loumf | 2 comments | | HN request time: 0s | source

This is the first half of my book, “Swimming in Tech Debt”. It is available at a pre-launch sale price of $0.99 (https://loufranco.com/tech-debt-book).

I have been working on it since January 2024. It is based on some posts in my blog, but expands on my ideas quite a bit.

In September 2024, excerpts appeared in Gergely Orosz’s Pragmatic Engineer newsletter, which helped me get a lot of feedback that expanded the book from my initial idea. This half is about what I expected to do before that —- the rest of the book goes into team and CTO practices.

Show context
conartist6 ◴[] No.45137491[source]
The swimming analogy is not a strong start. You disavow an obvious and strong analogy to monetary debt right away while dumping us into this strange metaphor that depends on us having an intuition for how you think and feel about swimming, and specifically swimming laps? Instead of setting the stakes high right off the bat you've lowered them and lost my attention with this wandering train of thought that has no clear relationship to the topic you wish to discuss...
replies(3): >>45138717 #>>45138824 #>>45142642 #
conartist6 ◴[] No.45138824[source]
I'm reading a bit more now and you're realizing that your debts are real and cost something all the time so that you will have to pay them. Nothing about swimming explains why this might be, though monetary debt sure does.
replies(1): >>45138888 #
loumf ◴[] No.45138888[source]
The analogy I am going for is the water resistance. The debt payment is the burst of momentum you get from pushing off the wall.

I think of tech debt as something you are dealing with all of the time and something inevitable.

I don't like the financial analogy because it implies that you "took out a loan" by taking a short-cut, and that you are obligated to pay it. There is definitely some of that, but mostly, I see it as good decisions that didn't age well. And also, that you may be ok with living with it.

replies(3): >>45139066 #>>45139367 #>>45139702 #
conartist6 ◴[] No.45139066[source]
You go right back to the monetary analogy when you need to explain that focusing on debt created value.

The thing that I think the swimming analogy doesn't capture well is that the resistance of water is fixed. The walls of the pool will be there to push off of no matter what you do. These are the intuitions you're asking people to draw on and they don't map.

replies(1): >>45139363 #
1. loumf ◴[] No.45139363[source]
I struggled with this. I didn't have the guts to not use "tech debt" in the title and throughout the book. I wanted to coin a new term, but didn't find anything that worked.

There are parts of the debt analogy that (I think) really hurt getting it dealt with. I think that explaining it like that to non-engineering decision makers will make them think they understand it and then quash projects based on some kind of ROI analysis of debt payments. They'll be happy to have the debt.

replies(1): >>45139844 #
2. chrisweekly ◴[] No.45139844[source]
Debt is the right metaphor. Some amount of tech debt is virtually unavoidable; just like w/ $, a low-interest student loan or mortgage might be a great investment, while using a high-interest-rate credit card, or usurious payday loans, represent catastrophe. Cutting a few corners for the sake of GTM is often the former. Forgoing proper tests, or letting PoCs shape architecture, is more like the latter.

I don't see "swimming" replacing it anytime soon -- and the energy you'd expend trying to shift the metaphor might be better spent elsewhere.

That said, "swimming in debt" still works, as a fairly common and intuitive metaphor. Break-even is treading water, profitability is flying above the waves, and accruing debt can put you in Davy Jones' locker.