I keep seeing software engineers spending copious amounts of time arguing about performance, using performance as a metric when comparing the relative merits of various code constructs, or using performance as an argument about doing something in a certain way vs. a different way. (Heck, even I sometimes make this mistake.) This post explains why this line of thinking is, more often than not, misguided.

Here is an infographic showing the dotnet version history from its introduction back in 2002 until today.

I just received the IriusRisk Associate certification.

I just received the IriusRisk Secure-By-Design (SBD) Essentials certification.

Behold, my latest contribution to the English language:

stan·dard·speak /ˈstæn.dɚd.spiːk/

noun [uncountable]

1. (disapproving, linguistic slang) The formal, highly stylized, and wooden jargon characteristic of technical standards, regulatory frameworks, and specifications. It is marked by rigid modal verbs (shall, should, may), passive voice, excessive precision, and legalistic phrasing designed to minimize ambiguity at the expense of readability.

Fun thing I learned today:

TCL (Tool Command Language) used to be pronounced "tickle".