One of the first things you learn in military Special Forces, like the Navy SEALs, is that slow is smooth, and smooth is fast. In today's fast-paced business world and constant communication, we often believe speed is the key to success. But is it? Let's dive into this from a startup founder’s perspective.
In this post, I share my thoughts and recent experiences with Scrum and Kanban. While the first one is my default choice, the latter turned out to be revolutionary for my team at the startup I'm currently developing. Why? What are the benefits? When Kanban can yield better results than Scrum? Read on to find out!
Your software is as good as its documentation. Even if it's a truism, it's worth remembering, especially when creating a SaaS solution with self-service capabilities and versatile APIs, or when building open-source (no, README.md in your GitHub is not sufficient).
Big tech companies know it very well. They invest significant money in creating and maintaining their documentation. They use dedicated tooling and have teams to build it. But what about startups? They are usually focused on building the product and acquiring customers. In this post, I give you my opinionated guide on how to create world-class documentation without investing.
Believe me, you can't afford to have bad documentation!
It is my ambition to say in ten sentences what others say in a whole book.
Being a (co-)founder of a technology startup often requires wearing multiple hats. Initially, it's a necessity due to budget constraints and the need to validate the idea. However, there comes a time when focus becomes more important than versatility. This post explores when to prioritize focus and avoid suboptimal work assignments.
Convincing a VC to invest in your idea isn't easy. You need to show that your startup is special and has the potential to grow. But how do you do that? Most ideas that seem to be unique at first glance are not after a closer look. So how to make your startup attractive to investors?