"Go" programmers should ask themselves 10 questions when writing code

Do you want to be a good programmer?

Well, now is the time to put down the "24-hour learning XXX language v8.3" Super Cheats book, instead, you should form a daily ask yourself the following 10 questions of the habit.

Is there a pattern in your code?

Find ideas or basic principles that seem irrelevant in a pattern that is feasible and impossible to discover. To get a deep understanding of your work, you have to ask yourself, "Is there a pattern?" "The habit.

It's not just for your code. Is there a model for adapting to various types of business change? Is there a model for technological development? Have you seen the same type of mistakes springing up?

The so-called understanding is to understand the pattern-to Isaiah

How to make the code easier?

Developers often want complex and scalable solutions. Do something extremely complex and feel that you are the master of your universe. The problem is that you'll never know how products and businesses will change in the future.

"Architecture" and code are more like gardening than architecture. You have to be able to adapt to the changing environment. The more complex the solution the more difficult it is to do.

Simplicity is the ultimate complication--Leonnado Dar Finch

Do you know why the program runs like this?

Knowing that something works like that and knowing why it works like that is two completely different things. If you know why things are that way, then you can make better decisions.

The difference between a great programmer and someone who knows a programming language is the depth of understanding why.

The same principle applies to problem corrections. "Restart the service. "Did you try to reboot?" "When something happens, we often think of these words. Every time you say so, you lose a golden opportunity to learn.

Understanding why such errors are occurring will fix the root cause and avoid the symptoms of a cure. At the very least, you should not make the same mistake again.

Has anyone ever written such a code before?

Whenever you find yourself inventing a complex algorithm, you are likely to be on the wrong track. Unless you search for a doctor's paper that someone else just solved the problem.

Need to write an algorithm that adds a label to the item next to the user's mouse? Look at Voronoi.
Tesselations. Want to find the shortest route for truck delivery? Look at Dijkstra. Want to find the closest tag for user input? should be to find it levenschtein distance.

This is just a few simple examples, believe me, they are everywhere.

I can see farther, that's because I'm standing on the shoulders of giants-Isaac Newton.

Do you know the origin of this technology?

Do you think you know rest?

Have you ever read Roy Fielding's original paper describing rest? Do you really understand the original purpose of it? The kind of blog that is written by a guy in the IDE V7 tool that is more than you use the Rest API Generation Wizard for 5 minutes doesn't count.

Do yourself a favor by trying to read the original document of concept or principle, and then use various means to understand the latest developments of industry leaders. If you don't know where they started, follow their footsteps. (Don't know where they come from, just follow them wherever they go!) ）

Do I like what I do now?

It's hard to deal with programming, though.

In addition to the difficult, programming is still developing quickly. The art framework has evolved from a 2-year-old "bulky dinosaur" to today's standard. In order to stand at the top of your "game", you must establish a lifelong learning and research belief.

If you don't like what you're doing, then you're not keeping up with the possibilities of other guys (who like what you do). So find the type of programming that makes your passion burn! Don't decide to become a security expert because of a market gap or a hefty income, and don't decide to become an UX expert because an article says UX is the hottest career.

Again, do what you like.

Do what you like and the resources you need will come with it-Peter McWilliams

Can the code be used anywhere else?

One of the biggest limitations I see for programmers is the imagination of their own failures.

If we learn something that adapts to a particular environment, or see the technology that solves a particular problem, we think it's the only place where it works. This is completely wrong. Whenever you learn something new, ask yourself: "Can you use it anywhere else?" ”

When the new great way to locate a node on a chart is found, is it possible to apply it to the positioning of interesting data in a two-dimensional data set? How can it be applied to an extensible backend service when it discovers a new way to send data from the client to the server side via WebSockets? Sometimes it's wrong, but sometimes it's right.

This brings us to the next question ...

Logic only takes you from A to Z, and imagination can take you anywhere-Albert Einstein

Is there anything wrong with today?

The simplest way to increase revenue is to reduce erroneous losses.

Game development company Valve and several other companies are very much in view of this view. This also applies to you as a web developer in the process of progress. If you are afraid of failure, you will not have a big breakthrough.

Brave, try, fail, learn and come again.

Don't be afraid of mistakes, it will let you know the failure, and then come back. -Benjamin Franklin

Is there really no way to do it?

It is impossible for us to live in a small place in the world (except for a few exceptions).

Let's say that whatever you do is feasible, and then push back backwards in a backward direction. You may find that what you want to do is impractical for the time being, but it is enough to change the world and may become reality faster than you think.

It seems like everything is impossible unless you finish it-Nelson Mandela

Who can I learn from?

Never work in a place where you are the smartest person in the group.

Pick a job and company that inspires and inspires you to do more. Do not relate to programming, there is a complete world outside the text editor and command line. Learn from other areas and try to apply it to your work.

Never be satisfied with your current job!

Original address: Http://www.techug.com/10-questions-developers-should-be-asking-themselves

"Go" programmers should ask themselves 10 questions when writing code