For further actions, you may consider blocking this person and/or reporting abuse
For further actions, you may consider blocking this person and/or reporting abuse
Yeom suyun -
Sloan the DEV Moderator -
Nathan Tarbert -
Brian Bethencourt -
Once suspended, ashishkapoor will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, ashishkapoor will be able to comment and publish posts again.
Once unpublished, all posts by ashishkapoor will become hidden and only accessible to themselves.
If ashishkapoor is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Ashish Kapoor.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag ashishkapoor:
Unflagging ashishkapoor will restore default visibility to their posts.
Top comments (3)
If you are referring to the title, it depends on the organization. I have seen people with 2 years of experience with "senior" titles. Titles have some meaning in the context of an organization, but there is no standard across different organizations.
If you are referring to the role, it depends on the experience. Time in the industry is part of it, but not the whole story. A senior front-end developer might be a very junior backend developer. And it gets even more nuanced. A senior front-end developer who has worked on Ruby on Rails for 10 years might be a very junior front-end Spring developer.
So.. seniority has to do with time in the industry, and experience in a given area.
In practice, you are a senior developer when everyone else comes to you to ask questions. You could be very senior in one team, and very junior in another team. It is really all relative.
In the quest of understanding when and how a software engineer becomes a Senior.
Usually, the person must've been in the tech industry for so long (eg. 20< years)