Premissas para ler esse texto (se eh qeu alguem vai ler, ele é ENORMEEE):
Hacker = Hard Coder não o significado abrasileirado deste termo.
Muito interessante, principalemente algumas partes como:
[quote=“Talking about Boring Work”]
I think the same thing happened at Google. When Google was founded, the conventional wisdom among the so-called portals was that search was boring and unimportant. But the guys at Google didn’t think search was boring, and that’s why they do it so well.[/quote]
[quote=“Ótima definição para trabalhos Chatos!!!”]
So it’s not just fastidiousness that makes good hackers avoid nasty little problems. It’s more a question of self-preservation. Working on nasty little problems makes you stupid. Good hackers avoid it for the same reason models avoid cheeseburgers.[/quote]
Ahhhhhhhhhhh…
to sendo bonzinho demais… to colando as melhores partes… nossa muito legal o texto… imprima ai e deixe no banheir, sempre que puder de uma lidinha (idéia do Zampa hahahaha)
cara … aonde vc achou este artigo ?!? muito bom ! Não consegui ir dormir sem antes terminar de ler …
fui “obrigado!” a separar algumas partes para comentar …
confesso que senti “ofendido”, será q o autor tem algum trauma com Java ?
me identifiquei muito com a situação abaixo … preciso mudar de trampo urgente !!!
[quote]It’s pretty easy to say what kinds of problems are not interesting: those where instead of solving a few big, clear, problems, you have to solve a lot of nasty little ones. One of the worst kinds of projects is writing an interface to a piece of software that’s full of bugs. Another is when you have to customize something for an individual client’s complex and ill-defined needs. To hackers these kinds of projects are the death of a thousand cuts.
The distinguishing feature of nasty little problems is that you don’t learn anything from them. Writing a compiler is interesting because it teaches you what a compiler is. But writing an interface to a buggy piece of software doesn’t teach you anything, because the bugs are random. [3] So it’s not just fastidiousness that makes good hackers avoid nasty little problems. It’s more a question of self-preservation. Working on nasty little problems makes you stupid. Good hackers avoid it for the same reason models avoid cheeseburgers.
[/quote]
concordo plenamente com a citação abaixo, preciso de uma chance !
[quote]With this amount of noise in the signal, it’s hard to tell good hackers when you meet them. I can’t tell, even now. You also can’t tell from their resumes. It seems like the only way to judge a hacker is to work with him on something.
[/quote]
por incrivel que pareça, isso é o que eu sempre falo quando alguém me pergunta como me tornei programador … hehehe
[quote]The best hackers tend to be smart, of course, but that’s true in a lot of fields. Is there some quality that’s unique to hackers? I asked some friends, and the number one thing they mentioned was curiosity. I’d always supposed that all smart people were curious-- that curiosity was simply the first derivative of knowledge. But apparently hackers are particularly curious, especially about how things work. That makes sense, because programs are in effect giant descriptions of how things work.
[/quote]
flw, espero mais comentários sobre o artigo. Muito interessante …
Eu sinceramente achei que ninguem fosse ler!!!
Roger vc é um dentre Poucos Parabéns!!!
Quanto ao que vc falou das linguagens. (vou ser crucificado mas…) Eu acho que o autor está certo sim. Os melhores programadores de Java que eu conheço ou ouvi falar sabem principalmente, Perl e Python. É fato.
Como ele disse: Só faça trabalhos chatos se vc for passar fome!
hiaheiuhaue foda foda!!!
Mas é isso ai.
Bom Roger, acho que somos poucos dentre os que irão ler esse post, e quem sabe os únicos a comentar aqui.
Mas só digo uma coisa que leu não se arrepende, é bem legal!