Cameron Watters Musings of a Proto-Millennial Software Engineer in the Pacific Northwest

Thoughts on Operational Responsibility[ for Software Engineers] —

When we accept that Ops and Development are mutually responsible for the health and functioning of production applications, our focus can shift to the question of how to better work together before, during, and after applications are deployed to production and delivered to customers.

We Learn By Changing Our Minds —

Dogma inhibits growth and makes us brittle; it's best kept it to a minimum.

MOAR Reading! —

A couple years ago, I published a reading list for first year software engineers. I've compiled a more complete list…

Take The Time To Truly Understand —

Often, we settle on an explanation based on an untested speculation rather than analysis. Mere plausibility is not an adequate threshold to stop investigating.

First-Year Reading List for Software Engineers —

The best engineers I have worked with over the past 20 years are constantly reading and aggressively developing their skills. You probably should be, too…

Honesty Requires a Thick Skin —

Candor can be unpleasant…

A List of Movies From Which I Draw Cultural References: The Eighties —

I often reference films that I watched during my formative years in conversation. Recently, I encountered someone roughly my age who was unfamiliar with many of the movies I assume everyone from my generation has seen. So, I made a list…

Microsoft Licensing Policies Are Kindof a Bummer —

The pain of dealing with Microsoft's licensing model(s) often overshadows the benefits of using their software…

On Brand Naming —

A clever brand name is unlikely to overcome poor execution.

Links for December 2006 —

A collection of interesting links from December 2006

Links for November 2006 —

A collection of interesting links from November 2006