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 written about metrics a number of times, since a lot of my career has been in tools to help people measure things. DURSLEy and CAPS talks about operational and business metrics, Product Sales Metrics is about measuring if your product is moving. There’s posts about measuring product quality, presenting metrics to leadership, building good

Let’s say you’ve been told to make a change and you’ve taken it to the team, and after everyone’s calmed down and thought about it, you are personally convinced it’s the wrong move. You now have a conflict, potentially serious, with the organization’s direction. What then? Are you going to push back, or let it

I wrote about communication tactics before, but that set of tips is more about status updates. Communicating a strategy is the next level up. Communication of the plan is not completed until the recipient is telling you the plan in their own words. Repetition is the key to this process. If you don’t feel like

Thinking about how SALAMI like CoPilot is supposed to make systems programming cheap and easy, in light of my challenge this week… The general problem statement: as a security analyst I want to know as much about an IP address as possible so I can make an informed decision, write rules, &c. The specific feature

There is a wealth of charting and reporting tools to use, but in my experience there is also a lot of struggle to build charts that effectively communicate. Since you typically need to put some reports into products and certainly need to use them internally, it’s important to build competence here. Building a general purpose