10 Hilarious Cartoons That Depict Real-Life Problems of Programmers

This content originally appeared on DEV Community and was authored by Pratik Chaudhari

And how they deal with them...

1. Estimations:

Estimating the amount of time required to complete your own work is nothing short of a herculean feat.

But the fun begins when you add more people to the equation.

Then estimating becomes a sport of throwing darts (and that too in the dark):

Image Credit: workchronicles.com

2. Fixing Bugs:

Humans prefer immediate gratification, which means we choose to indulge (or invest) in activities that could provide us with immediate rewards while conveniently overlooking the (heavy) price we may have to pay in the future.

But when we do this in our workplaces, we might not be ones paying the price in the end:

Image Credit: workchronicles.com

3. Dealing With Ambitious Sales Rep:

Sales representatives have targets to meet. We understand that.

But when some overzealous sales rep promises the moon to the clients, programmers are the ones who bear the burnt:

Image Credit: workchronicles.com

4. Socializing:

"Blessed are the Geek, for they shall reign over the world."

The Tech industry has had a tremendous impact on our lives: people can look up anything on Google and hook up with anyone on the likes of Tinder and Bumble.

As people who built the tech industry, we are its Alpha & Omega.

And yet, when it comes to in-person interactions and shaping conversations, we are at a loss for words:

Image Credit: workchronicles.com

5. Finding a new Job:

There are literally hundreds of websites out there that promise to join a potential employee and an employer into holy matrimony 😂

But none of them can help you escape recruiters who sound more like sales reps. Deciphering the actual meaning behind their words is somewhat of an arcane art:

Image Credit: workchronicles.com

6. Feature Requests:

"The 'stories' feature is so popular on the XYZ app. We should introduce it too."

"What if our users could find a date, book a cab, and rent a villa in Europe all at the same time?"

And so goes the discussion about the new features that we could provide to our users.

We understand that there's a need to experiment and evolve, but adding a feature just of the sake of adding it is not cool:

Image Credit: workchronicles.com

7. Status Updates:

The daily stand-up meeting in Agile is an excellent way for the team to discuss the overall progress on their work and any impediments that might be blocking them.

But once we are done with that, we are literally done with the status updates.

There was no substantial progress on that "critical" feature five minutes ago and there won't be any five minutes from now:

Image Credit: workchronicles.com

8. Showing off Our Work:

We are geeks. Many of us are introverts. Not all of us like announcing our work out loud to the entire world.

But that doesn't mean we aren't working hard enough or that we aren't worthy of a well-deserved promotion:

Image Credit: workchronicles.com

9. Getting Our Priorities Right:

Product Managers, please understand this:

If all the features are on priority, then none of them are on priority:

Image Credit: workchronicles.com

10. Meeting (Unrealistic) Expectations:

Need I say more:

Image Credit: workchronicles.com

(Okay, I admit this one's not specific to programmers, but it nevertheless depicts a chilling reality)

I hope you folks enjoyed reading this blog!

Feel free to leave your comments (if any) in the comments section below 👇

This content originally appeared on DEV Community and was authored by Pratik Chaudhari