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 author argues that well‑written, regularly maintained code comments explain design decisions, make future modifications safer, and therefore serve as an effective tool for lowering technical debt, despite common claims that clean code alone eliminates the need for comments.
The article explains how every line of code adds constraints and maintenance cost, turning code into technical debt, examines why developers often avoid repaying it, and offers practical strategies such as writing less, reusing existing components, and regularly removing dead code to keep debt under control.
The article explains RocketMQ's two‑layer locking mechanism that guarantees ordered consumption by holding a queue‑level lock inside a while loop, clarifies why autoCommit only affects offset reporting, and shows how the client correctly processes multiple messages in a single thread.
The article explains how RocketMQ’s transactional message mechanism guarantees consistency between order creation and inventory deduction by using half‑messages, a local transaction callback, a second‑phase confirmation, and broker‑side timeout checks, while highlighting common pitfalls and best‑practice recommendations.
The article explains that merely placing data on multiple machines constitutes sharding—a way to split data for capacity—but true distributed systems require coordinated nodes that communicate, replicate, and handle failures, illustrated with an e‑commerce warehouse analogy and guidance on choosing between sharding and distributed databases.
The article argues that agile is a set of guiding principles—early delivery, rapid feedback, and adaptation—rather than a rigid set of practices like Scrum or Kanban, and advises teams to tailor processes to their context instead of blindly following a prescribed workflow.
The article explains how architects who stop writing or reading code lose essential insight into the system, leading them to suggest impractical solutions like a non‑existent message center, and offers concrete practices to stay connected with the codebase.
The author explains how a three‑year partnership with the CTO created a tech team that follows a clear rhythm, focuses on delivering quarterly and monthly commitments, values execution over endless tasks, and demonstrates that true programmer productivity comes from effectiveness, not constant busyness.
The article argues that truly good code is measured by how rarely developers need to revisit and modify it, emphasizing design and programming techniques that make systems resilient to exceptions and adaptable to business changes without frequent code changes.
The article examines the trade‑offs between REST + JSON and gRPC for microservice communication, outlining REST’s simplicity and maturity versus gRPC’s binary efficiency, strong contracts, and streaming support, and provides a four‑point decision framework to help teams choose the right protocol for internal or external APIs.
