managing geeks [modified]
-
Todd Smith wrote:
Good IT pros are not anti-bureaucracy, as many observers think. They are anti-stupidity.
Typical geek attitude: we are smart because we know a thing or two about computers, and everybody else is stupid.
Nemanja Trifunovic wrote:
Typical geek attitude: we are smart because we know a thing or two about computers, and everybody else is stupid.
The trouble is that the worst of them can't do a damned thing with a computer. They can only write code.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Nemanja Trifunovic wrote:
Typical geek attitude: we are smart because we know a thing or two about computers, and everybody else is stupid.
The trouble is that the worst of them can't do a damned thing with a computer. They can only write code.
I wanna be a eunuchs developer! Pass me a bread knife!
Have 5 for that observation - I see one of these every morning when I look in the mirror. Let me code, do NOT ask me to set up your network, do NOT ask me to build you a box. There are a fair percentage here who like faffing around with the hardware, me I have absolutely no interest.
Never underestimate the power of human stupidity RAH
-
Nemanja Trifunovic wrote:
Typical geek attitude: we are smart because we know a thing or two about computers, and everybody else is stupid.
The trouble is that the worst of them can't do a damned thing with a computer. They can only write code.
I wanna be a eunuchs developer! Pass me a bread knife!
Mark Wallace wrote:
They can only write code
... if given a detailed enough spec.
-
Mark Wallace wrote:
They can only write code
... if given a detailed enough spec.
-
Have 5 for that observation - I see one of these every morning when I look in the mirror. Let me code, do NOT ask me to set up your network, do NOT ask me to build you a box. There are a fair percentage here who like faffing around with the hardware, me I have absolutely no interest.
Never underestimate the power of human stupidity RAH
A guy here has a T-shirt: "No, I will NOT fix your computer". He won't sell it to me for any price.
I wanna be a eunuchs developer! Pass me a bread knife!
-
... to misinterpret whilst at the same time believing that they understand the customer's requirements better than the guy who wrote the spec (despite never having met the customer).
djgroves wrote:
... to misinterpret whilst at the same time believing that they understand the customer's requirements better than the guy who wrote the spec (despite never having met the customer).
"Why on Earth would anyone want to do it that way? It's obvious that encoding the stream to XML and editing it there is much more efficient." That's a quote from an e-mail about managing documents that are produced by business analysts. The guy could not believe that writing in XML text files and outputting directly to PDF was not the best way to do it -- despite the tiny fact that the guys are Business Analysts, who have no clue about XML, and who really don't want to have to build a PDF 300 times just to check that table column widths are OK. Oh, and they all have MS Office installed, and are very familiar with it. It quite literally took me years (2.5 of them) to kill the ridiculous XML-documentation-production project, and dregs of it still come up to haunt me.
I wanna be a eunuchs developer! Pass me a bread knife!
-
A guy here has a T-shirt: "No, I will NOT fix your computer". He won't sell it to me for any price.
I wanna be a eunuchs developer! Pass me a bread knife!
-
I have mine from ThinkGeek. Bought it, .. uhm maybe 10 years ago. ;P
-
djgroves wrote:
... to misinterpret whilst at the same time believing that they understand the customer's requirements better than the guy who wrote the spec (despite never having met the customer).
"Why on Earth would anyone want to do it that way? It's obvious that encoding the stream to XML and editing it there is much more efficient." That's a quote from an e-mail about managing documents that are produced by business analysts. The guy could not believe that writing in XML text files and outputting directly to PDF was not the best way to do it -- despite the tiny fact that the guys are Business Analysts, who have no clue about XML, and who really don't want to have to build a PDF 300 times just to check that table column widths are OK. Oh, and they all have MS Office installed, and are very familiar with it. It quite literally took me years (2.5 of them) to kill the ridiculous XML-documentation-production project, and dregs of it still come up to haunt me.
I wanna be a eunuchs developer! Pass me a bread knife!
lol. Just for that, I would start writing all my documents in notepad. Get fancy and add some ascii art! ;P
-
lol. Just for that, I would start writing all my documents in notepad. Get fancy and add some ascii art! ;P
One of my initial comments was that it would take too long to do all the process-flow diagrams, web & GUI screenshots, etc, in ascii art, but it went right over his head.
I wanna be a eunuchs developer! Pass me a bread knife!