Throughout my career I’ve met many developers in the beginning of their journey in become a programmer. In general what I observed was common doubts and questions that could be generalized to a broader audience.
As a consultant, those behaviors started to become even clearer. In the end, the developers I worked with wanted to be the better version of themselves, but didn’t know how to get there. I don’t know either. I am not the one to give them directions, but I can share what I see what could lead to the desired outcome.
Truth be told, I am not the best in class to give such advice. Therefore, I share the difficult state that is to be in a X position and wanting to level up without any idea where to go.
The idea is to focus on starters, more experienced developers usually have an idea on what they want to specialize, thus, following a path is easier. THe difficult part is in the mastery, how to become the best in technology X, or maybe switching career path. On the other hand, new comers to the programing world, are often facing a field full of buzzwords, twitter discussions, which is best? Business also have no clue what to do when a new trend comes, influencing them to follow a path that might not be what they want.
New comers are the ones that need the guidance in a sense that requires more detailed explanation for the why’s, what’s and how’s. Often, such guidance relies on experienced developers career, which also have some problems.
One have experiences that happened to be there, which not necessary are true for the new comers or for the history they want to build. Using the experience as a source for such guidance might work, but lack the new comer context.
An alternative is to build a common source of knowledge (like this one), to give guidance in a more broader way, without relaying on a single reference, hopefully helping others to have a perspective on what to do or where to go next.