ai architecture artificial-intelligence blog blogging Book Review business career Compliance Content Corporate Life Customer Support cybersecurity data data-science DevOps education entropy fitness garmin leadership Licensing life marketing microservices Monitoring music Observability Operations Partnership philosophy Product Management Products saas Sales Security software-development technology User Experience wordpress writing

I’ve been reviewing the APIs of a number of software vendors lately, looking at how you pull data that they don’t support pushing. It’s producing a bit of flashback to working with ugly things from the old days. Here’s a fun fact, apropos of nothing specific to any current project I’m sure… humans might assume

Lorin Hochstein recently wrote about normal incidents, “a result of normal work, when everyone whose actions contributed to the incident was actually exercising reasonable judgment at the time they committed those actions.” Instead of an accident or an error, it is an incident which is the outcome of proper behavior. An example of proper behavior

Something must be done! Here’s something… The vast majority of my career has been in competition with Microsoft’s bundled solutions. I do not think that you win by doing what they do, but more expensively. And yet, this happened. When Microsoft really comes at you, they do it with EEE: Embrace, Extend, Eliminate. It is

I’m pretty fascinated by the effect of social code matching in product design. In order to market and sell products you have to fit them to the buyer: language, use cases, pricing, packaging, sales motion, and more. In large and small ways, a company’s go to market or an open source project’s landing page tells

It’s easy to dismiss novelty, the new thing is often just the old thing with some small tweaks. But small tweaks add up, and eventually there is real change. Here’s what it was like to demonstrate virtual IP based network redundancy in the year 2000, over twenty years ago. The technology Wait, what is “virtual