About
Accounts
Friends
-
Loading…Pumpkineer 1 day ago -
Loading…resocjalizator 1 day ago -
Loading…Aluslaw 2 days ago -
Loading…radmen about 11 hours ago -
Loading…Abad 35 minutes ago -
Loading…pajlot 2 days ago -
Loading…ivyl 38 minutes ago
Click here to check if anything new just came in.
September 21 2010
September 14 2010
September 13 2010
September 05 2010
(stackoverflow) What is your best programmer joke?
Q: Why do programmers always mix up Halloween and Christmas?
A: Because Oct 31 == Dec 25!
A man flying in a hot air balloon suddenly realizes he’s lost. He reduces height and spots a man down below. He lowers the balloon further and shouts to get directions, "Excuse me, can you tell me where I am?"
- The man below says: "Yes. You're in a hot air balloon, hovering 30 feet above this field."
- "You must work in Information Technology," says the balloonist.
- "I do" replies the man. "How did you know?"
- "Well," says the balloonist, "everything you have told me is technically correct, but It's of no use to anyone."
- The man below replies, "You must work in management."
- "I do," replies the balloonist, "But how'd you know?"
- "Well", says the man, "you don’t know where you are, or where you’re going, you expect me to be able to help. You’re in the same position you were before we met, but now it’s my fault."
“Knock, knock.”
- “Who’s there?”
- (very long pause…)
- “Java.”
A SQL query goes into a bar, walks up to two tables and asks, "Can I join you?"
A young Programmer and his Project Manager board a train headed through the mountains on its way to Wichita. They can find no place to sit except for two seats right across the aisle from a young woman and her grandmother. After a while, it is obvious that the young woman and the young programmer are interested in each other, because they are giving each other looks. Soon the train passes into a tunnel and it is pitch black. There is a sound of a kiss followed by the sound of a slap.
When the train emerges from the tunnel, the four sit there without saying a word. The grandmother is thinking to herself, “It was very brash for that young man to kiss my granddaughter, but I’m glad she slapped him.”
The Project manager is sitting there thinking, “I didn’t know the young tech was brave enough to kiss the girl, but I sure wish she hadn’t missed him when she slapped me!”
The young woman was sitting and thinking, “I’m glad the guy kissed me, but I wish my grandmother had not slapped him!”
The young programmer sat there with a satisfied smile on his face. He thought to himself, “Life is good. How often does a guy have the chance to kiss a beautiful girl and slap his Project manager all at the same time!”
Saying that Java is nice because it works on every OS is like saying that anal sex is nice because it works on every gender.
A physicist, an engineer and a programmer were in a car driving over a steep alpine pass when the brakes failed. The car was getting faster and faster, they were struggling to get round the corners and once or twice only the feeble crash barrier saved them from crashing down the side of the mountain. They were sure they were all going to die, when suddenly they spotted an escape lane. They pulled into the escape lane, and came safely to a halt.
- The physicist said "We need to model the friction in the brake pads and the resultant temperature rise, see if we can work out why they failed".
- The engineer said "I think I've got a few spanners in the back. I'll take a look and see if I can work out what's wrong".
- The programmer said "Why don't we get going again and see if it's reproducible?"
A computer science student is studying under a tree and another pulls up on a flashy new bike. The first student asks, “Where’d you get that?”
- The student on the bike replies, “While I was studying outside, a beautiful girl pulled up on her bike. She took off all her clothes and said, ‘You can have anything you want’.”
- The first student responds, “Good choice! Her clothes probably wouldn’t have fit you.”
Programming is like sex: One mistake and you have to support it for the rest of your life.
A Cobol programmer made so much money doing Y2K remediation that he was able to have himself cryogenically frozen when he died. One day in the future, he was unexpectedly resurrected.
When he asked why he was unfrozen, he was told: "It's the year 9999 - and you know Cobol".

