(dyskusja pod artykułem o błędzie w oprogramowaniu Apple)
<Ben L.> It's not so much a problem of with braces or goto, but more that they copied and pasted code too many times.
<gu3st> Samsung is gonna copy this bug in about 2 weeks.

http://forums.thedailywtf.com/forums/p/30999/356694.aspx

(post @ bbs.archforum.org)
As always, the Ubuntu devs interfered into a big Linux project (like GNOME for example) and created a mess.

Those guys should be banned from connecting to the internet.

//Dis function is used for takin’ your 3-dimensional array as a pointa to 2-dimensional array.

//WAAAGH!

unless ENV['fuck_sopa']
require 'rack/sopa'
config.middleware.use('Rack::Sopa')
end

Z https://github.com/travis-ci/travis-ci/commit/31c453c59d532109a7491ffedcf2c9df649415a6

Wchodzi przerzutnik RS do lasu i się zakleszczył

Stary matematyk nie umiera. On tylko osiąga punkt stały.

zrzut z sysloga:

+pid 39623 (smbd), uid 0: exited on signal 6
+pid 39624 (smbd), uid 0: exited on signal 6
+<<66>>ppiidd 4547285 72(7 (ssmmbbdd)),, uuiidd 0:0 ex:i teexdi toend soing nsailg n6a
+l
+ 6
+pid 45761 (smbd), uid 0: exited on signal 6
+pid 45762 (smbd), uid 0: exited on signal 6

Jest tak zimno, że nawet samba zaczyna się jąkać i gadać od rzeczy

Kobiety dzielimy na dwie grupy: jedne są homeomorficzne z kulą, drugie z torusem. Te pierwsze nie noszą kolczyków...

die('bitch');

Pewien profesor kazał sobie wszyć w spodnie zamiast zamka błyskawicznego suwak logarytmiczny - aby łatwiej mu było wyciągać pierwiastek.

The [UNIX] pipe is not perfect though, for it is unable to prevent people from inventing Perl. (...) -- ZhaoWay

- Dlaczego izopropanol staje w gardle?
- Bo ma rozgałęziony łańcuch...

<bastetmilo> Czy Wy wiecie gdzie ja jutro będę o tej porze?
<Voldenet> Wiemy.
<Voldenet> Ale nie będę Ci psuł niespodzianki

Here are some handy tips to make sure your team hates you and your project runs into serious trouble:
Make sure you don’t give your team enough time to do the work, and then blame them for not getting it done on time.
Routinely ask people to stop working on whatever they’re doing right now to take care of urgent emergency work.
Then utterly fail to follow up on that urgent emergency work.
Never let anyone on your team release anything or even talk to a user without giving it to you to look over first.
When they give you that work, make sure you send it back with a whole lot of vague and poorly thought-out changes – but make sure you don’t give any extra time to make them.
In fact, try to constantly find many small changes that your team should make, just to keep them on their toes.
Your team needs constant attention! If it’s been more than two hours since you’ve talked to someone on your team, drop by and tap one of them on the shoulder and ask for an update.
All organizations run on status. If the status updates stop flowing, a company can crumble and perish! Also, developers feel lonely if they haven’t given a status update in the last few hours. So make sure everyone has to fill out elaborate status reports, and make sure you hold at least three two-hour-long status meetings every week.
Did someone on your team do something differently than how you would do it? Reprimand them! They might tell you that it works just fine, and that their way is just as good. But it’s not your way, so it’s not right.
Remember: reading your mind is part of every team member’s job. That’s how they stay proactive!

Most of all, though, remember rule #1: Nobody is ever allowed to make mistakes! If a developer makes a mistake, it reflects badly on you, and the whole team suffers. Never admit that you were wrong about anything. If you said it once, it’s now the law and should never be questioned.

[Perl] combines the power of C with the readability of PostScript. - Jamie Zawinski