A public account focused on workplace, career growth, team management, and self-improvement. The author is the writer of books including 'SpringBoot Technology Insider' and 'Drools 8 Rule Engine: Core Technology and Practice'.
This guide explains how to dramatically speed up Docker image builds by applying Dockerfile best practices, enabling BuildKit, using the Buildx plugin, leveraging remote cache storage, and employing the new --link option for adding files, all achievable within a few minutes.
This article explains the Chain of Responsibility design pattern, shows how to apply it to multi‑step product creation validation and expense‑approval workflows, walks through abstract and concrete handler implementations, dynamic configuration, and client execution with full Java code examples.
This article explains the concepts of APIs and endpoints, clarifies how they relate, highlights their differences, and provides practical examples to help developers correctly design and use API endpoints in web services.
This article compares Java classes with Go structs, covering how each language handles state and behavior, inheritance versus composition, and visibility rules, while providing concrete code examples to illustrate the practical differences for developers.
This article presents fourteen practical guidelines for designing Go interfaces, covering small interfaces, avoiding type switches, using interfaces for mocking, composition, proper abstraction levels, avoiding empty interfaces, cautious type assertions, full implementation, behavior declaration, and other pitfalls to write robust backend code.
This article distills 22 universal software‑engineering habits—from obsessing over code details to proper logging and error handling—that help Go developers write maintainable, high‑quality backend systems and foster effective teamwork.
The article examines the long‑standing debate between tabs and spaces for code indentation, citing a massive GitHub analysis that shows spaces dominate most languages while Go uniquely enforces tabs, and explains the technical, historical, and practical reasons behind these preferences and how IDEs can enforce consistent styles.
The author reflects on how studying several programming languages—Java, Go, and Python—mirrors learning foreign tongues, revealing that cross‑language comparison sharpens understanding of data structures, HTTP fundamentals, and framework implementations, ultimately deepening overall software development expertise.
The article recounts a Go project's evolution of configuration handling—from hard‑coded DB credentials to a unified global struct and finally an init‑based implicit loader—highlighting how each teammate’s approach reflects distinct mindsets, knowledge gaps, and productivity trade‑offs, and invites readers to consider their own collaboration preferences.
Drawing from personal experience and interview insights, the article outlines five practical methods—practice, systematic study, AI‑assisted communication, teaching, and leveraging others' time—to efficiently learn Golang and sustain continuous learning ability in a fast‑changing tech market.
