Skip to content

F*cking programming

Yesterday I stumbled onto a delightful tool from Google Labs: Code Search.

Turns out Google is now crawling through source code. The GoogleBot, in its never-ending quest for sentience, searches inside tars, zips, and even dives into CVS and Subversion repositories. As Code Search is targeted at programmers, you can perform fantastically powerful queries using POSIX extended regular expressions.

Granted access to billions of lines of code and the awesome power of Google’s search technology, I did what any rational, thinking programmer would do: I typed in some profanity and hit enter.

In tribute to the valiant struggles of coders everywhere, please enjoy:

The best in programming profanity

/* We will NOT put a fucking timestamp in the header here.
Every time you put it back, I will come in and take it out again.
I’m sorry. This field does not belong here. We fill it with a 0 so
it compares the same but is not a reasonable time. */

/* Dear free software world, do you NOW see we are fucking
things up?! This is insane! */

# This job would be great if it wasn’t for the fucking customers.

/* Boy, would I like to make the thing expire one second ago, or what? Of course I would. But that slimy, stinking, load of pig manure that is called Netscape/1.1N doesn’t pay any attention to the seconds part of the time… after all, what’s a second or two amongst friends? So, I thought to make it expire one minute ago, but naturally, that didn’t work on 1.1N either. Losers. So, I made it expire 24 hours ago, which, if you ask me, is most heinous, considering the Last-Modified date could be later than that. I fucking hate you, you monopolizing piece of Netscape feces. */

# However, this only works if there are MULTIPLE checkboxes!
# The fucking JS DOM *changes* based on one or multiple boxes!?!?!
# Damn damn damn I hate the JavaScript DOM so damn much!!!!!!

# Trillian, again, is fucking stupid and crashes on just
# about anything its homemade XML parser doesn’t like.

/* TODO: this is obviously not right … this whole fucking module sucks anyway */

// gratuitous hack for Adobe SVG 3, what a fucking POS

/* if we get here, there are massive fucking problems, for a start our stack is fucked up, and we can’t return(). Just crash out. */

/* FIXME: please god, when will the hurting stop? Thus function is so
fucking broken it’s not even funny. */

/* XXX toshok why oh *why* god WHY did they do this? no fucking
sense */

# Note to self: I have no idea what this does anymore
# It looks like a cool fucking segment of code though!
# I just wish I remembered writing it… :-\

/* Outlook can’t fucking follow RFC if someone PAID them to do it…
oh wait, someone paid them NOT to do it. */

/* don’t fire dem packets too fucking fast */
usleep(1000);

## fucking imap fucking sucks. what the FUCK kind of committee of
## dunces designed this shit.

Fuck me gently with a chainsaw! Will someone please tell me how the fuck you resize a fucking widget?? Why, when I call whatever resize method I try with 64×64 does the fucking window end up 64×82? WHY???????? WHY???????? WHY???????? WHY???????? WHY???????? WHY???????? (why..?)

/* No we fucking don’t! DB entries should be stored in the same order
as they are in the file ! I can’t belive I was so fucking stupid !

# no, no, no, no, no, no, no, no
# no. fuck no. I am a fucking
# moron.

## aaahhh, user input. who would have though that such a simple
## idea would be SO FUCKING COMPLICATED?! because apparently
## Ncurses.getch (and Curses.getch), even in cbreak mode, BLOCKS
## ALL THREAD ACTIVITY. as in, no threads anywhere will run while
## it’s waiting for input. ok, fine, so we wrap it in a select. Of
## course we also rely on Ncurses.getch to tell us when an xterm
## resize has occurred, which select won’t catch, so we won’t
## resize outselves after a sigwinch until the user hits a key.
## and installing our own sigwinch handler means that the screen
## size returned by getmaxyx() DOESN’T UPDATE! and Kernel#trap
## RETURNS NIL as the previous handler!
##
## so basically, resizing with multi-threaded ruby Ncurses
## applications will always be broken.
##
## i’ve coined a new word for this: lametarded.

/* Sun, you just can’t beat me, you just can’t. Stop trying,
* give up. I’m serious, I am going to kick the living shit
* out of you, game over, lights out. */

/* Holy shit, we just updated more than one row!
What do we do now? */

/* 2,191 lines of complete and utter shit coming up… */

if (!(ptr = malloc (size)))
/* SHIT! SHIT! SHIT! */
die (“malloc failed”);

And my personal favorite:

# code below replaces code above – any problems?
# yeah, it doesn’t fucking work.

