Often new startups with a great idea for a cool new technology can struggle with knowing how best to go about actually building it. Ivan Zlatev, Lead Developer at MarketInvoice, talks development for startups, the pitfalls to be wary of and scalability.
What are the main principles of developing a new system for a startup?
The main thing is to stay focused.
Generally, engineers have a tendency to overcomplicate things. We like to build rockets, over-engineer, try to develop in the perfect way. That approach doesn’t quite work in the majority of startups.
When you’re developing a new system you need to stay very focused on delivering something at the end of the day and keep doing so rapidly. That doesn’t necessarily mean you have to build a fragile system with a lot of bugs and provide a bad customer experience - you can still develop a quality system but you have to find a balance between “good enough” and being able to get the product out there. And that takes experience and good judgement calls.
However, if you are out there just simply trying to validate an idea - you may want to pursue a different path. Pick a couple of components, products and services off the shelf and try to combine them in a prototype. Different approaches are required for different systems, different products, different markets, different teams, and so on. There’s no silver bullet I’m afraid.