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 explains that when core business modules are properly monitored with structured logs and dedicated alert groups, a flood of non‑critical alerts can be ignored, shares a lightweight Java StructuredLog utility, and outlines best practices for real‑time monitoring and log standardization.
This article walks through a production‑grade WeChat Pay V2 integration, detailing the multi‑layer architecture, required configuration, unified order parameters, thread‑safe service usage, signature generation, and a four‑step callback verification process—including signature check, idempotency, amount validation, and active order query—to ensure reliable payment confirmation.
The article argues that beginners should first grasp the three fundamental stages of Java program execution—compilation, dependency resolution, and runtime—by manually using javac and java, because understanding these processes reveals what an IDE automates, prevents hidden pitfalls, and ultimately empowers confident IDE use.
The author argues that, in most cases, a software architect must possess solid coding abilities because architecture decisions are validated through implementation, and without hands‑on coding the design often fails to meet real‑world constraints.
The article analyzes the requirements of a massive‑scale like feature, compares small‑scale MySQL implementations with the graph‑plus‑KV architectures used by ByteDance, Kuaishou and Xiaohongshu, and presents a practical hybrid solution based on Redis, MySQL and batch processing to handle hot content and super‑node challenges.
The article argues that as AI takes over most business code, hiring will shift from pure coding tests to evaluating system‑design skills and the ability to collaborate with AI, emphasizing decision‑making over rote implementation.
The article defines a clear rule for placing methods in DDD aggregates: a method belongs inside the domain object only when it can operate solely on data owned by that object, illustrated with order status and marketing activity examples.
The author releases the complete, production‑ready source code for four enterprise‑level projects—a flash‑sale service handling 60 million members, a high‑concurrency product system for hundreds of millions of users, a payment platform serving over a hundred million users, and a three‑year DDD migration case study—while the fifth column remains under development.
The article argues that using full‑pinyin identifiers for Chinese platform names and domain concepts improves code readability, searchability, and consistency, especially when no standard English term exists, and it illustrates the point with concrete naming examples and snippets.
The author argues that in real‑world software development the two paramount principles are system stability—ensured through architecture, degradation, alerts, testing, etc.—and code clarity, achieved via encapsulation, composition, separation of concerns, and controlled complexity, because they keep IT teams alive and code maintainable.
