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
- 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.