4 ms·
I’m fairly confident that I could have built more or less the same product that our team of 30 has built over the past 5 months in the same amount of time by my
by Aeolun 8y ago
I’m fairly confident that I could have built more or less the same product that our team of 30 has built over the past 5 months in the same amount of time by myself.
If I’d had 1 more senior developer and a designer/front-end dev, I’m fairly certain it could be done by now.
But there’s so many people involved in the process that everything slows to a crawl.
I’m sure our clients love hearing that the product is developed by 30 people over 1.5 years though.
- tcbawo 8y agoOwning your product (ie. reaping the rewards of your labor) is an enormous motivator. It takes a skillful manager/salesperson to keep people motivated as a company grows and they have less skin in the game.
- paulryanrogers 8y agoIME it's easy to look back and focus on doing the knowns. But starting from ignorance and alone is likely to take longer than a skilled team starting from scratch. Of course it must be the right size to explore and implement the solutions without too much overhead.
- saalweachter 8y agoThere's also a number of projects that it's super easy to do like 83% of. A couple of ambitious college students could make a basic web crawler and search engine using 2018 technology and not even that many cloud resources and get like 80% of Google's quality. But that doesn't mean they're only another long weekend from being the next Google: closing the gap really does require millions of manhours and billions of dollars of compute. (And their web crawler would be causing chaos and destruction across the web, but let he who has not accidentally deleted someone's will by crawling all the "delete this article" links cast the first stone.)
- dingaling 8y agoAre you good at business requirements gathering? Environmental architecture? UX design? QA functional and regressional? Fancy juggling AWS config and costs? Writing user manuals, help desk scripts? On a scratch-itch OSS project you can ignore those. But when you plan to sell it, things scale quickly. Coding is just one arrow in quivver.
- Aeolun 8y agoMost of those? There’s no point to me doing QA on my own product, and I hate writing any form of manual with a passion (things should be understandable without one). But the point was mainly that the actual product is essentially a glorified crud application. There is some value in having a larger team, but the time wasted is absolutely massive.
- bane 8y agoI just saw a demo by a team of 30 that had worked on a super secret project for a client for the last 3 years. It was a web page that let you enter in SQL queries and select which database from some set of databases they've integrated to run it against...and then save the query with a name. In my area, we've literally built something more or less like that a few times in the same time with one or two developers each time. In fact, I found out after the demo that much of the core logic came from a repo a guy on my team wrote in his spare time to plug a hole on a minor side project he was doing.