Programmer in the impression of ordinary people is a strict (KU) careful (BI) occupation, is also a funny fun of the occupation, programmers in the face of complex code beating computer will not even frown, but there is a word is the root of their pain, it is Bug.
Programmers tune in Bug feeling
This is the wave is not flat, wave after wave
Never tell a programmer about a Bug
Faced with bugs, some programmers get angry, frustrated, upset, or even frustrated, while others remain calm and composed. Therefore, how to handle the process of fixing bugs is also worth thinking about.
Cow X programmers and bugs between PK
Nobita would like to share some thoughts about what programmers go through when fixing their source code. I’m sure many developers and software engineers have gone through these hardships and laughed it off in hindsight. Which of the following have you experienced?
1. “I don’t know whether to delete it or rewrite it”
Looking back at old source code, there is a temptation to rework it into larger clusters. Ugly logical statements and long syntax make the code very hard to read!
But then again, if the code isn’t broken, don’t fix it. This kind of messy struggle is something I face on a regular basis, and it clearly bothers many software developers.
“Why does this script need so many libraries?”
Especially for more popular languages such as Java and Objective-C, the number of libraries can become ferocious. When building a framework that requires a lot of foundation, the number of libraries required becomes much more obvious.
Even some plug-ins for JavaScript require countless additional files. Sometimes, this can feel annoying — but at least it’s useful!
3. “Is there a plug-in for this?”
Why reinvent the wheel? Plug-ins are a great resource for expanding the user interface of any program or website. In addition, they provide some customization and unique options for developers. In case there really isn’t one available, why not build your own?
4. “The website works, but I’m afraid of Internet Explorer.”
The history of rendering web pages in Internet Explorer is full of trials we’ve seen or experienced.
Upgrading from version 5.5 to IE9 and IE10 always requires the support of more advanced browsers. Web developers can be afraid to debug Web pages because opening pages in IE6 is a rendering nightmare. Thankfully, those days are fading away.
5. “That doesn’t seem logical to a logical expression.”
There are logical expressions for if/else loops, for loops, while loops, do loops, and so on. As I looked through the sample code, I tried to figure out how my logic worked.
There are so many NOT operators and comparison tags. I often go back and update my own logic to better suit future practices.
6. “I spend 30 minutes writing the function and 2 hours making it work.”
Doesn’t that sound like our own programming story? You’re happily building something, but all of a sudden, the function outputs a fatal error.
So now you have to go back and delete some code blocks to find the line number where the error occurred. When you finally find the culprit and fix it, it’s exhausting but also comforting.
7. “After reading multiple blog posts, I realized THAT I had been wrong all along.”
I often start by diving in with my programming ideas, but this can lead to trouble if things don’t go as planned.
There have been many times when I started a project, got stuck, and then had to seek support from blogs and other papers.
In the end I found out that my whole approach was actually wrong and that it was easier to start over! It would save me time in the long run if I did some research at the beginning.
8. “It took a lot of effort to figure out the cause of the problem was the missing close parenthesis.”
Debugging is a step you have to take, two steps forward, one step back. It’s nice to stare at code for hours, thinking there’s something wrong with a function name or variable scope, only to discover that a parenthesis is missing. All that time was wasted because of a small grammatical error.
9. “Take a coffee break!”
Sometimes, you just need to stand up and step away from the monitor. Hovering your mouse over your keyboard for hours can help break the mold. Most health guidelines recommend taking short breaks every 30-60 minutes.
But it all depends on your needs, and if you find it more frustrating to take a break in the middle of a program, don’t interrupt.
10. “I should put this project on the back burner and deal with it later.”
Another option for a break is to step away from your project, not just your computer. If something else needs to be done, do something else.
This is a much better allocation of time and resources than having spent 5 hours trying to solve the problem and still not getting started.
11. “Oh my God, why didn’t I write a note before?”
When it comes to basic front-end HTML/CSS/JS, there is no need to write comments. But more complex scripts and programs require some form of organization when you need to look back months or even years later.
Sometimes you forget to comment out functions with their arguments, output formats, and other necessary data. This will undoubtedly lead to chaos over time. Also, when bugs start appearing, you have to debug the entire script to find a solution. Therefore, it would be helpful to have some helpful comments.
12. “Twenty minutes ago it was working…”
Probably the most frustrating part of building a program is when it goes from working to not working — and you don’t update any part of the code! I swear it’s true, and it doesn’t make any sense – maybe some other program is running a cached version?
There are many times when you update a little bit of code and the whole program crashes and stops working completely. Restore to the latest working copy and work your way up from there.
13. “No, I’ll just start over.”
Sometimes, after you’ve been racking your brain for hours, all you need to do is move your work files to your archive (or delete them) and start all over again. However, it’s hard to make up your mind given the amount of time you’ve already spent.
When I’m at a loss, I often choose to start from scratch, because that way I have a better chance of finding and finishing the project
The right path.
Why can’t programmers find their own bugs?
As a developer, as we adults, we always see problems with our own world view, resulting in the right and the true truth is hidden.
When programmers face bugs, how smart to shake the pot?
When you’re faced with a Bug, don’t panic. Here’s how to make it easier.
1. I didn’t write the code. Throw it out.
2. Lying through your teeth is normal on my computer, super innocent. Earn sympathy points
3. The other party uses the wrong opening method.
They must have opened it the wrong way. Try opening it again. I don’t know anything
4. Reprimanded the product manager, secretly changed it, the momentum should not be weak, the position should be firm, quickly into the role, there is no Bug, I am king.
The above mode can be arbitrarily switched to use, but eventually can not escape, secretly secretly, to change the fate of the Bug.
What do you want to say
Feel free to leave a comment below!
Follow public accounts
【 Pegasus Club 】
▼
AI Artificial Intelligence/Big Data /Database/Linear Algebra/Python/ Machine Learning /Hadoop
Reply number “12” small white | Python + + machine learning Matlab neural network theory + practice + + + depth video + courseware + source code, download attached!