像程序員一樣思考

by Richard Reis

理查德·里斯(Richard Reis)

如何像程序員一樣思考-解決問題的經驗教訓 (How to think like a programmer — lessons in problem solving)

If you’re interested in programming, you may well have seen this quote before:

如果您對編程感興趣，那么您可能之前已經看過以下引用：

“Everyone in this country should learn to program a computer, because it teaches you to think.” — Steve Jobs“這個國家的每個人都應該學習編程計算機，因為它可以教您如何思考。” —史蒂夫·喬布斯

You probably also wondered what does it mean, exactly, to think like a programmer? And how do you do it??

您可能還想知道，像程序員一樣思考到底意味著什么？ 以及你如何做到的？

Essentially, it’s all about a more effective way for problem solving.

本質上， 這都是解決問題的更有效方法 。

In this post, my goal is to teach you that way.

在這篇文章中，我的目標是教你這種方式。

By the end of it, you’ll know exactly what steps to take to be a better problem-solver.

到最后，您將確切地知道要成為一個更好的問題解決者應采取的步驟。

為什么這很重要？ (Why is this important?)

Problem solving is the meta-skill.

解決問題是超能力。

We all have problems. Big and small. How we deal with them is sometimes, well…pretty random.

我們都有問題。 大和小。 有時，我們如何對待它們……相當隨機。

Unless you have a system, this is probably how you “solve” problems (which is what I did when I started coding):

除非您有系統，否則這可能就是您“解決”問題的方式(這是我開始編碼時所做的事情)：

Try a solution.

嘗試解決方案。

If that doesn’t work, try another one.

如果那不起作用，請嘗試另一個。

If that doesn’t work, repeat step 2 until you luck out.

如果那不起作用，請重復步驟2，直到運氣好為止。

Look, sometimes you luck out. But that is the worst way to solve problems! And it’s a huge, huge waste of time.

看，有時候你運氣不好。 但這是解決問題的最糟糕的方法！ 這是一個巨大的浪費時間。

The best way involves a) having a framework and b) practicing it.

最好的方法包括a)擁有框架，b) 實踐它。

“Almost all employers prioritize problem-solving skills first.“幾乎所有雇主都將解決問題的技能放在首位。 Problem-solving skills are almost unanimously the most important qualification that employers look for….more than programming languages proficiency, debugging, and system design.解決問題的技能幾乎是雇主所尋求的最重要的資質……不僅僅是編程語言的熟練程度，調試和系統設計。

Demonstrating computational thinking or the ability to break down large, complex problems is just as valuable (if not more so) than the baseline technical skills required for a job.” — Hacker Rank (2018 Developer Skills Report)

證明計算思維或解決大型復雜問題的能力與工作所需的基本技術技能同樣有價值(如果不是更多的話)?！?-黑客排名( 2018開發人員技能報告 )

有一個框架 (Have a framework)

To find the right framework, I followed the advice in Tim Ferriss’ book on learning, “The 4-Hour Chef”.

為了找到合適的框架，我遵循了蒂姆·弗里斯(Tim Ferriss)關于學習的書“ 4小時廚師 ”中的建議。

It led me to interview two really impressive people: C. Jordan Ball (ranked 1st or 2nd out of 65,000+ users on Coderbyte), and V. Anton Spraul (author of the book “Think Like a Programmer: An Introduction to Creative Problem Solving”).

這使我采訪兩位真是令人印象深刻的人： C.喬丹·鮑爾 (排名第1或2日進行65,000+用戶Coderbyte )和V.安東Spraul (書“的作者認為象程序員：介紹創造性地解決問題 ”)。

I asked them the same questions, and guess what? Their answers were pretty similar!

我問了他們同樣的問題，你猜怎么著？ 他們的答案非常相似！

Soon, you too will know them.

很快，您也將了解它們。

Sidenote: this doesn’t mean they did everything the same way. Everyone is different. You’ll be different. But if you start with principles we all agree are good, you’ll get a lot further a lot quicker.

旁注：這并不意味著他們以相同的方式做所有事情。 每個人都不一樣。 你會有所不同。 但是，如果您從原則入手，我們都同意是好的，那么您會更快地獲得更多。

“The biggest mistake I see new programmers make is focusing on learning syntax instead of learning how to solve problems.” — V. Anton Spraul

“我看到新程序員犯的最大錯誤是專注于學習語法，而不是學習如何解決問題?！?— V.安東·斯普勞

So, what should you do when you encounter a new problem?

