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 breaks down a three‑round technical interview, explaining how senior developers test core skills, team leads assess collaboration and career fit, and CTOs evaluate industry experience and the candidate’s potential to add incremental value to the team.
The article explains that interviewers ask high‑concurrency questions not because the company’s workload is heavy, but to test candidates’ understanding of concurrency concepts, distinguish skill levels, and assess their ability to handle even low‑traffic scenarios that still involve concurrent operations.
The article recounts a painful e‑commerce architecture decision where marketing rules were hard‑coded into the order creation flow, causing bloated code, frequent releases, testing overload, and fault propagation, and then explains how introducing a dedicated settlement service restores clean separation and stability.
The author explains that when a senior technical expert challenges authority, managers should adopt a service mindset, respect and empower the expert, let him focus on AI Agent projects, and leverage his output as key reporting material to drive organizational AI adoption.
Drawing on nine years of team‑leadership experience, the author explains why big firms like Alibaba, Tencent and JD, as well as many smaller companies, routinely conduct background checks and urges candidates to be truthful on their resumes, especially for management roles.
An UPDATE in MySQL 8.0 acquires three distinct locks—a server‑level metadata lock, an InnoDB intention exclusive lock (IX), and a row‑level exclusive lock—so understanding the three‑layer lock architecture (metadata, intention, row) helps both interview preparation and troubleshooting.
The article explains Java SPI’s purpose, how the thread context class loader overcomes parent‑delegation limits, and compares the standard JDK SPI with the extended mechanisms used by Kafka Connect, Elasticsearch, Dubbo, and Spring Boot, providing interview‑ready insights and concrete code examples.
The author argues that in most companies you only need to write simple, single‑table or limited‑join queries and focus on index tuning and basic MySQL concepts such as InnoDB, locks, and execution flow, while complex SQL work often signals a poorly organized team.
The article explains that CompletableFuture always uses ForkJoinPool.commonPool by default, compares their suitability for CPU‑bound and I/O‑bound tasks, reveals risks of using the common pool under load, and provides concrete configuration patterns and benchmark results for safely isolating thread pools in production.
The article argues that rapid programmer growth comes from tackling challenging, end‑to‑end tasks—handling requirement analysis, design, implementation, and deployment—while actively seeking feedback from more experienced colleagues, rather than merely logging overtime or completing repetitive simple tickets.
