Parody: 7 Habits of Highly Effective Software Engineers

There is an article "7 Habits of Highly Effective Software Engineers" https://www.oschina.net/news/259604/7-habits-of-highly-effective-software-engineers

1. Quickly prototype ideas and conduct proof-of-concept
   . Clue: It’s too time-consuming. For an iteration of 2 weeks, there is no time for prototypes at all. If the prototype fails, the gain outweighs the gain. Projects built quickly are unlikely to fail, or the more failure and chaos they have, the better for you
2. Effectively evaluate the workload.
   Copycat: The workload evaluation depends on the scenario. If you are fighting for a new project, of course the evaluation will be shorter than others. In this way, you can be responsible for the project. If it is an old project maintenance and handover project, of course you must evaluate it from a pessimistic point of view. You do yourself no favors by accurately assessing. Instead of taking too long to evaluate, which will definitely lead to inaccuracy, it is better to evaluate according to your own needs.
3. Review code quickly and promptly
   . Copycat: People who have read this article ask themselves, have they really reviewed other people’s code? Do others really have time to review your code? Most of them don't even have Review's own code.
4. Proactively record code, design and processes to form documents.
   Cheat: a waste of time and no one will read it. It will be garbage after 3 months. Moreover, if you record it clearly, it will be easy to be replaced. I am the programmer who writes good code, writes good unit tests, and writes good documentation, and then is rushed to the next project, and the next project.
5. Participate in technical discussions candidly
   . Copycat: In conference room discussions, it is obvious that more caution is needed, and unilateral candor is unrealistic. Hold your ground instead of leaving it to others
6. Complete "shit" work.
   Parody: Work must continue and cannot be completed. Otherwise, the job will not be guaranteed, or you will have to do another shit job. Why try a new piece of shit?
7. Stay curious. Funny
   joke: Being curious at work will not make you do a better job. Polishing your current work carefully and keeping it in your hands is where your time should be spent.

About me I have been developing Java for 22 years. I have developed multiple access systems with tens of millions of minutes per minute. I have written 3 Java books and have two domestic open source books.

Fined 200 yuan and more than 1 million yuan confiscated You Yuxi: The importance of high-quality Chinese documents Musk’s hard-core migration of servers TCP congestion control saved the Internet Apache OpenOffice is a de facto “unmaintained” project Google celebrates its 25th anniversary Microsoft open source windows-drivers-rs, use Rust to develop Windows drivers Raspberry Pi 5 will be released at the end of October, priced from $60 macOS Containers: Use Docker to run macOS images on macOS IntelliJ IDEA 2023.3 EAP released

{{o.name}}

{{m.name}}