Giving advice

Photo by:

Photo by:

First thing about giving advice is that you should add a disclaimer:
“These are my experiences, views and opinions. Treat them as such and then make your own reflections on whether they’re worth taking to hear or not”

The version of me that existed a couple of years ago would not add the disclaimer. I’d just burst out my opinions as truths without blinking. Anything from advice on coding to career advice I’d lay out without giving it a second thought. That’s cool right?

Not really.

Luckily I’ve had an upgrade since then and I’ve gotten a module installed which adds perspective of other people and the ability to think outside my own personal context.
Advice given by people shouldn’t always be taken literally. You should reflect and decide whether the persons context relates in any way to your own. In the past I’ve said things like “don’t care about asking for permission, just do the work you feel is right”.
This might be great advice for some, but in a different context reading things like that just makes you more depressed. Say you work in a country with a soaring unemployment rate, you have a big mortgage and you have to support your family of five. You also happen to have a boss who’s unpredictable and fire people left and right.
If that’s your context and your  life when reading my advice, how would following my advice make any sense at all? You’ll end up unemployed and perhaps out of a steady income for months. If I was in that context, I wouldn’t give advice which clearly only works if you’re in a place of privilege.

When we give advice, we tend to forget to add the disclaimer about the advice being for a certain context. Not only when it comes to job related things, but also technology advice should come with more reflection than it usually does.

You’ve seen the blog posts. Everyone is doing X now, if you’re not on-board you’ll be professionally dead in the water in a couple of months. Those of us who’s been around a while now this to be false. Not once in my fifteen plus years in this business has something like that happened that quickly. Sure there’s a lot of new things coming out, but never is there an urgency to get on-board or perish. People are still making a living coding Flash for crying out loud! (and yes, of course there’s also the Cobol people).
When we write those excited posts, take a moment to reflect about people who aren’t as privileged that they can switch to new stuff constantly. There’s a million reasons why using some new technology isn’t possible, and that’s cool. We shouldn’t work so hard to elevate ourselves by talking down people who can’t follow all the trends. They can be just as amazing programmers as yourself. Working with legacy is so much harder than jumping on all the band wagons, we should recognize this and be a bit more careful when giving put advice.


The world is yours, and everything in it


I attended a great communityu conference in Bergen called Booster conf. They have a lot of students helping out as volunteers, which is a really great thing. Providing them with an insight into our industry is something that is really cool.

During the conference there are a series of Open Spaces and today I did something I’ve been thinking of doing for a while. I suggested giving some subjective advice to students. This was largely triggered by discussions during lunch related to working in fucked up organizations and projects. I just thought that they need to get a heads up on what to do, so they don’t end up wasting their talent and their opportunities. The session was really great and I think it wasn’t all “grumpy old guys telling war stories”. 


The future of the world does belong to the young, hence the quote in this post. Only problem is that they’re very seldom aware of this fact (I know I never was). Especially when you’re a young IT-student there are just so many opportunities out there just waiting for you. 

  1. Look beyond what you see around you. You can reach for jobs and careers beyond what is in your near proximity and what you think is possible. The opportunities available to you are greater than ever before.
  2. Take your time, you as a student should not be in a hurry. It is only those who try to recrute you who’s pressed for time.
  3. The best jobs are seldom posted anywhere, so try poking around in networks and communities for which companies are doing cool stuff. Figure out what you think is fun and try figure out who matches you best

I think that #2 is perhaps the most important. Especially in Norway where there are few signs of a decline in demand for fresh talent to IT companies you should not rush. 

Perhaps the best advice is to not listen to people who try to give you advice, figure it out on your own ;)