John Obelenus

I've written about “writing the software isn’t the hard part operating it is” before.

I am referencing a well known piece by Fred Hebert with my title about writing software.

There are four categories to examine the work we do, or our co-workers, or even the work our users are attempting to do with the products we make; work-as-imagined, work-as-prescribed, work-as-disclosed, and work-as-done.

We build software to solve problems.

Every year when the calendar starts getting to the end, and life starts to slow down a bit, I get an opportunity to step back a bit and think a bit more broadly.

A good friend and I were chatting about his job.

I have been putting together some interesting correlations that I have observed throughout my career.

When we talking about "who owns what" most commonly I hear people discuss it in terms like these: "Who owns this module in the codebase?"

I think the idea of "Strong Opinions, Weakly Held", as it is commonly received, is a terrible concept.

The aphorism "A person is smart, but people are stupid" has always stood out to me.