Skip to content

Latest commit

 

History

History
35 lines (24 loc) · 3.02 KB

become-a-senior-dev.md

File metadata and controls

35 lines (24 loc) · 3.02 KB

How to become a Senior Developer

One other thing that is super important is learning how to optimise learning and remembering things. We can get lazy watching videos, but then never reviewing what we learned. We have to make sure that the time we do get to study is VERY optimised.

A Senior Engineer's CheckList

Junior engineer takes any feature they're given to build. And if they've seen technology or maybe the solution before, they can solve it. Mid-level engineer takes any feature they're given to build.

And even if they've not seen the technology or solution before, they can figure it out because they've learned how to learn, they're problem solving strong. A senior engineer is somebody who can take any given feature, and not only just figure out for themselves, but enable the rest of their team to figure it out.

Because they have technical communication, the ability to explain what their code is doing to somebody else in their team, in a clear and cordial manner. But I'd also say even for junior mid-level developers, technical communication is gonna make your own mindset clearer. So the purpose of Hard Parts is gonna differ depending maybe on your background in JavaScript.

If you're someone who's a mid-senior developer, you've seen many of these principles before, maybe you've come from a computer science background. Then think of especially the earlier parts of JavaScript, the Hard Parts, as more about building up your technical communication. The ability for you to verbally work through exactly what's happening on the blackboard here, verbally talk through your JavaScript and your code with clarity and precision.

That's not only going to improve the way you reason as an engineer, it's also gonna make you a more effective, collaborative team member on your engineering projects. You're gonna now be able to take complexity and make it salient or meaningful to other developers in your team. If you're not as familiar with some of these really quite hard principles under the hood of JavaScript, then it's gonna provide you some of the building blocks that is gonna allow you to become a better problem solver.

What to focus on:

  1. Analytical problem solving
  2. Technical communication
  3. Engineering approach
  4. Non-technical communication
  5. Javascript and programming experience

======

I know my place of work well enough to identify situations that lead to success. I'm comfortable questioning those in authority when their expectations or request don't make sense. My 30 second elevator pitch rolls off the tip of my tongue. I communicate crisp, clear and concise. The need to be liked doesn't stop me from saying things others might not like to hear. When given a task with too little time or too few resources to complete it, I negotiate for what I need to make it more reasonable to accomplish. I seek high-profile assignments that will stretch my skills and let others see what I'm capable of. In every situation I believe I'm as smart as the person next to me.