3 ms·
The biggest problem I see with joining a startup after graduation is more often then not, Startups don't use any kind of best practices, as they just want to Ge
by ry0ohki 15y ago
The biggest problem I see with joining a startup after graduation is more often then not, Startups don't use any kind of best practices, as they just want to Get Things Done(tm).
It's not uncommon to run into a startup that doesn't use source control, code comments, have failover servers, or even have a dev/staging environment. There are some things that are best to get a good foundation for your career, and large companies provide these in droves.
That said, there are Startups that have their act together, and after college is probably the best time to take that risk.
- nicholasjbs 15y agoFor what it's worth, we're helping dozens of startups hire, and I think every single one uses source control, some have failover servers, and I'd the majority have dev/staging environments (I haven't looked at their code bases, so I don't know how well documented the code is). That said, you're right: Startups do focus more on getting things done and making sure people actually want what they're building, sometimes to the detriment of best practices. On the other hand, startups tend to use use better (and certainly newer) tools. For instance, git vs. svn or cvs.
- anorwell 15y agoI think there's a lot to be said for learning best practices the hard way. In my experience at a large company, these things can become a cargo cult, especially for less experienced people.