Writing
Technology, work, leadership, and field notes.
“Last updated” prefers the update date; posts never updated are sorted by publication date.
Sync the officially confirmed objective facts first, without covering up problems; then explain goals, stability, and the new ways of collaborating separately to superiors, the team, and collaborators.
Short
2 min read
Headcount ratios are only a dynamic concept. What matters more is aligning goals, markets, and resource constraints in time when expanding, contracting, or changing plans.
Short
3 min read
Part of the column “Engineering Collaboration” · Chapter 4
The core of a 1-on-1 is helping managers and reports understand each other's goals and needs; authorization must follow information and role boundaries rather than mistaking context for transferred decision rights.
Short
1 min read
A multi-region system can neither cram every difference into a single core nor rebuild everything for each region. The key is to identify stable boundaries, preserve extension points, and clarify module ownership.
Short
3 min read
Part of the column “Technical Systems” · Chapter 4
The goal of effective sync is not to send out everything you know, but to give a specific reader, at the right time, the information needed to judge, collaborate, or act.
Short
2 min read
The most expensive cost of remote collaboration is often not the time difference but the repeated loss of context. Clear closed-loop responsibility, asynchronous documentation, and limited overlap time make collaboration more stable.
Short
2 min read
Part of the column “Engineering Collaboration” · Chapter 2
Resource pressure is not something a call to "try harder" can fix. The team needs to reduce commitments, risks, and complaints back to facts, and make trade-offs openly.
Short
3 min read
Part of the column “Engineering Collaboration” · Chapter 3
Time management isn't about packing your calendar full; it's about clarifying your commitments—and what you won't do right now—based on role, value, and opportunity cost.
Short
2 min read
Most project conflicts are not about someone failing to cooperate, but about goals, facts, or decision authority never being made explicit. Only by clarifying these three things first can disagreements return to something solvable.
Short
2 min read
Part of the column “Engineering Collaboration” · Chapter 1
Every role owns its own delivery, and everyone shares accountability for production outcomes. A quality loop depends on monitoring, fast containment, precise fixes, and retrospectives.
Short
2 min read
Good collaboration is built on trust, shared information, and solving problems together; when goals conflict, don't make promises privately—escalate with complete information to align.
Short
2 min read
Good standards don't turn every step into an approval; they make the key handoff points — where distortion, rework, and accidents are most likely — visible, discussable, and reusable.
Short
2 min read
Part of the column “Technical Systems” · Chapter 3
Motivation is not manufactured through slogans or pressure. What a manager can do is distinguish whether the problem stems from the environment, the role, the rewards, or the person's own state, and offer honest but limited support.
Short
2 min read
Part of the column “Engineering Collaboration” · Chapter 5
A manager's distance from the code shouldn't be a fixed number but a consequence of the goal: close enough to judge architecture, risk, and blockers, far enough to spend energy on defining problems, unblocking collaboration, and securing authority upward.
Short
3 min read
Code decay rarely comes from any single moment of bad writing; it comes from local changes repeatedly bypassing shared boundaries. What truly needs maintaining is the consistency between design and collaboration.
Short
2 min read
Part of the column “Technical Systems” · Chapter 2
Technology can't manufacture a selling point out of thin air, but engineers can still help the team understand users more precisely, shorten validation cycles, and turn implicit constraints into choosable problems.
Short
2 min read
When entering an unfamiliar business or system, don't rush to start from a local solution. First map the users, the process, inputs and outputs, key constraints, and value, so you know what to ask.
Short
2 min read
Frontline management is not about doing a bit more work for the team; it is about continuously producing better judgment, predictable delivery, and a collaboration system that can repair itself.
Short
10 min read
Part of the column “Building Teams” · Chapter 1
Fourteen days in Jakarta in February 2023: a city folded and cut apart, where high-rises and street stalls each live out their own everyday.
Short
3 min read
Potential is not a label drawn from a résumé or a single performance. Rather than judging whether someone is "smart enough," observe how they learn, act, think, and recover from setbacks.
Short
4 min read
Part of the column “Growth & Self-Assessment” · Chapter 1