Adventures of a Computer N00b: This Code is Rated PG-13

Notice: If swearing offends you please avoid this post!

Have you ever had that day where the program you are working with is just not working. You've gone through restarts and trouble shooting, trying everything you can to get it to work and it just won't. Sometimes it's not the program and it's a coworker. They're asking questions you already answered. They are calling you about an email they sent just one minute ago to verify you got it instead of setting up a read request. As frustration builds sometimes we lash out quietly by typing or writing a quick note telling the program, co-worker, or boss exactly what we think of them before erasing it and completing our work.

This type of frustration happens often in the workplace and no one is immune to it. Even programmers, the fun thing for programmers is they get to write out their complaints in the code. Any programming language offers a way for the programmer to comment on the code they are writing. I'm sure as you can imagine from your own experience, there are days when the project a programmer is working on will just not work right. Sometimes something was done to the code to mess it up; or they forgot a piece of the code to make it work. A programmer might leave a snarky comment to let the program know exactly what they think of it at that point in time.

This is where the fun comes in, my research for a future post lead me to a neat little trick. If you go into your command line and type grep (insert swear word here) -R /usr/; you will see all of that specified swear word in the code of your programs. You can add on other files after /usr/ going through each individual file but I found this was the most effective way. Here is a screen shot of the command and some of the results that I found by switching up the swear word.