Not just “done”—truly sealed, completed, enchanted. DoD is your team's best protection against chaos magic.

If you’re still calling people “resources,” I’ve got a user story for you.

Some phrases overstay their welcome. And some start to smell.

(And reminded me why I fell in love with teaming, TDD, and the craft in the first place)

(Without Falling Asleep or Getting Assigned All the Action Items)

Scrum, but make it real. A story of one dev, one day, and one team that gets it right.

Why new team leads should plan for their own succession from day one—so they can take a vacation, step away, or move on without leaving a leadership vacuum. 🧳

Why new team leads should define clusters of responsibilities—called domains of execution—to ensure every project area is covered and supported. 🧩

Why new team leads should practice Real-Time Permission to encourage healthy conflict and foster team growth. 🔄

A practical guide for new team leads to navigate staffing changes—whether building a new team, adding a teammate, or handling transitions—by asking the right questions. 🧠

Why new team leads should practice Radical Candor on themselves—out loud—to build trust, model transparency, and navigate leadership fumbles with grace. 🤝

Why new team leads must define their boundaries—knowing when to step in and when to say, 'That's not my oven!'—to avoid burnout and maintain focus. 🔥

Why new team leads should document project milestones and decisions early—so they can tell a compelling story when it matters most. 📜

How doubling the frequency of my manager meetings led to more meaningful conversations and better accountability.

I'd like to share my favorite git aliases and settings.

My experience as a beta user of Dark, "the quickest way to code a backend"

My review of the new(ish) JavaScript frontend framework, Vue.

How to create your first HTML file, including setting up your development environment.

I built a thing that administers Mihaly Csikszentmihalyi's ESM test for flow, or the state of being "in the zone" in order to try out Vue and darklang.

A rundown of my team's experiment with dual track development

A behind-the-scenes look at SEP’s three-week rapid prototyping project—what it is, how it works, and what to expect from this kind of engagement. ⚡

I just want to take a minute to gush about a brilliant woman.

We, software engineers, have built an ecosystem that may neglect introverts.

My slightly satirical, stream-of-consciousness take on scrummy pregnancy.

The tv-show medium that KnowBe4 uses to share its security vulnerabilities content is sneakily powerful, and genuinely enjoyable.

Instead of wishing you could be less fickle when it comes to personal projects, just be you! Here are some resources for your spaced (dev) rehearsals.

My coworkers spent weekend doing napkin math to figure out how long their workflows were running on average. Here's how I found the same information in a matter of minutes.

What an anti-feminist taught me about being a good teammate

Instead of the classical performance goals, I want to set some learning goals for myself.

There's a bogus 15 minute sleep setting I can't undo because of HIPPA or something (it's probably not HIPPA, it's probably some other security measure I blindly follow because IT tells me to). So, I wrote a script.

In becoming someone's wife, I've realized that the best thing I can do for us, is to be aggressively real about my nature. Can I impose the same benefits on a business?

I woke up one morning last week and realized, _I'm lost_. Ever since, I've been in a perpetual brain-cycle of self-discovery. What is it about my day that makes me feel like I've abandoned who I am?

Why do we tend to invert a power dynamic, rather than level it?

OH.EM.GEE. I NEED GUAKE ON MY PC! I haven't found a thing that will do this for me, so I built one.

I have a really hard time with the precept, "Self-reliance is the key to happiness."

Why is it so hard to find examples of unit testing HQL?

I would like to expose a team which merged continuous integration and continuous deployment with scrum cadences.

Developing software as a trade quickly evolves into a cyclical game of problem discovery and problem solving. The problem discovery portion tends to manifest rather easily, so your time is dedicated mainly to the problem solving. If your project is anything like mine, you'll notice that every solution generally depends on some expert in that area. I call this person "the guy".

I started myself on a bit of an experiment. Like any great scientist (trust me, I took organic chemistry), I'd like to share my findings, lessons learned, and why 80% of the time this experiment made me a horrible developer.