A really good IDE is your brain

A really good IDE is your brain
 
I have always been affected by Java development, as if I can't write code without an IDE. It is good that IDE will greatly speed up our development to a certain extent, advanced automatic completion, and various intimate small functions, so that we are more and more dependent. Various IDEs. Especially the artifact Idea developed by Java.
 
Recently, I wrote Python and a little Nodejs. It felt incredible to see foreigners as text editors, so I chose Emacs among many text editors (Emacs, Vim, Sublime). Because I found it more suitable for my taste, I found it really cool after sticking to it for a period of time, and it also changed some of my feelings about coding. It may also be because Python and nodejs are dynamic languages. When you have an idea, start Emacs quickly, speed up the startup in the way of emacs client, and you can quickly enter the working state without waiting. No matter what language Emacs has a corresponding mode, syntax highlighting, automatic indentation, quick prompts, etc. It gives me total control over the code. I find that I have better control over the code. On the surface, I type more words, but my programming feels smoother. Nothing is interrupting me, so the process is all The methods are all in my head, and I don't have to find the method I want in autocomplete over and over again.
 
Thinking about it now, the best IDE is your brain, no matter how advanced the IDE, how advanced the weapon, cannot automatically realize your business and dreams. If your thinking is not clear and the design department is clear, even the best IDE can't help you half way. On the contrary, your thinking is clear, and your data structure is clear (I was watching K&R's C recently, and I found that the core of C is really simple and small, and I found beauty that was not found before), the data structure is determined, and the algorithm is determined. Your program flow is also fixed. Abstractly, our process consists of two parts: data plus programs (operations on data), but there is also no lack of artifact Lisp to realize the integration of data and programs, but so far I have not understood the profound truth, or the same as that in JavaScript. Similar to function, a function is a first-class citizen. It can be a function, an object, or data. The key is what your context requires. From the perspective of oop, we are looking at the abstraction of what kind of objects we need, forming an object system, how to communicate between objects, what objects need to expose, and what to hide. It may seem that this method is suitable for this object at the time, but in the object In the system, it is found that it is more suitable in another place. This requires a balance, and it is necessary to continuously spend time to find a better design that is closer to the problem area. A good architecture requires design, and constant refactoring helps us find better designs.
 
Good architecture comes from good design, and code is only the last step.

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=326849361&siteId=291194637