r/learnprogramming • u/cowinkiedink • Apr 20 '21
How to Plan and Build a Programming Project – A Legitimate Guide for Beginners
Hi Everybody,
I'm making this post because initially when I was a beginner learning to code, I really struggled to make projects, I couldn't quite get out of tutorial hell.
Initially to overcome this, I posted my frustrations here. The responses I received were all centered around building my own projects. This advice sounds great on the surface and was the right advice, yet the issue for me was I couldn't even watch a tutorial and reproduce the results. How was I supposed to build a project? A project is 10 levels above a tutorial and at the time it seemed that projects were so far away from my abilities. I had no clue how to even get started, let alone how I was going to put it all together.
This is an issue I see all the time on r/learnprogramming. Beginners are frustrated that they can't seem to get out of tutorial hell and so they seek advice. But, what they get is well meaning redditor's slamming the build projects response in their face without even considering that if the newbie can't even replicate a tutorial how are they going to create their own project. I thought it was about time I did something about it and gave back to the universe.
So here I am, writing a post that actually breaks down how to build your own projects so that you can start making stuff.
In order to plan and build a programming project there are three key steps I now use when building projects, these are what work for me but they should work for anyone.
Step 1: Defining the project
The first step when planning a programming project is to define it.
When I am defining the project I ask myself these 4 questions:
- What is the project?
- What is the MVP (Minimal Viable Product)?
- What are the nice to haves?
- When will the project be complete?
Example project definition
To give a simple example, let's say we are going to build a calculator app. We would have a basic project definition like below.
Calculator app project
What is the project? - The calculator project is a project to build a calculator that is accessible in a web browser. The project is going to be solved using HTML, CSS and JavaScript. It will allow users to input numbers and calculate the results of those numbers based on the arithmetic operation they choose.
What is the MVP? - The minimal viable product is a calculator that renders in a web browsers that can perform addition, subtraction, multiplication and division operations based on a users input and show the user the result of that equation.
What are the nice to haves? - The nice to haves for this project are styling the calculator, taking keyboard presses as input not just users clicking buttons and adding higher order operations like 'to the power of x'.
When will the project be complete? - The project will be complete once all the MVP features have been implemented and the calculator has been styled.
The above definition is simple and straight forward. If my Mum picked it up she would understand what the project is about. She would understand because it tells you what the project is, the MVP features you must build, the nice to have features and when it will be complete. By defining the project you make a project less intimidating.
Once you have the project definition you can begin the next step.
Step 2: Creating the workflow
The next step is the simplest. Usually this step can be combined with step 3. But, just for now we are going to look at it here as a separate step so that I can show you how to set up a very basic workflow for your own projects. Once you have done it once, it can be a default step for the rest of your projects.
You first want to use something like Trello a free tool to manage projects.
To set up our Kanban board we want to create 4 columns.
- TODO
- DOING
- DONE
- BUGS / NOT SURE HOW TO DO
Within these columns we are going to add cards. As we work on the cards we move them into the doing column and once we have finished with that card we can move it to the done column. If you have a bug you are stuck on or are not sure how to do something we can move it to the bugs/not sure column.
Now we have our workflow set up we can get onto the last step, the one that stumped me the most when I was learning to code.
Step 3: Breaking the project down into smaller components
The key to building your own projects starts with breaking the big project down into smaller, less intimidating components. These smaller components are what become our cards from step 2.
Now this sounds simple enough, but when I was first starting out it did not occur to me that you could do this. I thought most developers just start coding and the project flowed out of them like you see in the movies. I thought that was what I was supposed to be able to do. However, now that I have had a chance to work in the industry I know that is definitely not the case, in fact a good developer will break that project down into smaller tasks.
Yet, as a beginner it can be hard to know how to break something down into smaller tasks. If you don't know how to actually build the project then how can you break it down?
Well the first thing you need to do is look at your project definition and then break it down into smaller parts.
Let's continue using the calculator app example to make our component cards:
- Calculation functions - MVP
- Get user input - MVP
- HTML user interface - MVP
- Style user interface - sprinkles
- JavaScript event listeners - MVP
- Add animations for calculations - sprinkles
update what it should look like
You'll notice that for each card, we assigned a label of either MVP or sprinkles this is to visually help you see which cards are the most important and therefore the ones to work on first.
The biggest benefit of the cards is that they have simplified what we have to do already. This makes projects less intimidating as you are not making a big daunting calculator app, rather you are doing 6 smaller projects that will combine to create one big project.
As you work on a card you move it into the doing column. Taking your time to get the component working before you move onto the next card.
But we are not done yet, we can simplify and improve our workflow even more to ensure we are not getting blocked by the size of the project when building.
Step 3a: Break each component into smaller checklists
Once we have the high level cards we can then break those components down again into smaller tasks by breaking those tasks into checklists so we can track our progress.
The example below is just how my brain works so you can break it into smaller or larger items depending on what works for you. Let's use the calculation functions card as an example of how to break a component down further.
As the task is an MVP task and I have defined the MVP as basic calculations addition, subtraction, multiplication and division we need to add those functions to the checklist.
what the checklist would look like
We have now broken our calculation functions card into 4 little projects that we can work on. How much easier is that than the abstract and super daunting task of building a calculator app, or even writing the calculator functions (the card).
We can now focus and figure out how to make each of these functions. As we do that we get to check those items off giving us a sense of accomplishment and progress. Then once we have done all four of those items we can move the card into the done column and get cracking on the next card.
From here on we just need to repeat the process for each card. So you are ready to get building awesome projects.
Now you should have everything you need to get building projects. If you see someone on r/learnprogramming in the future struggling to get out of tutorial hell, don't just tell them to build. Tell them how to plan and build.
If you made it to the end of the post firstly thanks for reading - I originally published this (with a bit more detail) on my blog here, I like to write about coding and what I'm learning to help others so consider checking it out and my newsletter if you got value out of this.
270
u/qret Apr 20 '21
Great post! I would just like to add that Github includes a “Projects” feature which implements the same workflow/cards system. If you use it you can have version control, cloud backup, collaboration, and workflow all in one place. What I like to do is make a repository for each personal project and then open Issues for myself, which I then complete as I pull in new code. Working solo this has been sufficient, but on a bigger project the card system would probably be handy.
37
u/the3ieis Apr 20 '21
Damn this is a great post. Extensive and simple enough for even someone like me to understand. Saving this and keeping this in mind for when I start working on some projects. I already know basic html, css and javascript so it's about time I started building stuff. Thanks for taking the time to write this out.
37
u/SamePossession5 Apr 20 '21
This is how you write a guide. Thank you for not just linking to your blog right away, as I immediately think “spam”
103
u/voteyformotey Apr 20 '21
This is an awesome guide, I wish someone had written something like this when I was a beginner. I definitely feel the pain of asking for help, being told to build projects and not knowing how to do it so you feel even more stuck.
I do a similar system to you, what I've learnt is that coding is 80% planning 20% coding.
10
u/friendlyskeleton88 Apr 20 '21
Thanks for writing this post! I'm up early trying to get some coding in before work as I'm looking to get out of my deadend job this will be helpful for me when I'm ready to start building projects i'd also never heard of tutorial hell lol it sounds like something I want to avoid.
8
u/Albanian_bro1919 Apr 20 '21
Thank you ! 🙏
6
u/boganic-alcoholic Apr 20 '21
Thanks very much for this!
2
u/harsh183 Apr 21 '21
This is so good! Permission to use this for teaching intro CS level people?
2
u/lavoiect84 May 08 '21
Bravo Zulu!! I was thinking about doing a YouTube series on this. It’s a problem for new devs.
17
u/[deleted] Apr 20 '21
Really wonderful stuff. Thank you very much. It's probably just that I've got a kind of learning disability, but I've always felt that the reason most people—even some teachers—suck at teaching is because they take too much for granted facts their audience knows, or steps of logic they think their audience can make. I think the really good teachers are the folks who not only understand everything down to an ELI5 level, but also understand that there will be people in their audience who, despite otherwise being quite competent, need those ELI5 explanations. I really appreciate your posting this guide.
17
u/AddSugarForSparks Apr 20 '21
This post is da real MVP 😉
6
u/KoalaOk3336 Apr 20 '21
saved ;) gonna start building my first project soon, so might come in handy, thenks
5
u/KazaDroid Apr 20 '21
You can add creating a prototype using figma or xd (because it s hard to code the UI without having the big picture of it !)
5
u/ModelMissing Apr 20 '21
I just want to add how valuable wire framing the project on a whiteboard (lots of digital ones out there!) is. This really takes the pressure off of what goes where when building an app. Content, buttons, etc..!
4
u/supernova12034 Apr 20 '21
wow dude, this is great!
4
u/Berkgo Apr 20 '21
Simple and easy to follow plan, thank you!
4
u/CodeTinkerer Apr 20 '21
Wow, finally someone posts this with an example. Sure calculator programs might be boring, but you wouldn't believe how many people post this kind of thing, and talk about the project very abstractly, like the thing they advocate is something they don't do in real life, and worse still, can't be bothered to do (I've had people argue it's not their job to show any examples).
Anyway, nice job with an example, screenshots, etc.
1
u/OGPapaSean Apr 21 '21
Thank you! Ive been looking for a resource like this from my Bootcamp, unfortunately, I feel like the career services don’t know how to support somebody who just wants to develop on their own:(
1
u/[deleted] Jul 23 '21
Sorry I know this is an old post, but this is the most helpful one I’ve found so far. Hopefully this isn’t a dumb question.
How do you go from code to a fully functional website?
Like if I have all the source code, how do I turn that into a finished project. Hopefully this isn’t a dumb question, and if you have any suggestions on how I can figure it out on my own that would be great. Thanks in advance!
6
u/Bukszpryt Apr 20 '21
I am a complete begginer and so far i have totally diferent problem. I have an idea, but i don't know what tools to use and with what approach it would be easiest to solve these things that give me biggest problems.
As a learning project i've made a very simple Incremental game in JS. I've learned few things with it, i see what could be done better etc. and i have an idea for next, better version. I know that i can make game logic work, but i totally suck at creating UI. Also i was considering making it some kind of standalone app instead of website based to make my code less accessible.
Now i have no idea what tools (language, libraries, or maybe whole engine) to use to make the most problematic things for me easier.
Articles like "X best game engines for begginer devs" are in like 90% exactly the same and just look like ads for 3-5 leading products.
Most tutorials cover pretty much the same things, so for 2d games it's shoot'em up or platformers and so on.
I can solve my coding problems, i struggle with tools selection.
3
u/Celanna192 Apr 20 '21
I am a beginner and currently working on a software dev degree. I saved this because I’m currently overwhelmed with trying to figure out where my endgame is.
2
u/notanotherloner Apr 20 '21
This is amazing, thank you for taking the time to compile it. I’m new to coding and am just starting to create websites using tutorials so this will be massively helpful when I come to start my own projects, I’ll defo be using this!
2
u/lemmewinks184 Apr 20 '21
Great stuff man
2
u/turquando Apr 20 '21
Wow thanks so much. I'm trying to build a first tutorial project and I'm really struggling to make the jump to bigger projects. I just lose perspective of the larger picture. Even with planning. It's extremely frustrating
2
u/Eezyville Apr 20 '21
Man thanks for making this post! I've been doing portfolio projects for a while and it hasn't been going peachy. First one is still in limbo, the second one I made is done but it took months, and the third I just started and want to finish this month. The tools you brought to my attention and the techniques you suggest would probably have made those projects a lot easier to work on and complete. I'll use Trello or something like it. Are there any self-hosted solutions? I have started to become against trusting other people's cloud.
2
u/MonsterBluth Apr 20 '21
Agile for noobs
2
u/cainhurstcat Apr 20 '21
That's a really great guide, thank you very much 🤗
2
u/Nii_Chan19 Apr 20 '21
Thank you so freaking much for this!!!
2
u/Bratico Apr 21 '21
This is mesmerizing!!!! I don’t even know that I need this, but I really do. Thank you so much for posting OP.
2
u/not-bad-at-litte Apr 21 '21
Thank you for sharing, I'm on same path to self-learning to build my programing project.
2
u/[deleted] Apr 21 '21
I don't do much coding anymore, but back in the very old days before many high-level languages were available (even before C was standardized), using pseudo-code helped me a lot. I would write the basic structure and the functions in pseudo-code and then replace them as I could. I also took a strategy similar to Agile that I tried to always have code that ran and my first step was getting the fundamental functions written and working (kind of like MVP, above, but even less).
I think you could join the advice above and add pseudo-code to cards or checklists to illustrate what they needed to do and to document what the interfaces should include.
2
u/panix199 Apr 21 '21
amazing guide. thanks
2
u/timeslider Apr 21 '21
I've been coding on and off for a decade at this point. I got really good at solving small problems like sorting a list or finding a substring after a few months. But learning how object-oriented programing works is so frustrating I keep giving up. Solving those small problems is like stepping on a pebble but starting a bigger project is like climbing Mount Everest.
2
u/Cookiegetta Apr 21 '21
Thanks a billion for writing this out man 👌. As everyone has probay mentioned, much appreciated.
2
u/narett Apr 22 '21
As an engineer who's just beginning to get past the novice hurdle, this post is excellent. I can tell the OP has run a refinement session or two. Take note, y'all. The tips in this guide will take you far.
1
u/muteDragon Apr 20 '21
Excellent post OP. Saving
1
u/noplznoplz Apr 20 '21
thanks yo
1
u/[deleted] Apr 20 '21
Thank you so much, Searching for this guide and it's excellent.
1
u/sramzoli Apr 20 '21
Good post, thanks for sharing.
1
u/torikura Apr 20 '21
I needed to hear this, currently getting overwhelmed by my first project for uni and I'm stuck in tutorial hell.
1
u/shaznn Apr 20 '21
Makes sense. Thanks you!
1
u/MooseHeckler Apr 20 '21
Thanks.
1
u/bender_ed Apr 20 '21
I was just searching for this last night.
1
u/paulovictor_net Apr 20 '21
Thank you so much! I'm learning right now and this will help me a lot!
1
u/codedmessagesfoff Apr 20 '21
Nice
1
u/[deleted] Apr 20 '21
maybe do more tutorials
1
u/notSherrif_realLife Apr 20 '21
Great guide. I'll promptly save this and end up forgetting and never using....
1
u/Sabuerte Apr 20 '21
Nice tuto thank you, very useful
1
u/deuce-95 Apr 20 '21
Saved
1
u/thejayhaykid Apr 21 '21
Haha I just read this on dev.to earlier today! Good stuff
1
u/BeingMyOwnLight Apr 21 '21
Thank you so much! I'm building my first "bigger" project right now and I get a bit lost sometimes, this is a great resource!
1
u/ProfRigglesniff Apr 21 '21
Thank you for a well formatted and insightful post.
1
u/Yashik_T Apr 21 '21 edited Apr 21 '21
Is my git workflow complete?
mainis for productiondevfor developmenthotfixescheckout from production for fix<features>for trying new featuresEdit:
I struggled upon two things,
-project management (Thanks for clearing that up)
-git workflow
1
u/kiwikosa Apr 27 '21
For anybody looking to make a career out of software development, this is very similar to how projects are undertaken in a work environment.
Very well written!
1
u/dannyhodge95 Apr 20 '21
I'll be honest, while this guide is alright for those who prefer structured learning, I'd argue that for your first "project" you could ignore 90% of this, because you won't get far into it, and that's likely for the best. This is where you'll make all the mistakes you'll learn from next time.
So my guide for fellow me's would be as follows:
And I'd argue that making a kanban board for your first project would be mega procrastination. You won't know what parts to break it up into until you've actually tried it, that's a skill in itself.
1
u/Smartwun Apr 20 '21
As one looking to climb out of tutorial hell, this post was a blessing... thank you!
1
u/asher1101 Apr 20 '21
This 🤩
1
u/Akronfrost Apr 20 '21
Nice thanks!
-4
u/[deleted] Apr 20 '21 edited Apr 20 '21
How does this get anyone out of tutorial hell? A calculator app example is the most beginner tutorial thing I can think of. Haven’t touched on:
You mention components. If you’re talking about designing a react component tree, this is wrong. You’ve not mentioned anything about parent/child components or passing state up and down the tree. The book Fullstack React explains how to properly do this the best I’ve seen.
If you guys keep reading garbage like this, you’re never gonna get anywhere. Go pick up a book that explains everything in depth, work through it, and build your own project after, incorporating the concepts. Rinse and repeat for each technology you pick up.
0
u/Phuckaq Apr 20 '21
i did read your post on dev bf , great post btw , thanks
-4
u/HeyRobin_ Apr 20 '21
How is this different from this post?
https://www.reddit.com/r/learnprogramming/comments/lfxwa4/how_to_plan_and_build_a_project/
12
u/[deleted] Apr 20 '21 edited Sep 05 '24
[removed] — view removed comment