Since the turn of the year I’ve been going to the Gym most days. It’s a bit of a cliché but it has noticeably made me feel more energetic and affords time for reflection.
Anyway, this weekend my friends invited me to go on a trip up Snowdon. Having never really done anything like this before it was a good opportunity to get outdoors.
Armed with a new(ish) pair of boots and a new coat, off I went.
It was always going to be a gamble climbing a mountain in Wales in early March, and we did succumb to the conditions in the end. There was still snow at the peak, having passed a sign stating that Crampons and an Ice Axe were “essential”, we went as far as we could without the necessary Adventure Gadgetry, which according to the more prepared climbers coming back the other way was around another half an hour battling through the snow to the summit.
Though we didn’t make it to the top it was still a great challenge, and certainly pushed us. I’m hoping to come back and conquer it some time.
When have you pushed yourself, in work or otherwise? What targets have you set yourself?
There is a thin line between healthy and unhealthy competition. Competition can lead to self-improvement, which is great, but it can also be detrimental. Slow down, ask yourself a few questions:
Who are you competing against?
Competition in the Animal Kingdom is a natural instinct, see tongue in cheek Lion King example. Competition to be King helped no one in this instance. As humans we may feel pushed to tackle those ahead of us in whatever hierarchy situation we may find ourselves in, but we’ve also been blessed with the presence of mind to make a more informed decision about how this will impact those around us. In a team situation Collaboration normally trumps Competition.
What are you competing for and how?
It’s worth getting clear what it is you are competing for, this will be clear in a race where you have defined parameters and a clear understanding of the rules. The same is not true of the workplace where you may be competing (silently) against other people for a promotion. It’s easy for this situation to become unhealthy competition. An unhealthy way to approach this is to belittle others achievements in order to make your own more pronounced. Best case here is that you get the promotion, but your new “team” will know what you did to get there. Impressing through your own abilities, and respect for others is a more noble route to the same thing, there’s no real shortcuts here. It’s good to point out your own successes, but don’t try to tread on others, again, see Lion King.
Does anyone win in your Competition?
Competition can be a catalyst for self improvement, if you’ve picked the what and the how well.
Who can write the most lines of code in a sprint?
Imagine this competition, what are you really achieving? No one wins in a headbutt!
Motivation is really closely linked to Competition in many ways, but it can also be a bit of a minefield when it comes to competition within teams. Everyone has their own goals, but it’s great if these personal goals can align with the goals of the wider team. I’ve previously mentioned the idea of letting go. Losing the mental baggage that unhealthy competition carries will let you focus on bettering yourself. I’ve recently been doing this exercise myself.
Ohm’s law defines the relationship between the voltage, current, and resistance in an electric circuit: i = v/r. The current is directly proportional to the voltage and inversely proportional to the resistance.
Agile from a business perspective is all about zoning in on what it is that is really required to offer the highest business benefit, in the shortest space of time, a.k.a. finding your Minimum Viable Product (MVP).
There can be a lot of ceremony in Agile, I get the impression that this is what takes the front seat in people’s minds, particularly those that would consider themselves “non-technical”.
Agile, to a Developer, should be about far more than just daily Stand-ups and Retrospectives. Agile is a mindset and an approach, focusing on improvement, reducing your resistance.
It’s vital that any improvement you identify gets fed back into future sprints, like electrons flying round a circuit, this is what keeps the lights on.
Your backlog is your potential, like a battery, keep this topped up with ideas, both business, and technical and you will be able to run indefinitely.
Your voltage (potential difference), is what you can achieve between your two fixed points, start and end of the sprint; with your throughput, current, being everything you can potentially achieve, relative to your impedance.
As responsible Developers, we should be maximising output, and identifying and feeding back on anything that can possibly reduce our resistance. Sure there will be no surprises here, but:
Improving build/deployment processes can help greatly, with DevOps as a discipline justifiably being huge business now;
Scope changes mid-sprint can be a huge impact to output, this may not be fully understood by business owners, it’s important to feed this back, we would know about it if we waste their time, the opposite should also hold true (communication, and a good rapport is key here!).
Think about what you can do within your team to reduce your resistance and increase your output. Talk it through with your peers and make a list of improvements you’d like to make, over time it’ll make your bulb glow brighter.
A lot of people struggle with apologising. It can be difficult, particularly in the workplace, but apologising even for little things can make a big difference to those around you. Couple of really obvious examples:
Sorry, I broke the build
Sorry, I’m not going to meet this deadline
Now, it’s not likely you will need to apologise very often; in fact, if you are, it’s probably indicative of a wider issue. In the above examples, maybe you need some coaching on TDD from peers, or maybe you need to be empowered to push back on an imposed deadline. There will be occasion, however, when things don’t quite go to plan and you just have to hold your hands up and say “Sorry”.
Apologising shows ownership and responsibility for your actions, which for me have always been key qualities with respect to choosing who I want to work with. Those with “Teflon Shoulders” tend not to last very long. It also shows a respect for your peers, they will know you dropped the ball, denying it will do you no favours in the long run and a prompt apology can make all the difference in getting people on side to help with a resolution if needs be.
What is an apology?
To me, an apology has very little to do with what it is being apologised for.
What’s done is done, no point crying over spilled milk, and so on.
In fact, in my head, I’ve probably already moved on…
So, what is it?
To me, an apology is:
a contract of intent not to make the same mistake again;
a display of ownership of your actions;
Not apologising, is the opposite:
a contract of intent to make the same mistake again;
shirking ownership of your actions;
An insincere apology is worse than no apology, if you don’t mean it, don’t say it.
It’s rarely too late to apologise, (especially if you still have a job!). Apologising can help you get something off your chest and also have a profound impact on those around you and the way they act towards you.
Is there anything you’ve done and shrugged off into the Ether?
Next time you do something a little bit questionable, at work or outside (we all do, don’t deny it), apologise and see where it gets you.
I recently made the transition from Permanent Employment to the world of IT Contracting. Along with this change, came a different role for me with my new client; a much more hands on position writing a lot more code which is exactly where I wanted to be!
Moaning is great. Everyone loves a good moan, myself included. Moaning can be helpful and healthy, in fact indirectly it’s part of the agile feedback loop, what went well, what didn’t. Accompanying this, should always be next steps; how to negate what grievances you may have.
There’s definitely a right time and a place for moaning sharing your observations in the context of your team, you’ll be best placed to know when this is, but it may typically be a team retrospective, a workshop on where your team is heading or a one on one, planned or impromptu session with your mentor/lead.
You can’t always have the glamorous roles in the team, sometimes you just need to roll up your sleeves and get stuck in. As a good team player you should have no qualms in doing the grunt work. Grunt work leads to insight, and insight can lead to improvement in process. Developers are lazy, and that’s no bad thing. Do something once, do something twice and automate.
Don’t shy away from hard work.
You’re the one with the low level knowledge of your application(s), any potential improvements that don’t fit within the confines of the piece you’re working on should be logged, to be addressed at an appropriate time.
This will serve to broaden the teams understanding of how they should all be writing software, e.g. coding standards/patterns, and, in the same way that code reviews serve to manage quality going in to an application. Improvements serve to keep the application up to date. As soon as it’s committed, code becomes legacy, it’s a valuable resource and an opportunity to improve, it, and yourself as time passes.
An improvements log can serve as a satisfying alternative to a good rant. Log it and move on, your lead should be monitoring the situation and pushing things forward.
I spent the past couple of weeks in sunny (excruciatingly hot) Paphos, Cyprus. In a similar vein to last year’s Holiday Reading : Lanzarote, I took a lot of reading material with me…
With the exception of Sharp Ends they are all quite old books that I had never got round to reading.
Sharp Ends – Having read all of Joe Abercrombie’s other books this latest collection of short stories was recently released, thankfully in time for my holiday. It didn’t pull me in quite so far as the other books, but such is the nature of the short story beast. It’s always great fun reading about “The Bloody Nine” and the new characters introduced left me wanting more. Hopefully more is in the pipeline.
The Da Vinci Code – I watched the Da Vinci Code film many years back. Aside from vaguely remembering there was a blonde monk who enjoyed whipping himself, all other details had been lost. I read Angels and Demons recently and decided to continue with The Da Vinci Code. It’s fascinating how Dan Brown mixes history with story.
The Moon of Gomrath – This is another old book from the 60s, I read the Owl Service last year, and subsequently Elidor. Fast paced high fantasy, not a long read and won’t be for everyone. If you like Wizards, Cat Armies, Dwarves, Elves, Possession and Witches you’ll like this one.
Adrian Mole – Sparked by a recent conversation in the pub with a couple of friends I decided to revisit Adrian Mole’s Diary. The stories are hilarious and level of detail make it so easy to relate to.
Microsoft have made it extremely easy, almost trivial to deploy your web applications to the Azure cloud from Visual Studio. Cloud capability is incredibly powerful for scalability, particularly in enterprise level applications and affords Developers with the option to make their infrastructure as Agile as their Software.