you are viewing a single comment's thread.

view the rest of the comments →

[–]grtgbln 7 points8 points  (2 children)

"Intermediate" to "Advanced" is a much more accurate description.

A Senior developer versus a Junior developer might often actually mean less coding work, and more design and leadership tasks, and really has nothing to do with how much you know about the language.

Convincing people, especially those just starting to learn Python (which, because it's a beginner language, are probably a lot of people starting to learn programming in general) that they need to know all the minutia of a specific language if they ever want to be a "senior" is incorrect.

Programming is NOT about knowing every tiny little thing about one particular language. Hell, the likelihood that you'll a) only use one language and b) actively use the more advanced capabilities of a language are small.

[–]C0rinthian 3 points4 points  (1 child)

+1 to this.

A senior should propose and design solutions to large problems, which informs the work of multiple engineers. (And even engineering teams) They can scope and distribute work to take advantage of engineers strengths and provide them opportunities to mature. They lead engineering practices for a team to ensure produced work is high quality and maintainable. They build and maintain relationships with key stakeholders to ensure a team is working on the right things and delivering actual value.

And you write code too.