Easy Tutorial
❮ Android Tutorial Alarmmanager Android Tutorial Json ❯

Several Pieces of Advice for Programmers, with Engaging Illustrations

Category Coder Life

1. Think Clearly Before You Start Coding

Newcomers to the field, eager to demonstrate their abilities, often rush to start coding as soon as they receive the requirements—a big no-no!

In my view, the actual time spent coding is only 20%; if you don't think clearly, you'll spend the other 80% of your time fixing bugs.

2. Lack of Communication Can Lead to Headaches

Disliking speaking and communication can easily lead to misunderstandings in requirements, and you'll find out at the end that it's not what the product asked for.

Many features have to be redone due to lack of communication.

3. Documentation May Not Be Read, but It Still Needs to Be Written

The purpose of documentation is mostly not for communication but for record-keeping. Most requirements are communicated verbally, but without documentation for record-keeping, disputes can easily arise later on.

4. Always Write Comments

Not writing comments is like digging a pit for yourself and others because, over time, you may not even be able to understand your own code.

5. Don't Expect Requirements to Be Stable

Product requirements are constantly adjusted according to business needs, and changing requirements is the most normal thing. Don't complain; the only constant in this world is change.

6. Business Takes Precedence Over Technology

If technology does not serve the company's business, it will be worthless. The company making money is the ultimate truth, so I don't recommend everyone to pursue new technologies, but rather pay more attention to the application of mature technologies in commercial companies.

7. Don't Harbor Illusions

Where you vaguely feel there will be a bug, there will definitely be a bug.

8. Test Your Work Yourself First

Don't just throw your work to the testers after you finish. You should ensure the quality of what you've done.

9. Try to Solve Problems Yourself

When encountering a problem you don't understand, try your best to solve it first (Google, Stack Overflow, etc., can solve 90% of the problems). Don't just take a screenshot and ask others for help. Bosses and colleagues are not here to clean up after you, but if you really mess up, ask for help as soon as possible.

10. Use New Technologies Cautiously

Don't chase after new technologies; new technologies are all beta versions. Before the experts have written clear Chinese introductory documents, using them on your own is mostly a recipe for disaster.

>

Original link: http://www.techug.com/post/funny-programmer-pictures-2.html

❮ Android Tutorial Alarmmanager Android Tutorial Json ❯