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 argues that persuasion is unnecessary for leaders, who should make final decisions, and for non‑leaders the proper approach is to clearly present ideas to the leader for decision‑making, illustrated with a microservice request case.
A concise 1‑2 minute self‑introduction should distill your resume into clear highlights, stay authentic, follow a past‑turning‑point‑present structure, and use natural speech to turn your background into a compelling narrative that interviewers can quickly grasp.
The author explains how interviewers can uncover a candidate's strengths by asking about their toughest technical challenges and detailed problem‑solving experiences when a résumé shows no obvious highlights, and why this reveals genuine interest and expertise.
The article analyzes the write bottleneck of processing 30,000 payment orders per second on an Oracle‑Java‑Spring stack, explains why sharding was used historically, why MQ‑based peak‑shaving is discouraged, and compares self‑built sharding with modern distributed databases such as PolarDB‑X, TiDB and OceanBase, while summarizing public practices from major Chinese tech firms.
The article defines a true team as a group sharing a common goal and seamless collaboration, argues that a capable leader with frontline expertise is essential, outlines how to structure teams with core members and supporters, and provides practical guidelines for goal alignment, talent development, and continuous improvement.
The article argues that code cleanliness—careful naming, clear responsibilities, consistent abstraction levels, and purposeful design patterns—boosts maintainability and delivery efficiency, while warning against over‑formatting, premature abstraction, and needless refactoring of legacy code.
The article argues that most so‑called product managers are merely product assistants, outlines the true responsibilities of a genuine PM, and lists essential traits such as logical thinking, clear planning, and rigorous PRDs to avoid resource waste and low delivery efficiency.
This article reviews the end‑to‑end design of a payment platform that handles 500,000 daily orders, detailing the three‑layer gateway‑orchestration‑base architecture, independent channel services, reconciliation mechanisms, and how business constraints drive each architectural decision.
When a carrier recycles a phone number and assigns it to a new user, the system must detect the conflict, present the previous account’s masked details, and let the new user choose either to inherit the old account’s data or create a fresh account, while preserving audit trails.
During the COVID‑19 lockdown, the CTO demanded that the new sub‑brand’s online systems be completed in three weeks; the author describes asking the boss’s priority, copying the main brand’s code, setting strict weekly milestones, intensive testing, remote coordination, and ultimately delivering on time.
