Autor Tema: Silueta Billa Gatesa u Outlooku 2010  (Posjeta: 1775 )

0 Članova i 1 Gost pregledava ovu temu.

Offline Stjepan

  • Administrator
  • Jezerača
  • *****
  • Postova: 1909
  • Karma: +8/-2
  • Spol: Muški
Silueta Billa Gatesa u Outlooku 2010
« : Rujan 25, 2010, 02:56:50 poslijepodne »
Prazna silueta koja se prikazuje u Outlooku (People Pane) u slučaju kad nema slike za vaš kontakt je zapravo silueta Billa Gatesa koja je napravljena prema policijskoj slici iz vremena kad je zbog prometnog prekršaja uhićen u Novom Meksiku.

http://arstechnica.com/microsoft/news/2010/09/bill-gates-staring-back-at-you-from-outlook-2010.ars


Offline Sledgehammer

  • Jezerača
  • ******
  • Postova: 5157
  • Karma: +4/-3
  • Spol: Muški
  • oʞɐdoɐu šɐq ɯɐs sɐuɐp
Odg: Silueta Billa Gatesa u Outlooku 2010
« Odgovori #1 : Rujan 25, 2010, 03:13:56 poslijepodne »
Interesantne su mi te skrivene spike u Microsoftovim proizvodima - najčešće su skrivene u Wordu, no poznavanje mnogih kodova i shortcut-funkcija dovode te skrivene slike, pa čak i igrice, na svjetlo dana...
“Ja sam samo pas. I nemam svoj dom. A nemam ni glas. Ti mi moraš reći i ime i gdje ću naći svoju sreću kad zapuše bura ili padnu kiše. Ja sam samo pas. Pogledaj mi oči, dodirni me nježno, budi sve što trebam. Moj čovjek. Moj spas.”

Offline Stjepan

  • Administrator
  • Jezerača
  • *****
  • Postova: 1909
  • Karma: +8/-2
  • Spol: Muški
Odg: Silueta Billa Gatesa u Outlooku 2010
« Odgovori #2 : Rujan 25, 2010, 03:20:42 poslijepodne »
Je, te su fore poznate kao uskršnja jaja iliti easter eggs.

Npr. http://en.wikipedia.org/wiki/Easter_eggs_in_Microsoft_products

Čak su i neke web stranice posvećene tome, npr. http://www.eeggs.com/tree/153.html

Top lista: http://lifehacker.com/371083/top-10-software-easter-eggs

Ja trenutno najviše programiram u Pythonu koji u slučaju da kažeš import this odgovori u stihovima:

The Zen of Python, by Tim Peters

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!