Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>The key for me is to reduce tech debt before I release.

Also an indie founder, and I've had the opposite experience.

Early on, I focused a lot on elegant code that would minimize my maintenance burden long-term. Then I read Rob Walling's book, Start Small, Stay Small,[0] and he talked about how programmers are typically afraid of ever taking on tech debt because they've been in orgs that don't allow them to ever pay down tech debt. As an indie founder, you can pay down tech debt whenever you want.

I've found it more useful to accrue tech debt early on in a new project or feature because it's likely that the product will fail or that I won't end up having to touch the feature for years.

Every time I have to work on code that has tech debt, I pay down the tech debt a bit, so eventually the parts of my codebase that see the most change are the most flexible and maintainable. But a lot of my code has tech debt in ways that don't matter because the product flopped or I never ended up having to extend the feature beyond the initial implementation.

[0] https://mtlynch.io/book-reports/start-small-stay-small/



I didn't think of that. That's a good idea.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: