Why your tech-stack actually matters

The nice thing about prototyping and building Lean Offerings (or MVPs) is that you can choose your tech-stack when you are starting out. But what technology to use?

There are a million programming languages/frameworks to choose from. Everyday there is a new kid on the block. Developers tend to use the newest and shiniest thing, because they want to learn something new or think this new technology solves all the problems they had with their previous stack. Like I said in my previous post, you can’t do much wrong from a technical standpoint. But there is something you should watch out for:

Use something where you can move VERY FAST.

This is critical in Business Design Sprints. We need to validate and iterate quickly (within 10 weeks). Technology where you can move fast is often something which you know very good, which has a great ecosystem and comes with batteries included. Good examples in the web-tech world are Laravel (PHP) and Ruby on Rails (Ruby). With these frameworks, a lot of stuff which most web-apps need, is already included (e.g. authentication, authorization, email sending, background-jobs, DB access, queues, task-scheduling and much more).

Every bit of code you don’t need to write/maintain helps you to be fast.

In Business Design this is key: NO CODE IS GOOD CODE.