["hip","hip"]
(hip hip array!)
Once upon a time there was a shepherd looking after his sheep on the side of a deserted road. Suddenly a brand new Porsche screeches to a halt. The driver, a man dressed in an Armani suit, Cerutti shoes, Ray-Ban sunglasses, TAG-Heuer wrist-watch, and a Versace tie, gets out and asks the Shepherd:
- “If I can tell you how many sheep you have, will you give me one of them?”
- The shepherd looks at the young man, and then looks at the large flock of grazing sheep and replies: “Okay.”
- The young man parks the car, connects his laptop to the mobile-fax, enters a NASA Webster, scans the ground using his GPS, opens a database and 60 Excel tables filled with logarithms and pivot tables, then prints out a 150 page report on his high-tech mini-printer. He turns to the shepherd and says: “You have exactly 1,586 sheep here.”
- The shepherd cheers: “That’s correct, you can have your sheep.”
- The young man makes his pick and puts it in the back of his Porsche. The shepherd looks at him and asks: “If I guess your profession, will you return my animal to me?”
- The young man answers: “Yes, why not?”
- Shepherd: "You are an IT consultant."
- Man: “How did you know?”
- Shepherd: “Very simple. First, you came here without being called. Second, you charged me a fee to tell me something I already knew, and third, you don’t understand anything about my business…Now can I have my DOG back?"
Java programming is like teenage sex:
- Everyone talks about it all of the time (but they don't really know what they're talking about);
- Everyone claims to be doing it;
- Everyone thinks everyone else is doing it;
- Those few who are actually doing it:
--- Are not practicing it safely;
--- Are doing it poorly, and
--- Are sure it will be better next time.
September 03 2010
August 18 2010
I hope you fail!
I hope you have a personal project that you design wrong. I hope you get a runtime error that takes a long time to fix. I hope you get a nasty segfault that almost makes you lose all will.
I wish you numerous syntax errors and annoying memory leaks. I hope for tricky race conditions and terrible compatibility problems. I hope you need to rewrite a large portion of your code.
Why?
These are the building blocks of good programmers. We get the nasty errors and we learn from them. These errors get imprinted into our brain and we promise ourselves that we will never do them again, never to live through that horror.
After those errors, we can spot them a mile away, sometimes even before any code is written, and the more often we encounter these textual demons, the better programmers we become.
You can't learn programming by staying on the safe side of the fence, you need to jump over it, whip out your sword and start swinging. You don't know what to expect and you will get beaten down once in a while. But what separates a good programmer from a mediocre one, is that the good one stands up again, dusts off and remembers to duck next time.
So I wish you all the worst, and hopefully, you will live to tell the tale.
“— Going back to C - Story of a programmerWhen I was 12 someone gave me a Metrowerks IDE to learn programming on my mac. I learned a lot with it, and got programming in C. I never really wrote a large program in it, only things like ROM hacks that extracted levels and models from snes/psx games I liked. Later, I got a windows PC and messed around with MFC in C++. That was the end for me, programming UI's was too much work in C++ and I couldn't handle the encyclopedic knowledge needed to program the Microsoft framework.
Later, I learned Java, which was also the language most commonly in my college. Making UI's was a blast with it, I could factorize anything and really loved making as generic code as possible with it, even for small projects. Everything I made was made in Java.
Later in uni, I started learning functional languages, we used Haskell in one class. I got intrigued with Haskell and started solving Euler problems, up to this day I still have not written anything useful in Haskell but I love using it.
In the mean time I did some jobs for writing web sites. I used perl and php. After a while I only used php and used it more frequently.
After working for a while as a programmer I started to love higher-level languages, most of all Ruby. I became convinced that higher-level interpreted languages were the future because the slower execution times were to become meaningless. For any web projects I started using Ruby on Rails and to this day it still is my favourite framework.
Then, I learned Erlang because everyone was talking about it, and it showed me how to unleash parallellization, in whole new ways. I still think Erlang is the most amazing language I have ever seen. But then I found out it was also rather slow for the things I had in mind with it. I just didn't find any use for it and never completely learned the language.
Last week I wanted to make a big poster of a fractal. I wanted to compute it on a friend's octocore, and write a fast parallellized program. At first, I used Ruby, thinking it would perform better than I thought. And I quickly abandoned the idea because it was too slow.
Then I rewrote the same single-threaded algorithm in Haskell and saw that it was much, much quicker. But when I tried to parallallize it, I couldn't fathom how to do it in Haskell and abandoned the idea. I tried to write a parallellized version in Erlang, and while it spreak across the machine nicely, each individual process was way too slow, the parallellized algorithm was hundreds of times slower than the single-threaded haskell.
Because I really wanted that poster, I decided to switch to C because I had this idea that nothing could fail in C. And I started to code in a language I hadn't used for years, even a decade. And suddenly it hit me, everything made sense. Sure, I was writing so much boilerplate but it didn't bother me. I suddenly realized that everything I wrote would be inside the program's code, and that nothing more would. It was a great feeling.
I used simple pthreads to do the parallellization, and I used libgd to output my data to a png file. I started learning about mutex lock hierarchies to make the parallellizations overlap without endangering thread safety, it was all ugly code and the API's felt horrible compared to what I was used to.. but it all worked out. The resulting program was thousands of times faster than anything I had written.And now, I am seriously wondering where I have been all this time. Sure, I still think C is incredibly clunky. But now I got the dust off of my old course on writing compilers (Modern compiler implementation in C), and I want to write a compiler in C for a small programming language. I want to get down to earth again, and write things that are efficient and just run very quickly. I want to write lots and lots of code and know exactly what every line does.
”
“ Doing linear scans over an associative array is like trying to club someone to death with a loaded Uzi. ”— Larry Wall
“ A student who offered to have sex with anyone kind enough to complete her programming assignment has been at the centre of a scandal after her boyfriend found out about the affair and exposed her to students and faculty. ”— I wish I had such a colleague.
“ An even more impressive instance of remote debugging occurred on NASA's 1998 Deep Space 1 mission. A half year after the space craft launched, a bit of Lisp code was going to control the spacecraft for two days while conducting a sequence of experiments. Unfortunately, a subtle race condition in the code had escaped detection during ground testing and was already in space. When the bug manifested in the wild--100 million miles away from Earth--the team was able to diagnose and fix the running code, allowing the experiments to complete. ”— Peter Seibel
“ Dutch marriage rites require you to state your profession and I stated that I was a programmer. But the municipal authorities of the town of Amsterdam did not accept it on the grounds that there was no such profession. And, believe it or not, but under the heading "profession" my marriage act shows the ridiculous entry "theoretical physicist"! ”— from "The Humble Programmer" by Edsgar W. Dijkstra
“ beware of girls who talk about programming stuff like C++, Lisp, and Java. they take away your virginity. ”— quhaha on reddit
“ Walking on water and developing software from a specification are easy if both are frozen. ”— Edward V Berard
“ Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. ”— Rick Osborne
“ Perl - The only language that looks the same before and after RSA encryption. ”— Keith Bostic
“ If debugging is the process of removing software bugs, then programming must be the process of putting them in. ”— Edsger Dijkstra
Maybe Soup is currently being updated? I'll try again automatically in a few seconds...




Funniest source code comments