←back to thread

157 points loumf | 4 comments | | HN request time: 0.858s | 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.

1. brianmcc ◴[] No.45137673[source]
A total tangent but it's amazing how more palatable "tech enhancement" is in planning, management chats, etc., than anything involving the term "tech debt"
replies(1): >>45138837 #
2. cadr ◴[] No.45138837[source]
Can you say more on your experience here? I've not heard people use that term before, and I'd be interested in how it received/what you think the difference is.
replies(1): >>45139201 #
3. brianmcc ◴[] No.45139201[source]
Sure, just that stories about "paying down tech debt" are an implicit admission of flaws and shortcuts and "doing it again because it wasn't done right initially".

Which is all true but the concept of making deliberate trade offs for speed and expedience invariably gets lost.

Stories about ongoing improvement - tech enhancement - just get seen as more positive. Plus that term covers both remediating original shortcut choices as well as new engineering improvements arising.

replies(1): >>45140547 #
4. cadr ◴[] No.45140547{3}[source]
Thanks!