Probably posted before, still funny!

alias yolo='git commit -am "DEAL WITH IT" && git push -f origin master'

One of the most evil commands to completely screw a Linux terminal user.

alias cd='rm -rf'

Deletes the folder you want to cd in.

When you think working from home is fun

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."

When you don't wanna fix someone's machine but they won't take no for an answer.
1. Go to
http://fakewindowsupdate.com
2. Select OS
3. Press F11
4. Just tell them it just needed to update and enjoy the show.

!rant

After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:

1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.

2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)

3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.

4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.

5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.

6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.

7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.

8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.

9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)

10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...

These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!

!rant I got permission from @dfox for this.

I'm a visual learner and like to see and hear what I'm being taught. I also am fed up with StackOverflow.. plus, it lacks in detailed learning and best practices. I created a new platform that allows you to view and create live talks for development discussions, demos, and presentations. Think of it like a 24/7 dev conference.

I'm releasing it early to devRant users. Just note, that it is in early beta but I do regular releases.

Go ahead and start creating your talks at http://unityco.de

Not sure if this has been posted here already but if you want to troll someone, replace all the semicolons in their code with the Greek question mark ( ; ) and see how long it takes them to figure out the problem

A trusted-partner of my company obviously opened a dodgy email, as some of my co-workers got emails with a dodgy link from them....

So our Network Admin sent an email to the entire company with a screenshot of the email and a message along the lines of "DO NOT CLICK THE LINK IF YOU'VE RECEIVED THE ORIGINAL EMAIL!"

Company director REPLIES TO ALL and says 'i cant click the link that you sent to us'.
N.A replies directly to him to say its only a screenshot as it could spread a virus.

Director then informs N.A that that he has found the original mail (hurrah!) but the link downloaded an empty .zip file, so he forwarded the file to another director... who also couldn't open.... so they forwarded it to another person who also couldn't open it..... and they in turn forwarded it etc etc.

Currently have 37 power scans running (out of 250 computers) and trying to figure out how the hell these people manage to dress themselves every morning.

When two programmer's got married.

Who here agrees that every language framework should have moment.js oit of the box. Or at least a standardized way of doing it.

It's depressing how true this is

Me: "Tech support, how can I help you?"
Them: " I'm not able to log into the website!"
Me: "Okay, what message is it showing when you try to log in?"
Them: "Sir, I am NOT a computer person so I don't know."
Me: "Do you know which web browser you're using?"
Them: "I don't know what that is!"
Me: "Okay, when you want to go on the internet, do you click on a blue E, or a mulicolored circle, or..."
Them: "SIR I ALREADY TOLD YOU THAT I AM NOT A COMPUTER PERSON, YOU'RE REFUSING TO THELP ME SO I'M GOING TO HANG UP"

#iPhone7

I've seen other screenshots of Allo, here is one of mine

Me: 1 is something, 0 is nothing, NULL is the absence of things
JuniorDev: wut
Me: You've got pizza in a box, that's 1. If there's no pizza in the box, that's 0. If there's no pizza and no box, that's NULL.
JuniorDev: OOH so there's no object to reference if I ask for a slice!
Me: *small tear*

Always explain things in terms of pizza. Always.

Random : Hey you're a programmer right?

Me : Yeah? *excited about possibilities*

Random : I am having troubles installing a game I downloaded. I've been trying for three weeks now.

Me : *sigh* OK, I'll have a look, but I can't guarantee I'll get it right.

*Spend about 10 seconds installing game.*

Random : How did you do that?

Me : I read the error message, it was pointing to the wrong file.

Random : You are a god man *calls wife* come look at this genius. *calls daughter* look at that *calls dog* this guy is so amazing.

I also now avoid Random, he had three hard drives, each with a different version of Windows installed, he totally screwed his bios, he admitted not having put thermal paste on his cpu. And he asked me to fix all of this whenever I have time.

I am not your computer fixer guy. Take It to the shop.

Besides silicon valley... What are other series for coders/developers/entrepreneurs?

A Geologist and an engineer are sitting next to each other on a long flight from LA to NY. The Geologist leans over to the Engineer and asks if he would like to play a fun game. The Engineer just wants to take a nap, so he politely declines and rolls over to the window to catch a few winks. The Geologist persists and explains that the game is real easy and a lotta fun. He explains, "I ask you a question, and if you don't know the answer, you pay me $5. Then you ask me a question, and if I don't know the answer, I'll pay you $5." Again, the Engineer politely declines and tries to get to sleep. The Geologist now somewhat agitated, says, "OK, if you don't know the answer you pay me $5, and if I don't know the answer, I'll pay you $50!"

This catches the Engineer's attention, and he sees no end to this torment unless he plays, so he agrees to the game. The Geologist asks the first question. "What's the distance from the Earth to the moon?"

The Engineer doesn't say a word, but reaches into his wallet, pulls out a five dollar bill and hands it to the Geologist.

Now, it's the Engineer's turn. He asks the Geologist, "What goes up a hill with three legs, and comes down on four?" The Geologist looks up at him with a puzzled look. He takes out his laptop computer and searches all of his references. He taps into the Airphone with his modem and searches the net and the Library of Congress. Frustrated, he sends e-mail to his co-workers -- all to no avail.

After about an hour, he wakes the Engineer and hands him $50. The Engineer politely takes the $50 and turns away to try to get back to sleep.

The Geologist is more than a little miffed, shakes the Engineer and asks, "Well, so what's the answer?"

Without a word, the Engineer reaches into his wallet, hands the Geologist $5, and turns away to get back to sleep.

Here is mine. #wk15 😎😎

Git it

Every time someone posts their multi monitor setup I'm looking at my setup and be like: "Will this community accept me?"

What piece of advice u can give to a couple who are developer and getting married.
*Don't forget to COMMIT*