Shulou(Shulou.com)06/03 Report--

This article will explain in detail what the new ideas about software development are, and the content of the article is of high quality, so the editor will share it for you as a reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

Whether a person's intelligence is superior or not depends on whether he can hold two opposite ideas in his mind at the same time without hindering his conduct in the world.

A point of view that was previously doubted but is now shared.

When you need to work with developers with different experiences, it is more appropriate to use strongly typed languages.

Standing meetings (a form of morning meetings) are useful for helping newcomers

The retrospective session (the meeting used in the scrum development model to summarize the gains and losses of the previous iteration) is meaningful because it can help us correct mistakes in the development process; it is not a redundant meeting in agile development in which scrum master came up with a waste of time.

Software architecture is important. A good abstraction with a bad implementation does not have much impact on the code; but an incorrect abstraction and hierarchical omission can easily cause the code to rot.

Java is not rubbish.

Opportunistic and obscene code is not good code; readability of the code is the most important.

Don't blindly believe in programming paradigms. Bad code can be written in any programming paradigm.

The so-called "best practices" are specific scenarios, not a panacea. If you blindly pursue "best practices", you are likely to become the best fool.

Qualified engineers will not take the initiative to design a scalable system if it is not necessary.

Static analysis of code is useful. (for example, lint, but wrestling with specific rules, see the first article of "always agree with" below)

DRY (Don't Repeat yourself) is only used to avoid a particular class of problems, not a goal.

In general, relational databases (RDBMS) are better than non-relational databases (NoSQL).

Functional programming is just a tool, not a panacea

Newly learned ideas

The principles to be followed when programming should be in the following order: YAGNI, SOLID, DRY.

YAGNI:You aren't gonna need it, don't write features you don't need at the moment. Most predictions for the future are useless.

SOLID: five principles in object-oriented design:

Single-responsibility principle single responsibility principle

Open-closed principle modifies the closed principle for extended open pair, which is also referred to as the open-closed principle.

Liskov substitution principle Lee's substitution principle

Interface segregation principle interface isolation principle

Dependency inversion principle depends on the flip principle

DRY:Don't repeat yourself, do it only once.

If you know all three acronyms, you can try to compete with this point of view with your own ideas. if you don't understand all these nouns, it's best to learn in an empty cup mentality.

Pen and paper are still the best programming tools, but they are still not widely used

It is usually a good idea to make a compromise between purism and pragmatism

Adding more technology stacks is not a good idea.

Communicating directly with users tends to take less time and understand the problem more accurately.

The word "extensibility" is a mysterious superstition in the minds of programmers; the mere mention of the word drives them into a state of madness; it seems reasonable to do anything cruel.

Although they wear the high hat of "engineer", most of them decide to blindly use the existing technical framework or programming model without doing any technical analysis or research.

90% or even 93% of project managers are dispensable in the project; even if they suddenly disappear tomorrow, they will not have any negative impact on the project and may even improve efficiency.

After more than 100 interviews, I found that the interview was completely useless, but I didn't know how to do it better.

A point of view that has always been shared

People who struggle with code style, lint rules and other trifles are crazy.

There is no relationship between code coverage and code quality

Single warehouses are better in most cases.

TDD purists are the worst. There is no room for other existing ways of working in their fragile little heads.

What are the new ideas about software development to share here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.