Featured
5 เรื่องที่ Software Engineer ควรใส่ใจมากขึ้นในยุค AI
ช่วงนี้ผมรู้สึกว่า Software Engineering กำลังมีปัญหาใหม่ที่น่าสนใจไม่ใช่เพราะเราเขียนโค้ดไม่เร็วพอแต่เพราะเราเขียนมันได้เร็วเกินไปเมื่อก่อนการสร้าง…
· Medium · Read on Medium →
Aphidech Mahakoat (Jack), Software Engineer in Chonburi
I build software systems that stay understandable as they grow.
Software Engineer focused on architecture, developer experience, and how humans and AI agents build software together.
01 · Writing
Thinking in public.
I write about software engineering: architecture, developer experience, and how we build software now that AI agents are on the team.
02 · Beliefs
How I think about software.
A few principles I return to when systems get complicated.
“Software is a communication problem before it is a coding problem.”
The code has to convince the next reader, not just the compiler.
“Good architecture makes change cheap.”
The test of a design is how boring the next feature feels.
“The best abstraction is often the one you don’t need.”
Every layer is a promise someone has to keep. Promise less.
“Optimize for the reader, not the writer.”
Code is written once and read for years.
“Boring technology, thoughtfully applied, wins.”
Novelty is a cost. Spend it where it buys something.
“AI makes writing code cheap; judgment is the work now.”
The bottleneck moved from typing to deciding what is worth building.
03 · About
Engineer first, writer second.
I am Jack, a software engineer in Chonburi. I enjoy building systems that real people depend on, from university platforms and internal tools to storefronts, and keeping them understandable long after launch.
The engineering problems I find most interesting are structural: where should the boundaries go, what should be easy to change, and what can we leave out entirely. I care about developer experience because the people reading the code are part of the system too.
Beyond the code itself, I care about how software gets built: the conversations, reviews, and decisions between people. Lately I have been thinking about where AI agents fit into that process. I write about that here.
04 · Contact
Have an interesting problem? Let’s talk.
I enjoy conversations about architecture, developer experience, and building understandable systems, especially as AI agents join the team.