Skip to main content

Joining eyeo: A Year in Review

It's been well over a year since I joined eyeo. And 'tis the season for yearly reviews, so...

It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling.

Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes:

How given no other structures, silos will grow by themselves

This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies without them, but I haven't been there to witness them coming into existence before. It is a fascinating phenomenon, yet oh, so common. And a killer of great companies.

When you got no other reason for improving, go for lead time

There are so many reasons for why you would want to drive organizational change, stop the silofication, bring in some agile values, and so on. But the one reason that rings true and clear for any person in the company is lead time. Then you can slowly start to talk about the cost of WIP, hand-offs, and so on.  When explaining the why, start with lead time.

The best patterns for introducing organizational change in are inscrutable

I tried out several patterns, from early adopters, to whispering in the general's ear. I tried driving changes by committee and without. We tried bootstrapping, and we tried organic change. It always felt like a mix of hurt and help, but it seems through any of the changes, they were for the better (unless they are driven by targets, of course). The only way to know for sure whether I had the right strategy is to go back in time and compare how the options would work out in alternative realities. So we're left with, once again, gut feelings.

Developing the ubiquitous language of organizational change

In a company where the norm is to shun any hype, and avoiding cargo-culting by all means, it was not easy to use the language I had come to learn in the industry. Mentioning Agile would derail any discussion into shoot-downs, anecdotes and personal opinions and experiences. Few of the agile values, principles or practices were taken at face value. The more experienced colleagues had bad experiences with "agile transformations", and the large majority of younger colleagues (funny, cause I feel like I've always been the youngest where ever I worked, and suddenly here I'm in the oldest 15 percentile) have not suffered the pains of silofication, nor experienced the joy of successful organizational change.

As is the norm these days, "DevOps" has already been reduced to infrastructure engineering. Scrum is a fad, Kanban is a board on the wall, XP is some long gone neck-beard hippie thing. Sprints are pointless. Conway's law is unknown, as is Lean. Rationality, skepticism and pragmatism rules. Which can be good, but it can also grind conversations about organizational improvement to zero velocity (pun intended).

So, I started with a survey, "What should we call the things". By now, we've basically come up with our own methodology. Hell, it's even one of them "scaling" ones. And we use a lot of seemingly boring words to describe very powerful things.

The emerging trend of self-management in organizations is going to be big

As eyeo is at the steps of exploiting more agile values and principles, we also look to the horizon to see what is coming. The ideas of teal organizations rhyme very well with agile and DevOps, but they go way beyond. Surprisingly (and yet, perhaps not), a lot of these self-organizing principles are easier to apply to eyeo than the agile predecessors. Albeit eyeo is an overgrown start-up of sorts, with the expected chaos, their universal inner values are fairness and transparency. Armed with this, a lot of the self-organizing patterns are a great fit.

Balancing the act of dropping into Operations, while driving organizational change

This is where I failed the hardest. And perhaps where I learned the most. How can I reconcile the act of supporting one particular department, while I at the same time am trying to break them up across cross-functional teams? I went on for too long ignoring this conflict, and it cost a lot of soul to make things right, and there's still a lot to do.

Building bridges in a company which is both remote and not

I am a hybrid remote worker, which means I am simply not a remote worker (or remotee, as they're called at eyeo). As most remote workers know, a mixed remote/local team is the trickiest constellation to have in any company. It does work at eyeo so far, mostly for historical reasons and remote culture being deep in the DNA of the founders, but it will only get us so far. We can't become co-located, nor does the majority really want to, so we have to improve. I've got some ideas, but haven't gotten so far with this yet.

Team autonomy vs company standardization

This one's a real classic. How can you pick a company-standard chat tool, while giving teams the autonomy to pick their own? This topic is fairly exhausted in the DevOps literature by now, I guess, so I'm not sure it's worth it. I got a lot of thoughts on it, but they may not be so original. A lot of it comes down to decision making, which in its own right is a big topic.

It's like blog post tapas

So, those are the ones I had in my head right now. If you got this far, and you'd care to give me a tweet, let me know which one I should write first.

Comments

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities . It "was decided" that we'd be doing AES with a key-length of 256 , and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet! The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE  in order to do 256 bits. It's a fascinating story , the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them. Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password

What I've Learned After a Month of Podcasting

So, it's been about a month since I launched   GitMinutes , and wow, it's been a fun ride. I have gotten a lot of feedback, and a lot more downloads/listeners than I had expected! Judging the numbers is hard, but a generous estimate is that somewhere around 2000-3000 have listened to the podcast, and about 500-1000 regularly download. Considering that only a percentage of my target audience actively listen to podcasts, these are some pretty good numbers. I've heard that 10% of the general population in the western world regularly listen to podcasts (probably a bit higher percentage among Git users), so I like to think I've reached a big chunk of the Git pros out there. GitMinutes has gathered 110 followers on Twitter, and 63, erm.. circlers on Google+, and it has received 117 +'es! And it's been flattr'ed twice :) Here are some of the things I learned during this last month: Conceptually.. Starting my own sandbox podcast for trying out everythin

The academical approach

Oops, seems I to published this post prematurely by hitting some Blogger keyboard shortcut. I've been sitting for some minutes trying to figure out how to approach the JavaZone talk mentioned in my previous blog-post. Note that I have already submitted an abstract to the comittee, and that I won't publish the abstract here in the blog. Now of course the abstract is pretty detailed on what the talk is going to be about, but I've still got some elbow room on how to "implement" the talk. I will use this blog as a tool to get my aim right on how to present the talk, what examples to include, what the slides should look like, and how to make it most straightforward and understandable for the audience. Now in lack of having done any presentations at a larger conference before, I'm gonna dig into what I learned at the University, which wasn't very much, but they did teach me how to write a research paper, a skill which I will adapt into creating my talk: The one

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --