3 ms·
Ask HN: Fast vs. perfect, semantic front-end code for MVP?
Just wondering where web designers/front-end developers draw the line between quickly prototyping code for their startup (perhaps using something like Twitter's Bootstrap framework), and having long-lasting, semantic code that won't need to be written in the short term?
This is my first startup and I'm finding it difficult to know when work is 'good enough' rather than obsessing on the details as is customary when freelancing.
- cancelbubble 15y agoIt's good enough when it works acceptably in all your supported browsers. You can always come back and refactor. Really, the only people that truly care about the quality of front-end code are other snobby front-enders. I'm not talking about obvious poor performance, more semantics. Have you ever had a boss that cared about your code quality as long as it worked acceptably? Having "high-quality" code is awesome and should always be a goal, but in the end, the shit has just gotta work....Lord, I've been in Enterprise-land too long. BTW, I'm a front-ender since February of 1996, worked everywhere from an agency to Yahoo.
- bitsm 15y agoIt's always "good enough", except when it isn't. :) Seriously, though, startups -- and websites in general -- are continually moving targets. Your requirements are always changing, your user base and their needs are always changing. You ever see the inside of a FedEx truck? Eeek. Focus on what your customers need, over-deliver on that, and keep the rest together as best you can. You will learn how to manage your business properly with time, and you'll have time as long as your customers are happy.
- deleted 15y ago[deleted]
- iisbum 15y agoI'm not sure why you'd treat your own product any different from how you treat freelance work? What if the freelance client was someone building an MVP? :)