
personal journey, self-reflection, into product and web3 development

At first, I never thought that going solo is possible. When I started out on this field, I was literally weak on any skills. I know a bit about backend programming to spin up web server and interacting with database, that's all. But then I started to see more indie developers and solo builders out there. I still don't know how is it possible for them to literally work end-to-end and build everything from 0 to the point they are right now, with a single person in the team.
After years spending time across different fields, I started to have the basic of most skills needed to be a solo builder. First attempt of being solo builder was simply I have no one I can ask to for my 3rd/4th hackathon. Without an AI, I submitted my first solo hackathon, and won the 1st position on a specific track of that hackathon.
Winning a hackathon with my own hand, I feel a bit superior, but then I realized that I need to adapt to the AI era. Why? AI era simply push the productivity forward. Maybe I can cut the time from 3 weeks of development to only 1 week or less. It changes the way I think because now I need to improve the AI workflow instead of working on my own workflow. It enables me to do more things as well at a time rather than locking myself up for weeks to work on a single thing.
Before I learn much about the use of AI for development, I thought maybe its the time for me to find a team again. I previously participated hackathons with different teams. The problem for a team is, most of their goals are too blurry. When you want to do a test run for example, the other expect you to stay and contribute until the team successfully launch an app to mainnet. That's too much for a burden. The other team have an expectation of like you work more than you were budgeting too. When in reality you have your own priority, like family or even your own product.
These past weeks, I tried to have a test run between few teams, and that was exactly what I experienced. I cannot find the dynamic with them, our goals weren't clear, and we are not aligned, and also we have different priorities. Doing trial and error on teams really holding me back to work on my products.
So basically for that reason, I am announcing that I am going back to solo again. Solo might be my game for the upcoming months or even years. It's not like I don't want a team. I still have someone who I think as an ideal team, but I can't expect them to always be with me in a team because they have different life as well. Maybe one day in a hackathon or some sort, we can be a team.
Good bye team, welcome again solo!
At first, I never thought that going solo is possible. When I started out on this field, I was literally weak on any skills. I know a bit about backend programming to spin up web server and interacting with database, that's all. But then I started to see more indie developers and solo builders out there. I still don't know how is it possible for them to literally work end-to-end and build everything from 0 to the point they are right now, with a single person in the team.
After years spending time across different fields, I started to have the basic of most skills needed to be a solo builder. First attempt of being solo builder was simply I have no one I can ask to for my 3rd/4th hackathon. Without an AI, I submitted my first solo hackathon, and won the 1st position on a specific track of that hackathon.
Winning a hackathon with my own hand, I feel a bit superior, but then I realized that I need to adapt to the AI era. Why? AI era simply push the productivity forward. Maybe I can cut the time from 3 weeks of development to only 1 week or less. It changes the way I think because now I need to improve the AI workflow instead of working on my own workflow. It enables me to do more things as well at a time rather than locking myself up for weeks to work on a single thing.
Before I learn much about the use of AI for development, I thought maybe its the time for me to find a team again. I previously participated hackathons with different teams. The problem for a team is, most of their goals are too blurry. When you want to do a test run for example, the other expect you to stay and contribute until the team successfully launch an app to mainnet. That's too much for a burden. The other team have an expectation of like you work more than you were budgeting too. When in reality you have your own priority, like family or even your own product.
These past weeks, I tried to have a test run between few teams, and that was exactly what I experienced. I cannot find the dynamic with them, our goals weren't clear, and we are not aligned, and also we have different priorities. Doing trial and error on teams really holding me back to work on my products.
So basically for that reason, I am announcing that I am going back to solo again. Solo might be my game for the upcoming months or even years. It's not like I don't want a team. I still have someone who I think as an ideal team, but I can't expect them to always be with me in a team because they have different life as well. Maybe one day in a hackathon or some sort, we can be a team.
Good bye team, welcome again solo!
Share Dialog
Share Dialog
personal journey, self-reflection, into product and web3 development
Credits:
- Image is LLM generated by Midjourney by combining my own profile picture (NFT) and custom description
Credits:
- Image is LLM generated by Midjourney by combining my own profile picture (NFT) and custom description

Subscribe to 0xHirugohan

Subscribe to 0xHirugohan
<100 subscribers
<100 subscribers
No activity yet