(Previous: Coding Dojo: Algorithm Platform)
That’s why developers talk about Full Stack Development. In very general terms, a Full Stack, like a stack of pancakes has three parts: the front, back, and middle (more professionally referred to as the Front End, Back End, and Web Framework).
While each stack has some developers who swear by it and others who can’t stand it (just post an opinion on your social media outlet of choice and see for yourself!), there are enough similarities between the different stacks that once you understand one stack from front to back, it becomes easier to learn other stacks.
But jumping in and actually learning a full stack by creating a project can be overwhelming. There are a lot of moving pieces, and a lot of details to remember. And making a mistake in one part of the project can have unintended consequences throughout the rest of the project–it’s a lot harder to check for errors than when you’re working on a single page of code for an exercise or tutorial. Also, building a full stack project from start to finish is a much more significant time commitment than completing most tutorials.
So where do we start? And what resources, tutorials, and guided projects are already out there to help us?
In a future post, I’ll talk about my path through some of the MEAN stack resources I’ve found helpful so far (but without any pancake references, I promise!).