The day before yesterday, on the first of December in the year 2016 in
Gregorian reckoning, marked the end of my career at SSH Communication
Security. Barring one 363 day stint working solely for Clausal
Computing, I've worked for SSH non-stop since April, 1998. Depending
on how you count it, I've been at SSH for almost 18 or 19 years,
basically employed by the same man. I'm 41 years old now, so you could
say I've spent pretty much my whole adult life working at SSH.
It is quite the change.
I have learned a lot during my years at SSH. I have learned some good
things, and also how not to do certain things. A pivotal point for me
was reading the Clean Coder, by "Uncle Bob" Martin. In the book,
Martin outlines how software professionals should carry themselves. I
have been striving to be a pro since. Intuitively, perhaps, I had known
what it included before, but reading the book really moved me.
I feel the biggest contribution in my career at SSH has been my focus on
software quality. Pardon my hipster, but we were doing automatic
building and CI before it was cool. Our venerable build system,
perfected (as in, not really touched since) years ago by a couple of my
colleagues, is still in use and we just last summer migrated away from
it in Client/Server product line.
I have been trying to inspire my team by leading from the front; they
know best whether I succeeded or not, but I did try my best. I have
tried to keep the vision and goal of the project clear for myself and
the team, whatever team I've worked in or my role in it.
I have done my best to be direct and "unpolitical " in my messaging.
I worked hard to not just elevate my own team, but to think about what
is the best for the whole company. If I think something is wrong, I
speak my mind; I make no apologies for that. I was unfortunate enough
to have been right about certain missteps, as I saw them, in the company
focus and direction. Unfortunately I was not convincing enough to the
management before things unfolded, but at least I did speak out. I love
my colleagues at SSH and do not really bear a grudge towards the
management either, I'm sure they are doing what they think is best for
the company as a whole.
18 years. I had started looking for a new place already, but I
genuinely wanted to tie up the loose ends before leaving: finish my
thesis for SSH, make the new version of the Server and make a really
great GA version of SSH Cryptonaut. As is my way, I have not been
quiet during the on-going co-operative negotiations, but whatever my
feelings, I've done my utmost to keep working with the same gusto as
before and keep my team doing the same, despite the circumstances. But
I guess my frustation at the situation, and the looming, ever increasing
possibility that the company will do something which I considered, umm,
ill-advised, got the better of me and I opened my mouth one time too
many.
I hope things get better for SSH in the (near) future, and I'm available
for management consulting for a modest fee, also for SSH :)
Now I have six months of termination period ahead of me. Before I start
anywhere new, I'll finish up my master's thesis, which has been pretty
much on hold for the time I've had management responsibilities. To be
sure, I won't be laying on my laurels; I'll be back working on something
new by February.
Since the news broke, I've been contacted by former colleagues and
friends, who have been so encouraging and warm that I am really
overwhelmed. It is really nice to be appreciated, and I am humbled by
the feedback I'm receiving from them and my colleagues at SSH. From the
bottom of my heart, thank you all.
Sami