[sibit]

This is just like, my opinion, man but I think titles are just food for our egos. I think developers should focus on two things: 1) doing work that you enjoy. 2) take a good long hard honest look at yourself and determine your value, then find an employer that agrees.

The only advice from the article I liked was:

> Even if it's just "hey, can I come sit in on that meeting?" Take notes for yourself of anything you're unfamiliar with and ask about those things later.

I love sitting in on meetings just to take notes. Recently some Sr Developers and our DBA set up a weekly meeting to discuss overhauling our database schema and I asked to sit in. Even though most of what I heard aligned with what I already knew I still got a lot of value in just listening to other people's opinions. The DBA was a fountain of knowledge when it came to the nuances of using SQL Server.

[yladiz]

> This is just like, my opinion, man but I think titles are just food for our egos.

Yes, but that doesn’t mean that we should ignore the importance of what the title signifies. Titles may not be so important to you, but they are to others and they also help signify how others should treat you. If you were a very senior engineer, I would expect that you act very differently than a junior engineer, and the easiest way to understand what expectations I should have for you is your title.

[sibit]

I will concede that saying "titles are just food for our egos" is a bit blunt and that there's usually a difference in expectations between Jr Devs and Sr Devs at most companies.