DEV Community

Cover image for What is the nightmare for programmers?
Suraj Vishwakarma
Suraj Vishwakarma

Posted on • Updated on

What is the nightmare for programmers?

Introduction

The struggle of being a programmer is understood by none other than another programmer. We came across a lot of problems all day long and we have to overcome each and every obstacle.

NightMare

So today, I would love us to share things that a coder/programmer hates to encounter?

My thoughts

As a coder/programer I hate following things to encounter

  • No Network🌐
  • Stuck on one problem that takes a lot of time to get solve😨
  • Can't execute the program that I found on the web▶️

Discuss

  • What you hate most as a Programmer?
  • Nightmare for you as a Programmer?

Oldest comments (67)

Collapse
 
rishitkhandelwal profile image
Rishit Khandelwal

When you can't find solution to a problem any where in the internet.

Collapse
 
surajondev profile image
Suraj Vishwakarma

This is epic level of frustration

Collapse
 
darshkul24 profile image
Darsh

QUESTION :- What you hate most as a programmer ?
ANSWER :-
Hating levels
• 00 -- 25 = 😠
• 25 -- 50 = 😡
• 50 -- 75 = 😈
• 75 --.100 = 😫
What I hate are
• No network = 😈
• Bugs in code = 😠
QUESTION :- Nightmare for you as a programmer ?
ANSWER :-
Nightmare levels
• 00 -- 25 = 😠
• 25 -- 50 = 😡
• 50 -- 75 = 😈
• 75 --.100 = 😫
My nightmares are
• Code compiling failure = 😈
• likage of secret codes for a very big project = 😠

Collapse
 
surajondev profile image
Suraj Vishwakarma

All the point is very frustrating while you try to be in good mood.

Collapse
 
darshkul24 profile image
Darsh

Can we talk in dev.to connect for that follow me please and send me a massege please and i am going for some work i will be online in half an hour so dont worry if i dont reply at dev.to connect

Collapse
 
tolomei69 profile image
tolomei

Refactoring someones code that it's written VERY badly.... 100 in scale of hating...

Collapse
 
surajondev profile image
Suraj Vishwakarma

Yesss that's painful

Collapse
 
leobm profile image
Felix Wittmann

every code smells after a while....
I'd like to refactor others code. I first write testcases for the existing code (if no tests exist) and then I try to clean up the original code step by step.
I then always have the feeling that I have really improved something.

Important is that you really understand the "business logic" before you just throw away something you didn't understand.

Collapse
 
plaoo profile image
Paolo Monni

Incomprehensible tickets, poorly written.

Collapse
 
surajondev profile image
Suraj Vishwakarma

Yesss that's frustrating

Collapse
 
darkwiiplayer profile image
𒎏Wii 🏳️‍⚧️ • Edited

What you hate most as a Programmer?

  • Having to read code where someone was trying to be smart.

  • The "programming is just Ctrl+C Ctrl+V" meme.

  • Confused languages that think they're C when they're not.

  • Object-Oriented Programming taken too far.

  • PHP

Nightmare as a Programmer?

Simplifying poorly-written complex code with an equivalent but simpler expression, only to find out after deploying to production that it wasn't equivalent.

Collapse
 
surajondev profile image
Suraj Vishwakarma

PHP??

Collapse
 
darkwiiplayer profile image
𒎏Wii 🏳️‍⚧️

PHP.

Thread Thread
 
cubiclesocial profile image
cubiclesocial

PHP is better as a command-line language than a web language.

Thread Thread
 
surajondev profile image
Suraj Vishwakarma

Okay, I am a newbie to PHP.

Collapse
 
metalmikester profile image
Michel Renaud

"Having to read code where someone was trying to be smart"

So much this! After figuring it out, I'll think "well, that's pretty cool and clever". But then I will likely change it to something more readable because, more often than not, cleverness = maintenance nightmare.

Oh and, I've often been too clever myself for my own good. Go back into some piece of codes a couple of weeks later, come across "me being clever the other day" and going, "WTF does this do?"

Collapse
 
surajondev profile image
Suraj Vishwakarma

Yess a clear code is what we want

Collapse
 
dastasoft profile image
dastasoft

+1 to all the bullets lol

Collapse
 
surajondev profile image
Suraj Vishwakarma

🤣🤣

Collapse
 
