Taogen's Blog

Organize Docker compose.yaml examples here.

Organize Dockerfile examples here.

In this post, I will cover the technologies that should be used in new software projects in 2025.

Creating a Dockerfile is a critical part of building container images. Following best practices not only leads to optimized images but also enhances security and maintainability. The following are some best practices to consider when writing your Dockerfile.

In this post, I will cover Docker’s common use based on my experience.

Naming Conventions

File Names

Component files: Use CamelCase. E.g. MyComponent.js

Non-component files (like helpers, hooks, or utilities): Use kebab-case or camelCase. E.g. useCustomHook.js or myUtility.js.

Custom hooks files: with a use prefix. E.g. useFetch.js, useForm.js.

Directory Names

Use kebab-case for folder names. E.g. my-folder, components, utils.

Test folder name: __tests__

Often there is a lot of trivial code in open-source projects that we don’t need to read. To read a Java open-source project, the most important thing is to understand the core functionalities of the project.

In the post, I will cover common tools for reading source code.

In the post, I will cover the best practices in programming. It will be continuously updated.

Before exploring how to improve programming efficiency, we need to know the process of developing a software project.

1. Requirement analysis
2. System overall design and detailed design
3. Source code implementation
4. Testing and fixing bugs
5. Deployment
6. System iteration and improvement.