1. Technology isn’t helping

“Gee, that’s a tough question. I’m going to GitH

Many programmers have a great programming community or web site that they can use to improve their programming skills.

The worst nightmare for programmers is that no one in the top development community can answer their questions.

2. Your favorite keyboard shortcut is broken

“The scariest dream I ever had was when my semicolon button stopped working.”

“It took several lines of code before the control key stopped working…”

To save time, programmers prefer keyboard shortcuts to the mouse, so keyboards are important to them. However, not all keys are equally loved by programmers, and some keys are used far more often than others, especially in certain programming languages such as JavaScript, Perl, and Objective-C.

So it’s not surprising that programmers wake up in dreams where their favorite shortcuts are broken or not on the keyboard at all.

3. Internet disconnection and disconnection

“If there were no Internet, I wouldn’t be able to Google, I wouldn’t be able to find a solution, and I wouldn’t be able to find a solution!”

The Internet is like a treasure chest of open sources of code and some software. And without the Internet, access to remote servers and the cloud is almost impossible.

4. BUG cannot be copied

“In the company how to simulate the blue screen problem will not come out, in the customer there every month!”

To fix the BUG, the programmer must simulate the test environment in which the BUG occurred. But sometimes the BUG just can’t be simulated in a controlled environment.

5. Bugs appear randomly

“My worst nightmare is when bugs pop up during presentations to key customers.”

Bugs are usually fixed well before the production deployment phase, if you’re lucky. Many programmers are afraid of bugs appearing randomly. This kind of BUG can make programmers feel awkward in front of important customers.

6. Code has no comments

“Oh my God, why didn’t I write a comment, and now to look at such a long piece of code, it will crash!”

Without any comments or documentation, it is difficult for programmers to make sense of a complex and lengthy piece of code.

Not just code written by a third party, but code written long ago by the programmer himself, which can be painful to look at if not properly labeled.

7. Project requirements have changed again

“That’s not what you wanted yesterday. !”

Software developers love nothing more than to see project requirements clearly outlined and never changed. But in practice, these requirements come and go, sometimes from the project manager, sometimes from the client.

Whatever the reason, the fear of changing requirements haunts the programmer’s soul, especially in the last few minutes before delivery.

8. Code is gone

“WTF, where did the code I just wrote go?”

No matter what schedule the programmer plans for software development, if the code doesn’t survive, it doesn’t matter.

There could be many reasons why code doesn’t survive, but all of the programmer’s hard work, all of the work that goes into algorithms and functions, goes out the window.

How many of these nightmares did you get as a programmer?