Essence of Programming

ProgramWhat is the final composition of every day's busy program written by members? --Data andAlgorithm
.

Do you think so?

 

So is data/structure important? Or is "algorithm" more important?

Think about why we need to write programs?-- Process data
.

No, whether it's storage and reading, sending and receiving, listening and subscribing, the server and the client, we are turning over and playing with a bunch of "Numbers ".

Therefore, we can imagine that if the program is built on a poor data model, the cost of improvement will be far greater than the cost of building on a poor algorithm.

Data Modeling is the first step to build a good system. Just like building a high-rise building, a good foundation is the most important, and excellent algorithms are like gorgeous decoration. They can be seen as the icing on the cake, although this is essential in many cases ......

 

What are the difficulties in programming? Or how can we play "data" to the extreme? --Multithreading and memory
.

There is no end to the research and improvement of these two algorithms! Because they determine the security, robustness, and efficiency of the system.

Multithreading and memory algorithms have always been the topic discussed by experts, the difficulties in the interview, and the traps in their work. Think about it: high performance and high load of JVM cache ...... Both are closely related to the two.

 

An example of an improvement program:

Gaven King writes hiberate because it gets tired of converting between RD (Relational Data Model) and OOP (Object-Oriented Programming). Through JDBC + metadata, You can have full control over the object data model, so why not add a more tool layer to achieve this softening.