Highly recommended: the first 5 minutes of Dan North reading from the Book of Geek. Its funny and poignant:
In the beginning the software was without form, and void. The Architects said "Let there be light" and they separated the light from the darkness. And they called the light Architecture and the darkness Hacking.
And Maven brought forth a Plague of Apache Commons, and there was a flood of all the Libraries of the Internet as a judgement upon the people.
WELL THE Managers COME IN THESE PLACES
AND THE MEN ARE ALL THE SAME
YOU DON`T LOOK AT THEIR certifications
AND YOU DON`T ASK THEIR qualifications
YOU DON`T THINK OF THEM AS equal
YOU DON`T THINK OF THEM AT ALL
YOU KEEP YOUR MIND ON THE MONEY
KEEPING YOUR EYES ON THE Screen
[CHORUS]
I`M YOUR PRIVATECoder
A Coder FOR MONEY
I`LL DO WHAT YOU WANT ME TO DO
I`M YOUR PRIVATECoder
A Coder FOR MONEY
AND ANY OLD PC WILL DO
I WANT TO MAKE A MILLION DOLLARS
I WANT TO LIVE OUT BY THE SEA
HAVE An IPhone AND SOME IPods
YEAH I GUESS I WANT A Widescreen TV
ALL THE Managers COME IN THESE PLACES
AND THE MEN ARE ALL THE SAME
YOU DON`T LOOK AT THEIR FACES
AND YOU DON`T ASK THEIR NAMES
[CHORUS TWICE]
Swissfrancs OR DOLLARS
WTO or PBroker WILL DO NICELY - THANK YOU
LET ME LOOSEN UP YOUR processes
TELL ME DO YOU WANT TO SEE THE flipchart AGAIN
[CHORUS]
... now we are looking for a director to create the music video, the cast would be ready :-)
An Illustrated History of Failure is a very funny presentation about failures in software projects.
Thanks briankel for the recommendation (at the techtays presentation in Basel last week).
In the software industry we often use analogies from civil engineering. We use terms like "architecture" and "construction".
But there is a common claim that we should learn more from classical engineering disciplines like civil engineering. According to that claim the IT industry would be a better place if we would adopt best practices from the latter.
On the other hand there are sophisticatedexplanations why software projects cannot be compared to construction projects.
Now that's all nonsense! The following quotes show that we actually do adopt eagerly:
Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves.
If I remember correctly the topic of the discussion was about the topic if software engineering is really an engineering discipline or rather a craftsmanship:
Are you sure that what you do is software engineering? NASA is doing software engineering!
In commercial software the average cost for a line of code is estimated at 5$.
At NASA the average cost for a line of code is 5'000$.
They are not just Pair Programming, what they do could be called Swarm Programming!
"Humans and higher primates share approximately 97% of their DNA in common.
Recent research in primate programming suggests computing
is a task that most higher primates can easily
perform. Visual Basic 6.0™ was
the preferred IDE for the majority
of experiment primate subjects."
1842 - Ada Lovelace writes the first program. She is hampered in her efforts by the minor inconvenience that she doesn't have any actual computers to run her code. Enterprise architects will later relearn her techniques in order to program in UML.
This post joins the ranks of hilarious episodes of programming humor:
Today it was finally confirmed, that my journey to braindeadness was successful ... Im officially a Sun Certified Enterprise Architect for the Java Platform, Enterprise Edition 5 ...
Actually it was quite a challenge, because even though my brain was already proven dead, I had to personally ask Sun support because it was not confirmed on certmanager after six weeks ... supposedly there were technical problems preventing my automated step into zombie land ...
I wish I had already reached the next level of salvation, and could actually make sarcastic comments about my achievements... oh wait, did I just do that? ... braindead ...