(Links are to the original sources)

Stay tough out there guys. Happy Monday.

86 Comments

  1. Shannon wrote:

    I did this recently too at http://www.koders.com (same idea), but the results were no where near as good.

    It’s a funny thing, swearing in comments, really gives you the introspective insight into the coder.

    Monday, December 17, 2007 at 10:28 am | Permalink
  2. Pickled wrote:

    A nice, eloquent snippet:
    656: /* This is the fucking modify account dialog. I’ve fucking seperated it into
    * three fucking frames:
    * a fucking Login Options frame, a fucking User Options frame and a fucking
    * Protcol Options frame. This fucking removes the two fucking tabs, which were
    * quite fucking uneccessary. Fuck. */

    Monday, December 17, 2007 at 10:33 am | Permalink
  3. Tim Jansson wrote:

    Haha, gotta love this :) Almost fumbled out of my chair!

    Monday, December 17, 2007 at 11:07 am | Permalink
  4. Lars wrote:

    Try http://www.krugle.org/
    It’s nearly the same and I like the ajax frontend.

    Programming is sometimes so desperate…

    I found:
    // a random number per tick
    static int st_randomnumber;
    // Massive bunches of cheat shit
    // to keep it from being easy to figure them out.
    // Yeah, right…

    Monday, December 17, 2007 at 11:12 am | Permalink
  5. Jon wrote:

    aaah, this is great.

    my coworker was prompted to go through my old code and found this:

    <html and shit>

    Monday, December 17, 2007 at 12:19 pm | Permalink
  6. jon wrote:

    Fantastic, I’m dying over here!

    Monday, December 17, 2007 at 1:21 pm | Permalink
  7. rick wrote:

    What’s great about the

    ” Sun, you just can’t beat me, you just can’t. Stop trying,…”

    is that it has a 1 in 4 chance of being written by Linus Torvalds. :)

    Monday, December 17, 2007 at 1:50 pm | Permalink
  8. ZenKai wrote:

    I do this all the time myself, usually with stuff like:
    $LeaveThisVariableSetTo1SoIE7DoesntFuckUp = 1;

    But some other great ones I’ve found:
    31: GODDAMN=`find . -name \*.pm -size 0`
    if [ "$GODDAMN" ]; then
    echo “Oops, some of the .pm’s didn’t get built properly!”
    ls -l $GODDAMN
    echo “Time to die. Goodbye!”

    You can HEAR this guy grinding his teeth:
    # Allow alphanumerics, plus the following:
    # : [ ] ( ) – _ ! . ? ‘ ” ^ * $ | / \
    # because people must have their goddamn smilies and so on. And
    # then of course there are characters for pseudonyms already in
    # the database (i.e., selectable from the popup — don’t want to
    # have something selectable from the popup but then invalid!).
    #
    # Well, now it’s almost the entire goddamn ASCII table, so who
    # cares?
    if( $text =~ /[^\w\s:\[\]\(\)\-_!\.\*\?\’\”^\$\|\/\\]/ ) return undef;

    Another Awesome one:
    /* WARNING – this routine depends heavily on the */
    /* fact that letters have been mapped into internal */
    /* right-adjusted ascii. god help you if you */
    /* have subverted this mechanism. */

    And another
    # Un-Goldy hack number #5 for the SuperCOSMOS catalogue, for some
    # bloody stupid reason they’ve decided to label their magntitudes
    # B_J, R_1, R_2 and I. God help me, if I ever find the guy responsible
    # for this stupid idea. For now lets munge these here and cross our
    # fingers.

    And my FAV (This is all one program)

    * IT A ‘PLOT’ COMMAND, (HE’S PLOTTING AGAINST US)

    * PRINT STATEMENT, LET’S OUTPUT SOMETHING SO HE WON’T GET UPSET
    * WHILE STAREING AT THE TUBE WONDERING IF WE DIED

    * IT’S AN ‘INPUT’, LETS GIVE HIM A CHANCE TO DO SOME TYPING.. BUT
    * KEEP AN EYE ON HIM, IN CASE HE TRY’S TO PUT SOMETHING OVER ON US

    * LOOK’S LIKE HE CAN’T EVEN ENTER A SIMPLE NUMBER, CLEAN UP ANY STACK
    * HE MAY HAVE USED, AND LET HIM TAKE ANOTHER BLIND STAB AT THE KEYBOARD

    * DIMENSION, HE WANTS SOME ARRAY SPACE.. I SUPPOSE WE SHOULD GIVE IT TO HIM

    * EITHER HE’S TRIED TO INDEX A NON-ARRAY VARIABLE, TRIED TO INDEX A CHARACTER
    * VARIABLE WITH A VALUE GREATER THEN 34, OR HE’S PLOTTED OUTSIDE OF THE SCREEN
    * NO MATTER WHAT HE’S DONE, GIVE HIM A NASTY MESSAGE SO HE WON’T DO IT AGAIN

    * IT’S A ‘USR’ COMMAND, FIND OUT WHAT HE WANT’S, PASS CONTROL TO
    * HIS MACHINE LANGUAGE ROUTINE, AND GOD HELP HIM IF HE SCREW’S UP
    * BECAUSE WE CAN’T DO ANYTHING FOR HIM UNTIL HE RETURNS

    * IF WE GET HERE, HE MADE IT BACK IN ONE PIECE

    * IT’S AN ‘ORDER’, (HE THINKS HE KNOWS WHERE THERE IS SOME DATA)

    Monday, December 17, 2007 at 2:10 pm | Permalink
  9. Pablo wrote:

    Don’t tell me any of you HAVEN’T ever sworn in your comments or error messages before?!!
    I’ve done this so many times that you’ll probably find some of my comments in the code search. Honestly; it’s especially when I’m fixing bugs and stupid browser or platform fixes that really annoy me do I start writing a pretty bitchy comment.
    Also, I swear in my error messages; like PHP/SQL error messages, because I don’t really expect my server to crash and not allow me to select my database, so I just write funny error messages with a hella lot of profanity. It makes the job a little more fun.

    Monday, December 17, 2007 at 3:17 pm | Permalink
  10. Nicholas wrote:

    Your lives would be easier if your attitudes were easier on each other, you know you are powerful and when you consistently powerfully destroy each other you all leave each other destroyed. Maybe no one has ever told this before but because you are powerful you might not want to associate with people that have those types of attitudes. It isnt good for you, it isnt good for them, and it isnt good for anyone really.

    You do really amazing work youve brought us this far , there is no such thing as a deadline, when you get around to getting it done, it will be just what it needs to be.

    Calm down and you might find your work will improve.

    nicholas
    1 513 312 5204

    Monday, December 17, 2007 at 5:42 pm | Permalink
  11. Galo wrote:

    Ha! GREAT STUFF!

    laugs all around.

    thank you

    Monday, December 17, 2007 at 6:05 pm | Permalink
  12. joeytomatoes wrote:

    Love This.

    Monday, December 17, 2007 at 6:41 pm | Permalink
  13. Rob Orsini wrote:

    I think it’s even funnier when you see these kind of comments in O’Reilly books! :)

    Look for yourself…

    http://labs.oreilly.com/code/

    Monday, December 17, 2007 at 7:21 pm | Permalink
  14. That is seriously the funniest fucking thing I’ve seen on the interwebs in a long, long time (and yup, we’ve all done it) — the people in this coffee shop probably think I’m totally out of my mind rolling around laughing and spitting on myself trying to keep quiet. wow, THANK YOU!

    Monday, December 17, 2007 at 7:25 pm | Permalink
  15. ilyas wrote:

    hahaha..LOL.
    this is fucking hilarious!

    Monday, December 17, 2007 at 10:31 pm | Permalink
  16. Robert wrote:

    Damn! My esteem for programmers just went way way up. It gives you a whole new perspective on the fucking applications I curse everyday when I see the blood sweat and tears that went into the code…

    Monday, December 17, 2007 at 10:54 pm | Permalink
  17. Hilarious! Thank you for making my day easier to bear now…

    Monday, December 17, 2007 at 11:19 pm | Permalink
  18. CLancy wrote:

    I just busted my gut laughing so hard, literally fell off my chair, got shooshed from the misses and woke up my kid!

    Tuesday, December 18, 2007 at 1:35 am | Permalink
  19. sharkgila wrote:

    Hahahaha. The frust behind all that.

    Tuesday, December 18, 2007 at 1:36 am | Permalink
  20. Martin B wrote:

    Its not just profanity that lurks in the depths of code, sometime its pure evil!

    …….

    Private Sub TheDarkFallenEvilEvilDuplicateMergeOfDoom666SatansLuciferSub(EnquirySQL, NonEnquirySQL, MatchSQL, MergeType)
    ‘ EVIL EVIL, infact SUPEREVIL routines for merging enquiry records into applicant records

    Tuesday, December 18, 2007 at 1:45 am | Permalink
  21. Preky wrote:

    Great post! Made me to remeber all stuff I wrote or tought about when was doing some things.

    Thx m8!

    Tuesday, December 18, 2007 at 2:05 am | Permalink
  22. Harry wrote:

    My girlfriend just came into the room to discover me crippled over on the floor in utter tears and I was only half way down the page. Then I had to have her read the rest out loud.

    Loved it all, but the fave is:

    /* 2,191 lines of complete and utter shit coming up… */

    Tuesday, December 18, 2007 at 3:35 am | Permalink
  23. Heather wrote:

    …hahahahahahahahahaha…

    Oh man. You just made my day. *wipes away tears*

    Tuesday, December 18, 2007 at 6:15 am | Permalink
  24. at first but now wrote:

    At first I thougth you were just a slow/late adopter, because google has had the code search thing for a long time now. But your take on it was refreshing and funny. This is the second time in a week reddit has pointed me to your site. Keep up the good work. This post made me LOL, laugh out loud — for those late adopters.

    Tuesday, December 18, 2007 at 6:24 am | Permalink
  25. Jan Wikholm wrote:

    Thanks for making my week! ;-)

    Tuesday, December 18, 2007 at 7:04 am | Permalink
  26. Albin wrote:

    /* FIXME: please god, when will the hurting stop? Thus function is so
    fucking broken it’s not even funny. */

    This is awesome.

    Tuesday, December 18, 2007 at 7:53 am | Permalink
  27. Joe Gutierrez wrote:

    Son of Bitch! I thought nobody would read my code.

    Tuesday, December 18, 2007 at 8:30 am | Permalink
  28. Carmack has had some great comments.

    Check the Quake source…

    Tuesday, December 18, 2007 at 9:21 am | Permalink
  29. Nic wrote:

    I remember finding a website that tracks the number of profanities in the linux kernel sources. Lol.

    Tuesday, December 18, 2007 at 4:38 pm | Permalink
  30. Hysterical. Leads to an interesting question: if you add comments like this into your code, they’ll definitely get read and people will spend the time to figure out what you are cursing, so would one consider this a possible best practice for programming? Most of them do explain why the code was written the way it was and some of them are quite entertaining…

    Paul.
    http://theprogrammersparadox.blogspot.com/

    Tuesday, December 18, 2007 at 9:21 pm | Permalink
  31. Interrobang wrote:

    I haven’t (yet) sworn in my help source (I’m a technical writer), but I have put my name in, and one page of the big help I’m currently working on has “Muahahaha” commented into it somewhere. Only the Holy Avatar of St. Joseph Ossanna knows where it is now; that help file is about 450 (fucking) topics…

    Wednesday, December 19, 2007 at 6:50 pm | Permalink
  32. teeni wrote:

    I wish now that I had been brave enough to leave those kinds of comments back when I was programming. LOL. I’ve been away from programming so long now though that comments are probably the only part of code that I still understand. heh. :)

    Thursday, December 20, 2007 at 11:57 am | Permalink
  33. Grizz! wrote:

    Not exactly a code comment, but I bet it wasn’t for the general public…

    I was shutting down a not-to-be-named UNIX machine, one of the last things it does is send a TERM (Please stop) signal to all running processes. Then it sends a KILL (I said, STOP!) signal to all running processes. All processes should be gone now and the box shuts down.

    Except this one I had:

    Sending all processes the TERM signal…
    Sending all processes the KILL signal…
    WARNING: Some processes refused to die!

    Thursday, December 20, 2007 at 2:30 pm | Permalink
  34. Anonymous wrote:

    Hey!! Found your blog on yahoo – quite some good info thanks but i still don\’t get it all, J.Sanders

    Thursday, December 20, 2007 at 3:22 pm | Permalink
  35. Ahhh, swearing, pretty much the only (f#cking comfort which us programmers are left with….

    Thursday, December 20, 2007 at 5:21 pm | Permalink
  36. Nancy Odell wrote:

    Hello…Man i love reading your blog, interesting posts ! it was a great Thursday .

    Thursday, December 20, 2007 at 8:37 pm | Permalink
  37. Moreeen wrote:

    Indeed, as Mr. Homer says above it’s definitely a programming “best practice” to emote severely and often as you suffer through fixing some knothead’s code, or convolute reality and subvert the potential for concise coding beauty to meet some psychotic customer’s requirements. Excellent post; thanks for ID’ing the tool.

    Thursday, December 20, 2007 at 9:17 pm | Permalink
  38. sikanrong wrote:

    OMFGROFL that shit almost has me crying!!

    Thursday, December 20, 2007 at 9:27 pm | Permalink
  39. Javier wrote:

    quickie search… can’t believe this did not make your list:

    ShitEntry::getShitLevel() const
    {
    return shitLevel;
    }

    Thursday, December 20, 2007 at 10:54 pm | Permalink
  40. Keith wrote:

    I did not realize Google was now crawling through source code.
    Google is a great search engine, but I am not ready for them to take over the world just yet!

    Friday, December 21, 2007 at 5:58 am | Permalink
  41. Leon wrote:

    This is funny as hell…

    hahaha..
    i like the “note to self guy”
    It’s happened to me, i just write some shit up.. then forget how it worked..

    nice compilation!

    Friday, December 21, 2007 at 11:35 am | Permalink
  42. Bill White wrote:

    You mean that’s not how it’s done?? :-)

    Friday, December 21, 2007 at 3:13 pm | Permalink
  43. now, that’s some funny stuff!

    Friday, December 21, 2007 at 3:47 pm | Permalink
  44. durk wrote:

    I wish I had reasons to swear so much in my code.

    Friday, December 21, 2007 at 4:17 pm | Permalink
  45. Jan Persson wrote:

    Boy that was sure a funny read…

    Saturday, December 22, 2007 at 11:49 am | Permalink
  46. Guitarman wrote:

    I’d like to see more of this :)

    Saturday, December 22, 2007 at 1:34 pm | Permalink
  47. Gareth wrote:

    My favorite comment involved the word “between”, but I mistyped it as “betweek” and that segment of code got copied into every program in the company. That was 20-years ago. Every now and again, I make the same typo… and I giggle to myself!

    Saturday, December 22, 2007 at 2:55 pm | Permalink
  48. Alex Leonard wrote:

    Heh. Some amusing comments going on there. I think I’ve always managed to refrain from placing any profanities in my code, although there have been some close calls when our mock-up design work included some gripes about a client and nearly got sent on to the client by accident.

    We stopped that pretty quickly!

    Besides, most of our clients are alright. There’s just a couple of ******* ;)

    Monday, December 31, 2007 at 8:44 am | Permalink
  49. CJ wrote:

    Amen brotha!

    Wednesday, January 2, 2008 at 11:49 am | Permalink
  50. susan wrote:

    This is hilarious. In an old DOS program where we had to do something called “skips” to print fields in the right place on the page, one day when I had to go into that code I found
    // I HATE FUCKING SKIPS
    // I HATE FUCKING SKIPS
    // I HATE FUCKIGN SKIPS
    I think the person who touched it last before me hated skips.
    My contribution was a little more subtle. In one part of the code was a variable named “YAF” which someone translated for me as “Yet Another Flag”. When I couldn’t re-use that, I added “YAFF” – yep – “Yet Another Fucking Flag”.

    Wednesday, January 2, 2008 at 6:54 pm | Permalink
  51. JoyFM wrote:

    Thats Fucking funny :D
    *rofl*

    Wednesday, January 9, 2008 at 4:36 pm | Permalink
  52. Heiko wrote:

    /* If for any reason in this lame world */
    /* this script doesn’t work */
    /* DON’T send me email */

    Thursday, January 10, 2008 at 5:58 am | Permalink
  53. adam wrote:

    This is pretty hilarious. gg.

    Thursday, January 10, 2008 at 8:25 am | Permalink
  54. nev wrote:

    How does Google get into commented PHP code ????

    Thursday, January 10, 2008 at 10:32 am | Permalink
  55. UI Hero wrote:

    This may sound like a developer’s version of an urban legend but I swear it’s true!

    I recall one freelance developer that was working on a Flash website for a movie starring Jennifer Lopez, an actress he obviously had a low opinion of. He inserted some *colorful* messages into his debugger output and assumed they’d never be seen. He delivered the website, billed it and it went live on the Internet.

    The next day, the studio was ringing his phone off the hook because they had been getting complaints about a variety of four-letter words showing up in people’s consoles. Yeah, some people out there in the “real world” have debug Flash players too.

    If your source is public, mind your tongue. Your grandmother may read your code one day. If your source is not public, mind your debugger output. Your grandmother may install a debug player one day!

    Thursday, January 10, 2008 at 6:18 pm | Permalink
  56. Donetsk wrote:

    Hi from Donetsk, Ukraine. I am leaving comment here just to say thank you for this site, I am looking forward to reading more posts, hope it goes well, all the best, Jay.

    Sunday, January 13, 2008 at 2:31 pm | Permalink
  57. Jon Peltier wrote:

    I laughed, I cried, I practically wet my pants. Hilarious.

    Friday, March 21, 2008 at 1:37 pm | Permalink
  58. brenda wrote:

    tried searching for “hate” ?

    Saturday, April 19, 2008 at 1:44 am | Permalink
  59. Xavier wrote:

    My all time favorite:

    // Drunk… fix later

    Tuesday, August 12, 2008 at 10:29 am | Permalink
  60. blueboy35 wrote:

    //set damage when I be shooted

    Wednesday, August 20, 2008 at 8:08 am | Permalink
  61. Donace wrote:

    lol hilarious man; gonna go and do some searches of my own…on code ofc not profanities!

    Saturday, August 23, 2008 at 9:21 am | Permalink
  62. wohali wrote:

    Links aren’t working for me :(

    Tuesday, September 2, 2008 at 6:45 pm | Permalink
  63. Stone wrote:

    wonderful think))

    Sunday, January 18, 2009 at 1:46 pm | Permalink
  64. Pink wrote:

    such a real story..

    Thursday, January 22, 2009 at 6:59 am | Permalink
  65. Daneila wrote:

    There si so interesting for us! Thanks!

    Tuesday, February 10, 2009 at 4:12 am | Permalink
  66. Andria wrote:

    Aamzing idea, grazie!

    Tuesday, February 10, 2009 at 8:57 am | Permalink
  67. Rinw wrote:

    Where can I obtain larger information about this theme, except codeulate.cm?

    Tuesday, February 17, 2009 at 4:25 am | Permalink
  68. Onensiove wrote:

    5 февраля компанией «Полисет-СБ» будет представлена комплексная система безопасности под названием «Экспресс». Данная демонстрация пройдет в Москве в Выставочном комплексе «Крокус Сити», ведь именно здесь в это время и будет проводиться выставка «Технологии безопасности», тематике которой «Экспресс» полностью соответствует.

    Monday, April 13, 2009 at 8:42 am | Permalink
  69. keemsfami wrote:

    Теперь я скажу несколько слов о подводке к дичи молодой собаки и о ее стойке.(В работе собаки по дичи следует различать 4 момента (подразделения) ее работы:

    1 — поиск, длящийся до того момента, как собака начнет причуивать признаки присутствия дичи в доступном для ее чутья расстоянии;

    2 — потяжку — работа собаки, разбирающейся в донесшемся до нее запахе до момента окончательного определения ею наличия дичи; эта работа заканчивается

    Wednesday, April 15, 2009 at 3:10 am | Permalink
  70. Dalam wrote:

    Where can i get this theme?

    Monday, June 15, 2009 at 11:26 am | Permalink
  71. Mamboris wrote:

    гут!сам частенько подобное придумываю…

    Friday, September 11, 2009 at 10:36 am | Permalink
  72. Autodot wrote:

    Нелохо получилось. Есть ещё что-нибудь из этой серии?

    Thursday, September 17, 2009 at 3:06 am | Permalink
  73. У меня однажды такая же ситуация было. Довольно-таки красиво

    Thursday, September 17, 2009 at 3:51 am | Permalink
  74. Красиво получилось… Не знаю как остальным, но мне нравится. Кстати, как подписаться чтобы мне на электронный ящик приходило, если кто-то ещё оставил комментарий?

    Thursday, September 17, 2009 at 4:16 am | Permalink
  75. Sterlimastiv wrote:

    Привет. Образовалась проблема – прикупил я электродрель на магазин ру
    А она сломалась у меня в тот ведь день – гарантии практически никакой не дали. Просто почта пришла с коробкой, а там все на китайском. Написал в торговый центр данный, дали ответ, что обращайтесь в сервис центр, но у меня ни документов на руках нет, ничего. Как можно приструнить этот онлайн магазин? Есть ли какие-то компетентные органы, что писать. Куда писать, кому писать. Сделал ошибку, да, нужно было в торговом центре нормальном прикупить, хотя нужной мне модели просто не было, да и подешевле в интернет-магазине. А вот теперь сижу у разбитого корыта. Подскажите, что делать.

    Monday, October 5, 2009 at 1:33 pm | Permalink
  76. Спасибо, много полезного почерпнул.

    Wednesday, October 7, 2009 at 10:59 pm | Permalink
  77. Отличный пост! Я читал с большим удовольствием. Теперь буду чаще посещать ваш блог.

    Friday, October 9, 2009 at 7:08 am | Permalink
  78. Anonymous wrote:

    огромное спасибо!

    Friday, October 9, 2009 at 8:32 am | Permalink
  79. Я конечно мало что смыслю в посте но постараюсь осилить.

    Wednesday, October 21, 2009 at 11:12 pm | Permalink
  80. Big thanks…)

    Tuesday, November 3, 2009 at 2:34 am | Permalink
  81. Selva Sp wrote:

    i have never laughed so much. Thanks for the post.

    Wednesday, November 4, 2009 at 10:32 am | Permalink
  82. Asert wrote:

    Graet Blog! Super!

    Sunday, February 21, 2010 at 4:28 pm | Permalink
  83. dan green wrote:

    Found what i was looking for!Thanks for the info guys!

    Tuesday, April 20, 2010 at 6:21 am | Permalink
  84. Coder wrote:

    Thanks for the source of profanity, I was reading these comments for a long time!

    Sunday, June 27, 2010 at 6:37 pm | Permalink
  85. parag_jecmca wrote:

    /* Holy shit, we just updated more than one row!
    What do we do now? */

    ooh my good …… plz kept doing update like this ….

    Monday, June 28, 2010 at 2:10 pm | Permalink
  86. James wrote:

    Hey if it gets people interested in technology it can only be good. Maybe we should put sex in the code too, that will get people reading it more for sure.

    Sunday, July 4, 2010 at 4:08 am | Permalink

