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

At a former employer some of us used to joke internally that we made the world’s cheapest business intelligence tool and the world’s most expensive log search tool. Business intelligence (BI) use cases are cheap from a data platform perspective, because value and volume are inversely proportional. All the work is in complex and customer-specific

Often your first product manager job is for a module on a platform, a single feature of a complex product, or a simple standalone product. This is because, while of course difficult, those are a lot simpler than managing a platform. When you product manage a platform, you lose a lot of the simple answers

I recently heard “you’re either writing software or selling it” as a categorizer for enterprise software employees, and I’d like to dig into why and how that’s correct and incorrect, at least descriptively. I am biased towards incorrect because I’ve worked exclusively for platform companies, but that’s just my experience. First, where would this thought

DevOps: there is no QA, there is no infra, testing and support are everyone’s job. This works okay for unit test level work, but end to end functionality involving multiple teams breaks all the time. You can ask DevOps to take that on too, but they’ll just laugh. You can ship without doing any, and

As a monitor writer, I want to alert when a value has changed quickly a lot in one direction or another, but i don’t want to set hard-coded thresholds because the value’s range is expected to slowly evolve. My goal is to get useful alerts and avoid false alarms. Examples: What It Doesn’t Do It’s