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 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.
The article explains that Spring's @Transactional annotation does not affect private methods because transactions are applied via proxy objects, but using AspectJ weaving or programmatic TransactionTemplate can overcome this limitation and ensure proper transaction handling.
The article argues that local caches add significant consistency and management complexity, so they should be avoided unless a genuine performance bottleneck exists, illustrating the point with real‑world promotion spikes, GC concerns, and careful off‑heap testing.
Using clear prefixes like is, has, can, and should for boolean variables improves code readability, while pitfalls such as mixed prefixes, negative naming, vague names like flag, and boolean traps in method parameters can cause confusion; the article offers concrete examples and practical refactoring strategies.
The article outlines a practical framework for managers to balance delegation and oversight by confirming direction up front, monitoring risks during execution, and avoiding micromanagement, while adapting communication frequency to project urgency and team maturity.
A sudden surge in traffic caused a signature interceptor's synchronous database insert to consume all HikariCP connections, crashing core services, and the author resolved it by converting the operation to asynchronous execution while outlining more robust long‑term solutions.
The article argues that seasoned developers improve system architecture by removing unnecessary components—such as redundant Redis caches or message queues—rather than continuously adding new ones, because each addition raises complexity and maintenance overhead, while simpler designs are easier to manage and evolve.
The article argues that excellent software design requires anticipating non‑functional issues—such as sudden database load, traffic spikes, or third‑party timeouts—by implementing retries, degradation, monitoring, and boundary checks early in the design phase, and by isolating core modules, exemplified by a micro‑service per payment channel architecture.
The article reflects on a former YouTube engineer’s decision to quit, arguing that internal promotion ladders are poor measures of personal value and urging engineers to focus on real impact, problem‑solving, and leadership rather than titles.
The article shows that Scala’s built‑in object keyword lets you create a singleton with a single line, contrasts this with Java’s multi‑line implementation, explains why design patterns exist, and discusses when and how to use them responsibly.
