Hacker News new | past | comments | ask | show | jobs | submit login

I will always pick the cheap and dirty option until the project is at a stage where you have a lot of breathing room. Simple code trumps fancy code in reality where you don't have a large team, and you don't have a lot of time and you need something that works even if it's only half as efficient a solution.



this is the point where I say you won't get breathing room if your code is all quick and dirty. There is a balance between quick and dirty and well-formed and not needing tending every few weeks.

Just do high quality code that will remain maintainable into the future. If the business feels that has too much of a financial or time penalty the business needs to find money to pay for more high quality (slower) developers, or to find a different you.

Don't take someone else's problem / role on as your own to solve - it won't help you or them.




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

Search: