What’s in it for you

A guide to what this site is for, who it helps, and how to use topics, how-to paths, and podcast episodes.

This site is where I make sense of cloud, FinOps, AI, technology, money, and the human context around decisions.

The thread running through it is simple: context is everything. Numbers without context are noise. Tools without context become rituals. Strategy without context does not survive contact with engineering.

The site has three main ways in.

If you are new here

Start with Start here. It explains the main idea of the site and gives you the map: technology costs, architecture decisions, FinOps practices, business goals, incentives, culture, and governance are all part of the same system.

Use this route if you want the big picture before choosing a subject.

If you know the subject you care about

Use Topics. Topics are broad subject areas: FinOps, AI, AWS, internet infrastructure, leadership, communication, mental models, simplification, information management, and personal efficiency.

Use this route when you want to browse by area. For example:

  • FinOps for cloud economics, reporting, governance, and executive decision-making.
  • AI for AI cost, governance, workflows, and organisational change.
  • AWS for AWS pricing, cost data, operations, and commercial signals.
  • Mental models for better thinking, framing, and decision-making.
  • Leading and managing for leadership, teams, trust, and organisational work.
  • Information management for notes, knowledge, data, and context.

If you have a job to do

Use How to. How-to pages group articles around a reader goal rather than a subject label.

Use this route when you are trying to do something specific, such as:

If you prefer shorter spoken pieces

Use Podcast. Podcast episodes sit inside the same topics and how-to paths as articles. They are marked as podcast content, but otherwise they are part of the same map.

What you should get from it

The goal is not to chase every announcement or publish perfect doctrine. The goal is to leave useful thinking behind: ideas you can reuse, challenge, connect, or apply in your own context.

If you work with cloud costs, FinOps, engineering strategy, finance, AI, or leadership, this site should help you ask better questions before jumping to answers.

Sometimes that means a practical how-to. Sometimes it means a market signal attached to a topic. Sometimes it means an older essay that explains why the obvious answer is not enough.

The structure is there to help you find the right kind of context for the problem in front of you.