You’re talking about a new feature that’s being planned and prioritized to the dev-team. It’s straight-forward enough, but you sense that it’s latching on yet another feature to an existing long chain of functionality. The team has some reservations to expanding the feature chain even more before doing some adjustments to how it’s been architected to keep this maintainable. That’s when you hear from the product owner: “Just add an if…”. Continue Reading
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
I stumbled over this Gem? when watching Kylie Hunt and Lars Klint speak about “Boosting Productivity through Employee Happiness” on Pluralsight. 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 ?).
Scott’s Resources:
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