This guide explains Git branch naming conventions, their correspondence to development environments, recommended merge workflows, standardized commit message formats—including Angular guidelines and a simplified version—and provides a practical .gitignore template, helping teams maintain stable codebases and efficient collaboration.
This article explains the widely used Git commit message convention, detailing the subject prefixes such as feat, fix, docs, and others, their meanings, example usages, and the benefits of adopting a standardized format for clearer project history and automation.
Git Submodules let developers embed external Git repositories within a main project, enabling precise version locking, independent histories, and reusable code, while requiring specific commands for adding, initializing, updating, and managing submodule references, and presenting trade‑offs such as operational complexity and limited automation compared to modern package managers.
This article introduces five powerful Git commands—stash, reset --soft, cherry-pick, revert, and reflog—explaining their basic usage and advanced tricks, enabling developers to manage temporary changes, roll back commits, copy changes across branches, undo mistakes, and recover lost history efficiently.
A senior developer recounts how a Fortune‑500 project's ill‑planned outsourcing to a vendor using a massive MongoDB JSON store led to performance bottlenecks, hidden limits, and a frantic internal rewrite that forced the team to work through holidays and ultimately deliver a successful release.
This article, a follow‑up to “How to Become a Reliable Programmer,” offers practical guidance on effective communication, meeting organization, handling external dependencies, responding to emergencies, managing large volumes of messages, and fostering independent, critical, and systemic thinking for software engineers.
The article systematically distinguishes unrecoverable errors from recoverable exceptions and surveys five major handling strategies—global error codes, return‑value conventions, parameter‑based collectors, language‑level exception mechanisms, and OS‑level support—concluding that the optimal approach depends on performance constraints, code‑base design, and portability requirements.
Microsoft’s VS Code Python extension has ended official support for Python 3.7 and will progressively drop support for older 3.x releases, citing security, library compatibility, and the language’s new annual release cycle, while Python’s popularity continues to surge worldwide.
This guide explains Git branch naming conventions, maps branches to development environments, outlines a standard merge workflow, details commit message standards—including Angular guidelines and a simplified format—and provides a sample .gitignore, offering practical tips for clean, maintainable code management.
The article explains how Python now exists as both a typed and an untyped language, distinguishes infrastructure code from business‑logic code, and argues that embracing both styles—using type hints for business logic while keeping infrastructure flexible—strengthens developers and improves software quality.
The article explores how daily stand‑up meetings, a staple of agile software development, can become truly effective by addressing subtle details, common pitfalls, participant roles, timing, structure, and facilitation techniques that keep meetings short, focused, and valuable for the whole team.
This article explains why clear, standardized Git commit messages are essential, outlines a practical commit format with required types, optional scopes, and concise subjects, and describes a webhook‑based monitoring service that enforces the rules, improves traceability, and enables automated changelog generation.
Linux developers, led by Linus Torvalds, have approved a proposal to replace racially sensitive terms like master/slave and blacklist/whitelist with neutral alternatives, reflecting a broader industry move toward inclusive language in code and documentation.
A vivid story of a product manager and an app developer at China Ping An who physically fought over a request to change the app's theme color based on phone case color, followed by practical advice on handling unreasonable product demands and improving cross‑team communication.
This article explains how to solidify your Java fundamentals by thoroughly understanding the JDK’s three main components—JVM, core libraries, and development tools—and provides a practical classification of packages into four learning levels to guide efficient study.
This article explains how Java exceptions provide a consistent mechanism for identifying and responding to errors, and outlines three key principles—specificity, early throwing, and delayed catching—illustrated with a fictional JCheckbook class to demonstrate robust, user‑friendly debugging practices.
This article shares actionable advice from a former product manager and engineer on how product managers and developers can prevent conflicts, improve communication, and collaborate effectively through better requirement handling, realistic planning, and clear, data‑driven explanations.
The article presents a StackOverflow‑curated list of 29 non‑programming books—ranging from classics like The Hitchhiker’s Guide to the Galaxy and 1984 to titles on design, productivity, and human factors—ranked by recommendation count to help developers broaden thinking, communication, and professional growth.
