Start small! You don’t have to solve world most difficult problem

-
Start up meeting - Image by StartupStockPhotos from Pixabay

You don’t have to create new business or solve the world's most difficult problem. You can just start a small doable business by following other businesses that already exist, as long as you have better product, packaging and marketing.

People are too ambitious and think too far, it’s okay if you are Elon Musk, but if you just some random guy creating your own business, although it is possible to compete in space race, its chance is very slow compared to already exist doable business that you can just start

So, start small, don’t overthink things. Only when your capital is significantly larger, only then you can start to think about expanding your business. Most businesses will fail before 1 year, so be careful, you have to manage your resources carefully.

I read the book Atomic Habits, which can be summarized the following:

Atomic Habits by James clear is a definitive guide for breaking bad behaviors, showing you how small, incremental, everyday routines will compound into massive, positive change over time.

As someone working as a software developer, I don't even have to read the book to do what the book says. When we develop software or apps, we split large projects into smaller manageable action. We use scrum to track the progress of small doable tasks.

It applies to starting a startup, when you try to develop a product, you shouldn’t aim for the big result rather start things smaller that can grow overtime. Bigger things are harder to do than smaller one. It is very easy to understand yet very difficult to do, because our brains get more excited about bigger things than smaller one.

The problem is that your brain is a primitive brain, our ancestor's ways to guarantee survival in nature. When the ancestors go hunt, they will prefer big marmot over small easy to hunt animals. Think of it that way, our brain is a primitive mechanism that is not accurate anymore to apply it in the modern world, we must think hard to make our brain evolve.

I am not a businessman myself, but I have been helping them deliver the product for them by doing IT development for them, so I have been with some businesses that last long and what’s not. I observe what they are doing wrong and why they fail.

Ambitious project, if done correctly, can have a sweet ending, if not it thorns down apart, not just the project, but the team, the people working on it, and the company. Small project can have a sweet ending, if it fails it doesn’t hurt that much.

You have to think big, doing small projects is not categorized in that principle. Actually, a small project can grow into a bigger project, but a big project doesn’t, it is only doable if you have lots of resources, with the high risk that if it doesn't work it will hurt so many people involved.

Conclusions why you have to start smaller project

- Smaller project has less risk. It's more doable, easier to manage

- Schedule resources for doing the development are easier too

- Return on investment is faster, because doesn’t require large investment

- Smaller project is faster successes, bigger one is harder


Popular posts from this blog

ERROR 1348 Column Password Is Not Updatable When Updating MySQL Root Password

-
Image
MySQL and MariaDB password As already mentioned in the title of this blog, this error message sometimes occurred when we are trying to update our root password database, either MySQL or MariaDB, The error says: ERROR 1348 (HY000): Column 'Password' is not updatable This is because if we use this SQL command to update our database root password, and it turn out to be Restricted by MySQL to use update on mysql database. UPDATE mysql.user SET Password=PASSWORD('1234') WHERE User='root'; The solutions for MySQL Error1348 So you can not update a user password using Update commands, to update the password, use ALTER commands instead. like the following. ALTER USER 'root'@'localhost' IDENTIFIED BY '1234'; And then you need to do the flush privileges to commit previous queries (that alter command above) into the system, simply do like this. flush privileges; So now you have your root with password 1234. Although it is recommended to...
Read more

How To Create Spring Boot Project Using Netbeans

-
Image
Spring Boot is a handy tool that simplifies the development of Spring Framework applications by reducing the need for cumbersome configuration. In this tutorial, I'll guide you through creating a Spring Boot application using the Netbeans IDE. While you can certainly create a Spring Boot application in Netbeans manually, it's much easier with a plugin designed for Spring development. Here's a step-by-step guide to get you started: 1. Install the Spring Boot Plugin: Open Netbeans and navigate to the Tools menu. Click on "Plugins." Once the Plugins window opens, select the "Available Plugins" tab. Look for the "Nb SpringBoot" plugin, then install and activate it. 2. Create a New Spring Boot Project: After restarting Netbeans IDE, you can create a new project with Spring Boot. Go to File > New Project. Under Categories, select Maven, then choose "Spring Boot Basic." 3. Add Dependencies: With your new project created, open the po...
Read more

Spring Kafka - How to use ReplyingKafkaTemplate send and reply synchronously

-
Image
Microservice Spring with Apache Kafka Today, I want to share how to use Kafka. It's quite interesting once you get the hang of it, and I hope my explanation will make it a bit easier for you. So, Kafka is primarily known as an asynchronous messaging queuing system. This means it allows different parts of your application to communicate with each other without waiting for immediate responses. However, there are times when you might need a more immediate reply from another service in your project. Luckily, Kafka can handle this too. Here’s how it works: The client side sends a message to the server side via Kafka. This message includes a special identifier in the Kafka header request, known as KafkaHeaders.CORRELATION_ID, along with a topic where the server should respond. The server, after processing the request, sends a message back to the same topic with the same correlation ID. This way, the client knows that the message is a response to its initial request and can act accordingl...
Read more