🗡 You'll find yourself using a sword to cut vegetables because you didn't know that a knife exists. 🔪Â
Earlier in my career (and sometimes even today), I was so desperate to build and achieve the end result that I would use any tool I came across to build apps.
It was a horrible thing to do.
I often have sparks of ideas and I can't wait to make them a reality, but it's not always good. The sense of urgency needs to be balanced with your learning.
I started by building desktop apps using good old C# .NET in 2019. As soon as I learned it, I used it to build a file storage software to back up my stuff from the university's desktop computer because I didn't want to open my Gmail or Drive on an unknown computer.
It was a horrible tech stack choice. I made a desktop app and stored user data (like login and folder) in a GCP transactional database instead of a simple relational database. Really! Not to mention, who would install that software on every computer I used at the university? Exploring web app development would have been a better choice.
And not just in choosing a tech stack but within a tech stack you have many tools. Without exploring all the choices provided by the language/framework/library, you would most likely end up using workarounds to get the results.
Instead, step back; don't rush to get that app live. Focus on learning the right tools. Take a course if you need to. Even if you know a tool, take a course. You'll be surprised how much you didn't know existed that would have made your life simpler.
Earlier in my career (and sometimes even today), I was so desperate to build and achieve the end result that I would use any tool I came across to build apps.
It was a horrible thing to do.
I often have sparks of ideas and I can't wait to make them a reality, but it's not always good. The sense of urgency needs to be balanced with your learning.
I started by building desktop apps using good old C# .NET in 2019. As soon as I learned it, I used it to build a file storage software to back up my stuff from the university's desktop computer because I didn't want to open my Gmail or Drive on an unknown computer.
It was a horrible tech stack choice. I made a desktop app and stored user data (like login and folder) in a GCP transactional database instead of a simple relational database. Really! Not to mention, who would install that software on every computer I used at the university? Exploring web app development would have been a better choice.
And not just in choosing a tech stack but within a tech stack you have many tools. Without exploring all the choices provided by the language/framework/library, you would most likely end up using workarounds to get the results.
Instead, step back; don't rush to get that app live. Focus on learning the right tools. Take a course if you need to. Even if you know a tool, take a course. You'll be surprised how much you didn't know existed that would have made your life simpler.