35 Trackbacks/Pingbacks

  1. Speckz.com » F*cking programming on Monday, December 17, 2007 at 1:22 pm

    [...] out some of the comments GoogleBot found in source code. BTW, GoogleBot is not searching and indexing source code as well! A [...]

  2. [...] определённо, хит сезона суток — F*cking programming — google-поиск по открытым исходным кодам, перлы в [...]

  3. Adam Crowe - links for 2007-12-18 on Monday, December 17, 2007 at 5:35 pm

    [...] Codeulate – F*cking programming Haha! Google Code search reveals swearing in commented code. (We’ve all done it) /* 2,191 lines of complete and utter shit coming up… */ (tags: code comments google search funny) [...]

  4. [...] F*cking programming : Codeulate.: haha, this gave me a chuckle, i could definitely insert some of them in the code i’m working on now. [...]

  5. (Net.) product » Blog Archive on Monday, December 17, 2007 at 6:47 pm

    [...]  http://codeulate.com/?p=7 [...]

  6. Halting Problem » Blog Archive » Comments on Monday, December 17, 2007 at 7:38 pm

    [...] a blog post listing humorous occurrences of the word “fucking” in source code, courtesy Google’s Code Search. I found them hilarious — even if I don’t know the [...]

  7. links for 2007-12-18 « My Weblog on Monday, December 17, 2007 at 9:17 pm

    [...] F*cking programming : Codeulate. (tags: humor) [...]

  8. [...] F*cking programming : Codeulate. (tags: programming humor) [...]

  9. Mental Stability Log » Blog Archive » Comment Cursing on Monday, December 17, 2007 at 10:56 pm

    [...] Codeulate.com had a hilarious article about comments programmers make in their code. http://codeulate.com/?p=7 [...]

  10. roScripts - Webmaster resources and websites on Tuesday, December 18, 2007 at 1:15 am

    F*cking programming : Codeulate.

    F*cking programming : Codeulate.

  11. Chipping the web - peg out -- Chip’s Quips on Tuesday, December 18, 2007 at 6:40 pm

    [...] The best in programming profanity (thanks, Reg). [...]

  12. Now this is funny….. | My Random Thoughts on Thursday, December 20, 2007 at 7:24 pm

    [...] Codeulate posted about swearing in the comment of programs. I laughed. Knowing some of the issues my programmers have with code and debugging, I can imaging that some of these comments are in their code. I’m going to have to send this link to some of them. Ah the things we do when we don’t think anyone else will see. [...]

  13. Programmers Let Out Their Rage - We Honor Their Struggle | 13337 on Thursday, December 20, 2007 at 7:37 pm

    [...] programmers handled difficult problems.. Or just provide you material to laugh at. Codeulate has a great list of comment swearing. I gotta say, I'm guilty of this too, but at least my anger isn't usually revealed to the [...]

  14. mason garden » Programmer Potty-mouths on Thursday, December 20, 2007 at 10:20 pm

    [...] words on Google Code Search got old sometime last November, but Ben Orenstein has put together a hilarious collection of off color [...]

  15. rtaylor.info on Friday, December 21, 2007 at 4:29 am

    F*cking programming

    I often do this. Writing what I really think in my source code comments. I decided to search through some of my current employers source code and found the following gem:

    case “OptionSummary”:
        SetUpOptionSummary…

  16. hype.yeebase.com on Friday, December 21, 2007 at 3:42 pm

    F*cking programming : Codeulate.

    Mit Google Code Search interessante Komentare in Source Code finden. Jeder der Code dokumentiert wird den einen oder anderen Gedanken schon mal gehabt haben.

  17. Strubbl4Tokyopunk » Google Code Search - funny comments on Sunday, December 23, 2007 at 9:31 am

    [...] und was man dabei so findet: F*cking programming [...]

  18. hjays » Blog Archive » links for 2007-12-27 on Thursday, December 27, 2007 at 3:18 pm

    [...] F*cking programming : Codeulate. “Fuck me gently with a chainsaw” (tags: article blog blogs Culture development fuck fun funny geek humor humour list Nerds opensource programming Search software) [...]

  19. Kayak2U Blog » Blog Archive » Remember to comment that code… on Saturday, December 29, 2007 at 9:47 pm

    [...] now, apparently Google is doing its own code sniffing, and some of the things people have found in the comments are truly hilarious. MikeSoja – December 29, 2007 — 11:47 pm.  Filed under: [...]

  20. Coder Zone » Blog Archive » F*cking programming on Sunday, December 30, 2007 at 5:23 am

    [...] source AddThis var addthis_pub = ‘Jpjp’; ou Promouvoir via Additious   L’art de rompre | [...]

  21. Lunacy Lost » Blog Archive » Emotional Nerds on Friday, January 4, 2008 at 12:57 am

    [...] Often enough geeks and nerds are seen as not sufficiently expressing their emotions. But a look at their coding comments reveals a different picture [...]

  22. [...] F*cking programming: “Granted access to billions of lines of code and the awesome power of Google’s search technology, I did what any rational, thinking programmer would do: I typed in some profanity and hit enter.” [...]

  23. lte.cc » Blog Archive » lte.cc blog on Tuesday, January 8, 2008 at 1:46 pm

    [...]  Hier noch weitere Kommentare none [...]

  24. Aber auch lustig: -- zweitens-magazin.de on Monday, January 14, 2008 at 9:20 am

    [...] up… */ und ähnliche schöne Kommentare aus verschiedensten Programm-Codes gibt’s unter F*cking programming bei codeulate zu lesen, sogar mit Quellenangabe. « Jason Molina beim [...]

  25. [...] codeulate.com [...]

  26. Cool Content for Today : Zigzo Zlinks on Monday, January 21, 2008 at 3:28 pm

    [...] [LOL] The best of programming profanity [...]

  27. Fun with Google's Code Search | Charlotte Perl Mongers on Thursday, February 21, 2008 at 12:58 pm

    [...] Read more at http://codeulate.com/?p=7 [...]

  28. PTS Blog » Off Topic Friday on Friday, March 21, 2008 at 1:40 pm

    [...] F*cking programming [...]

  29. Yiyang’s Weblog » F*ck programming :) on Monday, April 21, 2008 at 12:47 pm

    [...] hahaha [...]

  30. [...] Sillybean, comes this wonderful link. (For programmers [...]

  31. [...] Ben typed in a bit of profanity — one would assume he started with the f-word in its present participle form — and got some great results. [...]

  32. Kod efter humör | PHP-kurs on Saturday, October 10, 2009 at 1:55 am

    [...] F*cking programming [...]

  33. Snarky and Amusing Comments Present in Palm webOS Code on Friday, March 5, 2010 at 9:31 am

    [...] present in Palm’s webOS code. While they aren’t as insane as the ones spotted by Codeulate (warning: NFSW), they are amusing and interesting in their own geeky way. While one developer [...]

  34. [...] present in Palm’s webOS code. While they aren’t as insane as the ones spotted by Codeulate (warning: NFSW), they are amusing and interesting in their own geeky way. While one developer [...]

  35. [...] http://codeulate.com/2007/12/fcking-programming/ http://www.kuro5hin.org/story/2004/2/15/71552/7795 [...]

Post a Comment

Your email is never published nor shared.