Skip to main content

My name is Ash, and I was a manager


 
"My name is Ash, and I was a manager"
Sometimes I feel like I should say that in a circle of other former managers and get a ripple of applause for admitting it. 

Pitchforks at the ready.....

Every time I open Twitter or LinkedIn I see a pithy saying about managers, the reasons why your manager is out to get you, or in the way, an unfeeling monster, the root of all that is wrong in the software development world. Managers are generalised and stereotyped mercilessly, oddly enough by those who accuse same managers of the self same behaviour.  

Some dislike specific managers or at least personality types of managers, some management as a concept, some say management is confused with leadership and vice versa. A legion of reasons to mistrust, expressed in many ways.

Because reasons....

Now, I'm not an idiot, this mistrust has been earned. As a consultant to various companies I've seen some very inhumane approaches to management executed by, quite frankly, unstoppable morons with some horrendous results. Broken confidence or even careers justified by terrifying organisational values (or the dreaded 'commercial reality', the catch all excuse for awful treatment of fellow humans), utterly opposed to the contradictions plastered on their marketing material. Maybe people think that about me. I hope not.

This might earn me some grief....

But you know what. for the most part, I'm proud to have managed people, helped them with their immediate and long term goals, provided direction if they needed it and most of all, trusted them to get the job done using their expertise. If I helped them meet their goals and represent the wider organisation, then I can stand by my work. The world is getting flatter and I'm all for it. I enjoy my autonomy, it is a fundamental need that most of us share.

Thinking locally....

Whenever I see the latest 'why managers are bad' schtick, I think of my own manager in my previous role. That person earned but never expected my trust, gave me timely, meaningful feedback and provided a non-judgemental sounding board. If someone can do that, how can it be bad? Maybe I was just lucky.

Now I've got no one to manage but myself. Hard work. :-)

Comments

Popular posts from this blog

A Lone Tester at a DevOps Conference

I recently had the chance to go to Velocity Conf in Amsterdam, which one might describe as a DevOps conference. I love going to conferences of all types, restricting the self to discipline specific events is counter intuitive to me, as each discipline involved in building and supporting something isn't isolated. Even if some organisations try and keep it that way, reality barges its way in. Gotta speak to each other some day.

So, I was in an awesome city, anticipating an enlightening few days. Velocity is big. I sometimes forget how big business some conferences are, most testing events I attend are usually in the hundreds of attendees. With big conferences comes the trappings of big business. For my part, I swapped product and testability ideas with Datadog, Pager Duty and others for swag. My going rate for consultancy appears to be tshirts, stickers and hats.

So, lets get to it:

3 Takeaways

Inclusiveness - there was a huge focus on effective teams, organisational dynamics and splitt…

Wheel of Testing Part 2 - Content

Thank you Reddit, while attempting to find pictures of the earths core, you surpass yourself.
Turns out Steve Buscemi is the centre of the world.

Anyway. Lets start with something I hold to be true. My testing career is mine to shape, it has many influences but only one driver. No one will do it for me. Organisations that offer a career (or even a vocation) are offering something that is not theirs to give. Too much of their own needs get in the way, plus morphing into a badass question-asker, assumption-challenger, claim-demolisher and illusion-breaker is a bit terrifying for most organisations. Therefore, I hope the wheel is a tool for possibilities not definitive answers, otherwise it would just be another tool trying to provide a path which is yours to define.


In part one, I discussed why I had thought about the wheel of testing in terms of my own motivations for creating it, plus applying the reasoning of a career in testing to it. As in, coming up with a sensible reflection of real…

Getting started with testability

At TestBash Netherlands, I said that, in my experience, a lot of testers don't really get testability. I would feel bad if I didn't follow that up with a starting point for expanding your mindset and explicitly thinking about testability day to day, and making your testing lives better! 

In large scale, high transaction systems testability really is critical, as compared to the vastness and variability of the world, testing done within organisations, before deployment, is limited by comparison. We need ways to see and learn from the systems we test where it matters, in Production.
Being able to observe, control and understand is central to testing effectively, and there are loads of resources and experience reports out there to help. I was/am inspired by James Bach, Seth Eliot, Matt Skelton, Sally Goble, Martin Fowler and a little bit of PerfBytes/Logchat, so lets see if it works for you! 

Overall Model:

Heuristics of Software Testability by James Bach

http://www.satisfice.com/tool…