Everyone hates estimating large software projects. It’s fraught with peril. Someone will ask you to estimate a large project and assure you that they won’t hold you to that estimate. Inevitably they are perplexed when the project isn’t done by that time.

Me writing for LeadDev. Turns out Microservices or sadness are not the only two options for working in a legacy codebases.

When I first became a Staff Engineer I struggled to keep up with Code Reviews. I was drowning in review requests from different teams and different parts of the application. I couldn’t keep up and I felt guilty about not getting to reviews quickly or providing detailed enough reviews. It turned out that the way to improve my code reviews was to spend less time doing them.

My 10 minute attempt to convince you that all codebases aren’t doomed to eventually become a nightmare to maintain.

I recently decided to start blogging but ran into trouble picking a blogging platform. I only had a few requirements. The blog needed to be fast, simple, and support posting from MarsEdit. Unfortunately I couldn’t find anything that ticked all of those boxes so I built my own!

I’m enjoying the newish 37 Signals dev blog. It’s great to see them writing about the patterns and approaches they use especially now that many of them have fallen out of favour.

It’s an exciting time for machine learning. What get’s me most excited though is the ability to easily leverage machine learning for building product features. The Elixir community has recently made big strides in making this easy. Tools like Nx, Axon, and Bumblebee make it easy to integrate machine learning into Elixir applications. If you’re anything like me though you may find it difficult to use these tools because you lack intuition on how they work under the hood. Let’s explore machine learning in Elixir without these tools.

My Sask Dev Talks aren’t my most polished talks but they are the most fun to give. They are, relatively, low pressure and the community is always awesome to interact with.