2012 taught me…..

In 2011 I worked hard in and outside of work to develop my core skills — SOLID, TDD etc. This year I learned many technical things with the bonus of incorporating ideas I learned during my studies of psychology.

When I think back, here’s what stands out….

**1. Context is king, objectivity is queen **

Understanding your constraints and your unique set of circumstances is usually more important than copying what others have done or the “best practices” and “principles” that have worked for them. 

Using your brain to be objective and take everything into consideration and try to deliver the best possible solution for all stakeholders and interested parties is the most important goal for me (not being SOLID or RESTful) 

**2. But not many people see things this way **

Oftentimes two parties will slug it out in an argument debating “this is the way to do it” or “no this is the way to do it”. From my recollection, nearly always people will agree that in some conditions X is the best and other conditions Y is the best. 

What I haven’t observed is people maintaining this mindset. So when the next debate rolls around its “this is the way to do it”… “no this is the way to do it”.

My life-lesson is to not get involved unless it contributes to my goals or I can genuinely help people.

**3. Work for a 7digital at least once in your life — preferably sooner **

Being part of a company that has an environment conducive to developer creativity and motivation is in itself one of the best experiences a career can bring you. 

I take my hat of the Rob Bowleys of this world for cultivating teams of amazing developers and giving them the freedom (mostly) to solve problems. I frequently remind myself how lucky I am to be in the same room as some of these people (and how much I begged Rob to get here). 

When you are deploying to live 25 times a day, and then you have 2 days innovation time to play with Erlang the next — you know times are good. 

**4. Years of experience means very little **

Steve McConnell wrote about it and this year I’ve seen it a lot. 

Across the different companies I’ve worked for and the developers I’ve met outside of them there is a gulf between those people who thrive for knowledge and live off motivation, and those people who turn up at 9 and leave at 5 (there’s no harm in that at all). 

In 2013 I’m making more of an effort to be surrounded by the former. These guys are the ones who motivate, inspire, and teach me the most. 

**5. Metrics are a BIG thing **

Big thanks to a colleague for opening my eyes to the importance of metrics . His message was so strong that every dev team in 7digital has statsd plastered all over their wall-mounted dashboard monitors. 

If in doubt, measure it — priceless. 

**6. The best devs aren’t the best leaders **

Over this year I’ve seen examples of technically brilliant devs being promoted into roles where their personality and leadership skills have seen them excel even further as leaders. 

Conversely, I’ve seen examples where a great technical mind doesn’t motivate others to work for them — doesn’t involve them in the bigger picture and take them on a journey to reach big goals. 

In the future, the people who are immediately directing me are going to be an even greater influence on the roles I choose to put myself in (unless the market swarms with decent devs and I’m grasping for whatever I can get).