Building a Return-to-China Proxy from Scratch: VLESS + Reality Pitfall Notes
From a temporary SSH direct connection, to accommodating phones and family, and finally converging on sing-box as a maintainable return-to-China network setup.
Tags
#Technology
Writing, research, projects, and photos around “Technology”.
Defining the Boundaries Before Bringing AI Capability into an Engineering Organization
A position paper based on the author's experience driving AI infrastructure and pilots in a real engineering organization: it proposes four kinds of boundaries—context, responsibility, authorization, and measurement—and offers a falsifiable pilot protocol plus a minimal harness as a demonstration of putting them into practice.
Read summaryData Measurement as Organizational Protocol: Definitions, Measurement, Tiering, and Retrospectives
A research-design and protocol paper: reframing data measurement from what belongs on the dashboard into a recomputable, reviewable, decision-supporting collaboration protocol, with minimal mechanisms for definitions, measurement units, metric tiering, dictionaries, and retrospectives.
Read summaryDeveloper Productivity Is Not a Tool Catalog, but a Feedback System
A research synthesis and position paper: defining engineering productivity as a continuously shortening "propose change — get trustworthy feedback — correct safely" loop, with metrics, a default path, and a falsifiable pilot protocol.
Read summaryFrom Prompt to Narrative Production: CanonLoom 0.2.0's Auditable Human-AI Collaboration Architecture for Long-Form Fiction
A system design paper: modeling long-form fiction collaboration as recoverable, auditable, author-approved state transitions, and proposing an evaluation scheme that does not mistake mechanical scores for literary value.
Read summaryTechnical Planning Is Fundamentally Business Analysis and Competitive Analysis
Technical planning is not a project list. At its core it is two things: understanding the business you serve (business analysis) and understanding the gap and level against competitors (competitive analysis), then linking them into a causal chain of goals, trade-offs, and execution.
Part of the column “Technical Systems” · Chapter 1
Shared Core and Local Variation: How Multi-Region Systems Evolve
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.
Part of the column “Technical Systems” · Chapter 4
Quality Is Not One Team's Job: Shared Accountability for the Outcome
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.
How Engineering Standards Reduce Rework Without Creating Bureaucracy
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.
Part of the column “Technical Systems” · Chapter 3
Why Code Decays: From Local Convenience to Systemic Debt
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.
Part of the column “Technical Systems” · Chapter 2
Data Measurement Guide (Part 5): Periodic Statistics and Retrospectives, Turning Numbers into the Next Action
From daily and weekly reports to problem retrospectives: how to maintain baselines, record changes, judge impact, and turn data conclusions into verifiable action items.
Part of the column “Data Metrics Guide” · Chapter 5
Data Measurement Guide (Part 2): Define What You're Measuring Before Arguing About Metrics
A publicly reusable metric dictionary: from requests and users to tasks, explaining how availability, error, latency, performance, and feedback data should be defined, combined, and interpreted.
Part of the column “Data Metrics Guide” · Chapter 2
Data Measurement Guide (Part 1): Data Definitions Are the Interface of Collaboration
Metrics are not numbers on a report; they are the shared language a team uses to describe the same thing. Only after defining the object, event, denominator, and time can data participate in decisions.
Part of the column “Data Metrics Guide” · Chapter 1
What a Reusable Engineering Retrospective Should Leave Behind
The value of an engineering retrospective is not in retelling what happened or blaming individuals, but in turning an experience into improvements that can be verified, maintained, and reused.
Technical Sharing Is Not an Event, but a Method of Knowledge Collaboration
Turn technical sharing from a regular talk into a knowledge-collaboration system that connects topic selection, research, discussion, and consolidation.
Why Technical Knowledge Bases Need Entry Pages
An entry page is not a pile of links, but the shared memory a constantly changing project leaves for its team: it helps readers enter by task, judge whether information is still valid, and find the people responsible for maintaining it.
Part of the column “Documentation & Knowledge” · Chapter 2
First Ride into Frontend: The Kindergarten Bus
An old signpost written for frontend beginners: information gathering, study logs, algorithm practice, interviews, and internships are all just the beginning.
Interview Questions and an Engineer's Growth Path
An index of interview and engineering fundamentals compiled after the spring 2018 job search; keeping it as a reminder that interview questions are never just interview questions.