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.
When traffic spikes, a multi‑table JOIN can hold database connections far longer than separate single‑table queries, quickly exhausting the connection pool and slowing the entire system, as demonstrated by concrete timing examples and a practical workaround.
The article explains that observability goes beyond simple monitoring by combining metrics, logs, and traces to pinpoint where and why a system issue occurs, especially in microservice and cloud‑native environments, and stresses the importance of correlating data rather than merely collecting more.
This article presents a detailed technical blueprint for building an enterprise‑grade single sign‑on system that combines Apereo CAS, OAuth2, and JWT across four microservices, covering service responsibilities, data models, API contracts, deployment trade‑offs, and operational safeguards.
The article shares three hard‑learned principles for dividing microservices—isolating core applications, avoiding delivery slowdown as teams grow, and defining service boundaries with concrete examples—illustrating why each rule matters and how it prevents outages.
The article explores a technical manager’s late‑night anxieties about losing coding ability, explains why engineering skills decay while management skills endure, and offers concrete strategies—including a two‑year trial period and a critical time window—to retain hands‑on competence and safely transition between roles.
The article reflects on a decade of programming experience, arguing that delivering customer value outweighs technical perfection, and shares practical insights on embracing uncertainty, pragmatic testing, selective use of best practices, collaboration, full‑stack knowledge, and maintaining a growth mindset amid inevitable imperfections.
The article explains that seemingly relaxed leaders have spent years paying the complexity upfront by enduring early intense workload, cultivating core talent, and establishing streamlined processes, which later frees them from daily firefighting and makes their teams operate autonomously.
The article explains that a programmer's level is determined by the complexity of problems they can solve—not by years of experience—detailing how junior, mid‑level, and senior engineers differ in responsibilities, mindset, and impact on their teams.
The article proposes a three‑step approach—study best‑practice designs, evaluate them against your specific context, and select the most suitable solution—illustrated with a comparison of using a message queue versus Spring’s event system for simple order‑notification needs.
The article explains that backend engineers often view frontend work as easy because it changes rapidly with user preferences, while backend deals with stable, long‑standing challenges like data consistency, making each side complex in fundamentally different ways.
