getting the product out is one of the hardest things for a early stage startup. people who can ship will increase the possibility of the product being released .
small example :
Business guy : guys we need to send a welcome email after a user registers.
coder1: adds code in the registration controller . ( 10 mins ) done.
coder2 : I think its better to use a event system to create an event for user registration and use a spool to send the email.
coder2's "idea" might be technically better than coder1's implementation but its waste as Coder2 doesn't actually take the initiative to code ..he knows just about everything in CS and for some reason prefers not to code . And still argues that coder1's solution is not correct.
"coder1: adds code in the registration controller . ( 10 mins ) done."
And once your code accumulates enough of these 10-minute hack jobs, it becomes incomprehensible and unmaintainable, and every little change will break something. At that point, progress grinds to a halt. You'll then need someone like coder2, who has a talent for system architecture, to refactor them back to a sane state again. (I've been both coder1 and coder2, under different circumstances.)
This is a pretty good example of what does it mean to be good at shipping. Sometimes you have to acknowledge that what you are doing right now is not the best solution architecture/design/whatever wise, but it provides the best quality/cost ratio.
Of course, it shouldn't be used as an excuse for releasing simply crap solutions. Experience comes handy when it comes to deciding whether it should be improved or it is good enough and should be refactored some time later.
Well, coder1 is leveraging technical debt. You have to find a balance because that 10 minute hack will come bite you in the ass later - sometimes only days later!
small example :
Business guy : guys we need to send a welcome email after a user registers.
coder1: adds code in the registration controller . ( 10 mins ) done.
coder2 : I think its better to use a event system to create an event for user registration and use a spool to send the email.
coder2's "idea" might be technically better than coder1's implementation but its waste as Coder2 doesn't actually take the initiative to code ..he knows just about everything in CS and for some reason prefers not to code . And still argues that coder1's solution is not correct.