Welcome to HackerNoon’s Meet the Writer Interview series, where we learn a bit more about the contributors that have written some of our favorite stories.
Let’s start! Tell us a bit about yourself (name, profession, and personal interests).
My name is Dechun. I’m a software engineer working in the UK, mainly on large-scale payment systems. I spend a lot of time thinking about how AI behaves once it’s deployed in real-world environments.
I’m particularly interested in how AI interacts with xhigh-impact domains like finance and healthcare, where decisions affect real people. I enjoy exploring how intelligent systems can support better outcomes while still remaining transparent, reliable, and accountable.
Interesting! What was your latest Hackernoon Top Story about?
My latest HackerNoon Top Story was “When AI Can Make ‘Perfect Decisions’: Why Dynamic Contracts Are the Real Safety Layer.”
It explored why AI systems can appear flawless on the surface, while actually hiding fragile decision boundaries underneath. I focused on ideas like decision constraints, dynamic contracts, and human-in-the-loop design — essentially, why “smart” systems still need to be designed in a way that keeps them observable and correct over time.
Do you usually write on similar topics? If not, what do you usually write about?
Yes, most of my writing revolves around AI systems, agent behaviour, and real-world deployment risks. Rather than tutorials or news commentary, I tend to write about how developers should think when building AI — especially in environments where errors have financial, medical, or societal consequences. Recurring themes in my work include AI governance, system reliability, prompt design as a control mechanism, and the limits of automation.
Great! What is your usual writing routine like (if you have one?)
I don’t really have a fixed routine. Most articles start with something I’ve been thinking about — usually triggered by new AI developments or problems I’ve seen in practice. I tend to jot things down as rough notes first, and only turn them into an article.
Being a writer in tech can be a challenge. It’s not often our main role, but an addition to another one. What is the biggest challenge you have when it comes to writing?
The hardest part is explaining complex technical ideas without either oversimplifying them or making them unreadable. It’s easy to build a system; it’s much harder to explain why it behaves the way it does in a way that actually sticks with people.
What is the next thing you hope to achieve in your career?
I want to keep working on AI-enabled systems in high-impact areas like finance and healthcare, where reliability and responsibility really matter. Longer term, I’d like my work — both technical and written — to help teams make better decisions about how they build and use AI.
Wow, that’s admirable. Now, something more casual: What is your guilty pleasure of choice?
Probably binge-watching Black Mirror. It often feels like the kind of future it talks about is slowly becoming part of everyday life.
Do you have a non-tech-related hobby? If yes, what is it?
I love playing badminton and swimming. Both are great ways for me to stay active and relax.
What can the Hacker Noon community expect to read from you next?
More writing about AI systems in real-world environments, especially around agent behaviour, decision-making, and the limits of automation. I’m particularly interested in how these ideas translate across industries like payments and healthcare.
What’s your opinion on HackerNoon as a platform for writers?
HackerNoon is one of the few places where you can go deep on technical ideas without needing to turn everything into marketing. The community seems to value honesty and substance, which makes it a good place to think out loud about complex topics.
Thanks for taking the time to join our “Meet the writer” series. It was a pleasure. Do you have any closing words?
Thanks for having me, and see you in the next piece.