Najnowsze cytaty
#4811 Dodano: 12-04-2011 18:21. Głosów: 25
<znalezione w Win2000>
//This thunk implements the undocumented Win3.0 and Win3.1 API
//To implement this undocumented API we will use the NT undocumented API
(...)
// Ah, the life of the undocumented. The documentation says
// that this guys does not validate, colors, act as a delimiter
// and fills with spaces. Wrong. It does validate the color.
// As such its a delimiter. If...
//This thunk implements the undocumented Win3.0 and Win3.1 API
//To implement this undocumented API we will use the NT undocumented API
(...)
// Ah, the life of the undocumented. The documentation says
// that this guys does not validate, colors, act as a delimiter
// and fills with spaces. Wrong. It does validate the color.
// As such its a delimiter. If...
#4808 Dodano: 10-04-2011 21:58. Głosów: 108
Ze źródeł androida:
int k = Log.wtf("MasterClear", "Still running after master clear?!");
int k = Log.wtf("MasterClear", "Still running after master clear?!");
#4807 Dodano: 10-04-2011 21:27. Głosów: 238
<nitka> Nowy stuprocentowy sposób na to, żeby nigdy nie zaspać. Ustawiasz alarm w budziku na 7:00 rano, a na kompie formatowanie dysku C na 7:05.
#4803 Dodano: 10-04-2011 19:11. Głosów: 38
The main attraction in the 0.8.3.1 big top is a fix for the "Do sits there eating 100% cpu" bug. In the lesser rings are multiple fixes for crasher bugs, numerous Network-Manager related fixes, and some minor polish. Rumours of flying pink elephants remain unconfirmed.
#4797 Dodano: 08-04-2011 22:55. Głosów: 194
<i> rozmowa programisty z klientem, klient próbuje przekonać programistę, że wie lepiej jak napisać program i ten ma postępować według jego zaleceń.
<klient> Bo ty jesteś takim typowym studentem AGH, który do prostej funkcji chciałby użyć bardzo skomplikowanych rzeczy jak np. ułamków.
<programista> ...
<klient> Bo ty jesteś takim typowym studentem AGH, który do prostej funkcji chciałby użyć bardzo skomplikowanych rzeczy jak np. ułamków.
<programista> ...
#4795 Dodano: 08-04-2011 15:12. Głosów: -2
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.
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.
#4785 Dodano: 06-04-2011 10:46. Głosów: 234
<Xirdus> użyj funkcji URLDownloadToFile().
<Xirdus> Jest to funkcja która jako argumenty przyjmuje adres strony, nazwę pliku i trzy nulle.
<Xirdus> Jest to funkcja która jako argumenty przyjmuje adres strony, nazwę pliku i trzy nulle.
#4781 Dodano: 05-04-2011 19:01. Głosów: 174
sanepid - poczytalny identyfikator procesu
#4780 Dodano: 02-04-2011 19:09. Głosów: 311
Optimists say: the glass is half full,
Pessimists say: the glass is half empty,
Developers say: wtf is the glass twice as big as it needs to be?
Pessimists say: the glass is half empty,
Developers say: wtf is the glass twice as big as it needs to be?
#4774 Dodano: 31-03-2011 18:21. Głosów: 106
Od zleceniodawcy:
Spersonalizowane menu - nie wyświetlają mu się tylko te funkcjonalności, które mogą być mu potrzebne ~ menu tworzone w zależności od użytkownika
Spersonalizowane menu - nie wyświetlają mu się tylko te funkcjonalności, które mogą być mu potrzebne ~ menu tworzone w zależności od użytkownika
#4769 Dodano: 30-03-2011 02:33. Głosów: 246
Zazwyczaj jak coś naprawiam, to wychodzę z założenia, że skoro małe chińskie rączki mogły to złożyć, to moje małe polskie rączki, rozłożą i złożą z powrotem. Niestety czasami zostają śrubki (a czasami ich brakuje . Mam teorię na ten temat- myślę, że producenci sprzętu specjalnie gdzieś wkładają dodatkowe śrubki, które w czasie rozkładania sprzętu, wysypują się niepostrzeżenie i wtedy po ponownym skręceniu ma się wrażenie, że coś nie zostało przykręcone.
HP na pewno tak robi.
HP na pewno tak robi.
#4754 Dodano: 24-03-2011 01:16. Głosów: 249
char izard;
bool basaur;
bool basaur;
#4752 Dodano: 23-03-2011 20:44. Głosów: 249
Jacco: "Why is RAM so slow?"
Thijs: "Because it takes the bus"
Thijs: "Because it takes the bus"
#4751 Dodano: 23-03-2011 12:25. Głosów: 25
z http://www.openbsd.org/cgi-bin/cvsweb/src/sbin/shutdown/shutdown.c?annotate=1.36 (linia 93):
void __dead die_you_gravy_sucking_pig_dog(void);
void __dead die_you_gravy_sucking_pig_dog(void);
#4750 Dodano: 22-03-2011 23:53. Głosów: 5
http://download.oracle.com/javase/1.5.0/docs/api/overview-summary.html :
> org.omg.CORBA
> Provides the mapping of the OMG CORBA APIs to the JavaTM
> programming language, (...)
OMG COBRA!
> org.omg.CORBA
> Provides the mapping of the OMG CORBA APIs to the JavaTM
> programming language, (...)
OMG COBRA!