It was one of the tiring day after work and all I wanted to go back and sleep. Which is what I did that day. I woke up the next morning with missed called from the office.
It would mean something broke and people needed everyone on call. I went to the office to enquire and was told that our requirement portal was getting huge amount of traffic on the web server. Apparently everyone thought that it was being DDOSed. All the network and tech "architects" came in to participate all excited about it.
Some rogue IPs were detected. People tried blocking it all at night.
Eventually after hours it was found that the load balancer was malfunctioning and other traffic was legit.

P. S: I do not know the details of the issue. Please dont ask.

Can we all stop using windows at schools and get back to Linux when we are taught c and c++ in colleges. Turbo c sucked.

When I ask how did you get the virus in your system.

1. My DataStructure teacher taught us the whole subject without a single code snippet.
2. I once had to sit and code in front of the teacher to prove that I did write the code this fast.
3. The first lab in CS bachelor's started with "This is monitor, mouse and cpu. The button in cpu switches it on". Some people still stood clueless there.

Step one:
Change their prompt.

# put this in their .bashrcexport PS1="Login: "

Step two:  
Add an alias for their username, and for any other account names they might try logging in as, for example, 'root'.

# put these in their .bashrc too:aliasjoe='stty -echo; echo -n "Password: ";read;echo;echo "Login failed.";stty echo'aliasroot='stty -echo; echo -n "Password: ";read;echo;echo "Login failed.";stty echo'

Step three:
Try not to laugh your head off, as they struggle.

Login: joePassword:Login failed.Login: joePassword:Login failed.Login:Login:Login: rootPassword:Login failed.Login:Login: pwd/home/joeLogin:

Truly devious folks may want to explore setting the "command-not-found" hook to prompt, read, and echo "Login failed" rather than using various aliases.  You can combine that with changing the PATH to be "/" or some other directory which is devoid of executable programs.

That doesn't cover every case - your victim could still, for example, run /usr/bin/vim or similar - but it goes sufficiently further that I'll omit the implementation for moral reasons.

Me after everytime people merge in.