Practitioners write the briefings
Every long-form article on this site is co-authored with a senior practitioner who actually shipped the work being described.
About the publication
A quiet publication and a small advisory practice, kept editorially apart on purpose.
Refine Orbit Daily is based in Seoul. It started in 2019 as a one-page weekly newsletter for engineers working on cloud cost and platform decisions, and grew into the editorial-led consultancy we run today. Two practices, one editor in chief, and a deliberate refusal to blur the line between the two.
Operating principles 01 02 03
Three lines we hold
No rewrites disguised as refactors
We will not endorse a "modernization" plan that quietly resolves into a rewrite. If a rewrite is the right call we say so plainly and pause the engagement.
Limitations are part of the deliverable
Every briefing includes a section on what it did not address. Engagements end with the same.
Team
Five people, named on every byline.
A small, deliberately fixed-size team. We do not pretend to be larger than we are.
Editor in Chief
Hyejin Park
Twelve years across infrastructure platforms, four years specifically on cluster economics in Northeast Asia. Sets the editorial line and runs the Friday review on every long briefing.
— Reads every draft before it leaves the building.
Cloud Refactoring Consultant
Ji-won Lee
Background in JVM platforms and large-scale modernization programs across retail and finance. Leads our advisory retainers for enterprise platform groups.
— Wrote our internal "no rewrites" position paper.
Platform Architect
Min-jun Seo
Six years inside product-driven engineering organisations in Seoul and Singapore. Reviews architecture diagrams before they reach the briefing stage.
— Will challenge any sentence with "obviously" in it.
Technical Reporter
Eun-bi Choi
Reports on observability, reliability, and platform spend. Sits in on retros at advisory clients with permission and writes from notes, not press releases.
— Maintains our "anti-pattern dictionary" longform.
Client Success Lead
Sang-hoon Kim
Runs the kickoff conversations on every retainer and quarterly review. Keeps the schedule honest for both sides.
— Refuses to start engagements without a written scope.
Timeline
A short history.
- 2019
Started as a quiet weekly newsletter
Two engineers at a Seoul SaaS company began circulating a one-page brief on cloud cost moves to a small private list. The list outgrew the personal newsletter format within a year.
- 2022
First advisory retainers
A handful of readers asked us to bring the analysis directly into their engineering reviews. We formalised the retainer with a written scope and a fixed-cadence model.
- 2025
Editorial team of five
We added a full reporting role and a client success lead so the publication and the advisory practice could keep their separate disciplines. We do not blur them.