The Importance Of Starting Small

So I have a little confession to make. Ever since I’ve been able to code anything I set my mind to, that’s what I’ve been doing. I’ve been coming up with project ideas and making them. Except there is one problem – I haven’t really finished any of my projects. Well, in software development, you’re never really finished. But I haven’t gotten them to the point where there is even a minimum viable product (MVP) that I’m proud to show off and talk about.

I think the problem is that my ideas are too big at the start. While I’m just starting out, my brain is filled with the vision of the product a few months from now, with all these features that I really really want. So as I’m coding, I’m never satisfied with where I am and easily give up at the idea of something new and exciting.

Well, you might have guessed it, but I’m now working on a new project. Except this time, I’m committed to pushing out something I can show off before moving on to a new idea. The way I’m going to do it is the same way I wrote my ebook¬†and learned to code, by breaking the project down into very very small and manageable pieces, that I know will eventually be the building blocks for something much bigger.

Enjoy the article? Join over 14,500+ Swift developers and enthusiasts who get my weekly updates.

  • Hi, Natasha. I can understand what you mean about having too many projects at once – I had started two PHP and SQL projects, Python lessons on Codecademy, a web design project and probably something else I can’t remember…

    Also, I like your idea of small and manageable pieces, are you familiar with the separation of concerns? I’m going to add a blog post about that to my blog this week, so don’t miss it.

    • Hi Charles,

      Let me know when you publish that post. Would love to read it!

  • Pingback: tinysteps for tinysale: landing page done!()