Last month I had a number of instances where people and organizations I had worked with in the past had come full circle to what I had tried so hard to convey 6 years ago.

At some point, a price has to be set for a product. Here's a real-world example of how a company landed on a number.

A script I had while on a team, affectionately known as DBNuke, is back. Let's go from nothing to a docker, fully restored database in minutes.

Differences between .net on windows and linux are subtle, and in this case, having dots in a configuration key make the app fail to find a value

How do you use the phrase "I was lucky"? I've noticed how I use it, and I realized I was indeed using it to cover up various things.

Code is um, code, so yes, you should test logging statements. It'll not only demo why you thought it was important, but give someone else a chance if something does go wrong. Otherwise, continue to scroll-scroll-scroll-scroll