This is a question about tech at large I think. While searching for jobs, everyone lists their techs and frameworks and on and on that they want, but it seems terribly vague to me what the day to day problems of a given position are. What are the kinds of things that a newer developer simply doesn't or wouldn't be able to handle effectively, since really everyone is playing in the same sandbox with the same rules. What are some of things I should know I dont know? Apologies if there is no good way to approach this question
Responses
Hey Brian! This is a great question. The way I think about it is that as you become more senior you design and build increasingly high-level abstraction levels. Tactically what this can look like is that when you are entry-level, you’re usually tasked with taking an existing set of patterns and applying them in a new context. So this can be using an existing codebases way of building a page and repeating that on a different page. The side effect of this is that you also learn processes for building, testing, and deploying code.
As you get more senior you’re tasked with deciding what patterns are used. At first, this can look like choosing specific libraries or making an existing pattern or library more efficient. Even higher up is making huge decisions such as the architecture of an entire project.
When you are senior you learn how to make these choices knowing that it could be years before the full implications of these critical early decisions. Suffice to say, these types of decisions and designs are challenging and require experience to learn what to choose and why.
There’s a lot more on this topic than one could say, but hopefully this starting point is helpful!
About Discussions
Discussions is where tech workers share tips, tricks, and stories about important career questions.
Start a discussion to get help from thousands of tech professionals.
