> Basically, I'd call someone a "senior" dev if they tend to answer more questions than they have to ask. IME "asking questions" has a bimodal distribution alo

> Basically, I'd call someone a "senior" dev if they tend to answer more questions than they have to ask. IME "asking questions" has a bimodal distribution along the axis of how good a programmer is: juniors ask the most questions, and seniors ask a ton as well. Sr.s don't ask language/framework questions (very often), but they dig in to requirements, project scopes -- they ask "why?" a lot.