Communication, General, Teams

Hitting Refresh

Unlearning is one of the hardest parts with any transition. You bring with you many years of experiences, expectations and biases. These have built up over time through different work situations you have adapted to. Past experiences allow you to hit the ground running when it comes to work and communication. They can also be heavy baggage, slowing you down. In a startup this baggage could be the very thing that’s holding you back. You’re looking at completely new problems with views that don’t match your situation.

Here at Dolittle, we’re hitting refresh on many of our previous assumptions. Looking at old problems with fresh eyes. How we approach our coding practices. How we are working with customers. How we are approaching contracts. How we are building products. We’re re-learning, and allowing our culture to grow.

“If your mind is empty, it is always ready for anything, it is open to everything. In the beginner’s mind there are many possibilities, but in the expert’s mind there are few. ” –Shunryu Suzuki

An example is communication. Coming from a very distributed team, a few of us wanted a more formal process. More documentation, more written communication. This is important down the line as we grow, but not so much in the beginning when priorities change almost daily.

Hitting refresh is an important part of starting anything new. Making it explicit that you need to take a step back and reconsider your expectations. You’re going to have new problems and you can’t deal with them if your focusing on solving the problems you had in the past. At the same time, it’s importatnt to leverage universal learnings and principles. It’s also important to recognise the context in which those are valid.

Are they really valid to you now?

Photo by rawpixel on Unsplash


This post appeared originally on the Dolittle blog

Agile, General

“just add an if”

You’re talking about a new feature that’s being planned and prioritized to the dev-team. It’s straight-forward enough, but you sense that it’s latching on yet another feature to an existing long chain of functionality. The team has some reservations to expanding the feature chain even more before doing some adjustments to how it’s been architected to keep this maintainable. That’s when you hear from the product owner: “Just add an if…”. Continue Reading

General

Submitting a Conference Talk Proposal

This is an inwards-facing post, which you may or may not find valuable. The short version is: TL;DR: Do something that scares you. Perhaps submit a proposal for a conferences Call-For-Papers?

Some time ago, I was fortunate enough to have the opportunity to speak at NDC Oslo, with a dear friend and colleague of mine. An experience I will cherish with personal growth and many connections made.

I feel, though, I had the home-side advantage. Presenting in my country of residence. On stage with a colleague that had my back. The topic was in context of my employer, who was well-known for the home audience.

I’m not trying to de-evaluate the accomplishment, but rather the potential and hunger to take the next step. But is it worth it?

The next step, maybe

Fast forward a summer vacation / paternity leave and the speakers-high has started to wear off. I’m curious if I can make the step to an international arena, alone. Searching around I stumble over The Lead Developer New York, and decide I want to try for that.

I take a first step, and ask for feedback on the talk from NDC Oslo. Feedback is decent, but there’s a lot of work involved to re-angle it for it to work in that setting. Challenge accepted…but not today.

A few weeks more go by, and I’ve procrastinated away my first opportunity as a CFP (Call For Papers) goes by. Too much going on, or so I say to myself.

Reality check. I can actually do this if I want to. Then Imposter Syndrome strikes. Hard. More procrastinating. Some interactions, and writing the blog post on Imposter Syndrome remind me of what I need to do.

Action!

Last week I submitted a proposal for a talk that’s been swirling in my head for some time for The Lead Developer London 2017. I have no idea if it will get accepted, but I’ve taken the first step.

The journey from idea to submitting a proposal is a tale of missed opportunities, failure to take action, internal struggles with my self-worth, but most importantly growth.

For the record, the title of the talk is “You are more than just your code“.

What’s holding you back from taking the first step towards something that scares you?

Reach out to me directly if you have any thoughts, questions or criticisms. Or leave a comment below.

Cover Image:  WilliamMarlow via Visual Hunt / CC BY-NC-SA

General

Podcast Interview – My Life For The Code

I love podcasts and consume them whenever I can, so when I saw the opportunity to be a guest on the My Life For The Code Podcast, I jumped straight on it. I had previously listened to Shawn’s interview with Scott Nimrod and loved his format and style.

So here’s the podcast link: Episode 20 – Coding with Empathy with Pavneet Singh Saund

Shawn was a great host and had prepared well. He managed to dig up a few of my breadcrumbs from the internet and  we had a blast talking about burnout, access 95, running and mindfulness.

He also asked me a few question that I’ve been pondering on since the interview, but more on that in another post…

Hope you enjoy it!

General

Start of an empathic journey

Firstly, thank you for taking the time to visit and read this blog.

As software developers we are challenged throughout our careers to deliver great code that accomplishes something valuable for someone. Sometimes that someone is yourself. Other times it could be a customer, end-user or even other developers. All have in common that there is a need that has to be solved and you as a developer have the capability to meet that need. Continue Reading