One of the things I like to do with my team is think through how to grease the skids for easy and rapid software development and deployment. Over the last year, I’ve done some work on my team’s deployment processes, trying to make sure there’s as little overhead as possible. Why is that? Well I want our team to be deploying all the time. Even while a feature is being developed and incomplete. Why is that? Well, I’m glad you asked. Pull up a chair and sit down…

There are many software engineers and web developers who really feel like all this typing is just annoying and gets in the way. But if you learn to embrace strong typing, you will actually write fewer bugs and have a more resilient system.

Your application is not your data, and modeling your application solely on the underlying data can cause some serious problems, and the world can go topsy-turvy if the underlying data model changes and you don’t have a concrete way to keep that from rippling through your application.

You can’t set cookies via header with the HTTP Streaming API, which React makes copious use of for async data loading and suspense boundaries. What do you do when you need to update a token stored in a cookie then?

Maintainability and comprehensibility are huge issues in software engineering. But it seems that many don’t optimize for either of those things when organizing their code. I’m here to help with that…

The service locator pattern is everywhere, certainly in Laravel (most famously by means of “facades”) but it’s in other places too. this is a pattern we should avoid and Brent Roose gives us a few great reasons as to why…

How can you advance your software and applications by bits and pieces at a time? There is a way, and I’d like to talk about it…

As a follow up to my post, “Incidental Duplication”, I thought I’d share this great article by Kent Dodds with you…

Is your software feeling a little too DRY? A spoonful of duplication may be just what you need. Hear me out…