Posted by loumf 9/5/2025
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.
You seem to be writing about other concepts and just redefining them as tech debt.
I left more detail in comments, but if I had purchased this book I would be seeking a refund, because I would be expecting a detailed exploration of technical debt, not just a focus on bad coding practice.
I really don't want people to buy it if they won't like it.
Its very much that its advertised as something its not.
You could do research into technical debt and bring other peoples anecdotes and experiences into the book and bring the content in line with the title and readers expectations.
Or you could update the title and therefore manage expectations to ensure there are no misunderstandings.
Very distinct babblezone liturgy.
I get that you might not like my writing, but it is mine.