Tag: #career

← All posts

• Fourteen Things Table Tennis Taught Me: Skill Makes the Relationships, a Title Blocks the Growth

  Fourteen principles from years of playing table tennis, and how they carry over into work and life. The structure that turns skill into an entry ticket to relationships, why playing only for fun never makes you better, a

  2026-08-16 · 11 min read #mindset#growth#deliberate-practice#sports#career

• The Road to Becoming an Expert: Feedback First, Volume Second

  This post moves the evidence set out in the previous four posts into an executable form. Narrow the domain to where feedback arrives, build the feedback loop before you build the volume, practise under the conditions you

  2026-08-16 · 14 min read #mindset#learning#expertise#deliberate-practice#career

• When Your Purpose Is Unclear — Clarity Is Not a Precondition for Starting

  Why does the strategy of waiting until purpose becomes clear fail, in a state of not knowing what you are living for? The view that purpose is discovered downstream of accumulation rather than upstream of planning, the l

  2026-08-16 · 12 min read #mindset#purpose#career#self-improvement#2026-08

• The Complete Guide to English Job Interviews: Passing on Structure, Not Fluency ♪ Listenable

  What stops you in an English interview is rarely vocabulary. It is the shape of the answer. This guide covers the length and order of a self-introduction, the frame that links an experience as situation, role, action and

  2026-08-16 · 30 min read #english#interview#career#communication#job-search

• Lunch, Hoesik, and Hallway Conversation — What Flows Through the Informal Channel

  An organization runs two information networks. The official channel carries what has been decided; the informal one carries what has not been decided yet. This post admits honestly that not participating has a cost, and

  2026-08-16 · 14 min read #career#workplace#korea#communication#boundaries

• Managing Up Is Not Flattery — It Is Designing the Flow of Information

  Most trouble with a boss is not a personality clash but information asymmetry. Your manager sees wide and shallow while you see narrow and deep, so the kind of thing each side misses is the same every time. This post cov

  2026-08-16 · 13 min read #career#workplace#managing-up#communication#manager

• The Order of Operations After a Mistake — Contain, Report, Record, Prevent

  The cost of a mistake is set not by the mistake itself but by the four stages that follow it, and people invert that order in almost exactly the same way every time: hunting for the cause instead of stopping the bleeding

  2026-08-16 · 13 min read #career#workplace#mistakes#incident#accountability

• Bad News Is Judged by Timing More Than by Content

  A good response delivered late is judged worse than a bad response delivered early, because bad news is evaluated on two axes: the size of the problem, and the number of options the listener has left. The size of the pro

  2026-08-16 · 13 min read #career#workplace#communication#escalation#reporting

• The Structure of Saying No — Work Piles Up by Routing, Not by Rating

  When work piles up on you, that is not praise. It means the cheapest path for someone to ask ran through you. This post first explains the structure that turns the reward for being capable into a penalty, then shows that

  2026-08-16 · 14 min read #career#workplace#boundaries#prioritization#communication

• The First 90 Days After a Move — What Gets Decided Before Performance Does ♪ Listenable

  What actually gets decided in your first quarter at a new organization is not performance but classification. People sort a newcomer into one of a few boxes quickly, and the box is hard to change afterward, because the i

  2026-08-16 · 15 min read #career#workplace#onboarding#transition#internal-move

• Writing as an Engineering Skill — What Design Docs, Postmortems, and Review Comments Actually Do

  Everyone says writing matters for engineers, and the reason usually collapses into a story about promotion. This piece runs the order differently. Writing is first a device for verifying your own thinking, then a tool fo

  2026-08-15 · 6 min read #career#skills#technical-writing#design-doc#postmortem

• Designing Verification — Tests as Grounds for Trust, Not Pass or Fail

  A green build tells you nothing on its own. Green acquires meaning only once it is settled what you no longer have to worry about. This piece covers treating tests as grounds for trust rather than as a pass-fail gate: at

  2026-08-15 · 6 min read #career#skills#testing#verification#craft

• A Sense for Production — What Looks Different After You Have Been Through an Outage

  Two people read the same design doc and one of them reads something else entirely: what logs exist when this breaks at three in the morning, how many minutes a rollback takes, and what happens to the data that already la

  2026-08-15 · 7 min read #career#skills#sre#production#reliability

• What Stays Expensive — Four Things That Gain Value When Generation Gets Cheap

  Answer the question "what should engineers prepare for" with a list of tools and the answer is stale in two years. This piece proposes a different axis: the skills that hold value are the ones that stay expensive to veri

  2026-08-15 · 6 min read #career#skills#ai#craft#engineering-culture

• Why Debugging Resists Replacement — The Craft of Elimination

  Debugging runs in the opposite direction from writing code. Writing produces one possible thing; debugging erases possible causes until one is left. This piece covers why debugging sits on the expensive-to-verify side, h

  2026-08-15 · 6 min read #career#skills#debugging#craft#troubleshooting

• Reading What Others Wrote — Entering a Codebase and Reverse-Engineering an Undocumented System

  Writing gets practiced under compulsion; reading does not. That asymmetry made reading the skill everyone performs daily and nobody trains, and now that generation is cheap it is the capability whose price rose fastest.

  2026-08-15 · 6 min read #career#skills#code-reading#craft#legacy-code

• Evidence From Outside the Company — What Works as a Portfolio and What Just Eats Time

  The weakness of work done inside a company is that it cannot be verified. It is private, it belongs to a team, and in the end it reaches people only through your own account of it. Work done outside is confirmed with a l

  2026-08-15 · 6 min read #career#side-project#portfolio#open-source#writing

• Why Domain Knowledge Is a Defensible Line — The Engineer Who Knows the Business

  Domain knowledge is not in the code and usually not in the docs; it lives in people and in organizational habit. That makes it the single largest contributor to the verification cost this series has been tracking, and th

  2026-08-15 · 7 min read #career#skills#domain-knowledge#ddd#ontology

• The Manager Track and the IC Track — What Is Reversible and What Actually Grows

  Because becoming a manager is habitually called a promotion, the two paths look like the top and bottom of one ladder. What actually differs is the kind of job, and whether an organization treats the two as equals varies

  2026-08-15 · 6 min read #career#management#individual-contributor#career-strategy#decision-making

• Being Visible Inside the Organization — Work Does Not Announce Itself

  There is almost always a gap between the work you did and the work that is known. That gap is not a problem of modesty but of how information travels inside an organization. This post explains why good work does not anno

  2026-08-15 · 6 min read #career#visibility#communication#one-on-one#growth