ANDREW / WRITING
Write down observations.
Keep the thinking going.
Engineering practice, how AI changes work, and how teams develop judgment. Short posts open questions. Longer essays develop the context.
From recurring firefighting to team decision capability.
Start with the organizational question, then examine my TL responsibilities and release decision experience. Steps two and three are sections of the same article; read in sequence or go directly to the part you need.
- Organizational perspective · DraftWhat does the organization learn from firefighting?
Look beyond workload at information, authority, and dependencies.
- Management practiceHelp TLs form a judgment and seek support early
Examine technical ownership and the boundary for management coordination.
- Decision and follow-throughAccept a feature gap to preserve shared development capacity
Examine the cost of stable, follow-up, and joint analysis across later updates.
Three questions I keep returning to.
- Management experienceFinding the Cause Is Not the EndUpdates and RMA each carry a cost. A technical answer still needs a handoff that frontline support can act on.Read the essay →
- Technical observation · DraftDoes a Firmware-Looking Problem Really Belong to Firmware?A technical judgment needs to make clear how far the available evidence supports it.Read the draft →
- AI × Capability · LinkedIn English originalBetter Output, Better Judgment?Beyond better output, I want to know whether human judgment is growing too.Read on LinkedIn ↗
Find an article
What are you looking for? Try release, responsibility, TL or AI.
Searches Chinese and English titles, summaries and keywords.
Enter a keyword or choose a filter.
No matches. Try fewer words, or browse the topics below.
Browse all articles
Jump to the full list for a topic.
Start with the problem you are facing.
Two reading paths through existing essays and the discussion worksheet. Follow the order, or choose the step you need.
When the problem is still unclear, what comes next?
- Question the apparent technical boundaryTechnical observation · Draft
Separate the symptom from assumptions about who owns it.
- Connect investigation to remedy and frontline supportManagement experience
Finding the cause still leaves choices about delivery and follow-through.
- Record the work you choose to deferDiscussion template
If investigation competes for resources, make the remaining commitments explicit.
When does a TL decide, and when is a Manager needed?
- Connect the TL’s thinking to the Manager’s supportManagement experience and principles
Explore option costs, the Manager’s timing decision and later reassessment through a version choice.
- Track the responsibility left by a priority decisionManagement scenario · Editorial draft
Explore what changes when several teams share limited resources.
- Bring the trade-off to a shared discussionDiscussion template
Identify decision authority, ownership and conditions for reconsideration.
A worksheet for your next discussion
When one piece of work must wait so another can move forward, use five questions to record the cost, remaining resources, ownership and review conditions.
Open the deferral decision worksheet →Includes an illustrative example and an editable record to copy or print. Nothing is sent or saved automatically; it supports discussion rather than choosing for you.
Articles are grouped by perspective; a piece may appear under related topics. Experience, observations, scenarios and discussion templates describe the kind of content; a draft label describes its editorial status. LinkedIn originals link to the source. Dated revision notes describe substantive additions, not the date of an incident or the original post.
Management
Priorities, decision authority and collaboration.
Technically Ready. Who Decides It Is Ready to Ship?
Evidence, decision authority and follow-through, with an internal baseline case and clearly labeled release reflections.
Technically Ready. Who Decides It Is Ready to Ship?
Connect validation evidence, remaining risk and decision authority, including who can halt, recover or change course after release.
When Managers Keep Firefighting, What Changes?
Look beyond workload to ownership, authority and dependencies: after the immediate fix, can the organization handle the next problem?
When managers keep firefighting, what does the organization learn?
Look beyond recurring escalations at information, authority, and organizational capability.
AI Made Work Faster. Who Decides Where the Saved Time Goes?
More delivery, investment in quality and capability, or higher expectations: leadership needs to choose deliberately how saved time is used.
Finding the Cause Is Not the End
Coordinate investigation, weigh the costs of an update or RMA and give the frontline team a basis for action.
Feature Progress and Shared Resources: How Does a Manager Weigh the Trade-offs?
A TL and Manager version decision weighing feature lag, cross-repository integration and maintenance costs, with conditions for reconsideration.
After Setting Priorities, What Does a Manager Still Owe the Team?
Making a trade-off also means tracking the cost of the work you defer.
Two Days of Work. Two Weeks to Move Forward. Why?
Execution and waiting are different kinds of time. Decision authority, cross-team commitments and reversibility affect when work can proceed.
Clarify Decision Authority Before Assigning Outcome Ownership
Can the person responsible for delivery also change scope, priorities and key choices?
Match Decision Speed to the Cost of Being Wrong
Reversible decisions can stay close to the work. Far-reaching choices need more context and evidence.
When Work Stalls, Understand What People Are Waiting For
Waiting may reflect missing information, authority or ownership. Identify the signal before trying to speed things up.
Organizations Need Refactoring Too: Examine Process Debt
Do approvals and meetings that once made sense still protect something important? Revisit their original purpose and ongoing cost.
After Removing a Management Layer, Who Picks Up the Work?
A flatter organization still needs coordination, coaching and trade-offs. Identify what disappeared, moved or lost a clear owner.
A Live System Is Not a Transferred Capability
Running a system is different from understanding, changing and recovering it. Distinguish intentional dependencies from unrecognized ones.
A Quieter Team: Alignment or a Lost Signal?
Less disagreement may reflect understanding or resignation. Preserve a path for dissent to influence decisions.
Repeated Escalation Is Information
After clearing a blocker, examine ownership, context and decision boundaries so similar decisions do not always return to the same manager.
What Keeps Moving When the Manager Is Away?
Unblocking work can also teach a team to escalate. Ask whether resolving the problem leaves the team more capable of acting independently.
When a Role Disappears, Where Does Its Capability Go?
Identify the context, exception handling and judgment embedded in a role before deciding whether AI or others can carry them.
Technology
Verification, code understanding and engineering delivery.
Same Code. Does Seniority Change the Judgment?
Experience can guide review, but titles may also shape evaluation. Examine the code, context and evidence behind the judgment.
Does a Firmware-Looking Problem Really Belong to Firmware?
Identity, interface observations and the limits of a single-device sample.
AI Makes Implementation Faster. Where Does the Team Get Stuck?
Identify absorption constraints, inspect the evidence and decide resource trade-offs as output grows.
From Field Signals to Engineering Delivery
How managers connect verification, responsibility and judgment.
More Output. Can the Organization Absorb It?
Distinguish execution capacity from the system’s ability to absorb it across review, testing, integration and release.
After AI Speeds Things Up, Where Is the Bottleneck?
Can review, integration and verification keep up with faster implementation?
You Generated the Code. Do You Understand It?
What assumptions and failure modes should engineers understand before asking others to review?
How Much Execution Speed Can an Engineering System Absorb?
How context, verification and responsibility keep up with faster code generation.
Cheaper Execution Makes Unclear Intent More Expensive
Code can compile and tests can pass while solving the wrong problem.
Make the Cost of Being Wrong Small Enough to Learn
Smaller steps, faster feedback, clear guardrails and easier rollback reduce the impact of mistakes.
Correct on Paper. Questionable in Use.
A parking-space observation is a reminder that requirements, implementation and real-world use need different checks.
AI
How tools change output, learning and team capability.
Same Code. Does Seniority Change the Judgment?
Experience can guide review, but titles may also shape evaluation. Examine the code, context and evidence behind the judgment.
AI Made Work Faster. Who Decides Where the Saved Time Goes?
More delivery, investment in quality and capability, or higher expectations: leadership needs to choose deliberately how saved time is used.
AI Makes Implementation Faster. Where Does the Team Get Stuck?
Identify absorption constraints, inspect the evidence and decide resource trade-offs as output grows.
Trust in AI Should Be Inspectable
Make confidence inspectable through sources, assumptions, reproducible evidence and review proportionate to risk.
When Execution Gets Cheaper, Does Senior Judgment Become Scarcer?
When more answers appear at once, which trade-offs deserve senior engineers' attention?
Where Did the Capacity Saved by AI Go?
A faster team may soon fill up with new demands. Saved time needs an explicit allocation decision.
When AI Removes Junior Work, How Does Learning Remain?
Which opportunities for investigation, feedback and responsibility need to be redesigned?
Less Repetition, Better Judgment?
How assumptions, mistakes and corrections in small tasks become engineering experience.
Better Output, Better Judgment?
AI-assisted delivery and capability development need to be observed separately.
Faster Answers from the Manager. A More Independent Team?
AI can expand a manager's responsiveness and increase upward requests. Clarify together which decisions belong with the team.
Autonomous Execution Still Needs Management Boundaries
Define access, stop conditions, escalation and recovery so human attention stays with consequential decisions.
More Capacity to Start. Who Decides What Should Stop?
As execution capacity grows, attention and priority become scarcer. Possible work still needs decisions about starting, continuing and stopping.
When Engineers Direct Agents, Their Role Changes Too
Allocation, supervision, evaluation and intervention raise new questions about skills, authority and accountability in multi-agent work.
Human in the Loop. Does Human Judgment Change the Outcome?
Place oversight where risk, ambiguity and consequence make judgment valuable. Excessive approvals can dilute attention.
SITE DESIGN / EDITORIAL DRAFTS
Notes on Building This Site
Editorial drafts on the reading experience and design choices, separate from the engineering management writing.
Clarity Is a Design Skill
How processing fluency can inform a website's reading experience.
Let the Work Speak, and Explain Its Context
How a clear identity, verifiable information and contact options support trust.
What Should a Personal Website Answer First?
Arrange the introduction, featured writing and contact options from the visitor’s perspective.
This is a themed selection of 33 original public posts by Andrew, not a complete archive or a chronological list. Titles and summaries are editorial adaptations; site essays are labeled as editorial extensions. The full LinkedIn originals remain the source of record.
Update checked: 2026-10-12. Three posts were added after full text, author, public visibility and original links were checked. The first 20 displayed activity-page posts were compared; this is not a complete archive. The firefighting LinkedIn original and its site editorial extension are labeled separately. Earlier sources retain their own check dates and methods. Publication dates were not inferred from relative timestamps, and cited research was not independently revalidated. LinkedIn may require sign-in.
View the source inventory (JSON) →Find more writing on LinkedIn ↗
Also available: pilot draft issue 001 →
Web pilot only. Subscriptions and email delivery are not available yet.
Add this link to your RSS reader. It includes site writing and tools with draft labels; it does not send email.