Dec 20 2016

Company given rank and how much it matters

Category: TechnicalIuliana @ 1:01

I’ve been promising for a while to start writing technical posts, but until I’ll have some time to write some code, I do have a few ideas regarding management and internal hoochy-moochy that happens inside IT companies. Bare with me, it might be either fun, either instructive, depends on how my mood changes while I write. Also, do not expect a small post that you will read in five minutes, you know I rarely do that.

I’m in my 10th year of experience in the IT field. I have worked on a lot of different type of projects, I taught at the university for a while, did some consulting and even written two technical books.  The company I work for currently has knighted me at the beginning of the year and therefore I am now called a software architect. My diplomas say that I am an engineer. And I find the term  software engineer much more suitable, because engineers break down problems into smaller problems and provide solutions or they concoct contraptions to make life easier and work more efficient. This is what I’ve been doing since 2010, concocting contraptions to make my work easier so I can be payed for being lazy.

But back to the original point. Last week, the company I work for sent me to a training/workshop where some guys were explaining something that I cannot currently write about and at the beginning of the workshop asked all of us to present ourselves. These guys were just there for the workshop, we will probably never see them again and the plan is to provide our own implementation for the thing they talked about. Nevertheless my colleagues started giving super details, their full names and full titles within the company. I just told them my first name,  the project I work on and the reason I was interested in the workshop. All done in 20 seconds or so. Bam!

I never liked labels, maybe because I was given so many while growing up (crazy, poor, weird, teacher’s pet, geek, nerd, etc). I do not like titles either. Unless you are freaking royal, then… oh well, you can have your title and shove it where the sun don’t shine. I have been doing architect work since 2010 when I had a full project on my hands, and I had to migrate it to some new technologies. And I did that and only missed the deadline because I broke my right hand and I had to program for two weeks only with my left hand. And I am right handed.(Since then I kinda started doing a lot of things with my left hand too, so now I think ambidextrous fits.) Returning to the original idea, bragging about your title when it does not fit you, is quite ridiculous. You can call yourself a manager, but you’re not doing much managing if your team members keep leaving. You can call yourself and architect, but if your solutions are crappy you’re not doing much … architecting(sic!). You can call yourself a web developer, but if you cannot develop a responsive web interface, allow me to have my doubts. And plus, a title given by the company you work in is as valuable as your wife knighting you the best lover in the world.

This is why I used to make fun of my architect title at the beginning. People who do not know me well, did not get my sarcasm. Many of my colleagues took my Lync status (I am architect, therefore I am God…) as bragging. I do not feel like an architect when I do not have architect specific tasks. So I present myself as a developer or engineer. It suits me better at the moment.  The way I see it, presenting myself as an architect, when I do little architect work, would be like presenting myself as Miss Romania, after I gained 20 kilos. So I do not present myself as an architect. I let others do it.

Another term I totally loath is expert. In the company I work for people like to use it a lot. I just started on a project called Regulator, people I interacted with, already started calling me The Regulator Expert. Then I switched to something called XBRL, I became The XBRL expert. Seriously???

I am no expert, in anything. Really. But what I am good at is keeping things simple and keep learning. Everything I do, I try to make it so simple that anybody with a little motivation could understand it, use it and maintain it. Why? Because I am lazy, I prefer the work to be self explanatory, than for people to bother me with questions. The other reason why I prefer not being asked questions about my work is that I kinda’ lack social skills. So if I develop something, expect tests, proper documentation with three types of UMLs  and some extra schemes drawn in Google Drawings. Anything to keep you away from me.

Also, company ranks mean nothing if you are not up to the task. And I’m the kind of asshole that even if you are a manager, if you are a crappy one, I will treat you accordingly and eventually tell you to your face, because negative feedback is also a thing.  :D

This being said, there is a post about negative feedback in the works. I hope you will enjoy that too.

Stay safe, stay smart!

Tags: , , ,

Leave a Reply