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 why a large product cache moved from an in‑heap Caffeine cache to an off‑heap OHC solution, detailing serialization trade‑offs, per‑dimension cache configuration, singleflight loading, and the performance gains observed during high‑traffic promotions.
The article explains how candidates should showcase only the most relevant, deeply‑involved projects—detailing background, role, challenges, solutions, and impact—to demonstrate technical depth and decision‑making ability during a Java interview, while avoiding superficial or overly lengthy descriptions.
The article walks through the JVM’s internal steps that turn a simple `new User()` statement into a fully formed Java object, detailing memory allocation, the object header’s type pointer, the Klass structure, and why methods are stored at the class level rather than in each instance.
The author argues that genuine reflection goes beyond simple post‑mortems, requiring a deep examination of one’s thinking model and the creation of new action rules, illustrated by a personal case where re‑thinking task‑assignment shifted focus from short‑term efficiency to long‑term team capability.
The article argues that mastering Spec‑Driven Development, especially when collaborating with AI, solves most programming problems, improves code‑generation accuracy, and makes the overall development workflow smoother than chasing countless AI‑generated code tweaks.
The author explains that a performance “A” is awarded only when an engineer exceeds expectations, illustrating this with two projects—a store scheduling system and a semi‑finished product dashboard—showing how independent handling of large‑scale work reduces management overhead and builds trust.
A July 13 incident revealed that sharing a single thread pool across order, refund, and status sync services caused queue saturation, task rejection, and data loss, prompting a four‑layer defense—pool isolation, CallerRunsPolicy with structured alerts, minute‑level DingTalk notifications, and a compensation tool—to ensure reliability and quick recovery.
The author recounts spending over two years trying to mentor a struggling developer, explains why endless training hurts the whole team, and concludes that while nurturing talent is essential, it must be bounded by a clear deadline.
The author argues that in clear business code, comments should cover both the overall process (what) and the rationale behind decisions (why), using concise flow annotations and explanatory notes to reduce reading cost while avoiding excessive commentary on already‑self‑explanatory code.
The author argues that the most critical skill for senior developers is the ability to independently design and deliver large, complex systems, emphasizing thoughtful architecture decisions, trade‑off analysis, and proactive problem‑solving throughout a project's lifecycle.
