The career of being a software developer can be a bumpy one. From the very start you are challenged by technical challenges you have no idea how to solve. Some grasp the concepts and principles easily, while others struggle. It’s an uphill climb of continuous learning. Constant failure, and success just a semi-colon away.
One of the biggest challenges during this process isn’t technical, but rather social. Around each turn you uncover new wonders, and new challenges. When you start a new job or position, publish a blog post, submit a pull request or even make a product. There will be people lined up to tell you how wrong you are and as a result; how you’re not good enough. I’m here to tell you, that you are!
I’ve been fortunate enough to be interviewed on the Legacy Code Rocks podcast. We had the chance to dive into empathy in software development and cover quite a few topics. I feel it was a really good conversation and I learned a lot. Hope you enjoy it! Continue Reading
When working in a team trying to deliver software things don’t always go right. Quite often they actually go wrong. Sometimes though they go so wrong that there are consequences for others. And when things go wrong, someone is to blame.
It’s natural to protect yourself and make sure all attention is on the next person by blaming and pointing. Perhaps you just sit idly and let others deal out blame and this helps you get by on a day-to-day basis. If you and the people around you are dealing out blame, you aren’t only making it bad for those around you, but for yourself.
Dear Lone ‘Team Player’,
Welcome to our team. We care about working together and improving as a whole. We know there are some challenges with the codebase, but are gradually improving as we deliver functionality. Continue Reading
Scott Nimrod invited me to a chat, which I gladly accepted. We speak about experiences and social intelligence in Software Development. I hope you find value in the converation. It’s available on youtube here: Talking to Pavneet about Software Development and Social Intelligence.
I first came across Scott in his interview on the Developer on Fire podcast. This happened to be one of the first podcasts I left a comment on. We are now twitter friends, and supporters of each others’ work. Scott has a focus on Software Craftsmanship and a wonderful drive to achieve great things. Check out his blog and multiple interviews (after you hear our chat of course 😁).
I would love to hear your thoughts on our conversation and any value you may have recieved. Reach out to me directly with you thoughts, questions or criticisms. Or leave a comment below.
You’re sitting there, writing code for another feature request and a message pops in. You know it’s important, since it’s a direct message. You glance at the notification and see the words:
Dev: “You broke the build…”
You click the notification and get taken to the 1-on-1 chat, where you read:
Dev: “You broke the build, you fix?
Short and to the point. An efficient message. Perhaps not the most effective though, since you’re sitting there and scratching your head. You’re feeling annoyed. Not because you broke the build, nor that this person let you know about it. It’s because you can’t seem to get hold of the feeling of the person behind the message.
Are they irritated? Maybe mad? Possible stressed out? None of the above? The uncertainty of this can easily put you in a negative state of mind, and that won’t help with collaboration. Continue Reading