I was discussing side projects with the head of engineering one day who told me that problems are a good thing in business.
Problems are a good thing in business because it means that you have done something right to get to that point in the business to get to have problems. It means something is going well for you to have problems.
I try to remember this whenever I start a new project.
When you take on a new project, build a website, start a new business you are bound to encounter unfamiliar territory. You will reach points were there is some new issue.
Take for instance building a website. You already know that you want to use a website builder or maybe even code the site yourself with HTML, CSS, & JAVASCRIPT. Or perhaps not and are unsure where to start. That my friend is a good thing because you can pat yourself on the back and acknowledge that you have initiated your journey to build a website. Moments ago you had not taken that step. And so you have made progress to your goal and are one step closer.
From there you could begin building your website, but then encounter another issue. How do I put my website on the web? What is website hosting? From there you can take pride in the fact that you have built a website and now are ready to have others see it. That my friend is a great thing! That is a good problem to have because you have made progress on your call.
From there you could have your site live on the web but are dismayed that you are not getting enough traffic to your site. Another issue. At this point you could get dissappointed or recognize another objective reached. That you built your site, you have added content to your site, you have even launched your site on the web. It is now time to learn more about SEO and taking advantage of tools to put your website in people's search results such as Google Search Console, Google Analytics, Google Business Profile, Google PageSpeed Insights, and more.
This is just an example of the importance of recognizing that problems are good thing. The sooner you recognize it, the better off you'll be. Also just from experiencing working from startups, there are always issues and improvements needed but it is way better to get off the ground then waiting until everything is perfect. For the most part you just have to be good enough and thatll do.
No fluff. Just real projects, real value, and the path from code to cash — one useful build at a time.