Reader and Writer Are Options, Not Architecture Rules
Choose Reader, Writer, and tool-layer boundaries from code size, domain distance, legacy constraints, and team conventions—not imitation.
Engineer · Writer
Build it. Run it.
Learn from it.
I’m Gemini Kim. I define software problems, test simple solutions, and write about what real-world operation teaches me.
Latest articles
Recent articles
The Common Module Trap: Organize Code Around Concrete Capabilities
Delay common modules until ownership is clear, and organize logging, exceptions, and shared protocols around concrete capabilities instead.
Join the Team Before You Try to Change It
Adapt to a new engineering team through timely questions, visible progress, early review, and small evidence-based changes after trust is earned.
How to Break Up a Giant Service Class Without Guesswork
Split an oversized service by mapping concepts, tracing responsibilities, testing boundaries, and comparing concrete refactoring options.
Keep Operational Tables Clean by Building a Separate Query Model
Design operational tables around business concepts, then serve complex history and admin searches from a separate query model.