charlesbjerg profile image
Charlie Underhill

Having to use version control in secret 😬

Collapse
 
surajondev profile image
Suraj Vishwakarma

Yep

Collapse
 
vindiv profile image
Vincenzo Di Vico

i'm maintaining some project made with a php framework, kohana (discarded in 2012 😫 ) and the log system don't work on php 7. so the nightmare is to resolve bug without a log or a clou

Collapse
 
surajondev profile image
Suraj Vishwakarma

That's really frustrating and hope it resolves soon

Collapse
 
orayodeji profile image
Tunji Ayodeji

Testing

Collapse
 
surajondev profile image
Suraj Vishwakarma

Yep that can be

Collapse
 
mzaini30 profile image
Zen

No internet. Hahahaha...

Collapse
 
surajondev profile image
Suraj Vishwakarma

🤣🤣🤣🤣

Collapse
 
aartboer profile image
Art Boer

Things on my hate list

  • Still having to support IE in 2021
  • Being forced to work with knockout.js and the great UiComponents in Magento :-(
  • Remote XDebug
  • Forgetting to flush redis or restart varnish and asking myself why the changes do not appear
  • Working in a framework that most of the maintainers (or all) don't really understand, Looking at you once again Magento
  • PHP, before typed properties and return types weren't a thing.. Thank god we have this now
Collapse
 
surajondev profile image
Suraj Vishwakarma

Hope your list get smaller over the time

Collapse
 
robertseidler profile image
RobertSeidler

I'm confident, that at some point IE users die out :D

Collapse
 
eljayadobe profile image
Eljay-Adobe

Edge. It's been Edge for a long while now. Edge!

I worked on IE 10 and IE 11, at Microsoft. I was surprised — and ecstatic — when Edge went live. Even many of us on working on IE didn't know about the Edge project in the works until it went public.

Collapse
 
leobm profile image
Felix Wittmann

to be bored with a task

Collapse
 
surajondev profile image
Suraj Vishwakarma

To be stuck at a problem is boring and frustrating

Collapse
 
cubiclesocial profile image
cubiclesocial

There are tasks that are truly uninteresting.

For example, "I've done this 100 times already" sort of mundane tasks. Writing boilerplate code where nothing new is being done is definitely up there on the boredom scale.

Another example is that some devs don't like writing documentation. Writing documentation can get repetitive. I personally like the activity since writing docs usually catches a few last-minute bugs in the software that might otherwise go unnoticed for months.

The key to combating boredom is to also work on interesting side projects. Side projects provide the drive and energy to overcome boredom and get the less exciting tasks done.

Collapse
 
jrop profile image
Jonathan Apodaca

Having a long turn-around time from pushing code => to being able to test while debugging critical bug.

Collapse
 
surajondev profile image
Suraj Vishwakarma

Yesss

Collapse
 
sashkan profile image
Pierre Olivier TRAN

What I hate most:

  • Uncommented bad code
  • Network issues
  • Haphazardous deployment

I work with 3 teams, one of them is based in the Bay area, another one in Vietnam, mine's in Paris. SF Team and mine are mostly senior devs, so we have access to push to production in case of emergency.

And for one of the US devs, it seems like a fckin CSS issue is an emergency. Dude branches out from master, to write some working code, without commenting or testing.

And we told him countless times to respect the chain of command, but still, he doesn't care, and bosses won't change a thing, because "Hey, most of the time, it works"

Collapse
 
ashiqsultan profile image
Mohamed Ashiq Sultan • Edited

Writing testsuit for a feature that takes more time than writing the actual logic for that feature.

Collapse
 
surajondev profile image
Suraj Vishwakarma

That's lot of time sometime

Collapse
 
redhap profile image
HAP • Edited

These fall under both categories:

  • Being forced to use the wrong tool for the job
  • Not getting good feedback during your career and having your legs kicked out from under you once you do get good feedback
  • Configuring JVMs and poor java app documentation
  • Too much meta magic in Python with too little documentation
  • ORMs that never support the database functionality you need
  • Programming practices that encourage poor resource utilization when using ORMs that mask the resource management.
  • Ignoring tweaks to existing technologies in favor of over-engineered solutions that are often difficult to setup, integrate, or end up brittle.

Some comments may only be visible to logged-in visitors. Sign in to view all comments.