There are lots of ways to draw lines between junior and senior developers
There are lots of ways to draw lines between junior and senior developers.
Here's a distinction I find useful.
A senior developer makes suggestions when they're asked to do the wrong thing, and "fills in the gaps" when requirements are incomplete.
Examples:
That's not accessible.
That doesn't match our standards.
Can we use the web platform for this?
That hurts performance. How about this instead?
This design omits loading state, validation, and error handling. How about this?