I’m not someone who writes five-year plans. But I have a clear enough picture of what I’m working toward.
Get deeper into Big DATA — practically, not theoretically
I’m already building AI integrations at Thornhill and running this blog on automated content pipelines. The goal is’nt just an AI User, but to become a ML, Data Analytics, Business Intelligence (BI) and Analytics profesional, also to be the person who actually ships AI-powered tools into production systems. Python machine learning, local LLM deployment, intelligent automation. That’s the direction.
Cyber security as a specialism, not a footnote
Most developers know enough security to be dangerous, they know the OWASP top 10, they sanitise inputs, they don’t commit keys. I want to go further: formal penetration testing skills, security architecture, the ability to audit a system I didn’t build and tell you exactly where it’s exposed. I’m already doing this at Thornhill. I want it to be a certified, recognised skill.
Build things that outlast the brief
The best work I’ve done is systems that ran cleanly long after I stopped touching them , migrations with no downtime, APIs that held up under load, pipelines that teams actually used. I want more of that. Less duct tape, more foundations.
Japanese
I worked as part of a multilingual Drupal build for Nestlé Japan and had to navigate Japanese content structures without speaking the language. That bothered me. I started learning. I’m still learning. It’s slow, which makes it useful practice in patience.
Write more clearly, think more clearly
This blog is part of that. The discipline of writing for someone else forces clarity. If I can’t explain it simply, I don’t understand it well enough.