I don't think of software as just screens and APIs. I think of it as infrastructure — something people lean on to do their work, run their business, or serve citizens. Especially in utilities and revenue, failure has real-world consequences.

That's why I care a lot about architecture, clarity and small details: how a retry strategy is implemented, how a migration is rolled out, how a customer support agent sees the state of a meter.

Some principles I keep close:

• Design for failure, not just for the happy path.
• Make things observable. Logs, metrics and traces are part of the product.
• Respect the domain. Talk to operators, finance teams, field engineers. Let real workflows shape the model.
• Ship in slices. Deliver value early, but build on foundations that can grow into a platform.

If this resonates with how you want to build, we'll probably work well together.