Programmer's nightmare, my loophole hurts others ....

For the vast majority of people, it is a cliché that they have nightmares: ghosts, spiders, hunted by killers wearing hockey masks ... But for others, the things they fear most are less common.

Take software developers for example. If you ask him what is the most horrible nightmare, then the answer is probably not related to witches, black cats, the real nightmare is that the key semicolon does not work or a Microsoft product. After analyzing a wide range of programmers ' concerns, here are some of the 13 most vexing nightmare for programmers.  

 

1. I can solve problems through the Internet   the
Stack Exchange-type web site has become a critical tool in the software Developer's Toolkit. There are, of course, many other forums where programmers seek help. The biggest headache for programmers is that seemingly endless sources of knowledge do not actually solve your problem in the life-saving straw.

"The same problem was seen on the StackOverflow website, but the final answer was not found for a long stroll. "--jorge Irun

      http://www.itlanbao.com/code/20150908/10000 /100513.html

2. The most important keys on the keyboard have broken  
It's easy to imagine that keyboards are of great importance to developers. But in the same way, not all keys are important to developers ' eyes. Especially in some programming languages, some keys are more frequently used than other keys, such as the semicolon keys in JavaScript, Perl, and Objective-c. To save time and avoid errors, developers love to use keyboard shortcuts, which are more frequent than the mouse. If a software developer dreams of a keyboard where his favorite buttons are broken or even gone, you don't have to be surprised to wake up in a cold sweat in the middle of the night.  
"The worst nightmare I've ever had is that the semicolon key is broken. "--ali Akbar

    http://www.itlanbao.com/code/20150902/10000/100499.html     

After hitting n lines of code, I found the Control key didn't respond ... "--nikesh Shetty

3. Network not connected, or dropped  
a" niche "nightmare is that a tool's forum is offline or out of maintenance to solve the problem, But it is more common to access the Internet when the line dropped, unable to access the site. Because after all, in addition to the purpose of visiting the forum unexpectedly, the network is more like a huge elephant nose, the inside filled with useful things, such as code snippets, open source software. If the internet suddenly dropped, it will cause the programming team can not contact, your favorite online music playback service is not available, let alone access to remote services or the cloud how difficult ... If you want to scare the programmer, yell "No network" is enough. Remember to always have the defibrillator ready for first aid.
Reference

      http://www.itlanbao.com/code/20150909/10000 /100518.html

If one day the internet and Google are gone, it will return to the secluded, dark antiquity. We can only do anything when we encounter bugs. "--thoriq firdaus 


4. Dangerous error   that cannot be reproduced;
in order to fix a vulnerability, the developer must reproduce the situation that caused the error in the development or test environment. If you're lucky, you can diagnose and fix errors before the development environment is deployed. Many developers are afraid of a vulnerability that occurs randomly and cannot be reproduced in a controlled environment. Such a damn loophole will get you worried and restless in front of your important customers. This is definitely a nightmare for programmers. &NBSP

refers to a vulnerability that occurs only when a public or a key customer is present, simply let me ... "--jeremy friesner

     http://www.itlanbao.com/code/20150911/10000/100523.html

" in the company when the blue screen phenomenon will never appear the second time, but one to the customer's home is old. "--joe Wezorek


5. No good documents, no document  
sitting down to understand an existing code without good documentation or comments is difficult. It's even worse if you don't have a document or comment. This applies not only to the code written by the third party that inherits the programmer, but also to the code that the same programmer wrote a long time ago that lacked good documentation. Whoever splits the code without a description of the document is always a nightmare.  

Reference

      http://www.itlanbao.com/code/20150907/10000 /100509.html

" It's no exaggeration to say that it is a nightmare for me to maintain old software without developing documentation. "--sam sartor 


6. Bad boss and supervisor  
Like everyone else, developers can be nosy and less capable bosses. Software developers are particularly disgusted with the non-technical management layer that randomly interferes with their code. Some leaders like to promise something we can't do, and underestimate the time it takes to slice code in a project. The thought of such leaders and technical decision-makers, programmers will cry even in the dream of the night.  

Reference

     http://www.itlanbao.com/code/20150911/10000/100524.html

" the worst non-manager for me is worse than a toothache. They snob and expect us to meet our customers ' needs early. These so-called managers also believe that programming is a trivial matter, code is like floating in the air, can be handy. "--rachit agrawal 


7. Clear and Beautiful code   for others;
For most programmers, they like and must continue to work on someone else's code, but don't forget that different timer codes will never be the same, right? Even a piece of third-party code with good documentation can become a hassle. It requires you to do debugging, refactoring, or structuring, adapting your code to code that might have been sliced up a few months ago. These jobs can make the programmers heartbeat abnormally. If not, thank goodness.  
    http://www.itlanbao.com/code/20150911/10000/100522.html

8. Changes in the requirements of the project  
Whenever software developers are in favor of applications that are articulate and not changeable. In practice, many of the needs are hastily formulated, sometimes even formal, and the reason for the change is partly the bad project manager, and the other is the complaints and interference from superiors or customers themselves. In short, for whatever reason, fear of a change in demand – especially at the last minute – is always a developer's heart.  
    http://www.itlanbao.com/code/20150909/10000/100516.html

9. Missing code  
No matter how long it takes the developer to dispatch the software, if the code is accidentally erased, all efforts will be wasted. The code unexpectedly disappears for many reasons, the most important thing is to forget to save the file, or unknown malicious vulnerability can not be saved. For whatever reason, whether it's not considered well-conceived, programmers are always afraid to take a lot of time and energy to get the algorithms and functions to ruin.  
    http://www.itlanbao.com/code/20150908/10000/100514.html

10.IE browser  
programmers often get fed up with some technology. For example, WEB developers are terrified of using IE as a developer. Although it is still one of the most popular browsers, IE is a nightmare for web developers. Worse, the older versions of IE are unfriendly, more users, and more support than modern, eco-friendly versions. If the movie "13th Friday" in the murder of Jason Vorhees frightened a web developer, his mask is probably IE Totem.
    http://www.itlanbao.com/code/20150907/10000/100510.html

11. Physical discomfort
Programming is not a physical task, but just as other professions that need to divide data on a computer all night and night, it is difficult to do so with arms, palms and fingers. Any factor that has a negative impact on the ability to think visually and rationally can become a big problem. As a result, the typical nightmare for software developers is the inability to use and even the loss of one or more important parts of the body-the personal injury lawyer (Personal injury lawyer) Baca Raton said.


12. My loophole hurts others
Any software developer will be the manufacturer of the vulnerability. But not all the loopholes are equally catastrophic. Some of these vulnerabilities are annoying but harmless, others will cause losses to the company or customers, and the person responsible for the development will be expelled. At worst, however, the vulnerability could cause physical harm and even endanger the lives of others.


13. Segment Error
There is a common nightmare in programmers and a mistake. This error is caused by an illegal access to the memory. In other words, the program attempts to access restricted memory or perform a restricted behavior. In general, accessing a memory unit in this case notifies the operating system, which in turn notifies the problematic, most of the process that ends with a hung horse program. The biggest headache for developers is finding the cause of the problem. As a result, there is a bug in the programmer's nightmare.

Programmer's nightmare, my loophole hurts others ....