Four engagements from the last year, each captured in the structure we use during steering committees: industry, the challenge that arrived on day one, and the measurable result the team chose to defend. We keep the format restrained on purpose — the briefings linked from each card carry the substance.
We publish long-form briefings on cloud cost refactoring and software modernization, and we run a small advisory practice for engineering leaders who want a clearer view of what to refactor next. The two disciplines stay editorially independent — and we say so up front.
How a Series B SaaS team trimmed 38% of their EKS spend without freezing delivery. Includes the rollback safety net we set up.
A small editorial discipline that has shaped how clients respond to our briefings.
Twelve patterns we keep encountering, paired with refactoring moves we have actually shipped.
Switch the toggle to see annual savings — paid annually trims roughly seventeen percent — and expand any tier to see what is actually included before any commitment.
A few of you reached out last spring asking how this publication ended up shaped the way it is, with limitations sections near the top and an advisory practice that we deliberately keep editorially independent. The honest answer is that the format came from a small embarrassment: I had been writing technical briefings for a previous newsletter that overpromised, and the first refactoring engagement I tried to support with one of those briefings went sideways in week two. The team had read past the caveats because the caveats were buried.
— Hyejin Park, Editor in Chief
Onboarding is intentionally short. Three questions on day one, two questions on day three, and a quarterly review thereafter. We have looked at session telemetry from comparable publications and concluded that asking more on day one increases churn rather than fit.
On account creation we ask three short questions about your team, the stage of your modernization program, and which topics you actively avoid. Your homepage feed is reordered accordingly. The default keeps the editorial mix; the answers nudge it.
Two delivery rhythms are available. A two-times-a-month newsletter for a calm, measured pace, or a per-briefing webhook into a Slack or Mattermost channel. We do not push more than the cadence you select.
If your subscription includes advisory time, you choose the cadence on day one — bi-weekly, monthly, or quarterly — and we set up the recurring scope conversation. The first session is dedicated to writing a short scope document together.
Six recent briefings, drawn from the cloud refactoring, modernization, and platform tracks; engagement fees apply when you access the full retainer notes attached to each piece.
A field-tested teardown of how a mid-size SaaS team trimmed 38% of their EKS spend without freezing roadmap delivery.
How a four-person platform group at a logistics startup built developer experience without becoming a permanent gatekeeper.
A patient, year-long modernization of a Java 8 monolith for a regional retail platform, told without the usual triumphalism.
A practitioner-led look at trimming observability spend without losing the signals that matter during incidents.
A short, opinionated briefing on how engineering throughput is shaped by ceremonies and review queues, not just architecture.
A careful, low-drama account of decommissioning a homegrown auth service and the eight months of preparation it required.
Forty-three engineering leaders subscribed to our editorial briefings this week, mostly through quiet referrals from existing readers. The number is real and audited monthly. We mention it not to manufacture urgency but because, in our experience, knowing who else is reading helps a leader decide whether the publication will be useful in their context. Subscriptions remain free; the cost only attaches when you choose to bring an article into a paid advisory engagement. We send roughly twice a month and the unsubscribe link is one click — we treat it as editorial signal, not as a problem.
Forty-three engineering leaders, evenly distributed across SaaS, enterprise platforms, and a handful of public sector teams.
See what they will read first →We do not push beyond two long-form briefings per month. Quiet weeks happen and we hold them rather than shipping filler.
Open a scope conversation →Each issue summarises the long-form briefings we shipped, names the limitations chapters worth reading first, and includes a single working note from one of our advisory engagements where we are allowed to share it. No tracking pixels. No drip sequences. One unsubscribe click and you are out for good.
We will not share your address. The signup itself is the only event recorded. See our privacy notice.