2 ms·
Developers should definitely write their own code when there isn't an open solution that they can leverage to solve the problem, but those situations are quite
by onion2k 10y ago
Developers should definitely write their own code when there isn't an open solution that they can leverage to solve the problem, but those situations are quite uncommon for the majority of startups. Most founders aren't doing the sort of cutting-edge development that no one has seen before; they're making a SaaS app that boils down to a few CRUD forms in a browser and some nice design[1]. Building a business around that is much, much easier and cheaper if you write less of your own code.
Use open solutions where you can, and don't use them where you can't.
[1] That is in no way denigrating startups that do that. If you can solve people's problems by making a better form then that is a Good Thing.
- exolymph 10y agoThe way I like to put this — or a related concept, at least — is that no business should waste time building the aspect of its product that isn't the differentiator.
- nostrademons 10y ago> Most founders aren't doing the sort of cutting-edge development that no one has seen before; they're making a SaaS app that boils down to a few CRUD forms in a browser and some nice design They should probably ask themselves what sort of defensible competitive advantage they're building, though. With many founders I know, the answer is "none". This is probably necessary in the very early seed stage - it's hard to build something unique and difficult and still get to market - but it's disturbing how many companies end up with $50M in funding and the answer is still "none". Probably a good indicator of a shake-out in the SaaS world in the near future.
- Hydraulix989 10y agoNetwork effects are a good example of something that is both non-technical and defensible. You can't build the next Facebook anymore because everybody's friends are already on Facebook.
- onion2k 10y agoThe competitive advantage those companies have is typically two-fold: knowledge and brand. Knowledge is the very detailed and insightful understanding of what their industry needs at the moment, and where it needs to move to in the longer term. Founders who build those businesses are typically experienced in their industry and are solving a pain they've seen firsthand. That is exceptionally hard to compete with if they're good. Just because that knowledge can be codified in a 'simple' CRUD app doesn't make it any less valuable. The brand advantage is comes from being the first mover. If the industry knows your company, trusts that you've proven to have an impact on their bottom line (or their competitors bottom line), then you're probably in a good position to retain customers and build a market. Competition is not a problem for a business that's intent on making a market $100m bigger rather than trying to take $100m of business from someone else. Neither of those advantages require any code.
- djsumdog 10y agoIt is a pretty delicate balance and requires good engineers. If you're a religious language defender (bleh, why are you using Java, Perl, etc.), you're not going to be objective. Different languages are useful for different problem spaces. Somethings are starting to show their maturity. For example, I use to write software that ran on OpenWRT based tiny/embedded systems in Python, because python-mini was present and I could install it, my dependencies and everything I needed in less that 16MB of space. There weren't many options for that footprint other than C, but that was 2011. If I wrote it again today, I'd have to seriously consider using Rust instead. Being a good engineer/architect requires a lot objectivity. It involves working at different shops with different frameworks, languages and design decisions and filtering through all of that. It involves constantly searching for "I really hate <x>" and "<x> is a piece of shit" every time you find something you really like and have pushed towards your production release, just to see what issues other people have and if their problems are things you may run into. By the same token, when you use something you hate, you want to do the opposite searches as well (e.g "I really love Powershell"). This article is really written from a business perspective. There are a lot of businesses that survive their startup incubation period with terrible design. Some even become profitable. Good luck keeping your developers though.
- new_hackers 10y agoYou hate PowerShell??? Say it ain't so!