那么，遇到新問題該怎么辦？

Here are the steps:

步驟如下：

1.了解 (1. Understand)

Know exactly what is being asked. Most hard problems are hard because you don’t understand them (hence why this is the first step).

確切知道要問什么。 大多數棘手的問題之所以棘手，是因為您不理解它們(因此，這是第一步)。

How to know when you understand a problem? When you can explain it in plain English.

如何知道您何時了解問題？ 當您可以用簡單的英語解釋它時。

Do you remember being stuck on a problem, you start explaining it, and you instantly see holes in the logic you didn’t see before?

您是否還記得被困在某個問題上，開始進行解釋并立即發現以前未曾發現的邏輯漏洞？

Most programmers know this feeling.

大多數程序員都知道這種感覺。

This is why you should write down your problem, doodle a diagram, or tell someone else about it (or thing… some people use a rubber duck).

這就是為什么您應該寫下問題，繪制圖表或將其他事情告訴別人的原因(或其他一些人使用橡皮鴨的事情)。

“If you can’t explain something in simple terms, you don’t understand it.” — Richard Feynman“如果您不能用簡單的術語來解釋，那么您將無法理解。” —理查德·費曼(Richard Feynman)

2.計劃 (2. Plan)

Don’t dive right into solving without a plan (and somehow hope you can muddle your way through). Plan your solution!

不要沒有計劃就直接投入解決方案(以某種方式希望您能摸索到底)。 規劃您的解決方案！

Nothing can help you if you can’t write down the exact steps.

如果您無法寫下確切的步驟，沒有任何幫助。

In programming, this means don’t start hacking straight away. Give your brain time to analyze the problem and process the information.

在編程中，這意味著不要立即開始進行黑客攻擊。 給您的大腦時間分析問題并處理信息。

To get a good plan, answer this question:

為了獲得良好的計劃，請回答以下問題：

“Given input X, what are the steps necessary to return output Y?”

“考慮到輸入X，返回輸出Y需要采取什么步驟？”

Sidenote: Programmers have a great tool to help them with this… Comments!

旁注：程序員有一個很棒的工具來幫助他們。

3.劃分 (3. Divide)

Pay attention. This is the most important step of all.

請注意。 這是最重要的一步。

Do not try to solve one big problem. You will cry.

不要試圖解決一個大問題。 你會哭。

Instead, break it into sub-problems. These sub-problems are much easier to solve.

而是將其分解為多個子問題。 這些子問題更容易解決。

Then, solve each sub-problem one by one. Begin with the simplest. Simplest means you know the answer (or are closer to that answer).

然后，一個一個地解決每個子問題。 從最簡單的開始。 最簡單意味著您知道答案(或更接近答案)。

After that, simplest means this sub-problem being solved doesn’t depend on others being solved.

此后，最簡單的方法意味著要解決的子問題不依賴于要解決的其他問題。

Once you solved every sub-problem, connect the dots.

解決了每個子問題后，將點連接起來。

Connecting all your “sub-solutions” will give you the solution to the original problem. Congratulations!

連接所有“子解決方案”將為您解決原始問題。 恭喜你！

This technique is a cornerstone of problem-solving. Remember it (read this step again, if you must).

該技術是解決問題的基石。 記住這一點(如果需要，請再次閱讀此步驟)。

“If I could teach every beginning programmer one problem-solving skill, it would be the ‘reduce the problem technique.’“如果我可以教每個新手程序員一種解決問題的技能，那將是'減少問題的技術'?！? For example, suppose you’re a new programmer and you’re asked to write a program that reads ten numbers and figures out which number is the third highest. For a brand-new programmer, that can be a tough assignment, even though it only requires basic programming syntax.例如，假設您是一名新程序員，并且要求您編寫一個程序，該程序讀取十個數字，并弄清楚哪個數字是第三高的。 對于一個全新的程序員來說，即使只需要基本的編程語法，這也是一項艱巨的任務。 If you’re stuck, you should reduce the problem to something simpler. Instead of the third-highest number, what about finding the highest overall? Still too tough? What about finding the largest of just three numbers? Or the larger of two?如果您遇到困難，則應將問題減少到更簡單的程度。 而不是第三高的數字，如何找到最高的整體呢？ 還是太強硬了？ 如何找出三個數字中的最大數字呢？ 還是兩者中的較大者？

Reduce the problem to the point where you know how to solve it and write the solution. Then expand the problem slightly and rewrite the solution to match, and keep going until you are back where you started.” — V. Anton Spraul

