This post describes a simple framework for evaluating career choices along three dimensions and helps you to choose what is most important to you.

You have two choices when new challenges emerge: Offer several reasons why things wouldn't workSeek growth opportunities from the challenge Let's talk about the latter option. Scenario Your team dances through complex rituals every month before it can successfully deploy a big batch of changes. Engineers dread the drain on developer productivity and attendant customer … Continue reading Taking on scary challenges →

Excuses are easy, take ownership and drive for results

How do you drive change across difficult environments? For example, presenting radical new ideas to an unreceptive audience or collaborating with parties with opposing interests

Late in 2016, I made a conscious decision to become a full stack engineer. It was a tough decision for me because it meant a career reset and came with some risk. I would also have to learn a lot and fast too to be an effective contributor.

This post discusses the traits of the excellent engineers I have had the opportunity to work with over the years.

Nearly everyone goes through moments wherein they doubt their capabilities.

Looking back on my time as a developer, there are a lot of things I would have avoided doing if I had as much knowledge and maturity as I did now.

I have made a couple of mistakes over the years and wanted to share those pitfalls so upcoming programmers know what to avoid and what works.

Effectiveness, (noun) : the degree to which something is successful in producing a desired result; success.