Henry Kemp
I live in Perth and work in technology leadership. Lately I have been thinking a lot about AI, software delivery, governance, and useful ways to contribute outside my day job.
If you found this because my email address ends in henrykemp.net, that is about the right level of publicity. This site is a low-key place for notes, links, and the occasional update.
Why this site exists
This is not intended to be a CV, and I am not trying to turn it into a polished personal brand. LinkedIn has the professional version. This is more of a public notebook: AI tools I am trying, things I am learning about software work, and community interests that do not fit neatly into a work profile.
I am interested in technology leadership in the practical sense: what should be built, what should be stopped, what risks are worth taking, and how people make good decisions when the technical detail is moving quickly. AI has made those questions more urgent, not less.
Things I keep coming back to
AI and software work
I have been trying coding assistants, OpenClaw, Copilot Cowork, and small application builds to understand what changes when working software becomes cheaper to produce.
Cloud and delivery
Cloud platforms, delivery models, and governance still matter. The AI layer does not remove the need for architecture, accountability, resilience, or operating discipline.
Community and public life
I recently stood for Nedlands Council. I am still interested in local government, volunteering, cycling safety, climate and environment, and useful civic work in Perth.
Professional interests, without the full biography
I have worked across infrastructure, cloud, consulting, and public-sector technology delivery. I do not keep a downloadable CV here, but my LinkedIn profile has the professional version if that is what you are looking for.
Lately, I am especially interested in AI’s impact on software development: not just code generation, but the wider changes to architecture, testing, delivery, team structures, governance, assurance, and how people outside specialist technology teams interact with software systems.
I recently stood for Nedlands Council, which sharpened my interest in local government, community decision-making, and practical ways to contribute outside work. I am interested in volunteer roles where technology, community, environment, education, or public service overlap in Perth and across Western Australia.
The board and executive angle
I am interested in board, advisory, and executive conversations where technology is important but the decision is not only technical. The areas where I can usually be useful are the places where strategy, delivery, risk, people, and public or organisational impact meet.
Strategy into delivery
Turning broad ambition into operating models, platform choices, partner arrangements, delivery constraints, and measurable progress.
Risk and assurance
Asking the practical questions behind technology decisions: resilience, data, security, assurance, supplier risk, cost, and accountability.
AI with judgment
Looking past novelty to capability, workforce impact, trust, accountability, and the controls organisations will need as AI becomes normal work infrastructure.
Where I can be useful
- Technology strategy, cloud platforms, digital transformation, and delivery operating models.
- AI adoption, coding assistants, governance, assurance, and the practical impact on software teams.
- Public-sector and community-facing technology decisions, especially where trust, service quality, and local impact matter.
- Risk, resilience, data, security, vendors, cost, and accountability behind technology investment decisions.
Perth is a practical place to think about change.
Perth is big enough for complex public services, major industries, and serious technology work, but small enough that local decisions and community relationships still feel close.
The things I care about often meet here: digital delivery in government and enterprise, safe streets and cycling, climate and environment, young people learning technical skills, and the ways AI might change the work people do.
Recent experiments and possible writing streams.
- Trying Copilot Cowork and agentic software workEarly observations on coding assistants becoming more agentic, and why direction, review, ownership, and assurance matter.
- Building a small expenses app as a test of AI-assisted deliveryA practical experiment in turning a familiar business process into software, and what it says about judgment when software gets cheaper.
- Experimenting with OpenClaw, and what cheaper code changesNotes from trying an AI coding workflow and thinking about the bigger shift that happens when code generation gets cheaper.
Get in touch
LinkedIn is best for professional context. Email is fine for direct contact, community ideas, or volunteer opportunities that connect technology, education, environment, or public service in Perth or Western Australia.
I am also interested in board, advisory, and executive conversations where technology, governance, and community impact overlap.