將問題減少到知道如何解決并編寫解決方案的程度。 然后稍微擴大問題范圍，重新編寫匹配的解決方案，然后繼續進行下去，直到回到起點為止?！?— V.安東·斯普勞

4.卡住了嗎？ (4. Stuck?)

By now, you’re probably sitting there thinking “Hey Richard... That’s cool and all, but what if I’m stuck and can’t even solve a sub-problem??”

現在，您可能正坐在那里，想著“嗨，理查德……這很酷，但是如果我被困住甚至不能解決子問題怎么辦？”

First off, take a deep breath. Second, that’s fair.

首先，深呼吸。 第二，這很公平。

Don’t worry though, friend. This happens to everyone!

朋友，請不要擔心。 這發生在每個人身上！

The difference is the best programmers/problem-solvers are more curious about bugs/errors than irritated.

不同之處在于，最好的程序員/問題解決者對錯誤/錯誤的好奇大于對錯誤的好奇。

In fact, here are three things to try when facing a whammy:

實際上，面對混亂時，可以嘗試以下三件事：

• Debug: Go step by step through your solution trying to find where you went wrong. Programmers call this debugging (in fact, this is all a debugger does).

  調試：逐步解決您的解決方案，以查找錯誤的地方。 程序員將其稱為調試 (實際上，這是調試器的全部工作)。

“The art of debugging is figuring out what you really told your program to do rather than what you thought you told it to do.”” — Andrew Singer“調試的技巧在于弄清您真正告訴程序要執行的操作，而不是您認為要執行的操作?！?–安德魯·辛格(Andrew Singer)

• Reassess: Take a step back. Look at the problem from another perspective. Is there anything that can be abstracted to a more general approach?

  重新評估： 退后一步。 從另一個角度看問題。 有什么可以抽象為更通用的方法的嗎？

“Sometimes we get so lost in the details of a problem that we overlook general principles that would solve the problem at a more general level. […]“有時候，我們對問題的細節迷失了，以至于忽略了可以從更一般的層面解決問題的一般原則。 […]

The classic example of this, of course, is the summation of a long list of consecutive integers, 1 + 2 + 3 + … + n, which a very young Gauss quickly recognized was simply n(n+1)/2, thus avoiding the effort of having to do the addition.” — C. Jordan Ball

當然，這方面的經典示例是一長串連續整數的總和，即1 + 2 + 3 +…+ n，一個非常年輕的高斯很快就認出了n(n + 1)/ 2，因此避免了進行添加的工作。” — C.喬丹·鮑爾

Sidenote: Another way of reassessing is starting anew. Delete everything and begin again with fresh eyes. I’m serious. You’ll be dumbfounded at how effective this is.

旁注：重新評估的另一種方法是重新開始。 刪除所有內容，然后重新開始。 我是認真的。 您將不知該如何有效。

• Research: Ahh, good ol’ Google. You read that right. No matter what problem you have, someone has probably solved it. Find that person/ solution. In fact, do this even if you solved the problem! (You can learn a lot from other people’s solutions).

  研究： 啊，Google不錯。 您沒看錯。 無論您遇到什么問題，都可能有人解決了。 找到那個人/解決方案。 實際上，即使您解決了問題，也要這樣做！ (您可以從其他人的解決方案中學到很多東西)。

Caveat: Don’t look for a solution to the big problem. Only look for solutions to sub-problems. Why? Because unless you struggle (even a little bit), you won’t learn anything. If you don’t learn anything, you wasted your time.

警告：不要為大問題尋找解決方案。 只尋找子問題的解決方案。 為什么？ 因為除非您奮斗(一點點)，否則您將不會學到任何東西。 如果您什么都不學，那您就浪費了時間。

實踐 (Practice)

Don’t expect to be great after just one week. If you want to be a good problem-solver, solve a lot of problems!

僅僅一周之后，別指望它會變得很棒。 如果您想成為一個好的問題解決者，請解決很多問題！

Practice. Practice. Practice. It’ll only be a matter of time before you recognize that “this problem could easily be solved with <insert concept here>.”

實踐。 實踐。 實踐。 認識到“使用“在此處插入概念”可以輕松解決此問題”只是時間問題。

How to practice? There are options out the wazoo!

怎么練習？ wazoo有多種選擇！

Chess puzzles, math problems, Sudoku, Go, Monopoly, video-games, cryptokitties, bla… bla… bla….

國際象棋難題，數學問題，數獨，圍棋，專賣，視頻游戲，加密小貓，等等……等等……等等……。

