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 demonstrates how encapsulating each step of an order‑submission process into well‑named methods makes the core business flow instantly visible, lowers modification errors, and illustrates a coding habit of keeping all methods at the same abstraction level.
The author reflects on the rarity of encountering a truly skilled programmer and explains how such a colleague’s disciplined habits, thoughtful design choices, and thorough exception handling can dramatically improve code quality and accelerate a developer’s professional growth.
The article shows how a Java 14 switch expression combined with a BiFunction and method references can replace duplicated if‑else branches in inventory‑change code, reducing maintenance effort and lowering the risk of missed updates when new types are added.
When a manager constantly piles work onto you, you can regain control by building an Excel task queue, delivering each task without leftovers, and evaluating each assignment from a growth perspective, ensuring quality, clarity, and career development.
A newly appointed leader identifies the symptoms of a fragmented software team, wins a few hard‑fought projects, restructures the core system, rewards key contributors, and adopts a front‑line leadership style to restore morale and deliver results.
The article reflects on the author’s admiration for business architects in a large tech firm, detailing their role in creating price and comparison systems, bridging departments, and designing flexible data schemas, and argues that deep business knowledge combined with technical skill yields greater impact.
The article explains that MVCC in MySQL InnoDB prevents phantom reads for snapshot (ordinary SELECT) queries by using ReadView, while write‑conflict scenarios that appear as phantom reads are handled by unique index checks and gap locks, highlighting the distinction between snapshot and current reads.
The article explains why engineers usually trade memory for faster response, illustrates the choice with caching and batch‑processing examples, and provides a decision framework based on IO bottlenecks, access frequency, data volatility and resource costs.
The article analyzes why a programmer’s ability to stay employed until fifty depends more on deep industry experience, cross‑functional capabilities, solid technical depth, continual adaptation to new tools, and organizational awareness than on any specific programming language or framework.
The article examines the deep uncertainties, heavy psychological pressure, and non‑linear outcomes that make programmers reluctant to become managers, illustrating the challenges with real‑world examples, performance‑grade authority, mental‑health data, and the amplified expectations from senior leadership.
