2 ms·
> How was he ever going to focus on the other code qualities? Even if you can, you shouldn't expend a non-trivial amount of brain cycles on that, especially ea
by jmstfv 5y ago
> How was he ever going to focus on the other code qualities?
Even if you can, you shouldn't expend a non-trivial amount of brain cycles on that, especially early on.
> If on the other hand you're experienced it's probably about finding that trade off between perfectly orchestrated software and having something that delivers your vision in an acceptable amount of time.
Don't.
As someone who built (and sold) a business before and is building a new one, I'd say it really doesn't matter before you get traction. Just ship the damn thing however you can!
The chance of a first-time founder succeeding is incredibly slim anyway. So, you're better off spending your time figuring out distribution and finding a good enough market.
- PUSH_AX 5y agoI think engineers gonna engineer though, even if it's subconsciously or small stuff, hell it might be half the fun. You could ask me to build a project with no trade offs regarding time to deliver, it's still not going to be in one single file, primarily because it's one of many "quick wins".
- jmstfv 5y agoThe key is not to go overboard. As a first-time founder, you don't know when to draw the line and focus on valuable stuff. It's very, very easy to get sucked into minutiae that don't matter at all (been there, done that). That's why I think first-time founders should ignore most engineering best practices and ship the prototype as fast as possible. > primarily because it's one of many "quick wins" Be careful with that, though. You might have an illusion that you're making progress, while in reality, you aren't. I'm with you on having the fun part!