In fact, a common pattern amongst successful people is their habit of practicing “micro problem-solving.” For example, Peter Thiel plays chess, and Elon Musk plays video-games.

實際上，成功人士中的常見模式是他們練習“解決微觀問題”的習慣。 例如，彼得·泰爾(Peter Thiel)下棋，埃隆·馬斯克(Elon Musk)玩電子游戲。

“Byron Reeves said ‘If you want to see what business leadership may look like in three to five years, look at what’s happening in online games.’“拜倫·里夫斯(Byron Reeves)說：“如果您想了解三到五年內業務領導者的模樣，請看一下在線游戲中正在發生的事情。”

Fast-forward to today. Elon [Musk], Reid [Hoffman], Mark Zuckerberg and many others say that games have been foundational to their success in building their companies.” — Mary Meeker (2017 internet trends report)

快進到今天。 Elon [Musk]，Reid [Hoffman]，Mark Zuckerberg和許多其他人說，游戲是成功建立公司的基礎。” — Mary Meeker( 2017年互聯網趨勢報告 )

Does this mean you should just play video-games? Not at all.

這是否意味著您應該只玩視頻游戲？ 一點也不。

But what are video-games all about? That’s right, problem-solving!

但是電子游戲到底是什么呢？ 是的，解決問題！

So, what you should do is find an outlet to practice. Something that allows you to solve many micro-problems (ideally, something you enjoy).

因此，您應該做的是找到一個練習的出口。 使您能夠解決許多微問題的事物(理想情況下，您喜歡的事物)。

For example, I enjoy coding challenges. Every day, I try to solve at least one challenge (usually on Coderbyte).

例如，我喜歡編碼方面的挑戰。 每天，我都會嘗試解決至少一個難題(通常在Coderbyte上 )。

Like I said, all problems share similar patterns.

就像我說的，所有問題都有相似的模式。

結論 (Conclusion)

That’s all folks!

那是所有人！

Now, you know better what it means to “think like a programmer.”

現在，您更好地了解了“像程序員一樣思考”的含義。

You also know that problem-solving is an incredible skill to cultivate (the meta-skill).

您還知道解決問題是一種不可思議的技能(超能力)。

As if that wasn’t enough, notice how you also know what to do to practice your problem-solving skills!

如果這還不夠，請注意您還知道如何去練習解決問題的技能！

Phew… Pretty cool right?

ew……挺酷的吧？

Finally, I wish you encounter many problems.

最后，祝您遇到許多問題。

You read that right. At least now you know how to solve them! (also, you’ll learn that with every solution, you improve).

您沒看錯。 至少現在您知道如何解決它們了！ (此外，您將了解到每種解決方案都可以改進)。

“Just when you think you’ve successfully navigated one obstacle, another emerges. But that’s what keeps life interesting.[…]“只要您認為自己已經成功克服了一個障礙，就會出現另一個障礙。 但這就是讓生活變得有趣的原因。[…] Life is a process of breaking through these impediments — a series of fortified lines that we must break through.生活是克服這些障礙的過程，這是我們必須突破的一系列防御性路線。 Each time, you’ll learn something.每次，您都會學到一些東西。 Each time, you’ll develop strength, wisdom, and perspective.每次，您都會發展力量，智慧和遠見。

Each time, a little more of the competition falls away. Until all that is left is you: the best version of you.” — Ryan Holiday (The Obstacle is the Way)

每次，更多的競爭就會消失。 剩下的只有你：你最好的版本?！?-Ryan Holiday( 《障礙就是路》 )

Now, go solve some problems!

現在，去解決一些問題！

And best of luck ?

祝你好運？

Special thanks to C. Jordan Ball and V. Anton Spraul. All the good advice here came from them.

特別感謝 C. Jordan Ball和V. Anton Spraul 。 這里所有好的建議都來自他們。

Thanks for reading! If you enjoyed it, test how many times can you hit in 5 seconds. It’s great cardio for your fingers AND will help other people see the story.

謝謝閱讀！ 如果喜歡，請測試您可以在5秒鐘內擊中多少次。 這對您的手指來說是很好的心臟鍛煉，并且可以幫助其他人看到這個故事。

翻譯自: https://www.freecodecamp.org/news/how-to-think-like-a-programmer-lessons-in-problem-solving-d1d8bf1de7d2/

像程序員一樣思考

總結

以上是生活随笔為你收集整理的像程序员一样思考_如何像程序员一样思考-解决问题的经验教训的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。