“I’m better than them, I should be doing that?” But you’re not, so you can either keep dwelling on it, move forward. No one is stopping from going ahead and doing it on your own, somewhere else, in another role, perhaps just not with there. The choice is up to you how long you want to let it hold you back.
“No, but I can learn it.” That’s all I need to hear in an interview, if I can hear that, I don’t need to dissect whether you know something or not or what level of syntax you know. That tells me that you are honest in what you know but you are driven to learn something new and contribute to our team by going beyond what is asked of you. What more could you want?
And other great developer messages… “Build Succeeded…” “Unit Tests Passed…” “Successfully Deployed…” “Pipeline ran Successfully…” Amazing how much joy these few messages have brought me over the years.
The question your team will ask over and over again if they don’t understand your vision, or if they forget, or if they get lost along the way. It can be frustrating for a leader to hear that after they have poured so much into making it happen, into making it worthwhile, into making it something only to be hit a dismissive – “Why are we doing this?”. Make sure they always know it, make…
Your membership has privileges. If you’ve been a member somewhere for a few years, that should buy you some goodwill – a thank you, some forgiveness if something goes wrong, a check-in, etc. That’s the whole point of membership – being part of something that people care about. We’ve devolved membership to be “Sorry to see you go.” as opposed to “What did we miss?”. If you’re building a program that requires membership, start first…