<sxrp> nobody is older than 1.01.1970
<sxrp> it's physically impossible
<@rocx> If they are, that's an epoch fail.

<Art> Będzie taka impreza, że wszystkie firewalle w okolicy wysiądą

"alfabet" informatyka:

a.. Dopóty dysk dane nosi, póki mu bootsector nie padnie.
b.. Jeden Celeron kompa nie czyni.
c.. Nie wywołuj przerwań z BIOS-u.
d.. Mądry Polak po errorze.
e.. Jak trwoga to do serwisu.
f.. Nie wszystko dioda co się świeci.
g.. Gdzie dysków sześć tam dużo formatowania.
h.. Komu w drogę temu laptop.
i.. Na twardzielu dioda gore.
j.. Co dwie kopie to nie jedna.
k.. Nie taki deamon straszny jak go killują.
l.. Tam gdzie deamon mówi shutdown.
m.. Z próżnego i recover nie odzyska.
n.. Tapetka z RAMu, Windows hej!
o.. Nie resetuj drugiemu, co tobie nie miło.
p.. Co wolno Adminowi, to nie Użytkownikowi.
q.. UPeeSy strzelają, Admin baty znosi.
r.. Nie chwal systemu przed pierwszym padem.
s.. Ciągnie się jak backup nad ranem.
t.. Gdyby Pani nie skakała, to by kabli nie wyrwała

<Orzech> studia na polibudzie sa jak wojsko, najpierw calkuj potem zadawaj pytania

A distributed system is one in which the failure of a computer you didn’t even know existed can render your own computer unusable.
— Leslie Lamport

Mój wydział właśnie wymyślił nowy system zapisu danych - według informacji na stronie plan w PDF ma 91.4990234375 kB

(analizując niemiecki CMS w PHP, z niemiecką dokumentacją)
<X> nie dziwię się, że Wanda rzuciła się do Wisły

- Why did the mathematician name his dog "Cauchy?"
- Because he left a residue at every pole.

//konstruktor
assert(instanceCount == 0, "This was meant to be a singleton, but I didn't want to write all the code. Since somebody has already created an instance of this class, you'll have to ask him for a pointer.");

instanceCount++;

// komentarze spod pytania na stackoverflow.com

Anarkie: I should be using the char *, since the Prof doesn't want std::string to be used.
Griwes: Why do all those stupid professors teach all the things the wrong way?
Robᵩ: @Griwes - They insist on teaching the difficult fundamental concepts before the easier, more reliable derivatives. Like how we teach teenagers how to distill gasoline from crude oil before they can get a driver's license. Or how we teach electricians to mine copper ore.

egoizm:

i > u

If you wrote chat messages and emails to another girl, on your girlfriend's computer, you can't be sure the files you deleted are unrecoverable. But you can make sure if anyone were to recover them, that you wouldn't get busted.
Code:
dd if=/dev/sda | sed 's/Wendy/Janet/g' | dd of=/dev/sda
Where every instance of Wendy is replaced by Janet, over every millimeter of disk. I picked names with the same number of characters, but you can pad a smaller name with blanks.



// za http://www.linuxquestions.org/questions/linux-newbie-8/learn-the-dd-command-362506/

canPlayType returns one of three values:
1. probably,
2. maybe, or
3. “” (the empty string).

http://html5doctor.com/html5-audio-the-state-of-play/

post z r/lolphp:

0x0 wat by Altreus (self.lolphp)
>>> 0x0 +2
4
>>> 0x0 +3.5
6.5
>>> 0x0 +2e1
757
:|

Here is an explanation I was provided with:
<mauke> once their lexer detects "0x", it skips all '0's, then calls strtol()
<mauke> so: tokptr = "0x0 +2;", toklen = 3
<mauke> skip 0x: tokptr = "0 +2;", toklen = 1
<mauke> skip all '0's: tokptr = " +2;", toklen = 0
<mauke> call strtol(" +2", NULL, 16) ==> 2
<mauke> then it proceeds to parse the remaining program starting from " +2;"
because that's where the previous token ends
<mauke> and this is how 0x0 ends up having the value 2
<mauke> 0x0 +2e1 ends up being 757 because the first pass interprets 2e1 as a hex integer
while the second pass thinks it's a floating point number
<mauke> so it's really 0x2e1 + 2.0e1

Programmers don't byte, just nimble a bit