3 ms·
Being able to prioritize building projects like this is a skill in itself, and I think it's a really important one. People seem to chronically undervalue optim
by ZephyrBlu 3y ago
Being able to prioritize building projects like this is a skill in itself, and I think it's a really important one.
People seem to chronically undervalue optimizing for shipping something. Mitchell does say "I don't talk about shipping", but shipping a demo for yourself is still shipping!
It doesn't matter how good you are if you can't stick at something for a long period of time. You're probably not going to be able to do the thing for long enough to generate big ROI.
Optimize for something usable. Go one step at a time. If you get discouraged or lose motivation it's game over, you gotta prevent that at all costs.
- lucasfcosta 3y agoDefinitely true. That's something my co-founder talks a lot about. If you just stick at it for a few months, projects get huge. It's incredible how much code gets written when you look 6-months back. If you had to look forward and try to guess, you'd never imagine this much would have happened.
- kqr 3y agoWhat do you mean by not being able to guess, specifically? I seem to start growing code at 1000 lines per week, decreasing to 200 after a small number of months, yielding around 15000 lines after six months. For reference, this is about half the size of Wolfenstein 3-D. Is that not a fair guess?