So you're a "Senior Developer" now? What does that even mean? Is it a title you get for being the last one standing in a difficult environment? Is it a label you get for being older than your peers? If you want to become a "senior developer" what are some things that can help you get there?

In this talk, Chris shares his experiences of being a "senior developer" on different projects across different companies across different programming languages. Some of the things discussed include:

- problem isolation
- mentoring
- tooling support
- domain knowledge

While sometimes it just takes time to get to be "senior", these tips can help apply structure to a job that often comes with less coding and more problem solving.


Comments are closed.

Mike Lehan at 17:12 on 4 Nov 2022

Great set of tips for those who are, or aspire to be, senior developers. Presented with all the grumpiness and experience we've come to expect!

Chris had a great delivery that was entertaining, humorous, and informative. Good life lessons shared and career advice. Loved the grumpy approach that is practical and realistic instead of sugar-coating things. Had the audience laughing and learning, mission accomplished.

Joe Theuerkauf at 10:11 on 5 Nov 2022

Great topic for devs at all stages. As a senior dev already, i got insight on the progress of expectations and responsibilities i need to be aware of. Younger devs may see a glimpse of the need for patience in their path - seniority isn't a linear timeline, and accepting the role is more than just a title to increase your salary/rates.