-- Access colleague system
-- Create a screen saver with an "Updating your Windows" snapshot.
-- Add shortcut key to start screen saver.

Anytime I noticed that they left their desk for a brief... I'll head up to their PC and press the key combination to start up the screen saver... Then return to my seat and put on my sorry face. 😒

No matter how many times I use it, I still have to look up how printf formatting works every so often...

*has a great company name idea*
*tries to register domain*
*domain taken*
*looks at whois*
*i already own it*
i don’t know how to feel

Does anybody know how to close this bottle? I can't figure it out.

Don't we all love a sophisticated chat bot?

When one of those "Your windows has been infected, click here to remove virus now" ads slips through the adblocker while I'm on my Linux

Being a dev by day and a simracer by night. I made a skin because I wanted to see what devRant would look like on a race car.

4 screens is better than 1.

NOTE: 4th Screen is Laptop Screen :)

CSS can kill you!

Once browsing through Google play store under what's new area of an app i found this:
*Removed bugs
*Added bugs to fix later

There seems to be a LOT of debugging going on...

Spaghetti wiring doesn't actually mean spaghetti coding. 😂

Same goes for my parents... lol

#Linux

"So, why do you want to work at our office in mexico?"
"I want to be a señor developer."

But that is my email....

6 hrs later still waiting.....
I think Microsoft uses a different measure of time.

Guess who said he will sleep at 11PM and now he scrolls DevRant at 4AM?

when eslint has had enough of your shit

Are you kidding me? 😂
This progress bar is the best

Arch guys !!

"Why isn't my code working????"

No words...

The pro puns here are beautiful

Every single time

How death comes...

The Top 20 replies by programmers when their programs do not work:

20. "That's weird..."
19. "It's never done that before."
18. "It worked yesterday."
17. "How is that possible?"
16. "It must be a hardware problem."
15. "What did you type in wrong to get it to crash?"
14. "There is something funky in your data."
13. "I haven't touched that module in weeks!"
12. "You must have the wrong version."
11. "It's just some unlucky coincidence."
10. "I can't test everything!"
9. "THIS can't be the source of THAT."
8. "It works, but it hasn't been tested."
7. "Somebody must have changed my code."
6. "Did you check for a virus on your system?"
5. "Even though it doesn't work, how does it feel?
4. "You can't use that version on your system."
3. "Why do you want to do it that way?"
2. "Where were you when the program blew up?"

And the Number One reply by programmers when their programs don't work:

1. "It works on my machine."

There are a lot of things that could rank up as the worst about being a dev, such as recurring meetings, documentation, shitty requirements, pm gnats, Monday, etc...but something that truly ruins it all is NO INTERNET CONNECTION.

We've all been there.

Simple way of storing keys.