Knowledge Planet: Old Dock's Tech Chronicles Zhihu: SamDeepThinking A technical manager who still codes heavily on the front line. From junior developer to tech lead, then tech manager, now leading the whole front‑ and back‑end development team—leveling up along the way. I have some insights on programming, career development, and tech management.
The article explains that effective management creates value beyond coding, illustrating with a tech director who, despite outdated technical knowledge, succeeds by delegating authority, securing resources, resolving conflicts, and taking responsibility, and outlines four criteria to assess a manager’s worth.
Over two years I promoted a junior developer to mid‑level, raised his salary, and increased his bonus after he consistently delivered clean DDD‑styled code, handled simple tasks flawlessly, proactively addressed third‑party integration challenges, and demonstrated the ability to take on greater responsibility, illustrating the true criteria leaders use for advancement.
The article explains why the guideline “favor composition over inheritance” is useful but not absolute, illustrates a fixed‑workflow scenario where inheritance simplifies implementation, and provides concrete code examples and decision criteria for choosing between the two approaches.
The article uses an iPhone design blueprint versus the actual phone to clarify that a Java class defines the shared structure and behavior, while each object is an independent instance that holds its own state and operates at runtime.
The article argues that early extensibility design should be driven by concrete industry certainty—such as established multi-system integration patterns, clear product roadmaps, or repeated historical changes—rather than speculative future needs, illustrating the approach with chain-store integrations, payment channels, and marketing rules.
The article explains how a Redis‑backed Bloom filter can deduplicate activity pop‑ups for 30 million users using only 35 MB of memory, compares alternative approaches, and details the underlying bit‑array and hash‑function mechanics, false‑positive rate, parameter sizing, expiration, and practical library choices.
A manager explains the performance review process, why results are rarely changed after publication, how adjustments are made with the CTO, and offers concrete advice on asking the right questions, setting specific goals, and maintaining continuous feedback throughout the year.
The article argues that employee loyalty stems not from devotion to a company but from the comprehensive cost‑performance of their current role—salary, workload, growth, leadership, and work‑life balance—so when this overall value remains high, people rarely switch jobs.
The article walks through several code‑review approaches I’ve experienced, detailing a rigorous merge‑request workflow with mandatory comment resolution, alternative informal methods, and practical advice on aligning technical proposals and focusing reviews on core modules.
The article argues that true object‑oriented design is about controlling software dependencies, tracing its historical roots from Simula to Smalltalk and C++, illustrating how polymorphism, composition, and proper dependency inversion solve real‑world problems while warning against over‑engineered OO patterns.
