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

This

A lot of people think following all best practices and offering a unit test sacrifice to Uncle Bob will lead to success

Shipping will put food on the table. Of course, if your system can't stand 5 simultaneous users it won't, still it's difficult to get that bad. (but yeah, some people manage to get to that level)

And some "online services" have very bad code, and still they sell millions. Get rich first, then you can improve your code.



Get rich first, then you can improve your code.


>Get rich first, then you can improve your code.

I agree with you, but the second part never happens.


Sure, but how can you fearlessly refactor the code without having automated tests in the first place for example?

Technical debt accumulates interrest.


Version 2.0

Or you start adding unit tests, which may be harder than rewriting

Doing a version 2.0 is easier (but maybe harder) than it looks




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

Search: