Slashdot Mirror


Are Quirky Developers Brilliant Or Dangerous?

jammag writes "Most developers have worked with a dude like Josh, who's so brilliant the management fawns over him even as he takes a dump in the lobby flowerpot. Eric Spiegel tells of one such Josh, who wears T-shirts with offensive slogans, insults female co-workers and, when asked about documentation, smirks, "What documentation?' Sure, he was whipsmart and could churn out code that saved the company millions, but can we please stop enabling these people?"

1,134 comments

  1. brilliant or dangerous? by p3on · · Score: 5, Insightful

    why are the mutually exclusive?

    1. Re:brilliant or dangerous? by tgatliff · · Score: 5, Insightful

      Exactly... To the average layman, the thought of a "Dr House" type principle always applies. For the people who actually do high end development or research work, however, they realize that intelligence is only useful if the person can work with other people or can effectively communicate his work. Also, documentation of that work is essential...

      In short... it is only mutually exclusive if you are in a room full of a bunch of business MBAs who apparently as a whole still think that solutions come out of some magic hat somewhere...

    2. Re:brilliant or dangerous? by Trifthen · · Score: 4, Insightful

      I was going to moderate this "funny," but thought the same thing myself. My answer to the OP's question was "Yes." Because anyone, really, can be these things, and we need to stop with the fallacy that only IT people can be self-absorbed assholes.

      Anyone can be brilliant. Anyone can be a jerk. Sometimes these two things overlap. I'm not convinced that there's a higher penetration of this in IT than any other profession.

      --
      Read: Rabbit Rue - Free serial nove
    3. Re:brilliant or dangerous? by neapolitan · · Score: 5, Insightful

      Agreed totally. I wish more people realized this and thought like you.

      I, too, can write obfuscated code and appear "genius-like." It is a whole lot harder to bring *everybody* along than to rocket yourself ahead, make yourself appear to be esoteric and "invaluable," and, in a sense, bully everybody else into compliance. Now, we don't have enough details on the particular story to know if his colleagues actually were bad.

      However, I spend a good deal of every day helping people that may be not as quick or sharp as me in many ways, but that is my job.

      Finally a point regarding documentation -- I'm sure that every programmer here has come back to code that he/she wrote, and thought, "Man, this guy (me) is a genius. However, it just took me 30 minutes to understand how I did this!"

      Early on in my programming life, I thought this was indicative of my awesomeness as a programmer. Now, I just think it is poor documentation, and largely a waste of time. If I can't figure out how I did something a year ago, it would take other people twice as long... They may appreciate the clever implementation, but in the large scheme of things that is not efficient, nor awesome.

      --
      Slashdotter, ID #101. UIDs are in binary, right?
    4. Re:brilliant or dangerous? by h4rm0ny · · Score: 3, Insightful

      why are the mutually exclusive?

      Or related?

      --

      Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
    5. Re: Brilliant Or Dangerous? by ronfuller · · Score: 1

      if he is really that valuable, a sensible solution would be to hire an assistant whose job is to run interference and document code. if those were the only duties his assistant had, the net would still be a big plus.

    6. Re:brilliant or dangerous? by Maxo-Texas · · Score: 5, Insightful

      The problem is that smart people get very irritated working with fools.

      Our corporation has now cut our productivity by 75% in the last 5 years due to SOX related procedural changes. It takes 45 days to put a 1 line code change into practice.

      The smarter developers got irritated, then angry, then acted out, then most of them left. The few who remained were mostly burdened with debt and couldn't afford to take the risk. So they take anger management courses and let the corporation destroy them as people.

      There are appropriate places for smart developers-- in projects where they save millions of dollars.

      There are fewer and fewer jobs for smart developers. Corporations prefer predictable pleasant programmers over brilliant good programmers. They would prefer that a project *definately* take 16 weeks instead of taking 2 to 9 weeks.

      Even tho I was smart enough to move out of programming and into management, the culture slowly driving me insane as well. As far as I can see after a few promotions is that it is is turtles all the way up and the problem is coming from somewhere above 5 levels of management above me.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    7. Re:brilliant or dangerous? by TheCreeep · · Score: 1, Troll

      why are the mutually exclusive?

      Mutually exclusive? It's not a XOR, it's an OR operator. Make sure your slashdot licence is on my desk by wednesday.

    8. Re:brilliant or dangerous? by Razalhague · · Score: 2, Informative

      The English word "or" is more often used (and understood) to mean XOR rather than OR.

    9. Re:brilliant or dangerous? by Skreems · · Score: 4, Insightful

      Exactly. I'm always amazed by people who think that writing impenetrable code is "advanced". Any jackass can write something convoluted and obscure that nobody else can understand (or maintain) -- what takes actual talent is condensing complicated logic into code that's simple enough a ten year old would understand it. If you can write a complex system such that a teammate can open any random code file and think "what's so hard about that?", then you deserve some of the appreciation that "Josh" made a grab for.

      People like Josh, on the other hand, should be fired on the spot. I can't tell you how many hours I've spent cleaning up the mess left by people who thought that sheer volume of output was the measure of a good programmer, and I'm betting I'm not alone in that.

      --
      Slashdot needs a "-1, Wrong" moderation option.
      The Urban Hippie
    10. Re:brilliant or dangerous? by tixxit · · Score: 5, Interesting

      One of the best courses, I think, during my undergrad was a practicum course. We started off with a fairly simple project. The teacher gave us some requirements, but told us that for the rest of semester, each assignment would simply be new requirements to the original project and that, as we are developing it, we must keep that in mind.

      Some people in the class just brushed it off, did the usual homework thing and just rushed it out as fast as they could. Others spent a little longer on the first assignment, trying to anticipate future requirements, and make it general enough that they could add them if needed. After each assignment (there were 4), she'd ask people how long they had spent implementing the new features. In the end, it turned out that saving an hour on the first assignment, cost you about 2 hours on the second assignment and, unless you basically rewrote the first assignment, it just got worse as time went on.

    11. Re:brilliant or dangerous? by qbzzt · · Score: 5, Insightful

      Paraphrased from something I read.

      Walking on water is nice - but to really bring value you need to freeze it, so other people will be able to follow behind you.

      --
      -- Support a free market in the field of government
    12. Re:brilliant or dangerous? by nomadic · · Score: 1

      Good point. One other danger in enabling the obnoxious behavior by the brilliant guy is that you create this mindset where everyone starts assuming that if you're obnoxious you must be brilliant. A lot of times the quiet guy in the suit and tie is a lot smarter than the obnoxious one in the insulting t-shirt.

    13. Re:brilliant or dangerous? by Anonymous Coward · · Score: 1, Funny

      NOT

    14. Re:brilliant or dangerous? by Myrimos · · Score: 5, Insightful

      TFA is confusing "quirky" with "asshole." I love working with quirky people -- people who look at the world in entirely different ways, people who solve problems in a different manner, and people whose idiosyncrasies make them genuinely fun to be around.

      I can't say that I enjoy working with assholes, though. It doesn't matter how good your code is or how quickly you put it together, I can find somebody almost as good who's a lot less of a pain to work with. The extra little bit of efficiency isn't worth the metric cockton of assholery.

      --
      Internet scofflaw
    15. Re:brilliant or dangerous? by tedrlord · · Score: 4, Insightful

      They may appreciate the clever implementation, but in the large scheme of things that is not efficient, nor awesome.

      Whenever I hear the word "clever" relating to code, I cringe. I generally use it as an insult. In any professional project, clever code generally means "unmaintainable."

      --
      [insert witty quote here]
    16. Re:brilliant or dangerous? by ClosedSource · · Score: 4, Funny

      "They would prefer that a project *definately* take 16 weeks instead of taking 2 to 9 weeks."

      I've obviously been working for the wrong companies for the last 25 years. They would prefer that a project definitely takes 1 week.

    17. Re:brilliant or dangerous? by homerjs42 · · Score: 5, Funny

      I've also encountered the corollary -- I find some absurdly written ridiculous piece of code and wonder what moron wrote it only to find my own initials in the comments.

    18. Re:brilliant or dangerous? by COMON$ · · Score: 1
      "However, I spend a good deal of every day helping people that may be not as quick or sharp as me in many ways, but that is my job."

      I agree, as a net admin, this is how I feel towards most dev's ;) I kid!

      But seriously, I have a BS in CS and if I cannot figure out what your code is doing by the comments and code then you are doing something horribly wrong. I can read most code, even if I have never used it before, without comments. Bu your comments should allow me, if you die, go insane, or get fired. To make simple changes and hire someone who can pick up where you left off. Being able to replace you is worth much more to me than Sheer Genius is.

      --
      CS: It is all sink or swim...oh and did I mention there are sharks in that water?
    19. Re:brilliant or dangerous? by bberens · · Score: 2, Interesting

      There's a give and take. In the grander scheme of things it's more important to have a cohesive team than just about any other single factor. At the same time when the proverbial stuff hits the proverbial fan it's that weird/obnoxious genius guy who comes through with the solution that saves the day more often than not.

      --
      Check out my lame java blog at www.javachopshop.com
    20. Re:brilliant or dangerous? by nine-times · · Score: 5, Insightful

      The problem is that smart people get very irritated working with fools

      Of course, really extremely smart people can outsmart fools into getting them to do what they want. Really smart people get more irritated working with other smart people who have opposing agendas.

      There are fewer and fewer jobs for smart developers. Corporations prefer predictable pleasant programmers over brilliant good programmers. They would prefer that a project *definately* take 16 weeks instead of taking 2 to 9 weeks.

      I don't do software development, but as a manager, yeah, I'd generally rather work with pleasant people who do their jobs "slow and steady" rather than the "brilliant" but unreliable guy. The real issue is often not the uncertainty about exactly how long a project will take, but uncertainty about whether you can trust what you're being told how long a project will take.

      What I mean is, yes, I'd rather have someone working for me who says, "I can get this project done in 2-9 weeks" and gets it done in <9 weeks then someone who says, "I can get it done in 16 weeks" and gets it done in 16 weeks exactly. 9 weeks is shorter, that's an easy call.

      The problem is dealing with someone who says, "I can get it done in under 9 weeks," and then sometimes it takes 2 weeks, sometimes it take 9 weeks, sometimes it takes 23 weeks, and sometimes it never gets done. I'd generally rather take the steady 16 weeks over that sort of thing. A steady-16-weeks allows me to make other plans, make promises to other people, and set other deadlines. With the theoretically-9-weeks-but-who-knows answer, everyone would actually be better off being told, "I have no clue how long it will take," because at least then there would be no false expectations.

      All of this is just to say, I'd rather have people that I can rely on than theoretically brilliant people who are just going to do whatever the hell they feel like.

    21. Re:brilliant or dangerous? by tedrlord · · Score: 1

      Pleasant programmers are, on the whole, more valuable to corporations than good programmers, for certain values of good. A total genius that writes awesome code nobody else can read is a terrible asset to the company. If the software product is their main product, it could bring the entire company down. Assuming it's their own fault because nobody else is as "smart" is just hubris, and probably delusion.

      An actual good developer, while needing actual ability and experience, also needs to be able to work with the rest of the team to write code that potentially any of them can maintain. The developer might quit or die, leaving everyone stuck, or he might just be on vacation when a P1 bug occurs. I know it's more personally validating for your manager to have to call you up because you're the only one that can possibly fix something, but it's really not valuable to the company.

      --
      [insert witty quote here]
    22. Re:brilliant or dangerous? by Austerity+Empowers · · Score: 2, Interesting

      Bingo. There's never been a shortage of self-absorbed assholes in any line of business, ever. The difference is that in most corps today, management types tend to be very socialized and promoted via american idol like popularity contests such that "Josh" is either THE boss (i.e. runs the company) or he's your coworker. Possibly "Josh" is most synonymous with software because it's a new field and relatively poorly understood...but this is changing.

      The issue is that in most companies Josh is totally unwelcome and short-lived, when in fact Josh is necessary. Quite often Josh is actually smart, and sees things others do not see. He knows that 10 dumb people working together as a group produce 5x the dumb output, the rest is released as waste in the form of donuts and coffee.

      Much like chemotherapy, he may do some good, but many think they would prefer the alternatives because they have less unpleasant side effects. The fact is it takes all types to succeed, and Josh should only be shown the door if in fact he does something so severely wrong there may be legal implications for the company. Otherwise he should be sanctioned appropriately, and for God's sake never promoted to management, but retained. Let him carry the cost of his personality in a stunted career and missed opportunities, and he may eventually grow to be a guiding light rather than a frikken shark with lasers.

    23. Re:brilliant or dangerous? by Imagix · · Score: 5, Interesting

      Exactly. I'm always amazed by people who think that writing impenetrable code is "advanced". Any jackass can write something convoluted and obscure that nobody else can understand (or maintain) -- what takes actual talent is condensing complicated logic into code that's simple enough a ten year old would understand it.

      I'm reminded of two quotes.

      One from Einstein: "Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction."

      The second from Kernighan: "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it."

    24. Re:brilliant or dangerous? by adrenaline_junky · · Score: 2, Insightful

      Convoluted or obfuscated code is no benefit to anyone and deserves scorn.

      However, there is nothing about being a brilliant programmer that requires one to write convoluted or obfuscated code.

      The best code needs very little documentation because it is immediately obvious to any other programmer what the code is doing, and long comments are only required in sections of the code where the purpose of the code is not immediately obvious.

      It does require a dose of humility to intentionally add minor inefficiencies to a program to make it more clear, though, and it sounds like the Josh in this story was sorely lacking such humility.

      Using five lines of code to show the intermediate assignments in a long calculation instead of doing it all in one line of code can make the logic flow easier to follow by orders of magnitude, but some programmers are unwilling to deface the elegance of their design with such simplicities.

      Ultimately the true genius is the person who can write brilliant code that is also easy to read and modify.

    25. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      wow!

      being a total ass only works in movies and no one is irreplaceable, even the brilliant ones. Honestly, unless you created the code by which you program, your just another mouse in the maze and it's only a matter of time that someone better will come along and find the answer or fix.

      The crazy smelly fat nerd with grease stained t-shirts only work from home or in movies.

      Get on with it, no many companies accept this kind of attitude anymore and YES when you want to change codes, it takes time because knowing the impact can result in either millions saved or millions lost.

    26. Re:brilliant or dangerous? by Anonymous Coward · · Score: 1, Insightful

      The key word is "definite". And the parent poster is correct, it's all about hitting dates. Any date will do, but hit it. Management has fallen in love with Gantt charts and Outlook calendars. Unfortunately, they have also fallen in love with outsourcing. This "love triangle" between management, calendar, and outsourcing results in satisfaction for no one.

    27. Re:brilliant or dangerous? by Foofoobar · · Score: 5, Interesting

      Here's one reason why... I was Bipolar II which meant I was mostly manic. As a result I was easily angered, very enthusiastic, easily empassioned and highly creative. My brain went a MILLION miles per hour in that state and I had brilliance that I couldn't contain at times. I already have an IQ of 160 and during that state it was up 5-10 additional points (when I could stay focused).

      Tack onto that the boundless energy the condition gave me and the fact that I never slept in that state and you have exactly what you described. I felt untouchable and alive like no one could imagine. So why did I go on meds? Well, that's the trick. How do you get bipolars or other people who have a self destructive disorder that makes them feel superior or more intelligent go on a med that dumbs them down or slows them down?

      I hit that point where I realized my condition was isolating me and shutting me off from everyone else around me. When I examined my life, I realized I had no one to blame but myself; I burnt people out like matches but couldn't see that I was the one common factor in all the damaged relationships. More exactly, my condition.

      I eventually got better and now write my own documentation, get along with others, don't have mood swings at work, etc etc. It took me years and lots of hard work and effort to get over old emotional habits... the meds don't do it alone.

      But I guess what I am trying to say is that sometimes brilliance comes with madness. Sometimes it's just madness, sometimes it's both. Getting them to help themselves though can be almost impossible though.

      --
      This is my sig. There are many like it but this one is mine.
    28. Re:brilliant or dangerous? by SatanicPuppy · · Score: 1

      So smart and reliable are mutually contradictory? A smart programmer would say 10 weeks to give himself a 1 week cushion past his worst case scenario, and still be done faster than the 16 week joker, with 1-8 weeks of possible slack time built in.

      I guess only a fool would work that way...

      --
      ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
    29. Re:brilliant or dangerous? by buddyglass · · Score: 1

      Sometimes solving a problem in the most straightforward and human-readable fashion does not result in the most high-performing solution. Sometimes the best code will necessarily be less easy to read than the "most readable" version. That's not a bad thing.

      Also, I feel like the idea that "the code is the documentation" gets crapped on a little more than it should. Programming languages have well-defined syntax. If one understands the syntax, one should typically be able to read a block of code and figure out what it does without the benefit of comments. For the most part, I find other developers' comments to be redundant and unhelpful. That's not always the case, but often it is.

      I will add, though, that poor developers often write code that is unnecessarily complex. Just because a block of code is complex, that doesn't mean it necessarily represents a brilliant or effective solution. It may just be that the developer sucks, and that's why the code is way more complicated than it need be.

      Personally I try to make my code as "concise" as possible, just as a personal preference. Sometimes that makes it slightly less readable than a more verbose (and less efficient) version might be. But then, rarely do I come back to something I've written and end up scratching my head wondering what it does.

    30. Re:brilliant or dangerous? by thedonger · · Score: 2, Informative

      There is a place for "clever" or "novel" code. We shouldn't be so locked into doing things a certain way that we never deviate from the path. It is important, however, to understand the history of what you are working on in order to avoid repeating past mistakes, or re-engineering the wheel.

      There very well may be a good reason why something is done a certain way, but that reason may simply be that no one ever thought of it before. That doesn't make it wrong.

      --
      Help fight poverty: Punch a poor person.
    31. Re:brilliant or dangerous? by hairyfeet · · Score: 5, Interesting

      But then there are also the flip side to the problem. I did some temp work with a company that had a "Josh", lets call him Jim, and hell, everybody really liked the guy. He could whip off code like you wouldn't believe and solve problems that others had been stuck on for weeks in minutes. So what was the problem?

      It was, for lack of a better description, what I like to call the "head too full" syndrome. The guy knew how to write badass code in what seemed like every language from BASIC to the latest language o' the day, but trying to get docs out of the guy(hell trying to get comments you could actually understand out of the guy) was nearly impossible because he had already moved on to the next problem in his head by then. I spent about a week setting up his new machines the way he liked them and talking to the guy. Afterwards one of the higher ups stopped me and said "You always seem to have good ideas about things. What would YOU do to make Jim's work day easier?". I could tell the company would frankly fall apart without Jim so I said "Honestly? Find a guy with a little programming knowledge who can sit in the office next door and write docs for Jim. Because every time someone asks him for an explanation or docs you are going to throw him "off his groove" and it will take him a day to get his groove back. Let him do what he does best and let somebody else follow behind him writing the HOWTOs."

      So I would say, yes some are quirky because they are frankly asocial asshats. But I'm sure there are plenty like Jim who just have "heads too full" that are just not thinking like we think. I mean, I would be having a conversation with the guy about the old days of Commodore and Atari programming when he eyes would glaze over and he would smile and then suddenly he would just blaze out this huge complicated mess of code that frankly WAS brilliant and would have taken anyone else weeks to cook up. Did he mean for it to be complex or weird? Not really, that was just how his brain worked. And expecting him to fit in the cubicle mentality would have just had the guy frustrated for a couple of weeks until he got tired of it and quit.

      So I guess what I am trying to say is that you really have to base how you handle a "Josh" based on the situation. Are they acting the way they do because they are asocial? Or because their brains really don't work that way? Because as we know Einstein had to have his address stuck on his coat when he was working on a problem because he would wander off deep in thought. I'm sure that most that ran into him would have thought him rude for not engaging them in conversation. But he wasn't TRYING to be rude, his "head was too full" to give even a moment's attention to anything but the problems in his head. And that was Jim to a T. Nice guy though. Maybe that is what makes the difference between a Jim and a Josh?

      --
      ACs don't waste your time replying, your posts are never seen by me.
    32. Re:brilliant or dangerous? by buddyglass · · Score: 1, Insightful

      I'd fire Josh just because he's jackass and I don't like working with jackasses.

    33. Re:brilliant or dangerous? by hondo77 · · Score: 2, Interesting

      Our corporation has now cut our productivity by 75% in the last 5 years due to SOX related procedural changes. It takes 45 days to put a 1 line code change into practice.

      For the record, I worked at a place where we could release SOX-compliant changes within an hour of the need arising. However, our normal release cycle was weekly and we passed all of our SOX audits. If your company's productivity has declined 75%, don't blame SOX.

      --
      I live ze unknown. I love ze unknown. I am ze unknown.
    34. Re:brilliant or dangerous? by ThreeE · · Score: 0

      In short... it is only mutually exclusive if you are in a room full of a bunch of business MBAs who apparently as a whole still think that solutions come out of some magic hat somewhere...

      There are just as many religious programmers as MBAs.

    35. Re:brilliant or dangerous? by 0xABADC0DA · · Score: 1

      Also, documentation of that work is essential...

      I, too, can write obfuscated code and appear "genius-like."

      I think the actual problem at all skill levels is programmers not working at their natural pace. Better programmers go too fast and their code is incomprehensible to others. Less capable programmers go too fast and their code is buggy and unreadable. In any case it's a maintenance nightmare.

      And the solution is ridiculously simple: developers need to fix bugs in and add new features to their own code, whether it is from last week or ten years ago. When documentation actually helps to be more productive programmers are rewarded for doing it by less hassle and more work done (which presumably management can recognize).

      The worst is when programmers just declare code done if it runs once, without testing, without removing hacks. In most jobs this gets the best reward because they programmer gets to claim it is 'done' faster AND it slows down anybody else that has to fix the bugs or add features to the code. If programmers would get mired in their own cesspool of bugs, they would either have to produce less or write better code. That would be an incentive to become better programmers and would limit the amount of damage they can do. This especially applies to the incompetent programmers, since they are always behind they have to cut more corners just to not look incompetent.

    36. Re:brilliant or dangerous? by Maxo-Texas · · Score: 2, Insightful

      Close.. but not what I'm saying.

      Given a choice of:

      * Definitely 2 to 9 weeks. Over 9 weeks 5% of the time- file a project change with reason at week 7.
      * Definitely 16 weeks. Over 16 weeks 5% of the time- file a project change with reason at week 14.

      Managers choose 16 weeks.

      And if they do have a 2 to 9 week person, they'll tend to let that person sit around doing nothing for 7 weeks (actually vetoing projects because they don't want to "spend money" for a person that will instead sit at their desk doing nothing, worrying about their job. i.e. the money is already frakking spent).

      You have to let go or it will drive you crazy. You just deliver on the deadlines- with all of your paperwork correct (7 documents these days) and the appropriate status reports and weekly meetings attended.

      Any truly brilliant developer will be driven insane by this. The only option in my opinion is for them to go to consultant firms or small companies.
      When I worked at a small company, I was free to change code, put it into production-- on the SAME day. When I worked at a small company, I was free to tell my manager, "Hey I'm not busy right now so I'm going to improve the code". We didn't have to schedule a series of meetings. When I was a consultant, at least I could say, "I'm done- bye" instead of being tied to a desk with no work. And as a consultant, the paperwork was SOOOOO much lower.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    37. Re:brilliant or dangerous? by ClosedSource · · Score: 1

      My point is that management is usually interested in getting things done ASAP, usually ASAI (As Soon As Impossible). I've never worked anywhere where management would reject a shorter estimate just because it couldn't be tied down to a specific date.

      Of course, an estimate like 2-9 weeks is so vague that it suggests that the coder might take a lot longer than 9 weeks to complete it.

    38. Re:brilliant or dangerous? by squoozer · · Score: 1

      You sir are most certainly not alone in having spent hours going through reams of anothers overly complex code. I have had that unenviable job for the last three years now and, while not religious, it has driven me to pray that there is a special type of hell waiting for dip stick that wrote this software.

      --
      I used to have a better sig but it broke.
    39. Re:brilliant or dangerous? by Miamicanes · · Score: 5, Insightful

      > The problem is dealing with someone who says, "I can get it done in under 9 weeks," and then
      > sometimes it takes 2 weeks, sometimes it take 9 weeks, sometimes it takes 23 weeks, and sometimes
      > it never gets done.

      In most cases like that, here's what really happens...

      Mgt: "How long do you think this will take?"

      Programmer: "Er, I guess 3 months or so, assuming nothing major goes wrong along the way."

      Mgt: "That's too long! We need it in 8 weeks. Can it be done?"

      Programmer: "I doubt it. Maybe if god parts the skies and makes a miracle happen."

      Mgt: "It's really, really important. In fact, it really needs to be done in 6 weeks."

      Programmer: "You're insane. There's no way in hell it's going to happen."

      Mgt: "OK, I'll allocate 8 weeks."

      Programmer: (sigh) "Whatever."

      8 weeks later ...

      Mgt: "Is the program done?"

      Programmer: "No. We'll probably be done in another month, maybe two at worst."

      I think you see where this is going. The programmer had a decent idea of how long it would take, and could have probably given a more realistic estimate within a few days had he been encouraged to identify the riskiest parts of the project (specifically, third-party libraries and things constrained by real-world hardware/network performance) and try to tackle them *first*. However, if management twists his arm backwards, or keeps pressuring him for a "better" (ie, shorter) estimate, he'll eventually get disgusted and throw them the number management wants... rationalizing that it's not *quite* a lie since miracles occasionally happen, and absolving himself of any moral responsibility for actually agreeing to a deadline he views as ridiculous since he was coerced into it.

      That, IMHO, is the root of more miscommunication between management and developers. Far too many managers don't quite understand that programmers *hate* interpersonal conflict, and will casually agree to just about *anything* if they think it will get the person to quit bothering them. The constructive way to deal with it is to begin by asking the programmer for a range (best case vs likely worst case), then ask him to identify the riskiest factors influencing the range, then nudge him to tackle those factors first so a better estimate can be refined quickly. Just don't make him feel like you're twisting his arm or browbeating him, because estimates are like information from interrogation -- torture will get you the answer you want quickly, but the answer itself will likely prove to be worthless.

    40. Re:brilliant or dangerous? by Marillion · · Score: 3, Interesting

      Damn, you beat me to it.

      Never the less, you are spot on. Some quirky programmers are both, some are neither.

      Perhaps it is conceited of me, but I've always thought of myself as brilliant. Enough people have made comments that reinforce that conceit. But, one of the most valuable pieces of advice I ever received was from another brilliant individual who once remarked, "You and I might understand this, but those who follow might not. We need to simplify it." From then on, I've always thought twice about getting "too creative."

      --
      This is a boring sig
    41. Re:brilliant or dangerous? by Ihmhi · · Score: 1

      Exactly. I'm always amazed by people who think that writing impenetrable code is "advanced". Any jackass can write something convoluted and obscure that nobody else can understand (or maintain) -- what takes actual talent is condensing complicated logic into code that's simple enough a ten year old would understand it.

      Actual talent? Yes. Actual job security? Not necessarily.

      To some people, write dox or mans is like training the new guy and you get fired at the end of the day. Guess who gets your job!

    42. Re:brilliant or dangerous? by tedrlord · · Score: 1

      I agree that sometimes it's required, especially where performance is the main factor and the compiler isn't able to optimize well enough on its own. Hopefully, it's either part of the original design, or at least discussed by the team beforehand. In those cases it needs to be commented very well.

      I was talking about cases where clever node is written for the sake of being clever, or because it was the most expedient solution to a non-performance issue. Those kind of things can really build up, and can ruin a codebase. I worked for a company where the only person that really understood the code was a developer they kept on as a consultant. There were years of cruft built up to the point where they attempted a re-write, which causes its own problems.

      --
      [insert witty quote here]
    43. Re:brilliant or dangerous? by Rorschach1 · · Score: 4, Insightful

      Generally true. Sometimes clever is necessary, though. I do most of my programming these days on embedded systems, where size and speed are absolutely critical. I'll occasionally do something horribly non-standard and convoluted (usually to avoid writing even more annoying inline assembly code), but I've learned to allow about a 3-to-1 comment to code ratio in those cases. Even something not that complicated but just unusual (casting a char array to a function pointer and calling it because that particular buffer is the only one available to hold the flash programming code that has to be copied down to RAM, for example) warrants a clear, concise description of what the hell is going on.

      No matter how sure I am that I'll remember how something works and why I did it, I still try to always comment it. I'm sure everyone here (who's been programming for more than 3 years anyway) has gone back to code they wrote 3 years ago and thought "what the hell is this, and what was I thinking?". In my experience that's usually followed by a quick correction, and then after a few hours of chasing down some obscure bug that subsequently appeared, remembering why you did that in the first place and putting it back the way it was.

    44. Re:brilliant or dangerous? by squoozer · · Score: 3, Insightful

      There is a flip side to this though. One place I worked had a habit of trying to make sure any code they wrote was always as flexible and general as possible so that future requirements could be satisfied easily. The problem was that everything took twice as long to develop and was unnecessarily complex. I noticed that the developers were generally fairly poor at predicting what the new requirements would be or when they would be wanted. I'm not advocating that every piece of code should be written as the shortest path from A to B but I think the best solution is somewhere between general and rigid. Your in class example isn't great because you knew up front that there would be new requirements in the near future therefore hinting to you that a flexible base is a good thing. In the real world you rarely get such hints.

      --
      I used to have a better sig but it broke.
    45. Re:brilliant or dangerous? by Dan667 · · Score: 1

      As a software developer who has managed large projects, one good programmer is worth 20 or more average ones. Even if a programmer tells you that it will take 16 weeks and delivers, if it is crap code that barely works you will have to refactor it over and over to get it into the project. This effectively takes even longer than 16 weeks and makes their contribution all the less while tying up other programmers. Now a lot of brilliant programmers have personality problems that can range from quirky to debilitating. Most of them are not bad people and if you can figure them out they are worth the effort.

    46. Re:brilliant or dangerous? by aurispector · · Score: 4, Insightful

      The key difference is the willingness to work well with others. In any organization you need cooperation or long term it just won't work. Coding strikes me as a task that's particularly vulnerable to long term maintenance issues if it isn't properly documented/commented.

      You can blame management for putting up with difficult people, though perhaps they simply don't understand the depth and breadth of the problem. Sometimes all it takes is for someone to confront the person in question with a set of expectations - and be willing to pull the trigger if the standards aren't met.

      --
      I have mod points. The reign of terror begins now.
    47. Re:brilliant or dangerous? by Maxo-Texas · · Score: 1

      We raised the issue all the way to senior management and they say our controls are in line with other companies our size.

      1 week... maybe for an emergency change.

      Any scheduled change has 4 weeks for the testing department, in the scheduled window (which add another 4 weeks if you miss the window), 2 weeks for the change control and scheduling meetings, 1 week for the actual installation process (so what 7 weeks == 42 days, yup) and then 1 day for coding, 1 day for testing (since you have to create a fairly substantial test packet with screenshots, scripts, etc. for the testing department), and 1 day I can't remember what it was for. Oh yea, the 1 week installation can slide if they have a competing installation.

      I'm not kidding, I'm not engaging in hyperboly.

      Any emergency changes are aggressively monitored because they screw up the scheduled changes.

      Here's a recent one.

      Change the password expiration period for one of our systems.

      We are on our *FOURTH MONTH* for what is a configuration change. Because of the paperwork overhead, it is now a full blown project of it's own. Testing documents, requirements packets, technical documentation, there will be a testing certification, there have been multiple meetings about when it will go live (since it is "high" priority).

      At ANY small company this would have taken 5 minutes.

      We are no longer allowed to change our own text configuration files due to SOX. This means another department has to edit the files- which means since they do not understand the risk, that they want full testing for any change before they will make it. And then, we have to schedule a window of their time to make the text change.

      So we wrote a file editor INTO the application to avoid this control- but we didn't include the password duration (no time- we were just sneaking in the file editor on the back of another project- took us 7 months to get it into production-- this was after it took 8 weeks to get "yes" changed to "no" in a text file to turn on some error logging back in 2003).

      For this particular change, the other department has decided they do not want to edit the file ("too risky, we could make a typo") so we are delivering them a copy of the edited text file that has passed through unit testing and quality testing.

      The pay is very good, but the work is soul-draining.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    48. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Programming is like sex, one mistake and you have to support it for the rest of your life.

      Perhaps the brilliance is in job security, not the ability to write obscure code.

    49. Re:brilliant or dangerous? by Rumagent · · Score: 2, Interesting

      Amen brother. To quote the great Hoare:

      "There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult."

      It was true then, it is true now and it will remain true in the future.

    50. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      - Coding isn't really that difficult.
      - The alleged 'brilliance' is often the cause of the issues.
      - You see these people types in all business roles the marginal benefit is just not worth the hassle.

      Hire a consultant to come up with the ideas and rough implementation framework - but let someone else do the actual code and documentation.

    51. Re:brilliant or dangerous? by Venik · · Score: 5, Insightful

      It is equally amazing how programmers of average ability insist on branding brilliant code they have trouble understanding as convoluted and obscure. The only thing that matters here is the bottom line. If Josh produces code that makes the company millions, then this is all that matters. It is entirely irrelevant if some of Josh's obtuse co-workers with a pronounced inferiority complex think that his code is convoluted. Most managers I know would rather fire every idiot complaining about Josh's shenanigans, than to fire their obnoxious but talented cash cow. I had the privilege of working with a couple guys like Josh. Understanding their work and their methods may be challenging, but it is also rewarding. Most can't stand brilliant co-workers, but not because of their alleged eccentricity. Bell curve riders feel inadequate and threatened working with talent. They demand endless meetings, ceaseless telecons, and detailed documentation, as if reading documentation would actually make them understand genius. People like Josh rarely get fired: they just get tired working every day with the same morons and go for a better-paying job elsewhere.

    52. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Well the post did not say he makes code more complicated then i has to be, maybe he just is programming stuff that other at his company simply could not.

      Their are geniuses out their.

    53. Re:brilliant or dangerous? by LunarEffect · · Score: 1

      x=brilliant
      y=dangeorous
      x y| x v y
      0 0| 0
      0 1| 1
      1 0| 1
      1 1| 1

      Not mutually exclusive in logical terms =)

    54. Re:brilliant or dangerous? by Maxo-Texas · · Score: 1

      We actually have a variant on that.

      The SALESPERSON tells a senior executive way above the IT president that an 8 week project can be done in 4 weeks.

      This gives a psychotic set of options.

      Either the project is done with our SOX controls and takes 16 weeks and the programmers sit around doing nothing for 4 to 8 weeks OR
      we hire consultants to lead the project- our SOX controls don't apply to them- and they deliver in 4 weeks. But they install directly to production with admin rights and very skimpy documentation- plus they actually get to code 40 hours a week so they do obscure unclear things to people who are getting to code about 4 weeks out of 16 (10 hours a week average).

      If it comes from below, it is subject to SOX controls and a requirement that it meet the scheduled date 100% of the time and is enormously slow.
      If it comes from outside the company, all bets are off.

      The fun jobs for real programmers appear to be with consulting companies. However, I am not willing to work 60 hours for 40 hours of pay any longer.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    55. Re:brilliant or dangerous? by s73v3r · · Score: 1

      I once tried to go into a job with a Dr. House mentality. I was fired after a week for suggesting that every problem was lupis.

    56. Re:brilliant or dangerous? by Orion+Blastar · · Score: 1

      This was the case in the law firm I worked at. They had a 90% turn around in four years of IT staff mostly programmers. I stuck it out, until I got so sick I could no longer work and went on short-term disability and soon after got fired for being sick.

      I saved the law firm millions of dollars in lost productivity by automating forms to electronic forms and developing and coding a docket calendar because lawyers would miss court dates and Palm Pilots and Outlook didn't work well enough when the court dates would get moved or a lawyer would go on vacation or leave the firm, and nobody knew what court dates he/she had to attend to and cover. Everything automated into a Web 2.0 application that could reassign court dates and court info to other lawyers when the original lawyer left the firm or went on vacation. Before that they would lose clients and lose million dollar cases and where bleeding money really bad.

      --
      Remember, Slashdot does not have a -1 disagree moderation, and no, troll, flamebait, and overrated are not substitutes.
    57. Re:brilliant or dangerous? by MadKeithV · · Score: 1

      The first time you write the code, it's the shortest path from A to B.
      The second time you write that code, you gnash your teeth, and still use the shortest path.
      The third time, you get down and dirty, refactoring the code until one piece can work for all three situations.

    58. Re:brilliant or dangerous? by El_Muerte_TDS · · Score: 1

      I think Robert C. Martin said it well:

      The proper use of comments is to compensate for our failure to express ourself in code.

      from "Clean Code: A Handbook of Agile Software Craftsmanship"

    59. Re:brilliant or dangerous? by MadKeithV · · Score: 1

      I use "cute" as the derogatory term for overly clever code. But clever code should be just that, clever.

    60. Re:brilliant or dangerous? by Maxo-Texas · · Score: 2, Insightful

      I've worked with many brilliant programmers over the course of 25 years.

      Good coding *is* difficult.

      Managers want to think that programmers are a generic goo. Our 2nd to last reorg 3 years ago took everyone away from their areas of competence because some management company said it would be a more efficient allocation of our resources. After suffering with it 3 years (I think because they didn't want to embarrass the executive that backed the plan), we have a brilliant new organizational plan-- we put people in their areas of competence.

      A good programmer can do quality work and quality documentation in 1/10th the time, with less architectural/design issues than a pleasant competent programmer. A brilliant programmer MUST write quality code- sub-standard code and design pisses them off and drives them crazy. You don't want *two* brilliant programmers in the same area. You need a brilliant programmer and 3 to 4 solid pleasant programmers and 1 to 2 eager novices.

      You don't need an asshat like Josh, but you may find your brilliant programmer does his ( I've met some brilliant female programmers recently but the vast majority are male ) best work from 1pm to 1am so you have to focus on project deadlines, not arrival times.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    61. Re:brilliant or dangerous? by tedrlord · · Score: 2, Funny

      Embedded programming is an entirely different beast, I'm sure. The way you talk about it, I think all programmers should be forced to write and maintain embedded code for a year or two before they're allowed to work on anything else.

      --
      [insert witty quote here]
    62. Re:brilliant or dangerous? by Talderas · · Score: 1

      Does Einstein's quote also apply to government?

      --
      "Lack of speed can be overcome. In the worst case by patience." --Znork
    63. Re:brilliant or dangerous? by TheRaven64 · · Score: 1

      Your in class example isn't great because you knew up front that there would be new requirements in the near future therefore hinting to you that a flexible base is a good thing. In the real world you rarely get such hints

      Being in the real world is the hint. There are very few real-world projects where the requirements don't change over time.

      --
      I am TheRaven on Soylent News
    64. Re:brilliant or dangerous? by NotInTheBox · · Score: 1

      I always thought that "being brilliant" was a proper subset of "being dangerous"?

      The real problem I think is that to many managers still want/need to handle programming as predictable production work, instead of inherently unpredictable design work.

      --
      What I cannot create, I do not understand
    65. Re:brilliant or dangerous? by alexhard · · Score: 1

      Anyone can be brilliant.

      You keep using that word. I do not think it means what you think it means.

      --
      Infinite time means everything that can happen, will. You being you is absolutely incidental. You do not exist.
    66. Re:brilliant or dangerous? by tedrlord · · Score: 1

      Don't underestimate the power of the re-org. Someone moves into a position above you, decides everyone needs a fresher approach, and suddenly there's a contractor in, documenting the code for you, and you're replaced by a cheaper or more friendly face.

      Watching it happen from the outside, the transition can be painful, but nobody is as irreplaceable as they think.

      --
      [insert witty quote here]
    67. Re:brilliant or dangerous? by tixxit · · Score: 1

      Yeah, good point. Mind you, this class (4th sem.) was in stark contrast to pretty much every other homework assignment given up to that point (small set of rigid requirements for a one-off project). My soft. eng. courses also focused on agile development, where you don't expect to have all requirements defined up front. It also wasn't so much an exercise in "anticipating" (guessing) future requirements, as it was on good design practices (loose coupling, programming to interfaces, etc.) Obviously, taking too much of a pedantic approach to OO design will just end up hurting your grades in school; the deadlines are just too tight. It was a great course though.

    68. Re:brilliant or dangerous? by jellomizer · · Score: 4, Insightful

      The reasons that the "Josh" usually doesn't get fired is because the company has a small enough Dev Team that makes him the big fish in the little pond. And most of the people don't know that he is actually quite bad. His code may make millions but the truth is someone else can write code that will make the millions too, and make change over that much smoother. So they keep him as they know the mess it would be when he leaves and hopes they can change jobs before it falls on their head.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    69. Re:brilliant or dangerous? by TheRaven64 · · Score: 1

      I find a good way of documenting this kind of code is to write the simple version first, comment it out, and then write the clever version (in addition to any other comments that may be needed). This has a few advantages. If there appears to be a bug in this code, you can just swap the comments around (this works best if you use #if 0/#else around the two versions) and to pinpoint the bug. People reading the code can compare the two versions and see if they agree that they should do the same thing. And, in future, if the code needs to be modified, it may be that the simple version has now become `fast enough' and the person doing the modifications can start from that instead of even trying to understand the clever version.

      --
      I am TheRaven on Soylent News
    70. Re:brilliant or dangerous? by DarkOx · · Score: 1

      Ok,

      I am with you for the most part. You do get coders, Engineers, Systems design people and Operations folks like Network Admins like your Jim; those are not like Josh from the TFA. Someone who get so engrossed in what they are doing and has its flow come so naturally to them might be valuable enough to work around. I might make sense to have junior to the position chase after them write their docs and manage some of their communication interaction. Yes its another salary but if they can do the work of two senior people then you are getting that work for 1.5 times the unusual cost.

      Josh though is taking a dump in the lobby plat. He is plainly full of himself, not at all a team player; by choice as well as personality quirks. He is pushing it because he thinks he is superior to everyone else. He thinks he is above the rules. Thats not ok, and its a recipe for disaster because sooner or later you can't make him happy and he is going to leave. When he does he takes all that information with him. He his problem and he needs to go.

      That is a far cry from your head to full Jim, who misses the big picture from time to time and does not cope well with interruption. Jim probably understands he is a bit a savant great at somethings weak else where. He is probably is happy to have that junior level person chasing his tale and doing things like docs and throttling the communications. He might not be the best team player either; but thats because others can't deal with his quirks and he can't over come them; and its not because he refuses to try. This is a different person. Jim is someone who might be worth the trouble because he is not trying to make trouble. Josh is trying to make trouble he likes to see what he can get away with and should not be tolerated.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    71. Re:brilliant or dangerous? by dawich · · Score: 1

      Or they get beer-trucked, and the company folds. Great business plan that.

    72. Re:brilliant or dangerous? by NormalVisual · · Score: 4, Insightful

      It is entirely irrelevant if some of Josh's obtuse co-workers with a pronounced inferiority complex think that his code is convoluted.

      Until he quits, is hit by a bus, or otherwise becomes unavailable to maintain the undocumented, uncommented spaghetti mess that usually comes from these kinds of people. When the total cost of writing and maintaining "brilliant" code exceeds that of "average" code that provides adequate performance, then there's a problem.

      On the other hand, I've also had the pleasure of working with developers that are far and beyond my skills, but also are decent people to work with and document their work so that it's understandable without having to spend a week tracing through it. Such people are worth their weight in gold.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    73. Re:brilliant or dangerous? by mdielmann · · Score: 2, Insightful

      And another Einstein quote I try to live by in my programming career: "Make everything as simple as possible, but not simpler."
      IMO, MS Office ribbons fail on the second part.

      --
      Sure I'm paranoid, but am I paranoid enough?
    74. Re:brilliant or dangerous? by phorm · · Score: 1

      However, "quirky" in the article seems to describe a case that's more "offensive", "arrogant" and/or "antisocial."

      I know plenty of quirky programmers. They do things in odd ways and are good out-of-the-box thinkers, but they're not jerks with a god complex. Whether with sysadmins or devs, you usually tend to get a bit of a "I know better than you" attitude (and often enough it's true), but a god-complex or arrogance is not a good thing.

      The line between confidence and a stand-up-for-my-work attitude (good) versus arrogance and I-can-do-no-wrong, is sometimes pretty thin. You don't want somebody who's going to question his/her own work and make dumb decisions due to pressure, but you don't want somebody who's going to deliberately offend/abuse co-workers and otherwise ignore anyone else's advice.

    75. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Your metric for good work is time spent?

      Do you make allowances for complexity, or just don't take much thought on to it?

      Can you really appraise someone knowledge and capabilities on his or hers behaviour alone?

      My experience so far, is:

      - People in general can't evaluate what they don't know.
      - People prefer to ask for early commitment on deadlines even before they have an idea of what they have to do.
      - After committing to a deadline what you have done is put your credibility at stake, you better know what you are doing (people are cruel and understanding is a scarce resource).
      - Many use theatrics as a way to signal competence, talking with authority on issues they don't understand, and using assertive talk to get away with it.

      Well, i don't have met that many brilliant people, sometimes i have came across with some not recognized brilliant work, but i do have met too many mediocre people and mediocre work. And tough they do a lot of work, most of the time it's inconsistent, full of traps, difficult to change and debug.

      I can say one thing for sure, many people have a misguided view of themselves and their work. And you can do all the right moves and noises, and your work is still crap.

      Maybe sometimes it's better to be good at marketing oneself than to do actual good work.

    76. Re:brilliant or dangerous? by Chicken04GTO · · Score: 1

      modded up for "metric cockton of assholery"!

    77. Re:brilliant or dangerous? by Jerrry · · Score: 1

      Exactly. Just look at Hans Reiser for a perfect example.

    78. Re:brilliant or dangerous? by markov_chain · · Score: 1

      The only place that "clever" code might still make a difference nowadays is in embedded systems, kernel code or tight, highly optimized inner loops. In other applications, most likely it is much more important to have a good system architecture than get bogged down in tweaking code.

      --
      Tsunami -- You can't bring a good wave down!
    79. Re:brilliant or dangerous? by NormalVisual · · Score: 1

      If one understands the syntax, one should typically be able to read a block of code and figure out what it does without the benefit of comments.

      That's not necessarily true if you're not aware of the code's place in the larger scheme of the system. Grab a programmer off the street, tell him there's a bug in an uncommented implementation of the Longley-Rice radio field strength prediction algorithm, and then ask him to fix it. Come back in a week and he'll be a quivering mass of Jell-O.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    80. Re:brilliant or dangerous? by Draek · · Score: 1

      Of course, really extremely smart people can outsmart fools into getting them to do what they want.

      Never tried to debate with a creationist religious fundamentalist before? well, manipulating your boss' boss into doing what you want is even worse, and the idiocy grows at an exponential level the more you rise on the management hierarchy. Plus there's the ethical implications of it, usually its best simply to walk away and let them self-destruct.

      I don't do software development, but as a manager, yeah, I'd generally rather work with pleasant people who do their jobs "slow and steady" rather than the "brilliant" but unreliable guy. The real issue is often not the uncertainty about exactly how long a project will take, but uncertainty about whether you can trust what you're being told how long a project will take.

      Pro tip: with software, you can *never* trust 100% what you're being told how long a project will take. You can start making some rough estimations when the software is already architected, designed and all it remains is to actually write the thing and test/debug it, but until then estimates are at best a shot in the dark, at worst an attempt to deceive their managers (meaning you) so they STFU and go bother someone else.

      With the theoretically-9-weeks-but-who-knows answer, everyone would actually be better off being told, "I have no clue how long it will take," because at least then there would be no false expectations.

      In terms of honesty, yes. But much like the people who write software even your grandma can understand, actually stating to your boss you don't have a clue about how long it'll take means you'll get fired next week, and replaced by an expensive consultant who *does* have the balls to lie to your face and tell you "I'll have it in less than five weeks", then make some excuses when its been 10 weeks and it's still a long way from being finished.

      --
      No problem is insoluble in all conceivable circumstances.
    81. Re:brilliant or dangerous? by BucketOfLard · · Score: 1

      I like your justification for not having Jim do his own documentation. However, I've found doing my own documentation is where I always find a cleaner/better/faster way of doing things. And, I usually document the day after I've written something because it helps me see improvements much clearer.

    82. Re:brilliant or dangerous? by billcopc · · Score: 2, Interesting

      they realize that intelligence is only useful if the person can work with other people or can effectively communicate his work

      So you're essentially saying everyone needs to meet the lowest common denominator, in order to be productive ? Fuck that, some of us do get hired because we "think outside the box" and can pull off feats of mental strength. Should we play dumb just because we share an office with a bunch of glassy-eyed imbeciles ? You're going to have different skill sets and intellectual extents in any office, the not-so-secret trick to being successful is to maximize each player's potential. If one guy is really talented at coding those mind-benders, but sucks at documenting his work in layspeak, you hire an assistant. Let the code wizard write code, and the doc wizard write docs. What's so horrible about that ?

      Do you expect your accountant to be a top lawyer too ? No ? Then why do you expect your programmer to be a top technical writer ? Yeah, we know a little bit about the "other side", the same as your accountant should know the rough guidelines of tax law, but one is never a replacement for the other.

      --
      -Billco, Fnarg.com
    83. Re:brilliant or dangerous? by cyphercell · · Score: 1

      If Josh weren't "No-Call, No-Show" all the damn time, I might disagree with you. Point is, he was tempting them to fire him, begging for it, I think he hated it there. I don't think Josh was just putting out gobs of useless code, it sounds to me like he was the one that came up with a solution in a week or so, while ~14 other developers were twiddling their thumbs. Better would be Josh->Skreems->Support Team. This way Josh never has to talk to a customer, never has to deal with a support team that is basically computer illiterate compared to him. If deadlines get cut short, then Josh's version goes live to be followed by a feature compatible upgrade. The important bit, is that Josh and the support team have an intermediary when refactoring code he understands perfectly well. Then when problems arise it goes support team->Skreems->Josh.

      --
      Under the influence of Post-Cyberpunk Gonzo Journalism
    84. Re:brilliant or dangerous? by Venik · · Score: 1

      Well, I never worked at a small company. My experience working with Josh-like characters comes entirely from working in very large companies. Thus, it would seem your big-fish-in-a-little-pond theory may be flawed. There is almost always somebody better somewhere out there, but that genius already works for your competition. Not to mention that their Josh is every bit as much of an eccentric a-hole as your Josh. The point is: this guy makes your company big money. Most managers would rather select a team that complements such talent, as opposed to getting rid of the talent and hiring more of the average coders with excellent documentation-writing skills. Here is the simple truth about computer code: if it's fast and reliable, then it is not convoluted, even if nobody else in your development department can make heads and tails of it. You just need to hire coders with better qualifications. You have a real problem if one of your guys is so much better than the rest. And the problem is not that this guy is an eccentric genius, but that you've been hiring mostly idiots, who can't even understand code that has been already written. In a situation like this, the department head should do some serious soul searching and, perhaps, have a serious talk with the HR head.

    85. Re:brilliant or dangerous? by Seakip18 · · Score: 1

      This is so true. I began working at an agency a little over three months and I'm still unsure about parts of the application.

      Anyways, the project manager for a SQL Server migration is asking me how long it will take to screen shot the entire application and then attach those screenshots to the pages responsible for the display.

      The answer she wants is "Oh, it can be done by EOB tomorrow." The real answer lies entangled with the problem that the many pages within the application are not sorted into a module or even known to be in use. She's trying to enforce a project timeline that is out of whack because if she doesn't meet deadlines, she looks bad to her boss, who looks bad to the boss above, and so on.

      It's made even worse by the point that we're a relatively new staff (only 2 of the 6 development staff have worked here for more than a year) and this fact is lost on her.

      --
      import system.cool.Sig;
    86. Re:brilliant or dangerous? by Requiem18th · · Score: 1

      The word you are looking for is "conflating".

      --
      But... the future refused to change.
    87. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Sounds like eBay management.

    88. Re:brilliant or dangerous? by coldsalmon · · Score: 1

      And, from the perspective of a different industry:

      Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that's creativity.

      --Charles Mingus

    89. Re:brilliant or dangerous? by shutdown+-p+now · · Score: 1

      It is equally amazing how programmers of average ability who know how to churn out convoluted, obscure and undocumented code using every trick on the book, regardless of whether its use has a point or not in any particular case, insist on branding themselves genius.

      Case in point: I had to deal with code written by a guy who was very much into functional programming (so am I, really) and specifically Haskell. The application itself was in C# 2.0. He insisted in doing everything the "FP way", effectively writing his own functional-style library with pairs and lists and map/fold, and so on, and using it everywhere. He further actively used higher-order functions, so at places you'd get to 3+ levels of that (function that returns a function that returns a function ...). Now, yes, this is aggressive code reuse, and the code was smaller, but...

      C# (back then) was not a language designed for such a thing. The syntax for closures was fairly clumsy, and standard library wasn't up to it. At the end of the day, code written in such a style was very alien and unreadable in C# context, even to people otherwise familiar with the concepts. Add to that the complete lack of comments, and wonderfully descriptive identifiers (such as function "MakeAF" taking an argument "fn"), and the result is a mess. Then the guy left... it took 2+ months to bring all that stuff to a manageable state, and that was a work done by two senior devs (myself included), because no-one else on the team was sufficiently qualified to handle this. And yes, that matters, too - like it or not, but businesses like people to be replaceable.

    90. Re:brilliant or dangerous? by shutdown+-p+now · · Score: 1

      There is a flip side to this though. One place I worked had a habit of trying to make sure any code they wrote was always as flexible and general as possible so that future requirements could be satisfied easily. The problem was that everything took twice as long to develop and was unnecessarily complex.

      It's not always worth generalizing things, but it is always worth documenting them (and I don't just mean specs and comments, but also descriptive identifiers even for local variables, and so on).

    91. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Hi Josh!

    92. Re:brilliant or dangerous? by SnapShot · · Score: 1

      I agree that sometimes it's required, especially where performance is the main factor and the compiler isn't able to optimize well enough on its own.

      I don't disagree, but there better be a documented change order in the system that explains EXACTLY which bottleneck is being addressed. IMHO, if you're still in the "let's get this working" pre-beta phase of the software development there had better not be any clever code being written.

      As someone who once tried to write clever code (when I was younger and smarter) I wish I could track down my younger self and beat him with my walking stick. There's a part of me that wants to find a new job simply so I can escape my old code...

      --
      Waltz, nymph, for quick jigs vex Bud.
    93. Re:brilliant or dangerous? by MartinSchou · · Score: 5, Insightful

      I'd place myself as slightly behind the bell curve (out of practice) at the moment (slightly ahead when up to speed). I'm quite capable of recognizing brilliant code. I'm also able to recognize code that makes absolutely no sense to me. At times those two are the same thing (meaning that the code is doing things way above my comprehension, not that the code doesn't work).

      The thing is - if that brilliant code turns out to have a subtle flaw or needs to be redesigned, how can you be certain that the originator is still with the company or the project? Sure, that brilliant code may have saved your company millions, but when the flaw allows people to siphon money directly from your bank account, how would you rather go about fixing it? Stepping through convoluted code or reading the documentation? Sure, "my code just works" is a nice reponse. I'm also certain that Einstein was a lot smarter than most of the Josh' out there, and if he'd just said "E=MC^2 - trust me" people would have told him to fuck off and come back when he'd shown the math that proved it.

      I've worked with people quite a few rungs above me. All of them are capable of writing documentation that I can understand. Documentation that cuts the time spent on my comprehension of how their code works by 90+%.

      Their job isn't just whipping out code. It's also showing that it works. How it works. The upside is I don't ask them nearly as many "stupid" questions, because while their code still in Klingon - but it comes with subtitles. It also means that once I've looked through this Klingon enough times, it'll start making sense. I might actually learn how to write some stuff in Klingon by reading what they've written (with subtitles). But in the software industry that's just a waste of time - who needs people actually learning stuff at work?

      Imagine the following scenario:
      Ed is a brilliant engineer and architect. He comes up with a way for us to build a trans atlantic maglev train route that runs under water in essentially vacuum tubes. He's even figured out how to make it cheap enough that trip from London to New York city will cost you 200$ and will take about two hours. His brilliance even allows the project to scale, so that if we swing the tubes upwards and really punch it, we can send stuff into orbit for a price of 1000$/ton.

      Now, instead of writing up the designs, specs for the materials, how to build the materials and so on, Ed's just going to tell the people involved how to do it by phone. Because of Ed's absurd brilliance and genius, this actually works for a full week, and his super human skills in JIT means we're now 12 miles into this tunnel.

      The 8th day however, Ed's rather unfortunate. Seems he decided to drop by the post office the same day that Dan the mail man went postal and killed everyone in the office. Including Ed.

      Since noone else knows how any of this stuff is supposed to work, we now have to give up on the tunnel project while we siphon through the few things Ed actually left behind.

      Now, in the real world Ed's demise would be somewhat of a setback, as we've now lost the lead engineer on the project. However, since Ed was a good engineer and architect, he knew he was supposed to put all these things down on paper before we started the project and put billions or trillions of dollars on the line.

      Now, in the software industry, we're very fond of calling ourselves engineers and architects. Unfortunately most of us (even in companies) really don't reach that level of excellence - we don't document what we do, either because we're too lazy or because the companies don't want to spend money doing that. That's fine - just don't consider yourself or what you're doing software engineering.

      I've actually had the pleasure of working for an engineering company as the only software developer/programmer. Imagine how flabbergasted I was when my boss asked me for documentation as well as actual schematics for the software I was making. Schematics as in fl

    94. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Doesn't sound like his head was too full. Sounds like he was just overworked.

    95. Re:brilliant or dangerous? by gbjbaanb · · Score: 1

      If you can write a complex system such that a teammate can open any random code file and think "what's so hard about that?"

      *exactly*. Its like any other area, the truly talented are the ones who "make it look easy". I'm sure you've seen a sportsman or athlete on the TV, and thought to yourself "I could do that". The problem is that you couldn't, its only because they made it look so effortless that you think you could.

      'Devs' like Josh are incompetent in comparison. Often I've found the people who write the most impenetrable code and the ones who think they're the greatest (a worrying sign in itself) and many others agree because they can't understand the code said "genius" came up with. There's a reason no-one can understand it - because its poop. Unmaintainable, probably slow, and possibly only written that way because it gives them some feeling of superiority.

      In my old teams they were told to get with the team, or get lost. They're not working for their amusement, they're working for the benefit of the company that pays them.

      Scott Berkun wrote a good article about teams and stars. Worth a read.

    96. Re:brilliant or dangerous? by Stratocastr · · Score: 1

      See now i would have just slacked off till end of semester and after all requirements were in, finished the whole thing off in a week of caffine-sugar haze known as programmer's heaven

      --
      Slashdot - I went there to fix their grammar that they're so bad at.
    97. Re:brilliant or dangerous? by computational+super · · Score: 2, Insightful

      How do you know you're not a jackass?

      --
      Proud neuron in the Slashdot hivemind since 2002.
    98. Re:brilliant or dangerous? by Venik · · Score: 1

      When the total cost of writing and maintaining "brilliant" code exceeds that of "average" code that provides adequate performance, then there's a problem.

      And, by extension of your logic, if this brilliant code is more profitable to the company, then it is well worth the cost of hiring someone with adequate skills to untangle the spaghetti and with mental fortitude to work with the spaghetti's eccentric author. We are in agreement then.

    99. Re:brilliant or dangerous? by DrLang21 · · Score: 1

      And those people are fools. If you're getting fired at the end of the day, that means one of two things. Your talent and skill has not been significantly honed with experience, and therefore, you are not moving into positions that simply can not be filled by a fresh recruit with little experience OR your management team sucks and doesn't get it. Writing documents and manuals is training the new guy who will take your place when you move up, quit, or die. If your company's management simply can't see how valuable that makes you, then you might want to start searching for a new job where the management isn't cancer. Fortunately for me, I work in a regulated industry, where failure to document will inevitably result in being ordered to shut down. Good documentation is highly valued here.

      --
      I see the glass as full with a FoS of 2.
    100. Re:brilliant or dangerous? by squoozer · · Score: 2, Insightful

      It's true enough that requirements often change during development but if requirements are changing drastically and / or frequently during development someone has screwed up.

      Like a lot of young developers I used to think that the "best" way to deliver a software project was just to jump straight in and start coding. As I've gained more experience and worked on progressively larger projects I now see that software development is a lot more like civil engineering.

      If you went up to the engineering team that was responsible for the Viaduc de Millau bridge and said I want it in purple half way through the project he would say fine give me X euros to re-paint it. If you instead said I want it to span the straights of Gibraltar you've screwed up with the requirements.

      --
      I used to have a better sig but it broke.
    101. Re:brilliant or dangerous? by JoeMerchant · · Score: 1

      I, too, can write obfuscated code and appear "genius-like." It is a whole lot harder to bring *everybody* along than to rocket yourself ahead, make yourself appear to be esoteric and "invaluable,"

      I had a kid who tried this - he lasted about 4 months before he was on the way out. The simple answer was: "if your co-worker can't make sense of it, it's worth nothing to the company and must be redone." "But, but, it works." "No, it worked yesterday, we need something that works tomorrow."

    102. Re:brilliant or dangerous? by Venik · · Score: 1

      And this is clearly a problem not with your former programmer, but with how your department operates. You know, there is no rule that requires you to wait for your lead talent to quit before you can try to analyze his code. Maybe he would even tell what this "fn" argument is all about.

    103. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Bollocks.
      You can believe someone that said "I can get it done in 16 weeks" only if this is a problem that has been solved before, by him and knows exactly what he is talking about.

      Exact deadlines in software projects that actually do interesting stuff not done before by others are by definition idiotic.

    104. Re:brilliant or dangerous? by usman_ismail · · Score: 1

      I had an instructor who loved this procedure he called it the Universal Conservation of Grief principle. You either put in the time(greif) at the start of a project, thinking about the problem properly. Or on the last feature which is ridiculously easy if only you had used a slightly different architecture but would not require major code rewrites.

    105. Re:brilliant or dangerous? by computational+super · · Score: 1

      Yeah, I work with a "quirky" developer who gets "god complex" accusations quite a bit. He's been banned from posting e-mails to the company e-mail list because he's suggested some "outrageous" things like "time tracking is moronic" and "we don't need to call a meeting every time somebody has a question". The fact is, although I personally disagree with him on a couple of technical things, the guy's not a prima donna at all - just a really smart guy who everybody else is mostly jealous of. And the really sad thing is I think they're either going to get him fired or he's going to quit in frustration and we're going to lose the guy - believe me, it'll be our loss, not his.

      --
      Proud neuron in the Slashdot hivemind since 2002.
    106. Re:brilliant or dangerous? by infonography · · Score: 1

      true you need to be insulting just to be taken seriously. If the think they can walk all over you your doomed to scut work and measly pay. It's all part of the herd mechanics of human society. If you don't like it I would suggest a species change, I hear Iguana is nice.

      --
      Sorry about the writing. Robot fingers, you know? Cliff Steele in DOOM PATROL #23
    107. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      I think you owe it to give a hint as to your employer, so that the sane among us may avoid them at all costs.

    108. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      I'm beginning to think that people like these are born but grown. I (interestingly enough a guy named Josh) often try to learn neat tricks that look cool, and I've written some pretty crazy code. But when it comes down to real work I do my best to make sure *someone* knows what's going on. If I don't at least document something, which I almost always do, I try to at least walk someone through the code or explain the script. I'm not perfect, but I try to make things as easy as possible for everyone who works with me. Our whole team really does this. And, I think, because we can trade off so easily (because we keep each other so well informed), it looks to management like we're actually not doing anything hard. Because we don't play the whole hero thing (and because they've never had a real IT department before), management doesn't see how good we really are.
      Because of this we've lately contemplated rewriting all our code in BrainFuck and Whitespace.

      The reason the stupid hero myth continues is that people unacquainted with a particular field will buy into it, and management is only acquainted with how to manage (not how to code). Good coders are driven to impress and often want to write code that's tricky or cool, but a truly good coder will see even greater value in maintainability and readability. Really great code is easy to reuse. But managers will never understand this, because managers don't understand code. To managers (or really to anyone outside the field) the harder something is to understand, the better it must be because, they assume, the smarter you'd have to be to write it. Until coders manager coders, instead of managers managing coders, the world will continue to be plagued with poor code designed more for job security than getting things done.

    109. Re:brilliant or dangerous? by jra · · Score: 1

      > Anyone can be brilliant. Anyone can be a jerk. Sometimes these two things overlap. I'm not convinced that there's a higher penetration of this in IT than any other profession.

      I think it is, for 2 reasons:

      1) People (still) don't understand IT, so it's still a priesthood, especially at the upper levels.

      2) As several people have noted in books, the span of productivity between mediocre programmers and heroes is larger than in almost any other endeavour; therefore the span of social behaviour which is likely to be tolerated is probably wider than for people who mop floors.

      Figher pilots get away with lots more shit than deck-swabs do, too.

    110. Re:brilliant or dangerous? by NormalVisual · · Score: 1

      if this brilliant code is more profitable to the company, then it is well worth the cost of hiring someone with adequate skills to untangle the spaghetti and with mental fortitude to work with the spaghetti's eccentric author.

      In 20+ years of professional software development, I've yet to see a prima donna that is *so* much better than everyone else that it's worth putting up with the drama, and there are precious few that make it justifiable even from a strictly dollars-and-cents perspective. Team morale and productivity are factors to consider as well, and it doesn't do any good to have a star player if they're pissing off everyone else to the point that it's affecting their output.

      There are certainly some truly gifted people out there, but I've yet to see one that's so gifted that I'd tolerate that kind of disruption to the team, and if they can't write clear, concise code, then they're frankly not that good. Steve Wozniak wrote some truly brilliant code for the Apple II *in assembly language*, but still managed to A.) write the code clearly and document it sufficiently, and B.) did it without being a total jerk to everyone.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    111. Re:brilliant or dangerous? by JoeMerchant · · Score: 1

      It is equally amazing how programmers of average ability insist on branding brilliant code they have trouble understanding as convoluted and obscure.

      My high school comp-sci class had a semester project of "doing base conversion", and the teacher had them write out special input/output cases (in BASIC) for base 2-10, 2-16, 10-16, 16-10, 16-2, and 10-2. The whole lot of 'em coded like rabid beavers for weeks and weeks.

      I hope more than one person here knows how to convert any number (up to the integer size restriction) from any base (2-36) to any other base in about 4 reasonable lines of BASIC?

      Some solutions are orders of magnitude "more brilliant" than what run of the mill coders come up with. Their elegance makes them more maintainable and useful than the "obvious" solutions. If your company does a lot of algorithm development, it needs people who can do these things, and whether the run of the mill coders like it or not, these people are indeed rare. As far as I can tell, run of the mill coders who do a decent job are also pretty rare.

      The real genius comes in taking the people you've got and getting the best out of them as a team, while still meeting critical needs (documentation, maintainability, etc.) There are actually people who are perfectly happy doing the documentation end of things without the pressure of coming up with solutions out of the blue. Pair these different personalities up well, and you've got a much stronger team than a bunch of guys who do a "decent job" at all aspects.

    112. Re:brilliant or dangerous? by ElitistWhiner · · Score: 1

      I've experienced 3 geniuses each who represent the range of character between brilliant and dangerous. One CIA-type speaks 14 languages and programs in as many. He holds the keys to the Federal money transfer codebase, wears a pager 24/7 and understands national security. Another founded Greenpeace before it had a name and proceeded to develop the rest of the planet despite the costs (think AIG). The last hacker programmer, groks boardlevel to crypto, easily bored.

      In all cases the outcomes are the same, parallel development, modularity and never allow access to the whole crown jewels. Anything less is stupid, irresponsible and risks the crown.

    113. Re:brilliant or dangerous? by Confused · · Score: 1

      If someone can't even hack the basic protocol of human interaction and social graces, he can't be much of a programmer.

      In my experience, getting rid of offensive people is always a boon. If a project needs primadonnas succeed, the project is doomed and won't succeed anyway.

    114. Re:brilliant or dangerous? by nine-times · · Score: 1

      Never tried to debate with a creationist religious fundamentalist before

      Debate with them regarding what? If you're going to debate a creationist religious fundamentalist over creationism or religion, for the sole purpose of getting them to say, "You're right, I'm wrong," then maybe the religious person isn't the fool in the conversation.

      well, manipulating your boss' boss into doing what you want is even worse, and the idiocy grows at an exponential level the more you rise on the management hierarchy.

      I've been there. I've convinced my boss's boss of things. I've also been the boss who has been convinced of things by an underling. And you know what? It's often not as simple as "stupidity". Sometimes you only think your boss is stupid because he's more concerned about things that you don't know about than he is about the things you do know about.

      Then, of course, some bosses are stupid-- I'm not denying that. But I've seen plenty of instances where employees were complaining about their idiot boss only to find out that the employees simply didn't understand how the business worked.

      Pro tip: with software, you can *never* trust 100% what you're being told how long a project will take.

      Yeah, this isn't unique to software development. Things go wrong. Still, time management (including gauging how long a project will take you) is a useful skill in itself. It includes being able to make good guesses/estimates on how long something will take, and how to appropriately pad your estimate given how likely and extreme the possible setbacks are.

      No one can tell me with 100% precision how long a project will take, but I'd rather work with someone who can give me a reasonable estimate 95% of the time than someone who is often slightly faster at doing the work, but whose estimates are way off 70% of the time. I think that preference is reasonable, too.

    115. Re:brilliant or dangerous? by Venik · · Score: 4, Insightful

      Interesting analogy but probably not applicable here. You see, Ed didn't just tell you how to build the train - he actually built it for you. True, the bastard hasn't produced a shred of documentation. And now, after Ed's unfortunate demise, you and your team of average engineers are scratching your heads, trying to figure out how to extend Ed's design to reach Tokyo. And the reason for your predicament is obvious: as an employer you lucked out to have a truly talented engineer working for you, but, being an idiot, you made no attempt to understand his work. You should have been searching high and low for engineers capable of understanding Ed's designs and working with him, however difficult that might have been. Instead, you hired some random guys off the street and let Ed work alone. Your problem is entirely your own fault.

      Talented people get bored easily. Something that you or I may find intellectually stimulating, they find obvious and prosaic. This is why, as the fortunate employer of a genius, you hire capable people who complement his talents. You don't make soup out of your goose just because he won't document the process of laying golden eggs.

    116. Re:brilliant or dangerous? by JoeMerchant · · Score: 1

      the culture slowly driving me insane as well. As far as I can see after a few promotions is that it is is turtles all the way up and the problem is coming from somewhere above 5 levels of management above me.

      If you're in a livable spot, maybe it's time to just learn to enjoy where you are.

      When I was in a "culture of molasses" I was actually worried about forgetting how to work. I could please more people and make more promotion points for myself by being an obstructionist jerk than I could by actually accomplishing anything.

    117. Re:brilliant or dangerous? by mooingyak · · Score: 1

      Whenever I hear the word "clever" relating to code, I cringe. I generally use it as an insult. In any professional project, clever code generally means "unmaintainable."

      Second that. When we're having design discussions, I sometimes veto ideas with the reason of "I don't want this library to be that smart."

      --
      William of Ockham had no beard. The most likely explanation is that it was chewed off by squirrels every morning.
    118. Re:brilliant or dangerous? by h4rm0ny · · Score: 1

      true you need to be insulting just to be taken seriously.

      I disagree. Many work environments will take seriously someone who has expertise and will actively seek out such expertise. But in those environments where you do need to be forceful to be taken seriously (and if you are, find somewhere better), you don't need to be insulting. You just need to be strong. The two are not the same and people who think they are demonstrating strength by insulting other people are usually compensating for some weakness and they also tend to suffer through people's quiet sabotage of them.

      --

      Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
    119. Re:brilliant or dangerous? by sigmabody · · Score: 1

      Man, this sounds so familiar from my experience with big companies ten+ years ago, and I'm sure it's gotten worse since then. Nothing impacts my productivity quite as much as a painful work environment, where you can't write good code no matter how smart you are, because the procedures just don't allow it. It takes a certain mindset to work in an environment like that, and usually it's not the mindset exhibited by the really productive developers. I always thought it would be a nice place to retire to when I care more about a steady paycheck and benefits than actually producing anything, but that time is still a while off.

    120. Re:brilliant or dangerous? by Matheus · · Score: 1

      The difference with a "Jim" is that he already got to that point the first time. Spending the time writing extensive amounts of documentation gets a "Jim" bored and he loses interest leading to a problem being left unfinished as he moves on to something better.

      A "Josh" is a whole different animal (not knowing him personally I'd have to reserve judgment but based on what I do know the term Jackass fits) and most of the comments I've read above don't distinguish between the two.

      I've known "Jim"s and "Josh"s aplenty throughout my career so far. "Josh"s you fire as soon as you own their intellectual property because they will cost you a fortune and other great employees in the long run. "Jim"s you do whatever you can to keep them happy because they are truly invaluable.

    121. Re:brilliant or dangerous? by sjames · · Score: 1

      I think the problem is that "Josh" is two issues rolled into one. ONE of those issues is well worth working around. That's the one Jim had and your suggestion is well worth while for that case. Jim may be quirky as far as a typical corporate workgroup was concerned, but he evidently was personable enough for you to have conversed with him.

      Such a person might "masquerade" as Josh like Tyler (referenced in TFA), but with a little patient instruction can work out fine. Perhaps they just need a translator who can codify enough of the social rules for them from a utilitarian viewpoint rather than "because that's what nice people do". Even if it comes down to nothing more than "it's an arbitrary social signal/convention that people respond to by being more cooperative". Some people are like that because they are unable to pick up on social cues.

      In other cases, a brilliant coder may seem antisocial because others unintentionally needle them. Being knocked out of your groove too often is quite frustrating and may even be painful in some sense. Anyone might behave poorly to others if they get obliviously kicked in the shins a few times a day (by people who don't often or ever get "in the flow" in the first place).

      However, it the person really is like "Josh", they may be more liability than asset. That is, if they won't directly help out, and won't even work with another person enough to get their work documented so it can be maintained AND they will just walk and leave you a bunch of unmaintainable code the first time they don't get their way, they are truly a liability. In that case, it might be best to get a backup plan in order and then try to approach them about the problem. Perhaps you just THINK they're unreachable and they'll respond well to proper instruction in social interaction and a genuine attempt to accommodate them (without being walked over by them). Or they'll leave in a tantrum and you go to the backup plan.

    122. Re:brilliant or dangerous? by JoeMerchant · · Score: 1

      Regardless of where I have been, the negotiation goes like this:

      How long will it take?

      About 12-18 months.

      Now, if we do X, Y, or Z, can we speed that up from 12 months to 6?

      X and Y might help, Z will only make things worse, but you're still looking at 10-18 months.

      Well, what if we restrict the scope, not do this, not do that, etc. Can we get it down from 10 months to 5?

      Freezing the scope now would be the best thing you can do, if we don't have any feature creep, and we get resources X and Y in here right away, I'd say we can be done in 9-15 months.

      O.K. then, we'll get right on X and Y, and we'll set an aggressive tentative goal for 8 months delivery.

      3 months later, X comes in, 3 months after that Y arrives...

      Total project scope expands by about 50%, regardless of reminders about schedule impact.

      Month 7 rolls around and the old delivery timetable for next month is dusted off and we sit around and have a vaguely recriminating session with some veiled finger pointing asking why we're missing our goal. A new schedule is laid out based on available resources, new scope, etc. Additional resources are offered and usually refused because they would do more harm than good at this point. At this point, really bad management forces the additional resources into the mix anyway. A new goal is set for delivery at month 10.

      Scope increases another 25%, Y turns out to be a liability, more or less canceling the advantage of X.

      Month 9 rolls around and the status review meeting happens again. Bad management will now set an arbitrary deadline at month 11 based on the company's needs, reasonable management will listen to the projection that another 5 to 7 months are required, and set a goal for month 12 anyway.

      Month 10, monthly status updates have begun. A few days after the status meeting, another 10% is added to the project scope.

      Month 11, weekly status updates, scope creep is down to +1 or 2% per week now.

      Around month 13, the scope creep stops when it finally becomes apparent (to management) that each new feature is setting the project back more than a week, the weekly status meetings are good for something afterall. The "new" project is starting to cook on the back burner.

      Month 14, weekly status meetings are starting to be canceled more than half the time. Increased interest in the "new" thing.

      Month 15 - project delivers. By now it's a total anti-climax, 7 or 8 months late, depending on who you ask, and anyway we really need to get cracking on the new thing.

      Be very afraid if there is no "new thing."

    123. Re:brilliant or dangerous? by phorm · · Score: 1

      Yup, but those are still fair bit different from wearing offensive shirts (depending on what "offensive" is classified as), insulting co-workers, and generally being an ass.

    124. Re:brilliant or dangerous? by cornercuttin · · Score: 1

      "The problem is that smart people get very irritated working with fools."

      as a 6'3", 300lb weight lifter, i often feel the same way with dealing with people weaker than me.

      just because one is smart doesn't mean they get to be an ass. if so, then my size should entitle me to quite a bit of leniency in my behavior as well. but i have respect for others, and i am patient and willing to help people with their manual labor (as well as their code).

      i disagree that there are fewer jobs for smart developers. i would just say that there are more jobs for bad managers.

      i have worked around quite a few quirky coders, and i can learn to tolerate their quirks. but if you establish from the beginning that being an ass will get them called out, then they will be scared to act out.

    125. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      So just for the benefit of the coders who haven't quite isolated the problem, can you give your coordinates and maybe the schematics of your building? Is that five floors up or five management levels up? Either way, I'd bring a helmet to work tomorrow. j/k, though I did want to test that modified USB missle launcher from Hackaday...

    126. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Even tho I was smart enough to move out of programming and into management

      I think this says all we need to know about Maxo-Texas's attitude and intelligence.

    127. Re:brilliant or dangerous? by CodeBuster · · Score: 1

      estimates are like information from interrogation -- torture will get you the answer you want quickly, but the answer itself will likely prove to be worthless.

      That is the most insightful thing that I have heard said about project estimates in a while here on Slashdot. I would liken this to the programmer who "plays dead" so that the cage match negotiator (i.e. the manager who you can never win an argument or negotiation with and who just wears you down until you say whatever it is that he wants to hear) will think that he has won.

      Background: The name of the antipattern, cage match negotiator, comes from the professional cage match wrestling where many wrestlers enter the cage, but only one exits the cage victorious.

    128. Re:brilliant or dangerous? by fakeplasticusername · · Score: 1

      That's fine, just please leave a comment explaining why you are doing things in a non-standard way.

    129. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Dip-shit programmers are made not born. IMHO This really is an argument about the point of diminishing returns. What is the point of writing a perfect algorithms 2 years too late... If I document and plan too the nth degree it becomes a case study; if I implement with no forethought it becomes quick sand. The 'who cares' mentality comes to me when I say 2 weeks and they say can't you get running right now? Then I say "yes, but then it will be incredibly buggy..." It's like working for point haired guy in Dilbert. When I produce 'write once code' I can do it very quickly, and the 'team' always says something like 'this is just a temporary fix' - then the temporary fix gets 12 more layers. Once management has a taste of fast, dirty and cheap they put the pressure on to get running code out the door. Every contract is super important and the next job is riding on us getting this one going asap. Everything is super maxi extra ultra critical. I get there early and watch everyone arrive and I leave after they have turned off half of the lights and the cleaning crew is milling through the building. I can work 14hr days for about 2 weeks before I lose my efficiency, I start to worry about the unknown disaster that could come at any time. Then one day, I quit. When they call and ask for the magic spell book, I say "I don't work for you anymore."
              Now I look for work where there is an engineering approach. A project plan, a documentation system, a team, code review, set working hours. The development team has 1 or 2 kid hotshots, 2 or 3 seasoned programmers, and one unix style sysadmin - someone who is a great resource, but a little heads down.

    130. Re:brilliant or dangerous? by jonno317 · · Score: 1

      With the theoretically-9-weeks-but-who-knows answer, everyone would actually be better off being told, "I have no clue how long it will take," because at least then there would be no false expectations.

      Except that generally "I have no clue how long it will take" gets the response of "I need to tell so and so when it will be done" so then you end up getting your 9 weeks answer anyway.

    131. Re:brilliant or dangerous? by jellomizer · · Score: 1

      I said a small Dev Team not a small company. There is a difference, these guys are actually hard to find in small companies because small companies you need to put on different hats to succeed. But big companies have small teams this is where the "Josh" gets into play. A job focused enough that he doesn't shoot himself in the foot immediately, but the teams that do different things and are small which makes him the big fish for his team often enables his bad behavior.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    132. Re:brilliant or dangerous? by Draek · · Score: 1

      Debate with them regarding what? If you're going to debate a creationist religious fundamentalist over creationism or religion, for the sole purpose of getting them to say, "You're right, I'm wrong," then maybe the religious person isn't the fool in the conversation.

      Debating them over the inherent foolishness of being at the same time a creationist and a fundamentalist, given that the heads of most of the world's major religions have accepted evolution. But try to explain *that* to them and you'll see how 'easy' is to 'outsmart' a fool.

      Then, of course, some bosses are stupid-- I'm not denying that. But I've seen plenty of instances where employees were complaining about their idiot boss only to find out that the employees simply didn't understand how the business worked.

      Sure, but there's also plenty of instances where bosses don't understand the way things work (developing software, in this case), and in my experience getting *them* to admit they're wrong is much harder than for employees, mostly due to who writes the checks and the leverage that comes with that. And that's why many smart people simply don't bother 'outsmarting' them. It's stressful, it's hard, it comes with a chance of being fired, and *that* will look much worse on your resume than quitting and looking for a job that has a manager with a clue.

      No one can tell me with 100% precision how long a project will take, but I'd rather work with someone who can give me a reasonable estimate 95% of the time than someone who is often slightly faster at doing the work, but whose estimates are way off 70% of the time. I think that preference is reasonable, too.

      In regular businesses, yes it's reasonable, but can they? IIRC, more than 50% of software projects never get finished, and the lion's share of the rest are the ones that manage to do so but go over the initial budget and/or go past the deadline, so I'd say that if you *do* have someone that can give you a reasonable estimate 95% of the time you have a 'genius' in your hands, albeit perhaps not of the coding kind.

      --
      No problem is insoluble in all conceivable circumstances.
    133. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Kernighan was obviously a smart guy, but I think his quote is a load of bollocks. Debugging is not harder than writing code. Debugging is a systematic process of narrowing down a problem. You can debug code you don't even understand, as long as you know what the failing effect is (though you might not understand the implications if you don't understand the code itself).

    134. Re:brilliant or dangerous? by Bill,+Shooter+of+Bul · · Score: 1

      As has been said multiple times, the true genius writes self documenting code that everyone can understand. documenting only the non obvious stuff like

      int function calcDoomFunc() {

      /* see Dr Farnsworth's paper on Talor series expansion of Non linear Globtrotter functions of the third kind applied towards doomsday device design*/

      return 2;

      }

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    135. Re:brilliant or dangerous? by Loki_1929 · · Score: 1

      People who don't code have no clue how long things actually take to do. They assume you're spending 98% of your days hanging out at Starbucks and playing pinball like some kind of wizard out of an old rock and roll band tune with the other 2% spent waving some magic wand to magically make their stuff work.

      I have customers who want things like database-driven ASP.NET web services to create and maintain customer mailing lists with automatic bounce detection (determining hard or soft bounce failure), automatic removal for hard bounces only, secure remote customer login for manual management, overrides for all behavior, online mailer creation, scheduled delivery options, throttling options (to avoid tripping spam filters at Hotmail, Yahoo, etc), customer-usable import/export functions for the mailing list (imported directly from .xls files full of irrelevant info), and a customized "theme" for his secure remote interface that exactly mirrors his intranet site interface.

      And I shit you not, he literally goes, "can you take care of this for me tonight so I can start mailing customers tomorrow?".

      Me: "No, Pete, this is going to take some time to do."

      Him: "Really? I figured you guys could whip up something simple like that in like 15, 20 minutes."

      --
      -- "Government is the great fiction through which everybody endeavors to live at the expense of everybody else."
    136. Re:brilliant or dangerous? by bwcbwc · · Score: 1

      Rules to live by:
      "Never get into a pissing contest with a dickhead."
      "Never waste time trying to tell an asshole they're full of shit."

      --
      We are the 198 proof..
    137. Re:brilliant or dangerous? by XanC · · Score: 1

      Wow, does it ever.

    138. Re:brilliant or dangerous? by nine-times · · Score: 1

      Debating them over the inherent foolishness of

      and

      in my experience getting *them* to admit they're wrong is much harder than for employees

      I think this is one place where you're missing my point. Who said anything about getting people to admit that they're wrong, or getting them to understand that they're being foolish?

      If you look at it in terms of "making happen the things I want to happen" instead of "getting everyone to understand my viewpoint and agree", then dealing with stupid/foolish people isn't quite as awful-- and it's much easier than dealing with other highly intelligent people who simply don't want the same things you do.

      Don't get me wrong, I do like to work with intelligent people who disagree with me, so long as they fundamentally want the same things I do and the disagreement is over how to get those things. That sort of thing can be enlightening. But if it's someone who is simply opposing my goals, then it's much easier to deal with someone who isn't as smart as I am.

    139. Re:brilliant or dangerous? by Rene+S.+Hollan · · Score: 1
      Exactly. I'm always amazed by people who think that writing impenetrable code is "advanced". Any jackass can write something convoluted and obscure that nobody else can understand (or maintain) -- what takes actual talent is condensing complicated logic into code that's simple enough a ten year old would understand it.

      Hmm, so when an efficient sort routine is required, I should code a bubble sort just so that a novice can understand it, instead of a shell sort that is more efficient (and, arguably, state of the art for modest sorting requirements)? [N.B. I'm using "sort" as an example: of course, it's likely that one has a black box routine availale to do this.]

      Often, the problem is that the hoi poloi aren't even up to basic standards of technical competence. They should be left to areas where they can do little harm, with more advanced, and critical, work assigned to those who are skilled at it, and need only be able to explain it's workings to their peers as far as level of competence goes. Document the interface for everyone.

      Do we try to make brain surgery so easy that a 10-year-old could do it?

      No.

      If I need to find an optimal cost path through a graph (say for a "nearest word" match), and have the memory for it, the solution screams "Viterbi Search!". It's common in the literature, but a bit non-intuative to a novice. Should I not use it? I would think that "adequate documentation" would be a cite to any one of the references on the subject.

      It used to be that one could assume one's coworkers were at least familiar with the material in Donald Knuth's "The Art of Computer Programming" (which covers Viterbi Search in the first volume quite well). Sadly, that is no longer the case.

      --
      In Liberty, Rene
    140. Re:brilliant or dangerous? by Maxo-Texas · · Score: 1

      Being a brilliant programmer is like being putting you with a team of people assigned to move 1,800 pounds of weights.

      Management requires that you only move one 5 pound weight per trip to reduce risk of injury.

      Your idea to use a dolly is turned down because of the 5 pound limit and lack of funding for a dolly (even tho one is sitting in the corner, it's allocated to moving the water bottles).

      Management estimates that a 5 minutes per weight, it will take 1,800 minutes (30 hours) to finish the job.

      If you finish the job in 30 minutes, you'll only sit around doing nothing and possibly be reprimanded for doing the job in a non-approved way.

      Now to make sure you do it in the standard way, they assign a two people two observe pickup and delivery of each 5 pound weight. They assign an incident number to moving the particular weight. When the system finishes assigning the incident number, they record it in a pad that you initial and give you a sticky receipt that you attach to the weight.

      At the delivery end, the other person certifies that you have delivered the weight correctly, hands it to a tester who certifies the weight is 5 pounds and creates an incident related certification notice which is attached to the incident. The tester passes the weight to a stacker who takes the weight and places it on the stack, removes the sticky receipt and puts it in a stack log.

      The average incident time is recorded and any weight moving incidents which take significantly longer or shorter than the standard time are recorded and you meet with your supervisor to explain the anomalies.

      Incidents that take *shorter* than the standard time are treated much more seriously because you must be taking some kind of risk or violating procedure if you are moving the weights too quickly.

      Any missing sticky incident receipts are also taken extremely seriously because those are "control" documents recommended by your auditors and failure to track them means your gym could be fined or closed down.

      ---

      Now, you, the 6'3" lifter of 300 pounds* are going to remain completely calm in the face of this. No irritation. No feeling "this just isn't right".

      Every step i outlined is an analogue to the development and SOX in place at my company. We have about 3 brilliant programmers left. The rest are decent but disengaged (but we have regular session on how to "engage" our employees so they will do quality work.)

      ---
      * btw, 300 pounds is pretty buff. I am 6'5" and do 160 pounds. When I try to do more, I usually develop joint problems of some kind. B(

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    141. Re:brilliant or dangerous? by PeanutButterBreath · · Score: 1

      Your mingling of terms like "inferiority complex" and "feel inadequate" with accusations of "idiot" and "moron" is a real tour-de-force of irony.

    142. Re:brilliant or dangerous? by Maxo-Texas · · Score: 1

      My methodology is this
      Rate from 1-5,

      Size of project
      Complexity of project
      Value of Project

      Turn this in to a "swag" which everyone understands is a swag for comparison to other projects.
      Getting the programmer to give a good estimation for size and complexity usually takes about 15 minutes per item.
      Value of the project comes from working at the same place 9 years and having a good feel of how much heat the managers are placing on the project combined with likely reduction of support or improved code base.

      Once I get a swag from a programmer, I apply an ongoing fudge factor which I develop for each programmer over time. It has values of .75 to 2.0.

      Once the project starts, I use an iterative approach with monthly build/checkpoints. High risk elements are addressed first- easy "crank it out" coding is left for last. If the project starts to fall behind schedule, I help address the reasons why, get more resources, and/or file a notice to management that the project will be at a new date with reasons why. I track all my reports vacations and holidays and confirm they do not over-allocate themselves.

      Once the project is 50% complete, I start looking for new work/projects for them to work on. I prefer to have programmers 60%/30%/10% allocated instead of 100% allocated to reduce downtime.

      For project workers, the main concern is meeting the deadline.

      I absolutely *hate* the waterfall method of programming. I think it is a terrible methodology prone to errors, missing requirements, is based on the fantasy that you can get a complete spec before you start coding, and produces architecture lockin way too early.

      To mirror your experience...
      My experience so far, is:

      - People have a reasonable gut feeling but are afraid of being crucified. Managers have no clue they are being unrealistic until things start failing. They are in fact TAUGHT that the only way to know people are fully loaded is to keep adding things until failure. So it is important to fail gracefully earlier rather than spectacularly later.
      - People prefer to ask for early commitment on deadlines even before they have an idea of what they have to do. (complete agreement)
      - After committing to a deadline, reasonable reasons for changing it will be listened to a few times, after that your ass is on the line- so save your bullets and fire them at the appropriate times.
      - managers HATE dealing with under-confident people. They don't want to micro manage, they want you to say "it's handled' and free them to move on to the next bit. They love competent subordinates who come across confidently. Under-confident subordinates keep managers awake at night worrying. As such, they are total suckers for confident idiots.

      Good post and good points, AC.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    143. Re:brilliant or dangerous? by Maxo-Texas · · Score: 1

      Yet my political sense and knowledge of the internet keeps me from giving that hint. B)

      However it is similar at *many* larger corporations. I can say this. We have had programmers from Exxon say that Exxon's controls, procedures, and buereaucracy are much worse than ours- tho we are gaining on them.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    144. Re:brilliant or dangerous? by jwhitener · · Score: 1

      IT gets a bad rap for having a large amount of "brilliant esoteric magic workers" because it is a field that is poorly understood by our society at large.

      If everyone understood basic code, management especially, that "brilliant but ahole magic programmer" would most likely be seen as just an average ahole with poor social skills.

      The vast majority of projects in IT can be broken down to simple code steps. "Brilliance" in code is usually not required.

      And I'd argue that the majority of programmers who are considered "brilliant" in an average workplace, are most likely just really motivated self-learners. That is not a measure of intelligence, more likely, it is simply a measure of how much a programmer enjoys programming.

    145. Re:brilliant or dangerous? by Maxo-Texas · · Score: 1

      And then the smart programmer, who programs because he loves the orgasmic rush when the code works, still sits on his ass for 8 weeks doing nothing.

      The point is smart programmers want to program. It's like sex. It's like breathing. They don't want to sit doing nothing for 8 weeks.

      When I was in my coding hey day, I would code 10 hours a day without extra compensation. The entire world went away and nothing was more fun, absorbing, or gave more meaning to existence. I could turn 60,000 lines of "hot developer" crap in to 28,000 lines of tight refactored well documented highly reusable gleaming elegance.

      To deny a real programmer the freedom to code and insist they write 40 pages Word documents detailing what changes they made (and those documents are filed and never *ever* looked at again) is a crime. It's like buying a racing horse and riding it 1 day a month while leaving it in the stables the other 29 days.

      Dogs will turn vicious when you don't give them the exercise they need.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    146. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Of course, really extremely smart people can outsmart fools into getting them to do what they want. Really smart people get more irritated working with other smart people who have opposing agendas.

      Not necessarily, depending on what you mean by being "smart". Some extremely technically brilliant people have very limited social skills, and will get frustrated rather than understand how to convince you, even if they are right. As a manger you prefer people that are easy to communicate with, but you should not assume someone who behaves oddly and/or fails to make an argument you can relate to therefore cannot be much smarter than you are and must be wrong.

    147. Re:brilliant or dangerous? by LearningHard · · Score: 1

      As the husband of an actual Psychologist I feel fairly well qualified to say you are full of shit. Manic episodes of Bipolar disorder don't do anything to your "IQ" (which is a pointless tool anyway). The manic means you are in a "good mood." Not you are magically smarter because you pushed the turbo button in your brain.

      I simpler thing to say is:
      I really only try when I care about something. When I care enough to focus I work with much higher efficiency.

      See? That way it doesn't sound like you are blathering on about things you know nothing about.

    148. Re:brilliant or dangerous? by hairyfeet · · Score: 1

      I agree there is a BIG difference betwenn a "Jim" and a Josh", which is why I asked if being likable was really the only difference. Just in case anyone isn't clear, everybody loved Jim. Hell of a nice guy. As long as he wasn't in his office he always had a smile and a "How's it going?" for you. But some seemed put off by how he would "zone out" sometimes and then go rushing back to his cave.

      After practically living in his office for 3 weeks setting up his system folks were like "how do you DO it? Jim doesn't usually let anyone into his inner sanctum and certainly doesn't talk while he is in there and we could hear you two laughing and kidding around. How did you pull THAT off?". So i tried to explain it like this: imagine a world class BBall player. Imagine he is in the zone and every ball that is leaving his hands is nothing but net. Just swish swish swish. Would you walk up to him in the middle of the game and go "Hey, what do you think of the stock market?". No, because you will knock him out of the zone and the next ball he throws is going to be a brick and he ain't gonna be a happy camper. You see, I explained, if we are laughing and joking and I see him zone out while I am in the middle of a story, I shut up. I know that when he does that he isn't trying to be rude, he just thought up something important and if he doesn't grab that ball and make a run for the net he is going to lose it and it is just gone.

      So i guess the major difference between Jim and a Josh is that Josh seems like a major asshole. He knows what he is doing is offensive, he just thinks he is all that and a bag of chips and therefor doesn't give a damn. Jim really isn't trying to be rude when he doesn't write comments or docs. He is just three pages ahead in his head and telling him to go back would throw his groove all to hell and by the time he got back he would be frustrated. That is why I told them to get some nice guy that knew a little bit about code to follow along behind him doing the grunt work. Because telling a Jim he has to write a bunch of comments and docs is going to throw a giant monkey wrench into his performance and slow him down to a crawl. And doing that to a Jim a few times it won't take him long to get frustrated and start looking for another job.

      And I don't know about you, but I would rather pay someone to follow a Jim and do the grunt work. Because a guy like Jim that could just whip off solutions to problems like that just don't come along every day. And everybody loved Jim, they just didn't understand him. That ain't really his fault. His brain just is three pages ahead of everybody elses, working on some huge complex piece of code in his head. Trying to get him to fit into the standard "code, comments, docs and meetings" mold just didn't work with him. Better to have a gopher sitting there to say "I'm sorry, but Jim has his groove on. May I take a message?" than to keep throwing off the man's flow. Because he really was a damned good coder. And I am sure we have all seen( or maybe if we are lucky get to be that) guy that hits the zone and has everything just fall into place. That was just Jim, as long as you didn't throw off the groove.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    149. Re:brilliant or dangerous? by LuisAnaya · · Score: 1
      I do not know. My company have a good way to handle these guys.

      Follow the Method of Operation.

      or... find another job.

      Follow the code of conduct.

      or... fine another job.

      These issues need to be solved straight away, nobody, and I mean nobody, is good enough for this kind of behavior. The reason why he managed to fixed the code in an hour is because he was the only one that understood his crappy code. The only reason he meet the deadlines, is because he writes crappy code.

      There's no need for those losers in an organization.

      --
      Vi havas e-poston.
    150. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Until coders manager coders, instead of managers managing coders, the world will continue to be plagued with poor code designed more for job security than getting things done.

      The problem is that most coders don't have the needed people skills to manage a kitten, let alone an office full of prima donna coders.

    151. Re:brilliant or dangerous? by shutdown+-p+now · · Score: 1

      You know, there is no rule that requires you to wait for your lead talent to quit before you can try to analyze his code. Maybe he would even tell what this "fn" argument is all about.

      Maybe. You could ask, but the answer might as well be, "if you can't understand it yourself, then you're too dumb to understand my explanations anyway".

      In case you've missed it in TFS, that's too often part of the problem - that the "genius" doesn't just produce unreadable code, but his people skills are way below zero. When it's not the case (and it isn't always the case), the problem is solved much easier simply by talking to person in question and explaining them why code maintainability is important etc.

    152. Re:brilliant or dangerous? by HTH+NE1 · · Score: 1

      "The Hitchhiker's Guide to the Galaxy says of the Sirius Cybernetics Corporation products that 'it is very easy to be blinded by the essential uselessness of them by the sense of achievement you get from getting them to work at all.' In other words -- and this is the rock-solid principle on which the whole of the Corporation's Galaxywide success is founded -- their fundamental design flaws are completely hidden by their superficial design flaws."

      --
      Oh, say does that Star-Spangled Banner entwine / The myrtle of Venus with Bacchus's vine?
    153. Re:brilliant or dangerous? by Nicolay77 · · Score: 1

      It totally depends, not only on the code the guy produces, but also on the related activities.

      If that somebody when asked about documentation, smirks, "What documentation?, then I would NOT want to have him in my team.

      Mainly because I know people that can write amazingly good systems, use source version control systems all the time, have everything well documented, and can work nicely with people in the office.

      --
      We are Turing O-Machines. The Oracle is out there.
    154. Re:brilliant or dangerous? by An+Onerous+Coward · · Score: 1

      Let me guess. You think you're a Josh.

      --

      You want the truthiness? You can't handle the truthiness!

    155. Re:brilliant or dangerous? by buddyglass · · Score: 1

      I don't. That doesn't change the fact that I'd fire Josh because he's a jackass and I don't like working with jackasses. If someone thought I were a jackass, I wouldn't fault them for firing me because they didn't want to put up with me.

      That said, perhaps the fact that I haven't been fired yet suggests I'm not a jackass. Or, alternately, that I'm so badass at what I do that my employer has decided to overlook my jackassery. Or the third possibility that my employer is so clueless, or so desperate, that he is either ignorant of my jackassery or feels like he has no choice but to put up with it. Personally, I think it's option #1.

    156. Re:brilliant or dangerous? by Carewolf · · Score: 1

      Of course, really extremely smart people can outsmart fools into getting them to do what they want. Really smart people get more irritated working with other smart people who have opposing agendas.

      No, that is a psychopath. Really smart normal people has natural empathy. Human empathy will constantly guide them to expect other people to behave similar to themselves, and be disappointed everytime other people fails. Some learn to live with the disappointments, others become anti-social.

    157. Re:brilliant or dangerous? by Venik · · Score: 1

      Technical talent and poor people skills often go hand in hand. I've seen too many expensive projects never come to fruition just because the only person on the team capable of getting things done ran out of the room screaming, after seeing the documentation requirements and the team meeting schedule. Aside from the issue of talented sociopaths, there is a much more troubling problem of socially well-adjusted morons who are exceptional freeloaders. Invariably, I prefer talented but maladjusted co-workers to sociable nincompoops. Of course, those who are talented and sociable are always better, but they make look bad :)

    158. Re:brilliant or dangerous? by seebs · · Score: 1

      They would prefer that a project *definately* take 16 weeks instead of taking 2 to 9 weeks.

      Then they're morons.

      If they'd prefer a *definite* 10 weeks to a *probable* 5 weeks, with variance from 2 to 12, then that's rational. But in the case you describe, it's stupid. Solution is to budget for a definite 10 weeks, then assign extra time to additional projects that aren't part of the planned requirements, cleanup, or other bonus development. You're still six weeks ahead *plus* whatever bonus time you get.

      Predictability is important, but if you're fast enough that your worst-case is better than the "predictable" case, then you're STILL better. (The same thing's happened to a lot of real-time systems; if you can't guarantee which millisecond something will be done, but it's always done in between a tenth and a third of the time you have available, that is good enough surprisingly often.)

      --
      My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
    159. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      A cleaner sig might be:

      Having an advanced degree doesn't make you an expert on topics you didn't study.

      Just a suggestion in the spirit of this topic :)

    160. Re:brilliant or dangerous? by Venik · · Score: 1

      No, but I think I am smart enough to work with one.

    161. Re:brilliant or dangerous? by CAIMLAS · · Score: 1

      I disagree with you on the argument over whether there's a higher concentration of brilliant assholes in IT. I think there most certainly are.

      IT, and other technical, fast-moving fields, tends to invite those who excel over their peers intellectually. This intellectual superiority, coupled with spite bred into them through years of condescending schooling and tedious tasks, leads to a general feeling of superiority and pretentious behavior. It takes a strong will to fight it.

      However, IT is certainly not the only field with people like this. Medicine and finance are full of assholes like this: they're drawn to the field because the field has the prestige they feel they are finally deserved, and due to their intellect and ability, they are able to earn it.

      The assholes in most other fields, while often smart and capable, don't compete on an even intellectual footing with the 'elite' fields. If they did, they'd make more.

      I'd also argue that the more socially dysfunctional 'intellectual elite' jackasses end up in IT. They're paid less than lawyers, doctors, etc. and are at the lower end of things, socially. From my experiences, they're probably more likely to have aspergers or something similar, and therefore be more mathematically/myopically inclined - arguably a positive trait for someone who has to micro-focus on mathematical tasks.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    162. Re:brilliant or dangerous? by colinrichardday · · Score: 1

      <voice style="alice">Must control fist of death!</voice>

    163. Re:brilliant or dangerous? by shutdown+-p+now · · Score: 1

      Technical talent and poor people skills often go hand in hand.

      This is an often-repeated statement, but it doesn't make it a fact. I would be interested in seeing the actual statistics, but from my personal experience, sociopaths make the minority of geeks (though quite often it's a vocal one online).

    164. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      You've never worked in the field of CGI visual effects.

    165. Re:brilliant or dangerous? by cerberusss · · Score: 1

      torture will get you the answer you want quickly, but the answer itself will likely prove to be worthless.

      As a professional torturer, I have to take offense here. I'm not looking for answers! Torture is a journey, not a destination!

      --
      8 of 13 people found this answer helpful. Did you?
    166. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      All of this is just to say, I'd rather have people that I can rely on than theoretically brilliant people who are just going to do whatever the hell they feel like.

      You are exactly the kind of non-programmer that I fucking hate to work for. You have no concept of what coding is, and how it is IMPOSSIBLE to predict how long it's going to take to code something that's never been done before. You think that the amount of time it takes to code something is a choice that the developer makes. Good programmers run as fast as they can from people like you.

    167. Re:brilliant or dangerous? by MrHops · · Score: 1

      Here's one reason why... I was Bipolar II which meant I was mostly manic. As a result I was easily angered, very enthusiastic, easily empassioned and highly creative. My brain went a MILLION miles per hour in that state and I had brilliance that I couldn't contain at times. I already have an IQ of 160 and during that state it was up 5-10 additional points (when I could stay focused).

      Tack onto that the boundless energy the condition gave me and the fact that I never slept in that state and you have exactly what you described. I felt untouchable and alive like no one could imagine. So why did I go on meds? Well, that's the trick. How do you get bipolars or other people who have a self destructive disorder that makes them feel superior or more intelligent go on a med that dumbs them down or slows them down?

      I hit that point where I realized my condition was isolating me and shutting me off from everyone else around me. When I examined my life, I realized I had no one to blame but myself; I burnt people out like matches but couldn't see that I was the one common factor in all the damaged relationships. More exactly, my condition.

      I eventually got better and now write my own documentation, get along with others, don't have mood swings at work, etc etc. It took me years and lots of hard work and effort to get over old emotional habits... the meds don't do it alone.

      But I guess what I am trying to say is that sometimes brilliance comes with madness. Sometimes it's just madness, sometimes it's both. Getting them to help themselves though can be almost impossible though.

      Amen. The primary differences for me was that I didn't use meds*, and it took being homeless for a year to force a change. I blame it on Asperger's. :-) (see earlier in this thread...)
      On the other hand, intentionally reconstructing my personality made me much better at self-analysis and learning the rules regarding social cues.
      I'm less "brilliant", but people talk to me now. :-)

      * No, I'm not one-upping anyone. The full story is tedious and irrelevant to this response.

    168. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      1 week is a luxury - usually it's "crap need this, tomorrow good for you?"

    169. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      I just finished a project like this. I gave a realistic detailed breakdown of each part how long it would take in hours, with a risk level for each part.

      I then presented this and was told "Too long, reduce the estimates.". So I reduced the figures. However this dosn't make the amount of work any less.

    170. Re:brilliant or dangerous? by frank_adrian314159 · · Score: 1

      How do you know you're not a jackass?

      If you care that you might be one, you're probably not.

      --
      That is all.
    171. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      only to find out that the employees simply didn't understand how the business worked.

      Because the workings of the business were poorly documented by bosses who wanted to keep it a magical black box that only they understand?

      I suspect that this happens as often (if not more, across all industries) as programmers wanting to keep their product a magical black box that only they understand.

    172. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Of course, really extremely smart people can outsmart fools into getting them to do what they want.

      Yeah, that's bullshit. You can't polish a turd. I have a CS degree, and my job has become "babysit the guys with the associate's degrees." You know, the ones that are lazy and can't program. So instead of belting out design docs or code, I get to spend all day correcting shit code I could have written faster myself. That only lasts so long before the smart person says "fuck it" and walks. there's no "tricking" shit programmers into producing quality work.

    173. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Even tho I was smart enough to move out of programming and into management

      Oh yeah - that's real smart. But at least the rest of us won't have to deal with your code. Oh, wait... now we will have to hear you say "I was a developer once you know - I know what I am talking about!"

    174. Re:brilliant or dangerous? by geordieboy · · Score: 1

      But is much code really "brilliant"? I accept that certain algorithms and ideas in computer science are brilliant (Djikstra's algorithm, quicksort, realtime collision detection), possibly also some ideas in software engineering and design, but code is usually just a set of logical steps in some programming language. It's easy for it to get complicated, but I think it's rarely brilliant, especially if the domain of the code is something prosaic like a desktop application or a database or networking. As many people here are saying, when it comes to code what *is* brilliant is figuring out how to avoid complexity in the first place.

      --
      The world is everything that is the case
    175. Re:brilliant or dangerous? by ukyoCE · · Score: 1

      Seriously now -

      "he would just blaze out this huge complicated mess of code that frankly WAS brilliant"

      What line of work are you in where there are problems that warrant "huge complicated messes of code"? Every huge complicated mess of code I've ever seen, period, has been a bad one, that someone could have done more readable, more maintainable, and usually in half as much code to boot.

    176. Re:brilliant or dangerous? by MartinSchou · · Score: 1

      Even if we extend my scenario to yours (Ed's managed to build the entire thing, on his own, in 7 days [aside, Ed seems to work on a slightly slower schedule than God]), how are you supposed to get Ed to explain this to you, when he's obviously too occupied in his work to answer any questions? After all, if he's building it in 7 days (I think a low estimate on the channel tunnel was about a decade, just to put things into perspective)?

      No matter how you cut it, if Ed doesn't document what he's doing (too busy), I'd like to know how you're supposed to have managed to find these engineers capable of understanding Ed's design - in those seven days.

      My point still stands - our field cannot be considered science nor engineering, if what we're doing isn't repeatable nor documented. It is, at best, akin to just whipping together some timber to make an outhouse.

    177. Re:brilliant or dangerous? by ukyoCE · · Score: 1

      Exactly, jellomizer. From what I've seen at bigger companies, guys like Josh don't exist when there are enough coworkers around to call him out as a dumbass who codes first and designs later (resulting in the convulted illegible code that is their hallmark).

      Re: the grandparent post's comment of: "It is equally amazing how programmers of average ability insist on branding brilliant code they have trouble understanding as convoluted and obscure."

      Code that is overcomplicated, convulted, and obscure is also unmaintainable, undebuggable, and all-around worthless.

      Errors go up with code complexity, as does the time and effort required to debug said code. If no one else on the team can work with the code, it's that much worse.

      If he can't design the code beforehand to be simple and well-documented (or self-documenting) then it isn't good code, and he isn't a good coder.

    178. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Wow, let me guess - you think you're a Josh. A one-man genius who is better than everyone else in the world. And they all hate you for one reason only - because they're jealous!

      I don't know what job you work at where "fast" is more important than "maintainable", but I suspect you're wrong even in your own particular job. And as for the reliable part, if nobody can make heads and tails of it, it's absolutely NOT reliable. If there's a bug in that code and your genius isn't around, or left the company, then you're screwed. It's about as unreliable as you can get.

      Reliability is far more important than speed. You can rearchitect for speed. You can optimize for speed when you find an *actual* bottleneck. You can add more servers. But if you've got an unmaintainable mess of a codebase that no one can fix, you're screwed.

    179. Re:brilliant or dangerous? by An+Onerous+Coward · · Score: 1

      You're right. There's only so much you can dumb it down without sacrificing the quality of the code. As they say, make it as simple as possible, but no simpler.

      Nevertheless, I would argue that you should be trying to accommodate a programmer less skilled than yourself.

      Sometimes an algorithmically inferior, but more easily understood algorithm, is actually the way to go. If your performance requirements are meager, and the elegant algorithm will take significantly longer to implement -- or for the next guy to comprehend well enough to debug -- then the simpler way is better for you, and for the people who come after you.

      However, if you think there are strong reasons for using the awesome algorithm, go for it. There's a huge difference between, "I have to write code that a less-skilled programmer can deal with" (which is true) and "I have to write code that a less-skilled programmer can deal with at his current level of understanding" (which is the strawman you seem to want to argue against).

      It's certainly proper to leave your explanation at "implements the Viterbi algorithm to find the most likely next keystroke", so long as the code itself is a pretty straightforward implementation. You might want to explain where you're keeping critical data, like your path history. But nobody is asking you to teach the concepts if they're documented elsewhere.*

      Do we try to make brain surgery so easy that a 10-year-old could do it?

      No.

      That depends entirely on whether or not a ten year old will be performing the brain surgery. You can complain all you like about your idiot co-workers, and how they're not fit to kiss Donald Knuth's loafers. Go ahead. I love a good rant. But like it or not, you're doing your employer a disservice if you write code that they don't have a prayer of maintaining.

      * If you've invented your own algorithm, don't gripe about having to document it clearly and thoroughly.

      --

      You want the truthiness? You can't handle the truthiness!

    180. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      If you can write a complex system such that a teammate can open any random code file and think "what's so hard about that?", then you deserve some of the appreciation that "Josh" made a grab for.

      Well, I RTFA'd and even clicked on a few links to his previous stories. I've since closed the tab so I can't tell you which one, but he told a story about two managers. One was nice, the other was a dick. Layoffs were going around, and I'm sure you can imagine how it ended up (the nice guy finished last).

      This is true in programming as well. When a moderately technical manager looks at some complicated spaghetti code, he probably won't be able to understand it. That will make him think it's doing something advanced and complicated, and his estimation of the person who wrote it will go up.

      If, on the other hand, you write code so clear that your boss (who maybe wrote a couple of Perl scripts back in the 90s) can immediately understand the whole thing and what it does and why it does it that way... he will think it's so obvious that anyone could do it. And his estimation of you will drop, because it probably took you quite some time to write code so clear that your boss thinks he could do it.

      So the bad programmer gets praised, awarded, promoted, etc., while you get left behind (or let go).

      It's a double-edged sword. You've got to have a boss who either (a) was a good programmer in his day, and knows that clear code takes a lot more work than you'd expect; or (b) knows nothing about programming and therefore has to trust his guys when they tell him the job was done right. Unfortunately, because of the aforementioned tendency to reward mediocre programmers who make simple tasks look very hard, usually the manager is a former mediocre programmer. A mediocre programmer who has been conditioned, due to years of undeserved praise, into believing that he's God's gift to software development.

    181. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      I can't tell you how many hours I've spent cleaning up the mess left by people who take dumps in the lobby, and I'm betting I'm not alone either.

    182. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Do not meddle in the affairs of Wizards, for they are subtle and quick to anger.

    183. Re:brilliant or dangerous? by pla · · Score: 1

      I'm not convinced that there's a higher penetration of this in IT than any other profession.

      CEOs, for example.

      I can't help but notice that most of the qualities that various highly-modded posters have called "intolerable" in programmers, count as goddamned prerequisites for upper management.

      The "Josh" in question could probably pass, in attitude if nothing else, for a Richard Branson.

    184. Re:brilliant or dangerous? by readin · · Score: 1

      That, IMHO, is the root of more miscommunication between management and developers. Far too many managers don't quite understand that programmers *hate* interpersonal conflict, and will casually agree to just about *anything* if they think it will get the person to quit bothering them. The constructive way to deal with it is to begin by asking the programmer for a range (best case vs likely worst case), then ask him to identify the riskiest factors influencing the range, then nudge him to tackle those factors first so a better estimate can be refined quickly. Just don't make him feel like you're twisting his arm or browbeating him, because estimates are like information from interrogation -- torture will get you the answer you want quickly, but the answer itself will likely prove to be worthless. It is an injustice that the parent post can only be given a +5 insightful rather than much higher number that would be more fitting.

      --
      I often don't like the choices people make, but I like the fact that people make choices. That's why I'm a conservative.
    185. Re:brilliant or dangerous? by Peaquod · · Score: 2, Informative

      Find a guy with a little programming knowledge who can sit in the office next door and write docs for Jim.

      Perfect answer. I've worked with several folks like Jim over the years, and consider myself to be in the same vein. Yes, we can and will write documentation if we have management that requires it. But we'd much rather be having fun solving problems, and wise management will make sure that is what we are doing most of the time. Right now I work for a very small research company - the entire tech staff is two engineers (not "software engineers" - computer vision & robotics) plus two programmers. Our code is messy and poorly commented with no documentation - we get away with this because it is research grade code, and because our team is so small. We (the engineers) understand it just fine. The poor programmers who must port it to other languages simply have to put the blinders on and copy the functionality. We could document the code to death, but that wouldn't be any substitute for the fundamental knowledge in physics, statistics and algorithms required to *really* understand the code. When and if we grow into a production environment where many people will have to support (and understand) the code, I trust our management will be wise enough to hire other folks to do the bulk of the documentation, with help as necessary from the engineers. Because there will always be more profitable things for us to be doing, which we actually enjoy.

    186. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      he didn't say "brilliant XOR dangerous", did he?

    187. Re:brilliant or dangerous? by JohnFluxx · · Score: 1

      Lol, you've clearly never had to debug anything complex.

    188. Re:brilliant or dangerous? by Trifthen · · Score: 1

      The plural of "anecdote" is not "data".

      As no studies I've seen have collected data on the statistical distribution or predisposition of specific personality archetypes within a career or general field, I sadly must defer to a random distribution of the human genotype among them, else I risk projecting my own cultural or personal bias onto the situation and reach a predetermined, and thus fundamentally flawed conclusion. But that is a constraint I place only upon myself; you, of course, are more than welcome to utilize your own methods of scientific inquiry when vetting dubious sweeping statements and agendas.

      --
      Read: Rabbit Rue - Free serial nove
    189. Re:brilliant or dangerous? by DriedClexler · · Score: 1

      Interesting point. I was once actually in a situation of over-general code. My project lead asked me to spend about two days reading some other co-worker's code[1] and finding out how to "cut out enough fat" (lines not essential to his current task and input set) and explain the rest to him so that he could understand how it worked. The reasoning being, he wasn't comfortable using it unless he understood it all himself and his "time to understand" was maybe exponential in the length of the code.

      But here's the thing: as I was reading through it, my reaction was more like, "Wow! This programmer did a really good job in making sure to gracefully handle everything possible that could go wrong". It was the kind of code I aspired to write myself.

      It gets stranger: the project lead had already gone back to the programmer with the same request, and the programmer adamantly refused to make the changes, and for reasons that took a very long time to explain. (And I probably made a lot of points in defense of the code that the programmer did.) Worse, the code (as you warned about) took a long time to write. Apparently, the project lead didn't check up on him.

      So, even given my reservations about reducing the code's generality, I went ahead and shrunk it down. Hopefully the lead kept the original for later ...

      [1] The code, if you're curious, implemented an algorithm that shifted around locations of masses to create a set of masses with equivalent centers of mass but met different position constraints.

      --
      Information theory is life. The rest is just the KL divergence.
    190. Re:brilliant or dangerous? by Javaman59 · · Score: 1

      That's where "experience" comes in. With experience, we learn to write the more general solution almost as quickly as the shortest-path. We have our naming conventions memorised, we've got a few favourite design patterns, and we get a "feel" for when to refactor - for when refactoring will expedite the initial development, not just the maintenance.

      With experience, we also learn to avoid fancy features which complicate the code, thus getting the best of both worlds - faster development, and better structure.

      We also learn when to leave well enough alone - when a bit of ugly, repetitive, unfactored code isn't doing any harm, and is worth 0 time improving.

      But I've always had a dislike for excessive time spent on building the more general solution, and I've come across several projects which were nearly killed by it.

      --
      I'm a software visionary. I don't code.
    191. Re:brilliant or dangerous? by allgoodnamesaretaken · · Score: 0

      I like this way of looking at it... and the fact that there are very few people posting on here with such an insight proves how well trained most of us are in conforming.

    192. Re:brilliant or dangerous? by Kjella · · Score: 1

      For the record, I worked at a place where we could release SOX-compliant changes within an hour of the need arising. However, our normal release cycle was weekly and we passed all of our SOX audits. If your company's productivity has declined 75%, don't blame SOX.

      While I don't doubt that it's true, I think the point is that by making it about legal compliance rather than actual business needs the IT department has absolutely no say in the matter. Your lawyers might have figured out that's good enough, their lawyers were of a different opinion and that's what count. It doesn't matter if the whole development team is in uproar as long as there's a lawyer standing on the other side saying "We must do this to be SOX-compliant" because your CFO sure doesn't want to be up federal charge and honestly, that kind of covering your ass I find perfectly natural.

      --
      Live today, because you never know what tomorrow brings
    193. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Clever code means simple and elegant in my world. I guess in yours it means a steaming pile of ....

    194. Re:brilliant or dangerous? by Aceticon · · Score: 1

      Elegance is the measure of truly great code - when you read a piece of code which does a complex functionality and yet it flows logically in an easy to follow way, you know.

      Making clever code shows that you are brilliant enough to build a complex logic and flow structure in your mind and transform it into something that works (no mater what the language).

      Making elegant code shows that you are brilliant enough to build a complex logic and flow structure in your mind and transform it into something that works (no mater what the language) and that you are brilliant enough to understand howy you, others and the software development process fit together and how the code you make and the externalities of how software is created and how it is used can be matched.

      Clever code might show genius, but elegant code shows genius and wisdom.

    195. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      For those of us who work in the real world, the reason is that the new guy is cheaper, and since he now knows "everything", he must be just as good.

      Yes, that falls under "your management team sucks and doesn't get it", but again, out in the real world, a job means money means food. "Management suck, I'll go find a new job with better management" isn't really an option. Oh, and if you do, you're likely to discover that the new management is just as bad.

    196. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Business people understand bridges. They don't understand software.

      Because of this, you requirements that you would never get when building a bridge. I compare this with having a house built: In software, the business people set the requirements for a single car garage, but after several changes to the requirements, what you are actually building has turned into a shopping mall with a skyscraper on top.

      Do this with a "real world engineer", they will get told: "That's not possible, the garage wasn't build to carry that weight. We would need to bulldoze the thing, and start over, and it will take 15 years to build". And that's final, you can't argue with the laws of physics, and if you try, your insurance rates will be higher than the requirements said the building would be.

      If a developer tries the same thing, the answer will be "we don't have time for a rewrite, and btw, the shopping mall needs to be done by tuesday next week, as we already promised the customer that we could deliver by that day before we even asked you".

    197. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Mgt: "How long do you think this will take?"

      Programmer: "Er, I guess 3 months or so, assuming nothing major goes wrong along the way."

      Mgt: "That's too long! We need it in 8 weeks. Can it be done?"

      That's the nice version.

      Where I've worked, it's been "We need this done in two weeks. We already promised the customer it would be done in three weeks". And that's it.

      Then one of two things happen:

      Either it did really take three months to do, and we lost the contract. And that was our fault, because we couldn't have it done to a deadline, even though we knew the deadline up front. It didn't matter that it was impossible, or that the business people had actually known about the deal for a couple of months before actually telling IT.

      Or, we somehow got lucky, or our estimate was completely wrong, and somehow managed (with a lot of overtime) to have it done in two weeks. In which case it usually turned out that the customer would be ready to actually receive the data for another couple of months, because our business people had put just as much pressure on THEM to get the deadline.

    198. Re:brilliant or dangerous? by Lilith's+Heart-shape · · Score: 1

      Really? Most of the people I've worked for expect the project to be done before I've finished reading the requirements -- which were usually scrawled on a paper napkin.

    199. Re:brilliant or dangerous? by aquatone282 · · Score: 1

      Now, in the software industry, we're very fond of calling ourselves engineers and architects. Unfortunately most of us (even in companies) really don't reach that level of excellence - we don't document what we do, either because we're too lazy or because the companies don't want to spend money doing that. That's fine - just don't consider yourself or what you're doing software engineering.

      Too right. I've worked with engineers, have engineers for friends, and I can tell you I'm no engineer, even though that's what my company calls me (and bills me out as). I'm a software developer of business information systems and I'd be embarrassed to ever call myself an engineer.

      --
      What?
    200. Re:brilliant or dangerous? by swilver · · Score: 1
      Sometimes things simply are complex. For example, recently I was working on an algorithm that given a list of (value, instantInTime) pairs would determine the biggest difference of 'value' in a certain time interval. The values are not evenly distributed, can contain huge gaps, or multiple measurements in short periods. The value (as measured) is valid until another value overrides it at a later instant in time . Which means to get the value at a certain point in time, you need to walk the list to figure out what the value is at that time.

      That's the easy part. Walking the list could be done using a binary search algorithm, but that wasn't even the complex part. To determine the biggest X second difference in a set of values that spawn 300 seconds, you could do this (X = intervalInMillis):

      0 int getBiggestDifference(ValueSet values, int intervalInMillis) {
      0 int biggestDifference = 0;
      0
      0 for(int t = 0; t < 300 * 1000 - intervalInMillis; t += 100) {
      0 int diff = Math.abs(values.getValueAtTime(t) - values.getValueAtTime(t + intervalInMillis));
      0
      0 if(diff > biggestDifference) {
      0 biggestDifference = diff;
      0 }
      0 }
      0
      0 return biggestDifference;
      0 }

      That's the simple, inaccurate, slow version. Inaccurate because it only checks steps of 100 ms, slow because it calls "getValueAtTime" very often. Increase the accuracy or the size of the period to search, and it gets even slower. It however works 99% correct and is easy to understand.

      The complex version took me quite a while to wrap my mind around, not to mention a lot of unit testing and comparing it with the "simple" version to make sure it really performed correctly (there's quite a few of nasty edge cases). It's also about 4-5 times more lines of code involving temporary data structures, and pretty much impossible to follow without a big comment to explain the algorithm used (I'm not even sure if there's a standard algorithm for it). It however scales far better when huge number of values are involved.

      I hate excessive simplicity for the sake of clarity, this just tells me it was written FOR people that cannot be bothered to learn the language they're using. A place I worked at was actually considering banning certain practices that are part of the language, like multiple returns, ?: conditionals, regular expressions, fall-through cases, and so on. That's all nice and dandy, until those dumbed down programmers need to debug some framework they're using and donot understand what some rarely used operator does. Let alone having them work on threading problems or figuring why a garbage collected language is running out of memory.

      If they cannot figure out a piece of complex, badly formatted piece of garbage code, then what hope is there they can debug real problems.

    201. Re:brilliant or dangerous? by swilver · · Score: 1

      The hit by the bus argument does not fly. It may take a while to figure it out, but there are people that can figure it out.

      When practically the entire senior programmer team quit on the spot at a company I used to work for (I was one of the ones that quit), I figured they'd be in a lot of trouble, as quite a lot of the code written was never even seen by the ones that remained. Yet, they're thriving. They brought in some young talent and raised wages for the remaining team, and they're doing just fine. Yes, it did wake the company up (teams were restructured, wages raised, programmers actually got a say in things) and there were some problems with the next release cycle, but they're doing fine again.

    202. Re:brilliant or dangerous? by swilver · · Score: 1

      Unfortunately, in the world of software development, a less brilliant programmer will also have less foresight or not have a proper grasp of complexities involved with multiple users, multiple threads, or anything else that involves scaling up an application to serve thousands instead of just him/herself when debugging it.

      A brilliant programmer can not only write code faster, they can do it with less bugs, more foresight, using better algorithms and more often than not produce something that is easier to maintain/configure/extend later on as well. The end result is often an order of magnitude better than what an average programmer produces. Unfortunately, management rarely realizes how big a difference it can make on the bottom line, and rarely will these people be actually paid a salary that is an order of magnitude higher (certainly not more than their "manager"...)

    203. Re:brilliant or dangerous? by NormalVisual · · Score: 1

      It may take a while to figure it out, but there are people that can figure it out.

      I never said people couldn't eventually figure the code out, but that doesn't do any good when it takes them three months to do so, and there's a deadline looming two weeks away. When I said "total cost", that includes lost opportunity costs, lost customer confidence, etc. in addition to immediate dollars and cents.

      You shouldn't ever assume you're truly irreplaceable, but that doesn't mean your former employer won't incur some industrial-strength headaches in adapting to your absence.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    204. Re:brilliant or dangerous? by nine-times · · Score: 1

      Yeah, but part of the question, really, is who is this "brilliant programmer". The problem is the "brilliant programmer" you're talking about probably isn't the same guy as one who struts around thinking the rules don't apply to him because he thinks he's such a brilliant programmer.

      People who are truly brilliant are invaluable. People who think they're brilliant are a dime a dozen.

    205. Re:brilliant or dangerous? by Foofoobar · · Score: 1

      Well according to many specialists on bipolarity including the author of 'Touched By Fire' who has specialized in the disorder, mania does in fact raise your IQ score. Mainly because you test better. As one doctor explained it to me, bipolarity isn't so much an emotional disorder as it is a disorder of energy levels and how they affect our emotional states.

      Regardless of your professional opinion, professionals in the area of bipolarity disagree with you. So I suggest as a professional doing some reading in this area before shooting your mouth off. Honestly I don't know many professionals who would tell someone who bears their soul that they are 'full of shit' so I have to also question your claim of professionalism as well.

      --
      This is my sig. There are many like it but this one is mine.
    206. Re:brilliant or dangerous? by Anonymous Coward · · Score: 0

      Have to say I agree with Skreems. I have worked with brilliant coders on projects, some of whom think they are geniuses, being rude and inconsiderate of their teammates. On the other hand some have been just as good if not better coders while also being considerate and clearly documenting what they have done.

      I think some of the worst are the people who like one language and spend their time bashing and refusing to get involved with projects that involve other languages. I've come across this mostly with people who like C/C++ and think that only the lowest of the low would get involved with php, java etc....

      However, there is sometimes a mid-point. The best C++ programmer I know will spend most of his time leading up to a deadline messing about and then put together the actualy software in a 48 hour burst. The point of all his playing about is that he will deeply understand what he is trying to do when he actually comes to write the software and it will be of outstanding quality. However, everyone else is pulling their hair out because there never seems to be enough time for him to finish it. He has yet to not meet a deadline.

    207. Re:brilliant or dangerous? by obarel · · Score: 1

      Whenever I hear of someone who's a brilliant bully, I think to myself "I bet there's someone even more brilliant who's also nice to work with".

      I've only met one genius (so far), and he was a very nice person. I've also met many bullies. There's no excuse to being a bully, regardless of quantity or quality of code (or amount of money made or saved). If you're that brilliant then surely you can learn how to be a human being.

    208. Re:brilliant or dangerous? by CountBrass · · Score: 1
      I'm sorry but that's just wrong.

      package binary;

      public class Finder {
      public static int find(String[] keys, String target) {
      int high = keys.length;
      int low = -1;
      while (high - low > 1) {
      int probe = (low + high) >>> 1;
      if (keys[probe].compareTo(target) > 0)
      high = probe;
      else
      low = probe;
      }
      if (low == -1 || keys[low].compareTo(target) != 0)
      return -1;
      else
      return low;
      }
      }

      This example from Beautiful Code published by O'Reilly is complicated (not really but it does require some basic comp sci knowledge you wouldn't expect a 10 year old to have). Or how about:

      (?<=,|^)([^,]*)(,\1)+(?=,|$)

      (example from http://www.regular-expressions.info/ which removes duplicate lines from text)

      I'd argue that in both the cases the "simple" and "readable by a ten year old" versions would be much more bug prone, complex and inefficient.

      Programming does require skill and some education and it is perfectly reasonable to expect that someone who is trying to understand some code is capable of spotting a binary tree search and is capable of interpreting some regex. If somone doesn't have that capacity then they should go work for HR and not expect the rest of us to dumb down to their level.

      --
      Bad analogies are like waxing a monkey with a rainbow.
  2. Reiser? by Anonymous Coward · · Score: 3, Funny

    Reiser?
    Couldn't resist.

    1. Re:Reiser? by Chrisq · · Score: 4, Funny

      Reiser? Couldn't resist.

      Neither could he

    2. Re:Reiser? by Anonymous Coward · · Score: 0

      Reiser?
      Couldn't resist.

      Neither could he

      too soon.

    3. Re:Reiser? by DiEx-15 · · Score: 1

      I got an answer - A Baseball bat upside his head!

      I am really surprised that this "Josh" doesn't have a ton of sexual harassment / discrimination lawsuits that would make Micro$oft blush in shame...

  3. Dangerous by Hatta · · Score: 4, Funny

    But only if you're married to them.

    --
    Give me Classic Slashdot or give me death!
    1. Re:Dangerous by phagstrom · · Score: 0, Redundant

      only if your name is Reiser

    2. Re:Dangerous by teknopurge · · Score: 1

      Killer filesystem you-say?

    3. Re:Dangerous by Anonymous Coward · · Score: 0

      Noooo... reeeeally? Congratulations on getting the joke.

  4. Can we stop enabling these people? by ivan256 · · Score: 5, Interesting

    Translation: Control is more important than productivity.

    I think it would be a lot harder for this guy to have made his point without such an extreme example.

    1. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 5, Insightful

      As an antisocial mindshare person, I resent this topic. Because perpetuation of my antisocial liberties is the precise reason I developed subject matter expertise in the first place.

    2. Re:Can we stop enabling these people? by cshark · · Score: 0

      Why do people feel the need to control quirky geniuses who are doing nothing wrong? Seriously, there's nothing in this example that's out of the ordinary, except for the women's t-shirts. That's what you get for having a casual work place. My thought would be that if the author has such a problem with this guy, maybe he needs to be skilled enough to replace him.

      --

      This signature has Super Cow Powers

    3. Re:Can we stop enabling these people? by Hozza · · Score: 3, Insightful

      Translation: Control is more important than productivity.

      Err..No that doesn't really match what he's trying to say. By being so belligerent "Josh" was controlling the whole process.

      So the choice is: control by a passive-aggressive mentant who refuses to talk to you, or control by management , who should (in theory) be much more approachable.

      Of course, if you management team has fewer social skills than an unwashed anti-social 16 year old, then go with the mentant every time.

    4. Re:Can we stop enabling these people? by DrLang21 · · Score: 5, Insightful

      if the author has such a problem with this guy, maybe he needs to be skilled enough to replace him

      That's part of the problem. Having irreplaceable people on your staff is bad for business long term. If someone is laughing at you for asking for non-existent documentation that they should have written, they should be fired immediately. The cost to business if this guy were to leave will only get worse with time and probably already outweighs the savings of keeping him on.

      Lesson, you are replaceable. If you are not replaceable, then you are too dangerous to have.

      --
      I see the glass as full with a FoS of 2.
    5. Re:Can we stop enabling these people? by Maximum+Prophet · · Score: 5, Insightful

      If your competitor hires this guy they might be able to outproduce you just long enough to put you out of business. Doing things right is important, but staying in business is the *most* important thing. (It's a gamble, like all of life, you roll the dice and take your chances.)

      --
      All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
    6. Re:Can we stop enabling these people? by CmdrGravy · · Score: 1

      Whats wrong in the example is that no one else in the business appears to have any clue what this guy was actually doing or how he was doing it. His work should definitely have been documented.

      On the flip side his manager should have been reviewing his work to make sure he was explaining it properly to anyone else who may have to work with it and it wasn't overy convulted or uneccessarily complicated.

    7. Re:Can we stop enabling these people? by Don853 · · Score: 4, Insightful

      That's not true. The guy is refusing to document code and skips work on a whim. He's not dependable but he tries to tie his coworkers to his capricious tendencies. He's arrogant and socially inept. Most of the most brilliant people I've worked with are very confident, but they're not all assholes. This "Josh" doesn't sound like someone I'd want on my team. The code doesn't need documenting? Seriously? Brooks thought that was outdated in 1970.

    8. Re:Can we stop enabling these people? by ShieldW0lf · · Score: 0, Flamebait

      Because it's not enough to stand on the shoulders of giants. They won't be satisfied until they've managed to put a bridle on.

      Thing is, the wise genius developer will realize, when the whole world is standing on your shoulders, you're already the ruler, forever and ever amen. They're nothing but little ants, and the situation will never change. Not because you hold them captive, but because without you, the quirky genius, they will be back in the muck where they belong, and their greed and self-importance will never allow that to happen. They are not the ones with intrinsic power, they are nursemaids for genius, or they are nothing at all. And they know it, that's why they're there.

      As a quirky genius, I have to say, if you don't like the way we do it... go fucking do it yourself. Should be good for a laugh...

      --
      -1 Uncomfortable Truth
    9. Re:Can we stop enabling these people? by ivan256 · · Score: 4, Insightful

      For the sake of argument, let's take for granted that nobody else can do what this guy does. Otherwise they'd have replaced him by now. Also keep in mind that he's using an extreme example to make a broad point. We'll take Mr. Speigel's words at face value, since we're to assume that he's not being hyperbolic about the behavior of said employee...

      "Sure, he was whipsmart and could churn out code that saved the company millions"

      His argument is that it's worth millions of dollars to not have to deal with this guy. Who has the bigger ego in this situation?

      If I'm running a business, and a middle manager tells me that the company should spend millions so the team doesn't have to deal with an asshole, I fire the manager, not the asshole.

    10. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      ok, I will. You're fired. How you like that asshole? You can leave now and please take your self importance with you.

    11. Re:Can we stop enabling these people? by SlashDread · · Score: 1

      That must be the stupidest lesson ever. Some people excell, and you want to FIRE those people? You must want everything to be run by Joe D. Minus.
      Enable him, and get a cheap geek documenting his ass. Contain and manage risk, not avoid all, especially not at the cost of all innovation.

    12. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Lack of documentation is a problem. Refusing to assist fellow employees until the last second when the customer is pissed off is a problem. What if rather than disappearing after being talked to about his attitude, he had died in a car crash or something random? The company would still have had to waste time and money cleaning up and documenting his code, whereas if he had just documented it to begin with it wouldn't have mattered.

    13. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Those "irreplaceable" = dangerous cliches get a bit tiresome.

      Everyone is replaceable. It's just more of a pain to replace some people than others.

      Customers might also decide to replace your product/service with something else.

    14. Re:Can we stop enabling these people? by talldean · · Score: 5, Insightful

      If you can't replace a relatively inexpensive employee, you're one traffic accident away from being out of business entirely. Let your competitor take that risk. "It's a gamble, like all of life, you roll the dice and take your chances." The odds of your competition hiring the guy - through a noncompete clause - and him being the tipping point of sending you out of business? Miniscule. The odds of a daily accident, or family problems, or the employee just leaving for greener pastures? Enormous.

    15. Re:Can we stop enabling these people? by Registered+Coward+v2 · · Score: 2, Insightful

      Translation: Control is more important than productivity.

      I think it would be a lot harder for this guy to have made his point without such an extreme example.

      While I agree the example was extreme, the point was valid.

      It's not about control but about creating a product that is sustainable over the course of its life. That requires code that can be understood and troubleshot by others; not just the author. As was pointed out in TFA; Josh's code may have been the casue of teh problem from teh start.

      The ability to write code that works quickly is not genius, it's the mark of an idiot savant. Real genius is writing tight code that works and can be understood by others.

      Despite the pain of rewriting the code once Josh left I bet the company was better off in the long run because they had fewer customer complaints and when they did they could actually fix the problem without dealing with Josh.

      --
      I'm a consultant - I convert gibberish into cash-flow.
    16. Re:Can we stop enabling these people? by Swizec · · Score: 5, Insightful

      You stop being a quirky genius soon as you declare yourself as one. Since then you're just a wannabe poser.


      See that's why I'm NOT a quirky genius.

    17. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      I get the feeling that Josh is an exaggerated strawman.

      Was Josh allocated the time to document his code? If not, then I think I know why he is laughing at you.

      As someone who has more in common with "Josh" than with the author of this claptrap, I have to say that being brilliant is dangerous.

      I generally lay low and hide my brilliance from everyone that doesn't need to know that I'm (alot) better than people who have 3 times as much experience as I do.

      It's gotten harder to hide my brilliance since I now write a newsletter about .NET for my company... but my lists of enemies and friends have increased exponentially.

    18. Re:Can we stop enabling these people? by __aagmrb7289 · · Score: 5, Insightful

      I have yet to encounter a situation where anyone is THIS good (or where every other employee is THAT bad). And if a business WAS in that situation? Better to put it out of its misery - it'll get killed off sooner or later, regardless.

      I'm not sure why people feel a need to defend the "quirky" walking lawsuit that these "great" programmers are all about. Very few businesses need genius programmers in order to stay in business. And most of the time, these people keep your business one step away from being sued into an early grave - and they don't provide a good product. A good product isn't something that does things in really neat ways. It's a usable product, well documented, that does the job its designed for really well - and can be updated and maintained as necessary. None of these are true of any product worked on by the described programmer.

      I have no interest in pretending that programmers need to wear ties to work and act like your average joe. However, being anti-social and incapable of writing a maintainable product? Not interested.

    19. Re:Can we stop enabling these people? by DrLang21 · · Score: 5, Insightful

      There are many excellent geniuses out there in the tech field that do what they're supposed to do. They document their work so that others can understand it. If they die or quit tomorrow, their company won't have to spend 2 years trying to figure out what they did. Getting a cheap geek to document these people holds its own high risk. What if the geek doesn't understand what they did? If this "genius" can't be bothered to document his own work, what makes you think they can be bothered to review someone else's documentation of their work? Mitigate your risk by paying more to hire a genius who won't put your company at risk of internal collapse.

      --
      I see the glass as full with a FoS of 2.
    20. Re:Can we stop enabling these people? by radtea · · Score: 4, Insightful

      His argument is that it's worth millions of dollars to not have to deal with this guy

      Not even close. This is a complete false alternative.

      First of all, "assume no one else can do what this guy does" is about as sensible as assuming unicorns are going to come charging through your door. The number of people who can do what no one else does is extremely small. And if your company depends on something that esoteric you're doomed anyway.

      More importantly, you could replace this guy with a couple of top-rank developers who might not have his "genius" but who would be able to save the company 90% of those millions, and do so in a sustainable, maintainable way, creating far more value downstream while reducing the churn you experience on the rest of the team because no one can stand to work with this jerk.

      Team skills are empirically known to be the most important predictor of developer productivity, not technical skills. Go look it up in your copy of "Rapid Development".

      It is never "either/or": a better team player with somewhat weaker technical skills is generally a better hire than a guru who can't play nicely with others, and the notion that gurus are so singularly valuable that they can't be replaced is simply false if you are running a viable business in the long-term.

      --
      Blasphemy is a human right. Blasphemophobia kills.
    21. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Well, if sociopathic temdencies run rampant in the boards.. This "Josh" seems to have a mental condition (can't remember the name of), and basically should be considered a disabled person. His special needs should be considered when placing him to the social setting of a workplace. He might perform better as a telecommuter. Alternatively, the coworkers could try to grow some balls of steel and recognize the wonderful diversity among the team.

    22. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      "Seriously, there's nothing in this example that's out of the ordinary, except for the women's t-shirts."

      Did we read the same article? "Josh" didn't document his code properly. The assumption is that he is writing code that will be used in a production/live environment. If something b0rks on the weekend and nobody can reach him, other staff need to be able to diagnose the issue quickly and easily. Proper documentation (either in code, or in separate documents) is critical for that.

      He also was extremely poor in communicating his workload to other teammembers. If Josh had said, "I can't help out, I've got my own critical deadline to work on", it would have helped.

    23. Re:Can we stop enabling these people? by Mr.+Slippery · · Score: 1

      Translation: Control is more important than productivity.

      No. Productivity is measured by more than the generation of code that works for the moment. Productivity is measured by the generation of code that can be maintained, i.e. is documented and not overly convoluted. This jackass was not productive.

      --
      Tom Swiss | the infamous tms | my blog
      You cannot wash away blood with blood
    24. Re:Can we stop enabling these people? by X_Bones · · Score: 1

      um, no. What do you think happens to productivity when this superstar asshole developer leaves for whatever (or no) reason, and everyone at his old job has to scramble to make sense of his poorly-documented code instead of getting their own work done?

      Sure the article probably isn't 100% unbiased, but it seems like the author did more or less the right thing. The developer was a dick, and his manager was either too short-sighted or too focused on making herself look good to actually, y'know, manage her developers.

    25. Re:Can we stop enabling these people? by 0xdeadbeef · · Score: 1

      Lesson, you are replaceable. If you are not replaceable, then you are too dangerous to have.

      No, if you are not replaceable, you are working for a company which has exceeded its station according to the Peter Principle. When you treat employees like subjects in an aristocratic hierarchy, you have no right to be upset when they invert the power relationship. The only solution for a company in this situation is to scale back their ambition and hire less skilled people, or give the "troublemakers" as much stake and authority in the company that they are every bit as cognizant of the risks and costs of their decisions as is the executive management.

    26. Re:Can we stop enabling these people? by turbotroll · · Score: 1

      Why do people feel the need to control quirky geniuses who are doing nothing wrong?

      People who value their individuality and resist corporate brainwashing are always regarded as "dangerous", especially in large companies. This is no wonder, since a flock of sheep is much easier to control and manipulate than a group of thinking individuals.

      Seriously, there's nothing in this example that's out of the ordinary, except for the women's t-shirts.

      Agree. The detail with his T-shirt slogans might indicate a lack of personal manners, if they are truly offensive. But then again, the sense of humor is a very individual thing and usually resides in the eye of beholder.

      That's what you get for having a casual work place. My thought would be that if the author has such a problem with this guy, maybe he needs to be skilled enough to replace him.

      In my experience, larger companies will be more than happy to get rid of a single good engineer and replace him with 5 mediocre to bad ones to replace him. Ask yourself why.

      By the way, we didn't hear the story from the other perspective, from "Josh" about "Eric". Would be interesting.

    27. Re:Can we stop enabling these people? by grodzix · · Score: 1

      True. If you work on some project you want to make each part of it a little black boxes (no matter whether it's software or real life stuff) which are as independent from each other as possible, with a nice description of each of those boxes.

      Same thing applies to team working on the project. You want to make the project as independent from the team working on it as possible. Best case would be if you could replace your team with some other and they would be able to pick it up quickly where the first one has left.

      --
      My Windows is NOT slow, it's special!
    28. Re:Can we stop enabling these people? by GMFTatsujin · · Score: 1

      Sounds like you'll rapidly run out of team, and be stuck with nothing but the asshole.

      Which is what you'll deserve. Enjoy dealing with the asshole! And when he leaves -- or worse, turns his capricious whims on you -- you'll have nothing left but to start from scratch. That, and explaining why the middle management -- you -- eviscerated your team for the sake of one schmuck who, it turns out, took over for you a long time ago because you ceded de facto control.

      So, what's *your* job worth now? Enjoy working for the asshole!

    29. Re:Can we stop enabling these people? by mcvos · · Score: 2, Insightful

      Why do people feel the need to control quirky geniuses who are doing nothing wrong? Seriously, there's nothing in this example that's out of the ordinary, except for the women's t-shirts. That's what you get for having a casual work place. My thought would be that if the author has such a problem with this guy, maybe he needs to be skilled enough to replace him.

      The T-shirts in the example are not the problem (though the hygiene might be). The problem is that he claims his code works and is self-documenting, when in fact it doesn't work the way the customer wants, and other programmers (the chief engineer at least) are unable to read his code.

      That's the problem. That and his anti-social attitude of calling them names instead of helping them to fix his incomprehensible code.

    30. Re:Can we stop enabling these people? by ThrowAwaySociety · · Score: 2, Insightful

      If your competitor hires this guy they might be able to outproduce you just long enough to put you out of business. Doing things right is important, but staying in business is the *most* important thing.

      The last thing you want is for your business to be dependent on one single person. Even if he's not some kind of cowboy/diva/jerk with no social skills, he may get hit by a bus, leave for personal reasons, or just get a better offer.

      Unless you're so small that you absolutely cannot hire another developer, you should start weaning your business off of such a person. Now, while it still has a chance.

    31. Re:Can we stop enabling these people? by ShieldW0lf · · Score: 0, Troll

      You stop being a quirky genius soon as you declare yourself as one. Since then you're just a wannabe poser.

      Yeah, and what if the owner of the company declares you one, and it happens in more than one company, and you regularly live outside the traditional chain of command of the company, answerable only to the owners?

      And the vast multitudes of people living their lives wrapped in the organizational framework you conceived for them, day after day, month after month, year after year, focusing entirely on what you decided was important long ago and ignoring anything that doesn't appear on their screen as though it didn't exist in the world... their significance just dwindles away?

      We're just wannabe posers. Who happen to run your lives in ways that you will never, ever understand, and you will never even acknowledge us, let alone be grateful.

      I should have gone into medicine...

      --
      -1 Uncomfortable Truth
    32. Re:Can we stop enabling these people? by tnk1 · · Score: 3, Interesting

      You may have missed the point where it was believed that it was possible that the millions of dollars saved was due to the millions of dollars worth of screw-up in his code, or even actual sabotage, to begin with.

      This guy was the mastermind of his project. If his code needs to be fixed in order to generate millions of dollars in savings, then the company didn't lose anything by losing him, except that which they let him control. If you churn out a high volume of good code and a high volume of crap, your net effect on the company tends to start looking like nil. That's before the millions in sexual harassment awards, of course.

      Don't get me wrong, there is nothing wrong with a "quirky" developer. I know many of them and most of them are harmless. They tend to get a little crabby at being pulled away from code, which is understandable because they like coding and they also tend to have deadlines. Most of them, however, understand the bottom line of the place that employs them.

      Documentation is not optional if you are in a workplace where your code needs to be used and operated on by others. If anything, it keeps people from annoying you later on (if you are of the antisocial mindset).

      Any developer who doesn't believe in documentation, or at the very least, does not even give lipservice to the concept is a long term liability for your company and needs to be corrected or be fired immediately. I mean, how hard can it be for someone who spends their time typing out text all day long to type out some extra text in English that explains things? When I code, its second nature to type a comment inline to make sure I remember my latest stroke of brilliance that was brought on by the hallucinations from the two liter of Mountain Dew I just drank. Those comments can easily be turned into documentation of a rough sort.

      It needn't be a book nor does it have to be flowery prose, that's what tech writers are for. It does have to exist, however.

      I have had to sit on the end of one too many developers who don't believe that their code needed documentation or even comments. I don't know if they saved the company millions or not, but I can tell you that it definitely cost us thousands of dollars in paid time for me to stare at their junk just so I could find the right place to make a simple change to the application.

      That said, you're right. The manager in this case should have been fired, but in addition to the developer. The manager, in all likelihood should have set limits on this person from the get-go instead of becoming dependent for their own performance on a person who doesn't even believe in showing up for work, let alone to help out in a customer situation. Such a manager is a lame weakling that was likely getting run over in more than one situation like that.

    33. Re:Can we stop enabling these people? by fl!ptop · · Score: 2, Interesting

      If you are not replaceable, then you are too dangerous to have

      my dad once told me, "a wise employee works to make him/herself irreplaceable."

      he continued, "a wise company manages their workers so no one is irreplaceable."

      --
      When you recognize love in another and realize how precious it is, everything else seems so insignificant.
    34. Re:Can we stop enabling these people? by turbotroll · · Score: 1

      if the author has such a problem with this guy, maybe he needs to be skilled enough to replace him

      In my experience it is usually the management who makes people difficult to replace. At one of my previous jobs my bosses noticed that I can handle the work load and cheerfully ignored my pleas to hire more people. I was forced to work even on my vacation and sick leaves. When I finally announced my resignation, I had to listen to comments such as "How can you do this to us", "You are immoral" (!) et cetera. Go figure.

      Lesson, you are replaceable. If you are not replaceable, then you are too dangerous to have.

      My words exactly. To bad many managers don't understand the same.

      As I noticed is one of my previous comments, this story is really about mismanagement than misbehavior of employees.

    35. Re:Can we stop enabling these people? by mcvos · · Score: 3, Insightful

      You stop being a quirky genius soon as you declare yourself as one. Since then you're just a wannabe poser.

      See that's why I'm NOT a quirky genius.

      Exactly. There's nothing cool about trying to be a quirky genius. But if you happen to be a quirky genius, it's definitely cool to try to be a team player. That's what makes your genius valuable.

      A genius asshole is just another asshole.

    36. Re:Can we stop enabling these people? by nomadic · · Score: 2, Insightful

      As a quirky genius, I have to say, if you don't like the way we do it... go fucking do it yourself. Should be good for a laugh...

      Please let us know what absolute brilliant pieces of programming have come from you so as to show that you are entitled to this attitude. At least let us know what companies you've worked for so we can at least know what world class programs you've helped produce.

    37. Re:Can we stop enabling these people? by Swizec · · Score: 1

      If others declare you a quirky genius you should act surprised and say "Stop messing with me! I just eat my spinach"

      Or something you know, never admit to being a quirky genius. Let others bother with labels, because a real quirky genius doesn't have time to care about them.

    38. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Except that of course... you're completely expendable. Programmers are a dime a dozen. Good programmers... a buck a dozen. Awesome programmers are worth too much, and they can just two good programmers.

      And as soon as your company realizes this, you get to learn how to flip burgers after your burn through your bridges and the cash that comes with them.

      Get used to the question "Could you supersize that?" You'll probably hear it a lot in the future.

    39. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      From my experience, it's not that nobody else can do what that guy does. Sure, there are a certain amount of things that they just don't have the talent for right away (maybe ever), but often that's because they've stopped growing as employees because of the quirky genius who becomes a giant crutch on which everyone else leans. The company, as a culture, relies on him to bring his genius to the table, and the other employees are never given the opportunity to challenge themselves and learn that they have some genius too. So, the whole organization becomes dysfunctional, waiting with great anticipation for the quirky genius to do his thing and solve all of their problems. When the quirky genius leaves, all of the sudden you discover that things continue to function at least as well, if not better, and you learn that the other employees really are quite capable of dealing with the problem at hand.

    40. Re:Can we stop enabling these people? by Dan+Ost · · Score: 5, Insightful

      If you can't be replaced, you can't be promoted. Hope you like your current job.

      --

      *sigh* back to work...
    41. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 2, Insightful

      What's the net cost?

      Let's accept for a moment the code may save millions of dollars as a line item.

      Does this guy's attitude cause more frequent turnover in his department incurring continual overhead in dealing with recruiters or new employee hire/training costs?

      Does his likely shoot-from-the-hip coding style work for his one use case and break things in ways he didn't bother to test or account for?

      Does he drop code in the repository that's of a huge, "everything's changed" variety which causes downtime as developers have to spend time trying to understand the quirks of his new million-dollar-savings?

      What was the nature of the change? Was it purely an infrastructure or refactoring type change that allowed maximization of existing resources, or did other departments have to message changes to clients? Was there any cost in client or customer service overhead as a result of this change?

      Were there additional refactorings necessary to user interface, help materials, etc as a result of this change that hadn't been budgeted?

      Great developers are awe-inspiring. Truly, I work with a handful of people who blow my mind on a daily basis, unlike anywhere I've ever been. One thing I've seen from all of these guys though is that they communicate their skills because they're smart enough to know that if they *all* know it (to a greater or lesser extent), or at least grok the important points well, they can improve upon it further. Compared with a lot of "superstar" guys I've worked with who couldn't be bothered to deal with people who "couldn't understand their greatness". Rarely are these guys the unmatched geniuses they think they are.

      Toxic employees are a liability... "superstar" is a label that is thrown around way too liberally.

    42. Re:Can we stop enabling these people? by DrLang21 · · Score: 2, Insightful

      I used to believe this. Then I found myself in a dead-end job because I was irreplaceable. I couldn't move up because the company couldn't afford to let me. So I found a new job. Unless you are content to be in one position for the rest of your life, being irreplaceable is bad for everyone involved. Now I contend that a wise employee starts training their replacement from day one.

      --
      I see the glass as full with a FoS of 2.
    43. Re:Can we stop enabling these people? by 0xdeadbeef · · Score: 3, Insightful

      Yeah, and what if the owner of the company declares you one, and it happens in more than one company, and you regularly live outside the traditional chain of command of the company, answerable only to the owners?

      Do you have an equal share of the company as the owners? No? Then I hope the pats on the head are worth it.

    44. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Except by saying implying you are a genius makes you not a genius, when you say you're not a genius you're likely suggesting you really are a quirky genius or at least about 50% or so.

      Or are you saying you're 50% asshole?

    45. Re:Can we stop enabling these people? by DrLang21 · · Score: 1

      As I noticed is one of my previous comments, this story is really about mismanagement than misbehavior of employees.

      That's about as fair of criticism as can be had. As the summary suggests, stop enabling these people. Only management can enable these type of anti-team employees. Give them the ultimatum, document your crap or get out. Don't let them entrench themselves for years with this behavior.

      --
      I see the glass as full with a FoS of 2.
    46. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      I'd fire the asshole. Every time.

      A sexual harassment suit could cost the company millions, or even put it out of business completely. If the plaintiff's lawyer discovered that a middle manager was fired for trying to fire someone for sexual harassment, simply in order to make the company more money, then the suit would almost certainly succeed because the company had an opportunity to prevent it and _chose_ not too.

      Now if the guy isn't an asshole, simply brilliant, then fine. Let him save the company millions.

      Frankly, this is all moot. The day when a developer discovers a way to save the company millions is about a day before a VP/Senior VP/CTO finds a way to claim it as their own idea.

    47. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 1, Interesting

      Yeah, and what if the owner of the company declares you one, and it happens in more than one company, and you regularly live outside the traditional chain of command of the company, answerable only to the owners?

      And the vast multitudes of people living their lives wrapped in the organizational framework you conceived for them, day after day, month after month, year after year, focusing entirely on what you decided was important long ago and ignoring anything that doesn't appear on their screen as though it didn't exist in the world... their significance just dwindles away?

      We're just wannabe posers. Who happen to run your lives in ways that you will never, ever understand, and you will never even acknowledge us, let alone be grateful.

      I should have gone into medicine...

      Just imagine how much more "genious" you would be if you weren't a socially inept asshole.

      You need to work on that. There's much more to it that being smart.

    48. Re:Can we stop enabling these people? by wfstanle · · Score: 1

      This brings to mind a saying I heard.

      "When on a safari, never fire your native guide until you get his maps of the area."

      To let anyone lead you somewhere, (or do something for you) and allow him to be the only one who can get you out of trouble is foolish.

    49. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      I have yet to encounter a situation where anyone is THIS good (or where every other employee is THAT bad). And if a business WAS in that situation? Better to put it out of its misery - it'll get killed off sooner or later, regardless.

      Jobs. Steve Jobs.

    50. Re:Can we stop enabling these people? by MrMr · · Score: 1

      You are the reason why the US is now entirely run by hairdressers, tired TV producers, insurance salesmen, personnel officers, security guards, public relations executives, management consultants; and telephone sanitizers.

    51. Re:Can we stop enabling these people? by oliderid · · Score: 2, Insightful

      Yeah, and what if the owner of the company declares you one, and it happens in more than one company, and you regularly live outside the traditional chain of command of the company, answerable only to the owners?

      It happens especially in little company. I remember a client of mine. They had an "in house" programmer. It was probably the shittiest codes I have ever seen. No logic, redundant functions, etc. I remember a meeting with him, he played the arrogant know it all in front of me. He finally noticed that I was a programmer just like him. The tone changed.

      He thought he was irreplaceable but the management has changed and the reason of my presence was to well outsource his work or to make him less "irreplaceable" due to the difficulties to get things right without crawling in front of him.

      There are a lot of people like him, as soon as they know "a little" more than their fellow co-workers, they feel like genius...Until they meet another professional who didn't past the last ten years sleeping on its knowledge without ever documenting himself about the last techniques/tools.

    52. Re:Can we stop enabling these people? by fdrebin · · Score: 1

      A situation like that happened in my place of employ. A long-standing PITA person - smart, but impossible to work with - was asked by a brand new manager 2 levels above him to provide some documentation and a summary of what he does.
      He refused, said "ask my boss". The 2 level up guy said "your boss works for me". The guy still refused.
      Next week, the guy was fired. Had been there 18 years. Funny, no one really misses him...
      /F

      --
      Stupidity... has a habit of getting its way.
    53. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 1, Insightful

      Productivity without control is like an accelerator without a brake. On a less extreme note, I worked with a guy who could crank out what seemed like klocs per day. Yet, when you looked at his code it mostly worked but had some dangerous problems, like servlets with member variables that had race condition issues.

      I inherited his code and told my boss I would need at least 4 weeks to clean it up, otherwise every little change would take a couple of weeks. The previous developer had a good mental map of the horror show that was his code so he could fix it in a day or two.

      My boss swallowed hard and I did the cleanup. I probably ripped half the code out and I reworked the rest into something approaching quality code. With the code base half as large, and appropriate javadoc comments, combined with a static class diagram, any idiot following after me should have been able to maintain it.

      And that's what being an engineer is. That's what makes engineering different from a guy tinkering in his garage. The guy tinkering in his garage may be able to bolt stuff together and make a gizmo, but it's a one of a kind only he understand how to make. An engineer may take weeks to do the same thing but it's a repeatable process, with standard instructions, that can be replicated and repaired as necessary.

    54. Re:Can we stop enabling these people? by grasshoppa · · Score: 1

      If the choice is between "the muck" or dealing with those like you ( it isn't, btw, but let's pretend ), I'll choose the muck every time. You are welcome to believe the world "needs" you, your life, your delusion. However, what the world really needs are good communicators, who can take what you might refer to as "mediocre" talent and tie it all together in to something wonderful.

      --
      Mod me down with all of your hatred and your journey towards the dark side will be complete!
    55. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      "If I'm running a business, and a middle manager tells me that the company should spend millions so the team doesn't have to deal with an asshole, I fire the manager, not the asshole." - by ivan256 (17499) on Monday March 16, @10:45AM (#27210111)

      Agreed, 110% - the manager's job IS TO MANAGE PEOPLE, & ALL kinds of people, even the "quirky" ones! IF you can't "manage that" (because most of these mgt. people couldn't write a lick of working code to save their lives mind you, nor have they ever professionally)?? Perhaps those types ought to get into a diff. job!

      (Got a guy that won't shower, shave, or otherwise take care of personal hygiene? You have 2 choices: Hang his job in front of him until he plays ball, OR, put him where he does not interface w/ others, or, others who can stand that type of behavior!)

      The only problem is, is that MOST of these "managers" have never even done the job of development themselves, hands-on, for years to decades (& I am sure most of you fellow coders here know what I am talking about)...

      I.E.-> How the HELL can you manage someone that you yourself as said mgt. figure, haven't even BEEN, yourself? This is what this person who wrote this article represents imo, because he's not able to do his job apparently, & is 'bitching about it' now publicly (odds are strong also, he has never done any coding himself, & that alone makes him incompetent for leading those that DO & HAVE professionally).

      APK

      P.S.=> "A good manager doesn't ask his boys to do anything he cannot or has not done himself" so, whatever happened to THAT type of thinking? It 'went by the wayside' when people started hiring in "clique supporters" & have only their b.s. in business admin or @ most, an MBA imo!

      That? That is what today's working world in MIS/IS/IT, truly IS rampantly full of (packs of rats supporting one another, bosses that haven't done the job themselves & have NO CLUE on themselves... & their view of "hell w/ the company, it's their monies, not mine, so long as I get mine" type mentalities)... apk

    56. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Psychometric definitions of "genius" intellect place geniuses at/above an IQ of 140 or 180, depending on whose definition you use. This means that non-geniuses comprise 98.77% of the population (IQ 140) or 99.994% of the population (IQ 180). Given a world population of 6.76 billion people, there are somewhere in the neighborhood of 500,000 to 83 million "geniuses" in the world. I'm betting it's a lot closer to the 500,000 than the 83 million.

      So what does this mean? It's very likely that you are not a special individual flower of quirky genius. In fact, it's entirely more likely that you are a reasonably intelligent antisocial asshole who's read "Atlas Shrugged" one too many times and feels like his "smarter than average" - but likely far below genius - level of intellect entitles him to abuse the people around him since he's always felt the sting of their lack of acceptance.

      I'm thankful that your attitude also probably makes you unlikely to reproduce.

      Color that "-1 Uncomfortable Truth," douchebag.

    57. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Why should we stop enabling these people?
      If he can produce overall value to the world, then let him. If the overall value to the world is negative (due to say poor documentation etc), then dont.
      Take it on a case by case basis.

    58. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Anyone found to be irreplaceable should be fired immediately.

    59. Re:Can we stop enabling these people? by Greg_D · · Score: 1

      If you were half the genius you claim to be, you'd be the one running the company.

      You aren't, hence, you aren't.

    60. Re:Can we stop enabling these people? by Americano · · Score: 1

      Yeah, and what if the owner of the company declares you one, and it happens in more than one company, and you regularly live outside the traditional chain of command of the company, answerable only to the owners?

      The same owners you previously declared to be incompetent morons you were selflessly rescuing from "the muck" they belonged in? The same people "riding on your shoulders" that you had "complete control over"?

      So what you mean to say is, "People who fawn over me and tell me I'm important are good. People who don't agree with this assessment are bad."

      Is that about the extent of it?

    61. Re:Can we stop enabling these people? by SatanicPuppy · · Score: 1

      No one is irreplaceable. No one.

      It's not good to have a guy who does all his work without oversight, but those people absolutely can be replaced. There is no reason to be afraid of it, and there is no reason to put up with it.

      It's funny; people always tell me I can't be replaced, and I always tell them, "That's what the person I replaced thought." At my current job, I've replaced 3 developers with a combined experience of 75 years. I just ported their crap to modern systems, and went on with my life. The places where I couldn't support their crap, I replicated the functionality, and moved on.

      --
      ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
    62. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      This might be true if you have a three-person development team. For anything bigger, the productivity losses caused by douchebags like this outweigh any individual productivity benefits. People like that cause other good employees to quit, and good programmers have to spend time cleaning up after them.

    63. Re:Can we stop enabling these people? by SatanicPuppy · · Score: 1

      This sort of mythology builds up around a lot of arrogant little jerks. I've never seen one who was all that. It's smoke and mirrors more than anything else: when the smoke clears, the code is usually pretty straightforward.

      You've got to remember, this isn't rocket science we're talking about here. This guy's not working at NASA. This is business code. It just ain't that complex.

      They need to fire the dude. Worst case scenario they have to replace him with a different jerk. But chances are it'll turn out that there was nothing so special about his work that he couldn't be replaced.

      --
      ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
    64. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      I don't care how great you are technically. If you are incapable of working with others and create liabilities for the company then you are not that good of an asset.

    65. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      incomprehensible ramble is incomprehensible.

      Also, it is filled with too many 'imo,' '@,' invented quotations, exclamation points, and capital letters FOR EMPHASIS.

      You lose.

    66. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Randroid alert.

    67. Re:Can we stop enabling these people? by javilon · · Score: 1

      Well, this could very well be said about Steve Jobs and many other "rock star" executives.

      Should they be fired immediately?

      --


      When his defense asked, "Which computer has Jon Johansen trespassed upon?" the answer was: "His own."
    68. Re:Can we stop enabling these people? by turbotroll · · Score: 1

      That's about as fair of criticism as can be had. As the summary suggests, stop enabling these people. Only management can enable these type of anti-team employees. Give them the ultimatum, document your crap or get out. Don't let them entrench themselves for years with this behavior.

      The problem is much deeper than enabling such people. People like "Josh" and those who enabled them (their immediate superiors, probably) are merely symptoms indicating that there is something seriously wrong with the whole organization, perhaps even top management to begin with.

    69. Re:Can we stop enabling these people? by Hoi+Polloi · · Score: 1

      If your business success hangs on one person then you have far greater issues than them.

      --
      It is by the juice of the coffee bean that thoughts acquire speed, the teeth acquire stains. The stains become a warning
    70. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      As a quirky genius, I have to say, if you don't like the way we do it... go fucking do it yourself. Should be good for a laugh...

      I guarantee you there's not a thing you can do that a team of offshore developers couldn't do faster or cheaper. Keep up that smug attitude and you may find that out firsthand.

    71. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      I "lose"? Lose what??

      (Oh, I see: Your "wannabe I am a fantasy Ph D in English" test???)

      Newsflash: This isn't the "english grammar" section of /. (is there even one of those here?) You're off topic and ought to find yourself a job teaching English (do you have a Ph D in English, by the by? Doubt it...)

      Seems YOU LOSE in failing to note this isn't English Class (nor my last will & testament, nor, anything remotely linked to anyplace I have to meet some MINUS A PH D in English spelling & grammar checker's criteria, especially on slashdot here, because you apparently cannot even READ & COMPREHEND that this isn't "the grammar & spelling check" section of this website)

      Answer those questions, we'll see who "loses" here... especially in regards to your non-existent Ph D in English!

      APK

      P.S.=> Oh yea, another 'bitch' I have on this website (& many others), is these "spelling & grammar nazi's" who when faced with data they cannot get the better of, they resort to saying "YOU DON'T KNOW HOW TO WRITE" etc. et al crap, & it's only to shield the fact their dyslexia or ADHD addled brains get lost if you use anything remotely technical in nature as regards the field of computers in your prose... "Hooked on Phonic" is for YOU! apk

    72. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Non-compete disclosure handles that.

    73. Re:Can we stop enabling these people? by Hoi+Polloi · · Score: 1

      If a second person can document your work as thoroughly as you could then that person could probably do your work too. They would need an equal level of understanding of the code.

      If that person is so brilliant then they'd understand the importance of documenting their own work.

      --
      It is by the juice of the coffee bean that thoughts acquire speed, the teeth acquire stains. The stains become a warning
    74. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Josh? Is that you? :)

    75. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Wow, even more quotes, capitalization FOR EMPHASIS and rambling diatribe! And you discovered a new trick - the BOLD tag!

      You lose in that you have failed to convey any point that is not a litany of things that annoy you mashed together into an incomprehensible train wreck of a whole.

      It's called a sentence. Learn how they're constructed. It's called a point - learn how to make one. It's called communication - learn how it works.

    76. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Because it's not enough to stand on the shoulders of giants. They won't be satisfied until they've managed to put a bridle on.

      Thing is, the wise genius developer will realize, when the whole world is standing on your shoulders, you're already the ruler, forever and ever amen. They're nothing but little ants, and the situation will never change. Not because you hold them captive, but because without you, the quirky genius, they will be back in the muck where they belong, and their greed and self-importance will never allow that to happen. They are not the ones with intrinsic power, they are nursemaids for genius, or they are nothing at all. And they know it, that's why they're there.

      As a quirky genius, I have to say, if you don't like the way we do it... go fucking do it yourself. Should be good for a laugh...

      I honestly don't care how much of a genious you are, I've known people that wrote 3d code on a 8086 when they were grade schoolers, and yet, they are still replaceable.

      If your an asshole and can't write some easy goddamn documentation, you need to be backhanded.

    77. Re:Can we stop enabling these people? by Hoi+Polloi · · Score: 2, Insightful

      That "millions" number was probably pulled out of thin air but anyway...

      How much would it cost to replace the good coders who might leave for a better work environment? How much would it cost to debug or port that guy's code after he left with no documentation? How much would it cost to defend the company in, say, a hostile workplace lawsuit?

      Even the president of the US can be replaced as the last election showed. No one is irreplaceable, especially a hostile person.

      --
      It is by the juice of the coffee bean that thoughts acquire speed, the teeth acquire stains. The stains become a warning
    78. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      You DO have trouble reading, don't you? You failed MY test of:

      1.) Producing proof of your Ph D in English (which you obviously do not have)...

      AND,

      2.) You also omitted an answer to my question of whether this is the "english grammar & spelling" section of this website (it's not, & you're off topic)

      (LOL!)

      Typical, as per usual, no Ph D in English (& yet this "spelling & grammar nazi" has the sheer gall to tell others how to write) & another off topic trolling wannabe Ph D in English (or human grammar & spelling checker).

      APK

      P.S.=> Answer the 2 questions I re-enumerated for you above, for the 2nd time now already (Now, IF you do have ADHD or dyslexia? Again - "Hooked on Phonics" is for you (you off topic wannabe Ph D in English))... apk

    79. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      He was making a rhetorical point. If you accept the premise of the article (guy is worth millions of dollars, we haven't replaced him already, and he should be fired), then it seems stupid to come to the conclusions the article writer did.

      The article was probably exaggerating, and yes, in the real world, there are thousands of little mitigating factors which add costs on to benefits. But if you actually take the "saved the company millions, full stop" as factual, then yes, the guy is worth millions.

      You just have to look at professional sports to see this kind of thing play out in a real economic situation...

    80. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      He also mentions later that the problems that could potentially cost millions of dollars were most likely created by the guy "worth millions of dollars".

      Sounds like a zero-sum game to me.

    81. Re:Can we stop enabling these people? by DrLang21 · · Score: 1

      I think it's fair to say that the Board of Directors at Apple should have long ago foreseen that they needed a protege for Steve Jobs. Whenever Steve Jobs left Apple in the past, they stumbled badly. He has been both the best and the worst thing to ever happen to Apple. A good CEO is a hard thing to do without for even a short period of time. Apple should make Steve Jobs replaceable and then keep him. If he refuses to become replaceable, which doesn't seem to be the case, then yes they should get rid of him as soon as they reasonably can.

      --
      I see the glass as full with a FoS of 2.
    82. Re:Can we stop enabling these people? by Maximum+Prophet · · Score: 1

      3 out of 5 small businesses fail within the first year. This happens all the time. (although some of these businesses don't have any geniuses, and just fail.)

      --
      All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
    83. Re:Can we stop enabling these people? by Maximum+Prophet · · Score: 1

      3 out of 5 small businesses are going to fail within the 1st year. If you have one product and your genius programmer leaves, you have 0 products, and your competition eats your lunch whether they hire him or not.

      The standard answer, diversify, doesn't work for most companies, because they don't have the capitol to spread out. If you try, your resources get diluted for your products and the competitor wins.

      Look at Wall Street right now. They are giving > $1,000,000 bonuses to people who failed miserably, because, "That's what we have to do to keep them..." (Like they'd be able to go anywhere else) I've actually heard execs being interviewed complain about $500,000 salary caps because they are worried their "best" people will leave the country.

      --
      All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
    84. Re:Can we stop enabling these people? by __aagmrb7289 · · Score: 1

      I'd argue that none of those business had genius, and zero of them failed because they "lost their genius". There are exceptions of course, but they are rare.

    85. Re:Can we stop enabling these people? by blanks · · Score: 1

      I think people are misunderstanding the level of work many of these people do and are assuming these people might be doing simple work that they themselves could do but without the attitude.

      I have known many developers though the years but have only known 2 who fit into the category of absurdly good developers. These guys were not just very good developers who could just be replaced with ok or good developers with no attitude. These were guys who made the companies. The ones who did make millions for the business and were capable of doing work that no one else was capable of doing. Were not talking about fancy or creative coding; were talking about coding that only a few people in the world can do.

    86. Re:Can we stop enabling these people? by ShieldW0lf · · Score: 0, Troll

      Do you have an equal share of the company as the owners? No? Then I hope the pats on the head are worth it.

      You're the sort of guy who thinks having the deed to the Mona Lisa is the reward. I'm the sort of guy who thinks having painted the Mona Lisa is the reward. I could give a shit about the pats on the head... I draw comfort from knowing that my influence reaches out with invisible fingers to wrap the globe like a giant fist and keep my stupid, ungrateful little children safe and warm. That is my reward, and no bankster will ever deprive me of it.

      --
      -1 Uncomfortable Truth
    87. Re:Can we stop enabling these people? by saiha · · Score: 1

      Non-compete clauses are illegal in california at least (even out of state ones), probably other areas as well.

    88. Re:Can we stop enabling these people? by saiha · · Score: 1

      In this economy I think most people would say "I like _having_ my current job".

    89. Re:Can we stop enabling these people? by saiha · · Score: 1

      Yep, just like the developer may be encouraged to write quick code over manageable code, his superiors may be encouraged to promote this type of environment all the way up to the top.

    90. Re:Can we stop enabling these people? by marco.antonio.costa · · Score: 1

      Lesson, you are replaceable. If you are not replaceable, then you are too dangerous to have.

      That's a good warm blanket for mediocre people to snuggle under, but not really true. There is a reason Josh wasn't fired for a long time and quit his job just like that, and that is because he was probably just picked up by a competitor in a snap.

      Nuclear weapons may be dangerous, dirty and hated by many, but you'd rather have them, than your adversary.

      I'm sorry, but this story is laughable. Comments about a dark, cave-like office? "I tried to sound cheerful: 'Hi Josh!'"? Smells?

      The bottom line is, people feel threatened and diminished when they just can't do what you do. Especially if you look weird and act weird.

      --
      Send your spendthrift head of state this
    91. Re:Can we stop enabling these people? by mooingyak · · Score: 1

      The last "quirky" genius I worked with had a habit of looking at things he'd just finished and declaring somewhat loudly (and vaguely reminiscent of a Guinness commercial) "GENIUS!"

      One day he asked me why I didn't go about bragging about my abilities, as if the lack of bragging somehow made me a lesser being. I told him that if I were a genius, it'd be self evident to anyone looking at my work and they wouldn't need me to tell them.

      --
      William of Ockham had no beard. The most likely explanation is that it was chewed off by squirrels every morning.
    92. Re:Can we stop enabling these people? by tonyreadsnews · · Score: 1

      "Sure, he was whipsmart and could churn out code that saved the company millions"

      is likely negated by the risk produced by:

      wears T-shirts with offensive slogans, insults female co-workers

      What good is saving the company millions if its likely to be taken away or spent on lawsuits.

      It is likely even greater risk because they are allowing it to happen, so they might lose many multiple of what they could save with this guy's supposed 'irreplaceable genius'.

    93. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      LOGIC ERROR. ARGUMENT HALTED.

    94. Re:Can we stop enabling these people? by fl!ptop · · Score: 1

      If you can't be replaced, you can't be promoted

      i don't think this is what he meant. he meant that you should strive to work hard so the company wants you around. it doesn't matter what position the company puts you in, they know you'll do the job effectively.

      he didn't mean that you can do your job so well that no one else can do it (or be trained to do it) as well.

      --
      When you recognize love in another and realize how precious it is, everything else seems so insignificant.
    95. Re:Can we stop enabling these people? by DrLang21 · · Score: 1

      That's not what it means to be irreplaceable. Irreplaceable means that if you left tomorrow, the company would suffer immense losses because there would be no one around who could pick up where you left off in any reasonable amount of time. Lack of documentation of what you are doing is the most effective way to make yourself irreplaceable. If you become too entrenched in the critical functions of a company, your incapacitation could cripple the company. That's just bad policy for everyone.

      --
      I see the glass as full with a FoS of 2.
    96. Re:Can we stop enabling these people? by jasmusic · · Score: 1

      Lesson, you are replaceable. If you are not replaceable, then you are too dangerous to have.

      Sounds like someone opposed the TARP bailouts. Welcome, fellow capitalist!

    97. Re:Can we stop enabling these people? by Fulcrum+of+Evil · · Score: 1

      They are giving > $1,000,000 bonuses to people who failed miserably

      No they aren't. They're giving >$1mil commissions to people who met contractually stipulated conditions. If they didn't, they'd be sued.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    98. Re:Can we stop enabling these people? by bwcbwc · · Score: 1

      This guy's dangerous to have even if he IS irreplaceable. If I was a female or PoC working there and coming in contact with this guy, I'd be looking for an EEO lawyer to file a rainmaker lawsuit.

      --
      We are the 198 proof..
    99. Re:Can we stop enabling these people? by cptdondo · · Score: 1

      He. I lsot a high level job interview over this very topic. I was asked how I would handle a long-term employee who has a lot of unique, irreplaceable knowledge about the system but refuses to divulge it or to work with other employees.

      Without hesitation, I said, "Fire them". The entire interview panel leaned back in their chairs, as if I just puked up blood or had the alien baby rip open my gut.

      Needless to say, I didn't get the job, even after explaining that a person who won't do their job is detrimental to the team, and any knowledge they may have is useless if they refuse to share it.

      No one is irreplaceable on a team, and if you don't want to be a team player, I don't want you on my team.

    100. Re:Can we stop enabling these people? by Brandybuck · · Score: 1

      In one of my past companies, we would have taken "Josh" out back and beaten the shit out of him. I'm not saying it's right, I'm just saying that anti-social behavior can have its consequences.

      --
      Don't blame me, I didn't vote for either of them!
    101. Re:Can we stop enabling these people? by khellendros1984 · · Score: 1

      Please document that sentence. Its meaning is unclear. Thank you.

      --
      It is pitch black. You are likely to be eaten by a grue.
    102. Re:Can we stop enabling these people? by 0xdeadbeef · · Score: 1

      On behalf of an ungrateful world, I salute you, noble sir.

    103. Re:Can we stop enabling these people? by Bradac_55 · · Score: 1

      You've never worked for a local county (US) government facility have you? They all run AS/400's and have four to six programmers. The only requirement to be a programmer is that you have a college degree and know someone that works there. Most of them are females with art degree's with little to no programming background/experience. Every once in awhile you will see a 'real' programmer burn out show up for a few years and they are *GODS* at fixing there cobbled together sh!t. There allowed to act however they want as management knows as soon as they de-burn-out(?) they will leave for better paying jobs.

    104. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Very few businesses need genius programmers in order to stay in business.

      I think you've hit on the important point...it all depends on what type of programming you need the employee to do. If it's just business logic on top of a SQL database with a web front-end, you can find well-adjusted programmers who are perfectly capable of doing the job and getting along with everyone else.

      If you're business is pushing the boundaries of video compression, cryptography, compiler design or something else that is of that level of complexity and rules out 99% of the programming workforce, there's a much better chance that the right move is to tolerate more anti-social behavior from a brilliant programmer. However the right move is to also hire another programmer who's main job is to interface with the brilliant programmer(s). Send the well-adjusted programmer to meetings and have that developer work on most of the documentation. It's not important that the well-adjusted engineer can contribute to pushing the state of the art, but only that they can understand when those who do explain it to them. It's a great chance for that developer to learn a lot and yet do most of the busy work for the brilliant programmer. This keeps you from having marketing, support or anyone else in the company interfacing in any professional capacity with the anti-social genius.

    105. Re:Can we stop enabling these people? by pla · · Score: 1

      If you can't be replaced, you can't be promoted. Hope you like your current job.

      This topic deals with "really good" coders. Who, for the most part, hold management in utter disdain and don't want to climb the corporate ladder.

      The mediocre programmers, who struggle through getting the job done and want nothing more than to climb above the pit, can have their sad middle-management positions. They just need to know their place, and stay out of the way of the actual talent.

      I don't say that to defend the prima-donnas, BTW... We all need to understand our limits, and even superstar coders have them (just not when it comes to coding, for the most part). Me, I consider myself among the ranks of "really good" coders, though certainly not a superstar, and I have one really big humbling weakness - I suck at the business world and at marketing myself. If not for that, I'd have no use for "the company", but accepting reality, I do my part to get along with everybody that needs to work with me.

      So perhaps anyone dealing with a "Josh" needs to figure out what Josh needs from the company; if "nothing", he wouldn't waste his time there.

    106. Re:Can we stop enabling these people? by pla · · Score: 1

      You may have missed the point where it was believed that it was possible that the millions of dollars saved was due to the millions of dollars worth of screw-up in his code, or even actual sabotage

      Why yes, the author of TFA does come across as extremely paranoid.

      He has no evidence of that accusation, nor even and reason to believe it, other than his inability to accept Josh as "just that good".

    107. Re:Can we stop enabling these people? by easyTree · · Score: 1

      Does anyone ever get the idea that the PHB's aren't really clueless and self-contradictory with no short-term memories but instead, are desperately trying to keep developers on the hop to prevent them from using their superior ability to manage information and turning that into power ?

      It's gotta be. There must be some reason why *they* are in charge.

    108. Re:Can we stop enabling these people? by DrLang21 · · Score: 1

      I believe it would be more accurate to say that this topic deals with really good coders who have a God complex and refuse to document their code. There are plenty of great programmers out there that can write good documentation. There is a lot more available in climbing the ladder than business management. You think organizing a large scale project, be it an application with millions of lines of code or an IC with millions of transistors, is a sad middle management task best left to mediocre programmers? That kind of work takes hardcore systems engineering from someone who is very experienced and understands a broad range of technical skills AND is capable of organizing engineers and programmers of various disciplines to make it happen. I don't think any good systems designer would want someone on their team that could compromise the entire project by their leaving.

      --
      I see the glass as full with a FoS of 2.
    109. Re:Can we stop enabling these people? by CAIMLAS · · Score: 1

      I don't know who this Josh is; but he's a caricature of the Coder BOFH variant. Personally, I've never met anyone like him.

      Oh, I've met IT people with poor BO. I've been accused (falsely, because it was a convenient stereotype) of it myself. I've met people who are socially inept and say inappropriate things. But, by and large, these people are also the best at what they do. Sure, they're cocky.

      What it is, is a pecking order game. They think they're the best. In my experience, it's not so much a matter of being respected for being the best, or left alone, or any of that. They just want to do their thing, yes - and a little healthy competition (real or perceived) for the "alpha geek" role can help this out tremendously.

      I've been accused of having borderline Asperger's before, though I would argue that I've got a great deal more social graces than most who have the 'geek disease'. For the most part, I'm able to go between the haves, and the have nots. What I have found is that the best way to relate to them is the way they relate to others - as much as possible. If they try to intellectually domineer people, show them, or pretend, that you're tops. No, you don't have to lie to them. But that posturing/soliloquy stuff they do to bolster their self confidence and show you they're intellectually/whatever on top? They (we) tend to respect that, if as nothing other than healthy competition and "one of our own". Kid gloves (where you treat them like a child, or generally treat them 'sensitively' like you would a normal employee) doesn't work.

      Again, this "Josh" is a cruel caricature. Nobody is like that: attitudes like that don't make it past interviews.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    110. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Very, very few businesses have a genius behind or in them. Being a small business owner myself and seeing many businesses come and go around us I can see why so many businesses fail. It's not because of genius or lack there of, but because of a bad business plan or lack there of.

      Oh, I like making models, I'm going to open up a hobby shop. I don't know anything about business, but I'm going to do it. Poof, gone in under a year, couldn't even make enough to cover rent.

      Oh, I cut hair, I've been doing this for 15 years, I should go into business for myself. I'll sell clothes too because I like clothes even though nobody will know I exist because I have no customer base and I don't advertise, I'll buy 1000s of dollars of inventory. Poof, gone.

      Oooh, I have an idea. I'll open up a restaurant because I like to cook. This will be my 5th restaurant that I've opened up. Even though I've had to close the other 4 because they didn't make money, this one will do it. I didn't feel like working today so I'll just be closed, yes that's right my sign says 7 days a week, but I wanted to go home early or I wanted to say home and watch the game today. Oh I alienated customers because they have no idea if they can get lunch or dinner on any given day. Hmmm, I don't see the money I was expecting to see. Let me change the menu for the 4th time this year....

      Yeah, he's gone too.

      Most of it's just been people with no idea of what the hell they were doing.

      It's basic. My expenses are X, thus I need to make X just to break even. Pay your bills first before paying myself, any profit is mine. It's simple, yet so many "business" owners don't get it. They don't even know about their own industry, it's just something they like to do and they don't educate themselves about what is happening.

      We have 3 businesses "near" (within 4 miles) one of our stores, our "competition", struggling because they don't have the expertise about their industry. One will be out of business this year. The other 2 might last another year maybe 2 if they don't get any competition that's closer to them than we are. For instance, if we or a another small, local chain opened another store a few blocks from them, they'd have to close their doors in a couple of months.

    111. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      And the hits just keep on coming.

      It doesn't require a PhD in English to tell you that your posts are a meandering mess bearing no semblance to a thoughtful comment, nor does it require advance grammar or spelling to point out to you the fact that you would be wise to learn how to express yourself clearly.

      I never corrected your grammar & spelling, I simply pointed out that your diatribe had no point or apparent function. That has nothing to do with grammar or spelling, and everything to do with your inability to formulate a coherent sentence that conveys meaning.

      Again: you lose.

    112. Re:Can we stop enabling these people? by pla · · Score: 1

      Team skills are empirically known to be the most important predictor of developer productivity, not technical skills.

      "Predictor" != "Descriptive". You don't use a predictor when you have a known quantity, you use the known quantity itself.


      The number of people who can do what no one else does is extremely small.

      Taking that as hyperbole, lets call him "merely" one in a million... So the planet has a mere 6000+ people as good as him at his niche. And you want to hire an entire team to replace him? Talk about taking the importance of "teamwork" way too far! I agree that we shouldn't always favor gurus over reproducibility, but gurus do have their place - just not on a team, and if you try to squeeze them into one, don't blame the tools when the nail bends under repeated blows from the only monkeywrench you have handy.


      a better team player with somewhat weaker technical skills is generally a better hire than a guru who can't play nicely with others


      That depends greatly on what your company needs. If you need long-term solutions to a relatively stable problem set, I would agree. If you need to beat the competition to the punch or you'll find yourself on the dole next month, you want a guru.


      creating far more value downstream

      Put bluntly, that requires a "downstream" to exist.



      Overall, I have to agree with the GP. If you told me "fire the PITA on my 'team' who saved us millions", I'd fire you instead.

    113. Re:Can we stop enabling these people? by dbIII · · Score: 1

      If someone is laughing at you for asking for non-existent documentation that they should have written, they should be fired immediately

      No. They should be managed better instead of looking for another "universal work unit" which only really exists in the dreams of HR. Think back to your schooldays when the misbehaving kids were not expelled at the first minor offence but were dealt with by different means. Why fire somebody productive when a change of schedule or a bit of assistance may be all it takes - or maybe even just a short talk to find out their problems?

      Of course people are replaceable - but it's usually and expensive and sometimes project killing effort to do so.

    114. Re:Can we stop enabling these people? by DrLang21 · · Score: 1

      If you can show that management truly never told them that documentation was part of their job, then sure, give them a second chance. However, employment is nothing like school. You are being paid to do a job, not being forced by law to learn. If management has told you that documentation is part of your job and you are giving snarky replies about your failure to do so, then you should be fired. This isn't school. This is the real world.

      --
      I see the glass as full with a FoS of 2.
    115. Re:Can we stop enabling these people? by dbIII · · Score: 1

      It's not about blame, it's about getting things done. Management might have to tell them a second time that documentation is part of their job, there might even be a shouting match, but if a few hurt feelings are required to get things changed instead of possibly a year of getting a replacement up to speed then so be it. The "real world" should involve better management than firing people by email and then watching as better managed competitors get there first. I also find it very funny that you are describing an office work environment as "the real world". What's real to you or me is a protected ivory tower to others.

    116. Re:Can we stop enabling these people? by arilian · · Score: 1

      Actually I'm one of a group of the 'brilliant people' who can get it done but don't document (haven't been insulting staff members lately but I promise to try harder). I became a sudo manager last year and I've noticed something. As much as we can quickly and 'instantly' fix a problem. 'We' always have to be there to fix it. The organisation is under as much threat from a loss of knowledge or lack of stability because of these people as it is a loss of productivity if we lose them. Might be an extreme example but these days I want people who share with their team mates and take time to document because people that are ultimately a LOT more productive that the one off brilliant guys.

    117. Re:Can we stop enabling these people? by jcr · · Score: 1

      Another person who doesn't get what Atlas Shrugged is all about. Did you ever read it?

      The heroes in that book don't abuse anyone, they just refuse to be abused themselves. They go on strike.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    118. Re:Can we stop enabling these people? by dkleinsc · · Score: 1

      The last thing you want is for your business to be dependent on one single person.

      Tell that to Apple.

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    119. Re:Can we stop enabling these people? by swilver · · Score: 1

      Exactly, my only "promotion" path was towards a management job. I don't want to stop programming, ever (if I can help it). So instead I checked my options (after 8 years of solid service), found that the company did not want to actually reward my performance better, so I quit. I work freelance now, and can safely say that it is far more rewarding in more than one sense.

    120. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      "Team skills are empirically known to be the most important predictor of developer productivity, not technical skills. Go look it up in your copy of "Rapid Development"."

      CAUSE IF IT'S IN A BOOK ABOUT PROGRAMMING, IT MUST BE TRUE!

      What are you, a manager? Get a fucking clue (not from a book, from real life).

    121. Re:Can we stop enabling these people? by Anonymous Coward · · Score: 0

      Like writing the code in the specified language, for instance?
      Every single time I've seen PHP projects offshored, the resulting files are always ASP.

      Maybe there's not that many quirky geniuses around, maybe it's just that the majority of humanity is f*cking retarded.

  5. without clowns like this by justicenfa · · Score: 1

    How else would we get attention from the office females?

    1. Re:without clowns like this by Red4man · · Score: 5, Funny

      The office females already notice you.

      Right before they say things like "Oh dear God that THING.. that mouthbreather is looking at me again. I wish he'd just go away. Ewww gross, look how sweaty his palms are. Think he's ever heard of a shower?"

      --
      Sock Puppets: damn_registrars=pudge_confirmer=jimmy_slimmy=raiigunner=cml4524=a_klavan=red4men=ronpaulisanidiot
    2. Re:without clowns like this by justicenfa · · Score: 1

      Well, actually, that's the developer in question. When they look at me, they're drooling.

    3. Re:without clowns like this by Anonymous Coward · · Score: 0

      I'll assume that you work at a nursing home.

    4. Re:without clowns like this by Anonymous Coward · · Score: 0

      Because as we all know, office females just love to behave like abusive petty little mean spirited shallow cunts bristling with supressed anger due to a lack of self esteem as a result of their lowly station in life and lack of meaningful achievements.

  6. Nice made up story... by sunking2 · · Score: 5, Interesting

    It should ensure that lots of bored IT people with god complexes flock to his article and dream about how important they really are. Of course the reality is that just about everyone could get hit by a bus and within 2 months their names will be forgotten and the company will be just fine.

    1. Re:Nice made up story... by ethan0 · · Score: 1

      just about everyone could get hit by a bus and within 2 months their names will be forgotten

      well, yes, if everybody got hit by a bus, then who would be around to remember anybody?

      also that would be quite an impressive bus.

    2. Re:Nice made up story... by Anonymous Coward · · Score: 0

      I've actually encountered someone like this.
      He was at least around reliably, though.

      As our positions weren't originally programming positions I was the only other person in the building that could have a chance at understanding what he did.

      He did not document as he felt his code was self documenting. He meant the code itself, no comment lines at all.

      When he left I was asked to either pick up or restart his project. I was encouraged to restart it because even the management felt the previous one was too complicated. It used excel, ASP, an access database, and at least another language (so I'm told). His files were all over the place so I had a lot of trouble tracking down where the program really started at.

      In the end I spent 4 weeks redoing the 'core' of his project (which spanned months) to get a working prototype with absolutely no error checking in it. This included reverse engineering a working project that I didn't have source access to.

      When I left, the person I suggested to take my place did so and used the notes and source I left behind to continue on. He used a different approach but found my comments in the code and the notes of dissassembly I made quite useful.

      The first guy was nice enough but no one could keep up with him and he didn't slow down to explain what he was doing or where it was going.

    3. Re:Nice made up story... by machine321 · · Score: 1

      Of course the reality is that just about everyone could get hit by a bus and within 2 months their names will be forgotten and the company will be just fine.

      Tell that to Terry Childs.

    4. Re:Nice made up story... by JohnFluxx · · Score: 1

      And who would be left to drive the bus?

    5. Re:Nice made up story... by Anonymous Coward · · Score: 0

      Why would the bus need driving?

    6. Re:Nice made up story... by Binestar · · Score: 1

      Tell that to Terry Childs.

      Who?

      --
      Do you Gentoo!?
    7. Re:Nice made up story... by Anonymous Coward · · Score: 0

      It's not a god complex if you really are a god.

      Now if you'll excuse me, I have to catch a bus to see my pancreas doctor.

      - SJ

    8. Re:Nice made up story... by dzfoo · · Score: 1

      Maybe everyone just ran really fast towards the bus and rammed it.

              -dZ.

      --
      Carol vs. Ghost
      ...Can you save Christmas?
    9. Re:Nice made up story... by dzfoo · · Score: 1

      Aha! You almost had me, but--alas--I see right through you, fake Steve!

      The REAL Steve Jobs would demand that the pancreas doctor bus over to him!

                -dZ.

      --
      Carol vs. Ghost
      ...Can you save Christmas?
  7. Perhaps by mewshi_nya · · Score: 1

    It's not necessarily "enabling". I've known a lot of people who are just eccentric but incredibly bright (and have been told I'm one, which surprises the hell out of me), and it's probably just part of the territory.

    If he's taking a shit in the plants, though... yeah, get that stopped...

    1. Re:Perhaps by Anonymous Coward · · Score: 4, Funny

      Yeah, get him a proper litter box. That should solve the problem.

    2. Re:Perhaps by electricalen · · Score: 1

      Reminds me of the movie Grandma's Boy. It was about a bunch of game programmers and testers. It had the stereotypical genius/crazy/anti-social programmer diva.

      http://en.wikipedia.org/wiki/Grandmas_Boy

    3. Re:Perhaps by ultranova · · Score: 5, Insightful

      It's not necessarily "enabling". I've known a lot of people who are just eccentric but incredibly bright (and have been told I'm one, which surprises the hell out of me), and it's probably just part of the territory.

      A guy who mutters to himself while working is eccentric. A guy who insults his co-workers is an asshole. And a guy who smirks while informing others that documentation doesn't exist is just plain malicious.

      Assholes should be kicked out of any team, because no matter how bright they are, they won't be able to compensate for the lowered productivity of everyone else who has to waste their time and energy to deal with their little power games. As an added bonus, it makes every other employee happy, thus making the world a bit better place. Profitable and morally right, firing assholes is a win-win situation. Even the asshole might benefit from the wake-up call.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    4. Re:Perhaps by gmack · · Score: 2, Interesting

      A few years ago I worked for a company that had one such person on the team. Everyone thought he was a genius and tolerated the fact that he couldn't even be bothered to bathe or wear clean clothing. He would come when he felt like it and he would leave when he felt like it

      One day we had issues with his software and the boss went to find him only to find out he wasn't in the office. When the boss woke him up at 1:00 his only reply was "I didn't realize it's monday"

      Needless to say he was replaced and, as the poor new guy quickly discovered, it turns out the reason no one could understand his code was that he was an alcoholic who couldn't organize his code any more than he could organize the rest of his life.

      Being eccentric is not an excuse to be a selfish jerk.

    5. Re:Perhaps by CFTM · · Score: 1, Interesting

      Go back to happy land.

      Assholes are on every team and it has nothing to do with eccentricities. Part of being an adult is working with assholes.

    6. Re:Perhaps by Anonymous Coward · · Score: 0

      And a guy who smirks while informing others that documentation doesn't exist is just plain malicious.

      As usual, the summary was wrong. The smirker was the "moron" who couldn't figure the original problem out. I guess I'm displaying my lack of Slashdot-fu by having read the article--it was short, with small words.

    7. Re:Perhaps by GMFTatsujin · · Score: 2, Insightful

      Truth.

      I've always considered that the indispensable genius/jerk should be given as many independent entrepreneurial opportunities as possible. As in kicked out the door. Go run your own business, genius.

      I'll happily go head to head with someone who routinely alienates the people around around him and can't get his personal shit together.

    8. Re:Perhaps by Em+Emalb · · Score: 2, Insightful

      Oh bullshit. Being an adult means not being an asshole to your co-workers.

      As you said, you've all got to get along, so why allow one jerkoff to ruin everyone else's day?

      I have no problem firing people that suck at life. I've never suffered for it.

      Don't let one ass-clown's childish behavior cause issues in the work place. You'll have a more productive work place because of it.

      --
      Sent from your iPad.
    9. Re:Perhaps by Burnhard · · Score: 1

      A guy who insults his co-workers is an asshole. And a guy who smirks while informing others that documentation doesn't exist is just plain malicious.

      I think you make two points here that aren't really related. There are a lot of clever people in IT who are, it seems to me, suffering from some form of Autism (I can think of two people in my code-shop just off the top of my head). Once you understand that and take it into account, you'll find they are no longer so insulting, even when they are being insulting, if you see what I mean.

      Your other point is a common "joke" among us developers. We often don't have the time to fully document something and even if we did when requirements change (as they always do), the documentation is out of date. Keeping it up to date is a constant struggle. I have found from experience that a few pages explaining general principles, followed by clear code, with in-place comments, is far preferable to a 100 page document explaining everything in detail. Consider also that documentation is not going to help you if the code isn't written to be easily extensible. It seems to me that the design is the more important document, far more important than ex post-facto explaination.

    10. Re:Perhaps by buddyglass · · Score: 1

      Funny you should say that. The person in the cube next to me mutters to themselves while working. In French, no less. Possibly a good thing I don't speak French.

    11. Re:Perhaps by CFTM · · Score: 1

      I don't disagree that you shouldn't behave that way, but that doesn't mean people don't.

      Most of us aren't in a position where we can just "fire assholes". I'm certainly not. Awesome for you that you are though, me? I have no choice in the matter.

    12. Re:Perhaps by Anonymous Coward · · Score: 0

      So Dr. House should be fired?

    13. Re:Perhaps by agentultra · · Score: 2, Interesting

      Assholes, exactly -- people who are not genius' can act this way too. I've met countless sales people and executives who've had sexual allegations against them and who've siphoned off company money to fund affluent lifestyles; act like complete pricks to everyone they meet; and generally be very "Josh" like. Yet they seem to lack one thing: intelligence.

      I can understand a lot of the "devil's advocate" positions; but the reality is that this editorial is supporting a straw-man argument.

      A genius developer isn't universally predisposed to defecating in public and verbally abusing people.

      They may be eccentric and the scale of their eccentricities vs. their practical value to society will certainly determine how far they go. More often than not, such people will either disappear from corporate life or else end up running it. The worst thing possible for an eccentric genius developer is probably being stuck as a "cog in the machine." They'd probably be more likely to flourish in research, leadership, or academic positions.

    14. Re:Perhaps by 91degrees · · Score: 1

      Hell yeah! He's a liability to the hospital and most of the work is done by his subordinates anyway.

    15. Re:Perhaps by clintp · · Score: 1

      Amen, brother. Preach on. This is enabling at its finest.

      To the detractors: putting up with people you don't like is one thing. The lady that burns popcorn in the microwave every week, the guy selling Amway that insists on "networking" with you, and the fellow in the next cube who regularly yells at his kids on his cell phone. Dealing with these things are just good manners and social grace.

      Social misfits can be harmless or harmful. In the workplace wearing mismatched socks or begging off lunch invitations out of shyness is harmless. Insulting co-workers, failing to bathe, growing fruit-flies in a dung-heap of a desk, and refusing to help those beneath you is harmful. These people need to be fired.

      Putting up with an asshole who's endangering your livelihood and your sanity are quite another. Code can *always* be rebuilt in exchange for time and money, but a working, productive development team is damned-near priceless.

      --
      Get off my lawn.
    16. Re:Perhaps by Anonymous Coward · · Score: 0

      And a guy who smirks while informing others that documentation doesn't exist is just plain malicious.

      haha! *hides*

    17. Re:Perhaps by Anonymous Coward · · Score: 0

      Read it carefully. The guy who smirks is the support guy who has worked with this developer's code before. It's like this.

      Support guy: I'm having problems with one of Josh's application
      Manager: (I can't believe I have to manage these morons) Have you read his documentation?
      Support guy: (I can't believe they promoted this idiot - hello, this is Josh we're talking about?) What documentation?

    18. Re:Perhaps by Anonymous Coward · · Score: 0

      What amazes me is how many people continually seek to justify asshole behavior.

      Methinks they see too much of themselves in that mirror...

    19. Re:Perhaps by CAIMLAS · · Score: 1

      There's more than one way to cut this loaf.

      One: fire him.
      Two: put him on a 'team' of one, in charge of his own work and projects alone.
      Three: put him in charge of his projects alone, and allow him to -request- specific things from other projects (ie Photoshop logos and what not).

      I'd say #2 would likely be the most profitable for the company in the long run.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    20. Re:Perhaps by Anonymous Coward · · Score: 0

      I find my level of asshole decreases with expectations and on an inverse proportion to pay scale.

      When I was literally running all the tech behind an ISP pretty much by myself on $38k, I was a right asshole, somewhat malicious and don't you dare touch my network! Now I'm working with a team, in a nice relaxed environment on $50k, I'm a much much nicer person. Even my co-workers from my previous job actually like being around me now.

    21. Re:Perhaps by jcr · · Score: 1

      Assholes are on every team and it has nothing to do with eccentricities.

      If you've found assholes everywhere you've worked, then you need to do a better job of screening potential employers. I've worked in a lot of places, in organizations ranging from Fortune 50 companies to four-man shops, and over the course of more than 25 years, I've only encountered about a half-dozen assholes in my career. In most of the places I've ever worked, my colleagues have been decent, well-meaning people.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
  8. Lack of Documentation == dangerous by yincrash · · Score: 4, Informative

    Lack of documentation only chains you more to a developer. It makes it that much harder for someone else to maintain the code base.

    1. Re:Lack of Documentation == dangerous by Joe+the+Lesser · · Score: 5, Insightful

      Maybe there would be more documentation if you established reasonable deadlines.

      Just sayin' sometimes there's another story.

      --
      "I only speak the truth"
      Karma: null(Mostly affected by an unassigned variable)
    2. Re:Lack of Documentation == dangerous by techprophet · · Score: 1

      Which is probably why he does it. Think: if it is much harder for them to switch developers without documentation, the chances of them keeping him on after a couple hundred thousand lines of code is greatly increased.

    3. Re:Lack of Documentation == dangerous by Samalie · · Score: 4, Insightful

      Now THAT is absolute truth right there...if I had mod points, I'd mod you up.

      I'm a SQL developer (yeah, the pansy-asses of the developer world - I admit it) - and often times my documentation is sorely behind. Of course, if I didn't have 50 projects all due within 10 minutes of the conception by the end user, I'd have time to document everything too.

      That being said, I *still* do my damndest to document my code. Its not perfect, but its better than the renegade who does nothing ever.

      --
      09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
    4. Re:Lack of Documentation == dangerous by morgan_greywolf · · Score: 5, Insightful

      Exactly. There's always two sides to a story like this. One reason documentation often gets missed is because "make it work and make it work NOW!" and "we forgot to tell you, it also needs to Z in addition to X and Y!" gets nice'd above documentation.

      If we all had all the time we needed to do everything, the documentation would get done. But this is the real world and in the real world, IT management is definitely going to put functionality well above documentation on the importance scale.

    5. Re:Lack of Documentation == dangerous by Anonymous Coward · · Score: 1, Insightful

      I'm with you, I love to make my code full of documentation, but when you are given unreasonable deadlines and expected to meet them sometimes good habits just get thrown out the window.

    6. Re:Lack of Documentation == dangerous by Anonymous Coward · · Score: 0

      Awesome! It only took you 90 words to say what he did in 11.

    7. Re:Lack of Documentation == dangerous by Qzukk · · Score: 5, Funny

      It only took you 90 words to say what he did in 11.

      Obviously he had the time to clearly document his thoughts, while the other guy needed to make his post and make his post NOW!

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    8. Re:Lack of Documentation == dangerous by bigdaisy · · Score: 2, Insightful

      it also needs to Z in addition to X and Y!"

      Or my personal favourite: "You know how we said X was critical to the success of the company and how you spent several months of your life implementing it? Well, we changed our minds. Now we think Z is critical. And can you make a few changes to Y while you're at it to make it more like W, so that when we change our minds again next week and resurrect X, Y won't work with X anymore and you'll have to redo X a different way from scratch? Thanks. Oh, and if you can have it on my desk by COB on Monday, that would be good, as I have a status meeting to go before my golf game. How's the documentation coming along? Not good? Nevermind, you can get back to it later."

      OK, so I'm reading a little between the lines, but I get that most weeks.

    9. Re:Lack of Documentation == dangerous by Chris.Nelson · · Score: 5, Insightful

      If there is no documentation, the answer to the question, "Is it ready?" is "No." It's likely that the PHB doesn't know enough about what you're doing to disagree with you and grab your raw code from the repository and use it. If you establish a precedent for being done quickly (without documentation) then you get caught in a vicious cycle of it being expected that you'll be done quickly. It's best when the system supports proper documentation, etc. but if not, sandbag your estimates to give yourself time to do the job right, or at least half right. Over time, your productivity will catch up when you can figure out last month's or last year's code more quickly for a new feature because you took time then to document what you were doing.

    10. Re:Lack of Documentation == dangerous by Hordeking · · Score: 2, Insightful

      Lack of documentation only chains you more to a developer. It makes it that much harder for someone else to maintain the code base.

      So let me get this straight:

      If I conveniently don't document my code, I hereby increase my job security, because it'll make it harder to shitcan me because the other developers won't have a clue what I did because there's no documentation. Sweet, all I have to do is make it more expensive for them to shitcan me than keep me. It's pure brilliance!

      --
      Disclaimer: The opinions and actions of the US Gov't are in no way representative of those held by this author or its ci
    11. Re:Lack of Documentation == dangerous by tedrlord · · Score: 1

      It's called commenting. Proper commenting is just as good and often better than documentation. -Especially- when you're being rushed through a deadline, because that code is probably going to be badly planned and may bite you or someone else in the ass later.

      --
      [insert witty quote here]
    12. Re:Lack of Documentation == dangerous by Dare+nMc · · Score: 1

      The other that gets me worse, is a poorly planned project scope.
      IE when 100 small changes effectively destroys the original documentation and layout. (however, as the developer half the time that is my fault) I usually can get enough time to document, and design the first implementation, it is only after initial release I get the 100 different "I need this small change tomorrow" then it all degrades.

    13. Re:Lack of Documentation == dangerous by digitalgiblet · · Score: 1

      I wouldn't bet on it. Documentation is painful for many developers, and given an infinite amount of time, they would add more code and put off the documentation.

      I tend to favor reading clearly structured code with as few "brilliant" pieces as possible. That helps with the inevitable lack of documentation...

      Many things that can be done in a very terse, "brilliant" fashion can also be done in a more verbose but readable fashion. Sometimes complexity is required, but sometimes it is not.

    14. Re:Lack of Documentation == dangerous by Stonekeeper09 · · Score: 1

      Pansy Ass and Sore Behind? What was it you did again?

    15. Re:Lack of Documentation == dangerous by somersault · · Score: 1

      Sounds familiar!

      Plus, has nobody else noticed that "Lack of Documentation == dangerous" is a complete waste of code unless it is combined with some program control statement? A single equals would be desirable if we're talking c style languages.

      --
      which is totally what she said
    16. Re:Lack of Documentation == dangerous by Jaeph · · Score: 2, Interesting

      "Maybe there would be more documentation if you established reasonable deadlines."

      Nonsense. I despise this excuse - you make it sound like documentation is difficult to write. If it's clear in your head, it will take you moments to put down onto paper. If it's not clear in your head, you have a problem.

      I have never understood the so-called geniuses who have time to work overnight on some problem but can't find a spare hour to document and comment. Heck, if you're doing it right you should be commenting as you go anyways, just to keep your own thoughts straight.

      But go ahead, don't listen. Blame the bosses. It's always their fault. The genius hacker is always beat up by evil management in the standard slashdot saga.

      Again, utter nonsense.

      -Jeff

      --
      Please learn the difference between a dissenting opinion and a troll before you moderate.
    17. Re:Lack of Documentation == dangerous by GigaHurtsMyRobot · · Score: 1

      Yeah, there is something to be said for this. Considering that a lot of management would shit-can you in a second if they could get a minimum wage employee to manage your shit, sometimes you have to take some steps to ensure that you actually get paid for the value you provide. An hour of my time is worth a lot more than they pay me, and the solutions I provide are top notch. I do not withhold information, and I'm very helpful and instructive when questions are asked, but I don't go out of my way to document or comment my code... I am focused on accomplishing the task.

    18. Re:Lack of Documentation == dangerous by KagatoLNX · · Score: 1

      Maybe it's a declarative language?

      --
      I think Mauve has the most RAM. --PHB (Dilbert Comic)
    19. Re:Lack of Documentation == dangerous by SatanicPuppy · · Score: 1

      That's basically what I do for a living: prove to little smartasses that they're not as smart as they think they are.

      We canned a 25 year cobol developer from another property about 9 months ago, and she confidently predicted that we'd have to hire her back because she was irreplaceable.

      Turns out, not so much.

      No one is irreplaceable. I worked behind this one guy, real perl genius, wrote some of the finest obfuscated code I've ever seen: custom C libs with no documentation, the works. 10 years of custom crap. I reduced the code base by 90% in 5 weeks, and increased the performance by a factor of 10. By the time my 3 month contract was up, they'd have lynched the guy if he walked by the building.

      --
      ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
    20. Re:Lack of Documentation == dangerous by justfred · · Score: 1

      But what about when the "bosses" require a certain kind of documentation (ISO 9000?) that fits some ugly formatting standard, does not help you understand the code or the process, and no one ever reads?

    21. Re:Lack of Documentation == dangerous by blanks · · Score: 1

      "f there is no documentation, the answer to the question, "Is it ready?" is "No."

      You seriously believe this? Management or marketing could care less about documentation. To them documentation is something that might make your job easier or faster or make you more productive but has no value on the release of a product.

      Management: So is the project done?

      Developer: No, everything is done besides documentation.

      Management: So its done? We can use the product?

      Developer: No, like I said we still need to add documentation...

      Management: So it done then.

      I am not saying that documentation is not important; its as important as the code you write. But when it comes to a missing a deadline for a product release simply because your documentation management will not care (or understand) why they can't release a product because of the need of documentation.

    22. Re:Lack of Documentation == dangerous by Kidbro · · Score: 1

      Yep. And as you can see, the idea is hardly new.

    23. Re:Lack of Documentation == dangerous by Chris.Nelson · · Score: 1

      No, that's not what I'm saying. The conversation should go:

      Management: So is the project done?

      Developer: No.

      Don't agree, don't release it, don't support it until you believe you're done. You should be documenting as you go and can continue to document to fill time while testing is going on. But you don't have to say you're done until *you* believe you're done. Hedge, hem, haw, delay, and stall. Lie if that's what you want to call it but you're not done until you've documented so don't say you are. If you insist, the conversation above can continue:

      Management: When can I have it?

      Developer: What I've got now is suitable for an alpha test if you have a friendly customer. I could give you something better in N days.

    24. Re:Lack of Documentation == dangerous by shutdown+-p+now · · Score: 1

      If there is no documentation, the answer to the question, "Is it ready?" is "No."

      God forbid you make a demo to show off to the suites, or even a presentation with screenshots. "- Are those real? - Well, yes, they're made from a working build, but it's not yet fi... - Great, we can release that in a month then!".

    25. Re:Lack of Documentation == dangerous by shutdown+-p+now · · Score: 1

      If I conveniently don't document my code, I hereby increase my job security, because it'll make it harder to shitcan me because the other developers won't have a clue what I did because there's no documentation. Sweet, all I have to do is make it more expensive for them to shitcan me than keep me. It's pure brilliance!

      Any decent IT manager knows the trick, so the moment he thinks you're trying to pull that off, he'll kick you out to prevent any further damage you may cause.

    26. Re:Lack of Documentation == dangerous by CrazedSanity · · Score: 1

      If there is no documentation, the answer to the question, "Is it ready?" is "No." It's likely that the PHB doesn't know enough about what you're doing to...

      Sometimes PHB's just don't understand simple logic. Telling them you either need more time or they will have to deal with poorly tested and completely undocumented code doesn't sink in.

      I had an employer (thankfully I was smart enough to get away from there) that took away our profit-sharing, holding it as "incentive" for the programmers to build this new feature quickly. Being the leader, I was forced to try reasoning with him.

      I told him that we needed 4 more months than he was giving us, and that taking away our profit sharing and calling it "incentive" or saying that it is a "bonus" is BS (keep in mind, we'd had this for many years and were originally told that it would never be taken away). He smiled and offered two extra months, but that the money would still be held.

      I pleaded with him, explaining that one of the devs just bought a house with his wife and that he would lose the house if he had to go that long without the money (these checks were literally 30-50% of our monthly income), but he wouldn't budge. "Fine, we'll push hard and get it done in your timeline, but there's probably going to be a metric ton of bugs to deal with because we won't have time to do much error-checking." His response? "Just get it done on time. And don't let there be any bugs."

      The moral of the story: Some PHB's just don't care: "Documentation? I'm the PHB, I don't care." "Error checking? Don't waste your time. Oh, and don't allow any errors."

      --
      Sanity is like a condom: rather have it and not need it, than need it and not have it.
    27. Re:Lack of Documentation == dangerous by Fynnsky · · Score: 0

      and Perl did it in 10 words

      /sbin/service perlinsultsd start

    28. Re:Lack of Documentation == dangerous by CrazedSanity · · Score: 2, Insightful

      I absolutely agree!

      At one point at a previous job, I was tasked with putting all of our projects into our project management software and prioritize. I built a tree structure with parent projects and sub-projects, where the furthest-out projects needed to be completed before the parent project could be done (so the root projects were easy to understand for the PHB, and we could deal with the smaller bits). Each level was prioritized based on the level, so I could tell what piece should be completed first (I worked that part out with the other developers so we all understood what it all meant, along with figuring out some of the lower-level priorities and building best-guess timelines).

      After a week of prioritizing, arranging, and setting timelines, I brought it to the PHB. I explained the logic of the thing and how much I'd worked with the other developers in order to get it organized as such. He gave me a blank stare, asking why there were so many sub-projects and why he couldn't find the project he was looking for, etc. I explained the organizational logic, and he just gave me that blank, glazed-eye stares and then excused me.

      The next morning I was called into his office, where he showed me (with a huge smile on his face) how he'd rearranged everything. There were no trees (projects with sub-projects) that explained dependencies. The timelines were changed to what he wanted them to be, causing 10-12 projects to overlap on very tight timeframes. EVERYTHING was a project (the sub-projects that were dependencies of parents were suddenly their own projects with incredibly low priority). Only the projects he was interested were prioritized, and there were dozens of projects set with the highest priority.

      The funniest thing? Some time later we had a meeting where he told us adamantly that we should only EVER have ONE priority 1 (highest priority) item and that we shouldn't work on anything else until that priority 1 project was done. *sigh*

      --
      Sanity is like a condom: rather have it and not need it, than need it and not have it.
    29. Re:Lack of Documentation == dangerous by computational+super · · Score: 1
      Management: So its done? We can use the product? Developer: No, like I said we still need to add documentation...

      Lucky you. For me it's usually:

      Management: So is the project done?

      Developer: No, just the UI mockup. There's still no backend or business logic, and they haven't given us any requir-

      Management: So you mean there's a screen? And I can see it? So that means I can use it, right?

      Developer: No, like I said, we still need to add the backend, the business logic, and get some require-

      Management: So it's done then.

      --
      Proud neuron in the Slashdot hivemind since 2002.
    30. Re:Lack of Documentation == dangerous by saiha · · Score: 1

      Coding and documentation are two different beasts.

      For me (others) pulling the all-nighter coding session is not something I could do with documentation. They are two different beasts entirely. One is fun, the other is work.

      No it isn't always managements fault, but it is part of managements job to foster and environment where documenting is encouraged and does not become a horrible horrible chore.

      Also not everyone is like you, there are plenty of people who find coding orders of magnitude easier than documentation. A lot of it may simply be overcome with practice, but its not something you can switch on.

    31. Re:Lack of Documentation == dangerous by saiha · · Score: 1

      I think this is in fact part of the reason for obfuscation/lack of documentation. I never experienced it but I heard a lot of stories of developers training their outsourced (out of the country) replacements. They thought they were just training, but were fired immediately afterward. I don't know if this still happens but I do know those stories have stuck with me.

      While I'm sure there were documentation problems before this type of thing happened it sure doesn't make me feel good about training others how to do my job.

    32. Re:Lack of Documentation == dangerous by Anonymous Coward · · Score: 0

      And bad documentation == no documentation

      For example:
      // adds sum1 and sum2 and puts it in the total
      int total = sum1 + sum2;

      or

      // returns the total
      public int getTotal()
      { ... (more than a one liner)
      }

      At three years out of school, I was working with a developer and I saw some comments like that. I told the developer that I delete comments like that. He gasped. I then got our group together, including some "senior" developers. I showed those comments and told them I delete those comments. They all gasped. I explained that you should make comments about how a piece of code relates to other pieces of code, not precisely what it is doing. The "senior" developers were appalled that I countermanded their orders in front of everyone. I was chastised. I wondered what made them "senior" developers. I figured it was age. Later I realized I just wasn't working for a good company. I am still looking...

    33. Re:Lack of Documentation == dangerous by easyTree · · Score: 1

      Oh, oh, and I almost forgot. Ahh, I'm also gonna need you to go ahead and come in on Sunday, too...

    34. Re:Lack of Documentation == dangerous by Anonymous Coward · · Score: 0

      Yeah, I've tried to sandbag a reasonable amount (estimated dev time, multiply by 1.5-2 for mistakes, add time for qa and documentation) on projects before. Then the fucking CEO/Owner of the small business says "OK, then you'll have it done by two weeks from now." I had told them 1.5-2 months for a project and was given two weeks to complete it.

      When you try to sandbag, even because you're trying to release a good product to the customer, management will often shit on you with a bullshit date. They've all seen the movies, so they all known that when the smug man at the top tells the fidgety nerd doing the important thing to have it done in a fraction of the time, it's done on time and works perfectly and the movie ends good.

      I wish it worked the way you say it should, but it doesn't. MBAs sell something, and tell you to deliver regardless of how unreasonable the feature set or deadline happens to be. If you have to resort to lying about it, there's no point to sandbagging; they won't give you the time. They're too hung up basking in their own awesomeness to pay attention to the fact that they're paying you for your professional skills, then ignoring what they paid for you to say.

    35. Re:Lack of Documentation == dangerous by dkleinsc · · Score: 1

      However, it should also be noted that it makes it impossible for you to get promoted out of your coding role. So if you're a good programmer, not documenting well is to stunt your own career growth. If you're a bad programmer, not documenting is a method of self-preservation.

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    36. Re:Lack of Documentation == dangerous by bitingduck · · Score: 1

      Sweet, all I have to do is make it more expensive for them to shitcan me than keep me. It's pure brilliance!

      That's exactly the claim they're using for not fighting the bonuses at AIG...

    37. Re:Lack of Documentation == dangerous by Nicolay77 · · Score: 1

      Just curious, are you the kind of person who believe that you can write code that work for all cases, or are you the kind of person who believes that corner cases will always crept in your code and make it more complex than you really like in the long run.

      This is not a trick question, but an honest one.

      --
      We are Turing O-Machines. The Oracle is out there.
  9. Funny... by mdm-adph · · Score: 5, Insightful

    I've never met one of these coders in real life. For that matter, I've never been with a company who's internal politics would even allow such a person to exist.

    What cyberpunk novel does this hypothetical "Josh" live in?

    --
    It is by my will alone my thoughts acquire motion; it is by the juice of the coffee bean that the thoughts acquire speed
    1. Re:Funny... by Matatouille09 · · Score: 1

      Huge corporations around 10 years ago. These "Josh" developers were all over the place. The weirder you looked the better developer you were sought to be.

    2. Re:Funny... by forgotten_my_nick · · Score: 1

      I have met people like that. That seem to think the company revolves around them.

      Like who was told he was being moved onto a different project (because the developers on the team couldn't put up with him). He proceeded to convert all the java class files to single lines (no cr/lf/formatting) and then erased the CVS server and checked it all in. Three guesses who was in charge of the back ups. Months of work. Still he programmed in his own text editor when we just did reformatted the classes back to spec I might add with Eclipse.

      If it had been anyone else they would of been fired but there was so much trash code that only he knew we couldn't replace him so quickly.

      And another where I had spent 2 days trying to figure out why an API call was failing and when I mailed the developer working on that area his response was "You are doing something wrong". Well duh. A day later after going "WTF?" to my manager he comes around and explains that I had to send in a string with an id of his initials in order for the API to work. Ignoring how screwed up that was it was totally undocumented and obfuscated in the source.

      These were in production products we were trying to sell to customers. o_O

    3. Re:Funny... by coaxial · · Score: 1

      That's interesting at shdh30 I was talking with this one guy who pointed another guy across the room. Apparently the other guy was fine engineer, but constantly complained about how the code "wasn't clean enough" and the design "wasn't right" and all the other standard moans of engineers, but to the point that he would constantly get in fights with the other engineers. (There's a certain level of mess and incompleteness/wrongness you have deal with. Nothing is perfect, not even your own work. Eventually, you have to grow up and learn to deal.) So the guy quit to do consulting on his own where he only takes projects that he can write all by himself.

      The thing that weirded me out was the fact that the guy I was talking to genuinely admired antisocial engineer. My comment was, "Huh. I wouldn't hire him. There's six guys in this room that that could do his job without having me put up with shit."

    4. Re:Funny... by tixxit · · Score: 1

      His example is extreme, yes, but these people are certainly out there. In a professional software shop, I'd hope not, but in a lot of offices with a handful of programmers, there will be one guy who is considered the guru by all the non-programmers, because he gets-things-done and gets-em-done-fast. Of course, to all the other developers, he's the guy who documents nothing, causes more problems then he solves, and always has to do things "differently." To everyone else, you not being able to understand his convoluted code written in a language known to 1% of programmers, is an indication of his genius... Of course, since you are the non-genius, you still get delegated to fixing all the bugs in the POS program, while he makes even more unmaintainable code. This is actually a management issue, and the best course of action is not to complain, but to quit and run for the hills.

    5. Re:Funny... by Anonymous Coward · · Score: 0

      Kinda related...

      Have you ever wondered what the 'MZ' stands for at the start of almost every Windows .EXE file?

    6. Re:Funny... by drew · · Score: 1

      Oh, they definitely exist. I always thought they were apocryphal, too, until I worked with one. You're right, though, that it does take a certain amount of dysfunctional office politics to allow them to do any real damage. In my case, the company was split between multiple offices. "Josh" drove everybody who worked in the same office as he did crazy. But the highest ranking person in his office couldn't fire him without approval from somebody in one of the other offices, who only saw the work that he got done, and not all of the problems that he caused. By the time it became apparent to everyone that he needed to go, there were too many critical systems that only he understood, and he guarded his knowledge jealously. He would talk directly to clients without involving the project managers, so only he knew what was going on with his projects. He would shrug off questions about code that he had written in a very similar way as the Josh described in the article - "Why should I help somebody who's not smart enough to figure it out on his own?" I know at least one person got fired to take the fall for him because we couldn't afford to let him go... yet. When he finally was let go, everything was a disaster for about a month while we scrambled to decipher some of his processes and consistently ran up against little gotchas that he must have known about and figured out how to work around without ever telling anyone else. After the first month, things were far smoother without him than they had been with him, but even six months later we were still running into random surprises buried away in code that he had written.

      --
      If I don't put anything here, will anyone recognize me anymore?
    7. Re:Funny... by buddyglass · · Score: 1

      He proceeded to convert all the java class files to single lines

      That's the most ridiculous thing I've ever heard. I could see maybe running them all through some sort of source-code formatter and checking the re-formatted versions back in. But single line files? Wtf?

    8. Re:Funny... by ThemsAllTook · · Score: 1

      I've worked with several who weren't quite at the level described in the article, but honestly weren't far behind. Back when the company I'm at was smaller (it's grown more than 10x in size over the duration I've worked here), they had a much easier time getting away with it. Now, we have better managers and better processes that help ensure these people either turn their act around or get kicked out.

      Shamefully, I must admit that I nearly become one of these "quirky" developers several years back. I was young and foolish, and had gotten a lot of praise and let it go to my head. There was a turning point, though; I got a fairly negative performance review (delivered clearly but quite tactfully by my reviewer), realized I was going down the wrong path, worked hard to reverse it, and got a glowing review the next time around. So, don't give up on these people; sometimes all they need is a gentle but firm push in the right direction.

    9. Re:Funny... by RightSaidFred99 · · Score: 1

      Probably at podunk little shit companies. No large company would even remotely put up with this laughable self-image. If there's one thing you learn working at a large company it's that absolutely anyone is replaceable and that life will go on for the company if you're fired.

    10. Re:Funny... by yttrstein · · Score: 1

      I've only worked for companies with coders like that. The lack of interesting things in your life is no one's fault but your own.

    11. Re:Funny... by Anonymous Coward · · Score: 0

      I worked with an individual who had his own office that was kept as dark as possible. He was quite sociable as long as the topic was him or whatever he was working on. Problems would occur when issues were brought up that were not in line with his agenda.

      In another company I had the privilege to work friendly coder who had superpowers that made the entire floor of the office smell like sweat within minutes after his arrival.

      In that same company we had smart fellow who wrote a lot of clever code that was tricky to work with because of all the undocumented side effects. Because he thought he was the companies' best asset he started to make unreasonable demands and eventually left the company because another company offered him a lease car (he didn't have a driver's license at the time).

      An art director I had to work with almost caused his entire department to quit because of his narcissistic nature combined with some severe tendencies to be an overall asshole. It was resolved by moving said director off to a position where he couldn't do as much damage.

      If you get to work for different companies for some period I'm sure you'll find similar people. In short: I've seen "aspects of Josh" and I guess Mr Spiegel was unfortunate enough to run into someone packing all of those wonderful traits in one...

    12. Re:Funny... by funaho · · Score: 1

      Obviously you never worked at Big Net. :)

    13. Re:Funny... by bwcbwc · · Score: 1

      I've never met one with the total arrested development of the guy in the article, but I've met plenty of coding prima-donnas that made it clear they thought they were better than the people on the test teams, documentation teams, production support teams and all the other teams it takes to put together a product, simply because they were deeper into the technical details. Not enough to get themselves fired or even kicked off the project, but enough to drag down the overall team morale by just that much.

      Even in Hollywood, there are stars who are a*holes and think they run the show just because their last movie made $50-60 million and those who are team-players. So it isn't just the techies.

      --
      We are the 198 proof..
    14. Re:Funny... by Fulcrum+of+Evil · · Score: 1

      Since he also nuked the CVS server, I'd say it was spite.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
  10. news? by Anonymous Coward · · Score: 0

    company gets all productivity from one guy, guy leaves, costs company money to get productivity back

    i thought this was a news site

    1. Re:news? by JerBear0 · · Score: 1

      "i thought this was a news site"

      Really? That's so cute!

      --
      Bad experience is a school that only fools keep going to.
  11. Well... by Anonymous Coward · · Score: 0

    ... use scrum techniques and such to try to get "normal" programmers to produce more until they burn out and quit, instead :)
    Manager should start realizing that developers are people, and they aren't just "codemonkey", if they want a codemonkey they'll have to put up with it. Who else is going to want to go to work to code all day with a manager cracking his whip to "code faster, better, more efficitient, faster!"

  12. I'd say most are less extreme by Trepidity · · Score: 5, Interesting

    Most quirky developers don't defecate in the lobby or egregiously insult coworkers. They just have poor social skills, may have poor hygiene, may perform poorly on teams, and so on. In those (by far more common) cases, I've almost never seen a situation where the company would be better off without that person in some capacity. Usually it just requires moving them off some team project to a big one-person project that's been festering on the TODO list.

    It's actually pretty hard to find really good coders, so I'd say unless they actually are so terrible in other ways that it's screwing everything else up, if it were my company, I'd try to find somewhere to put them that plays to what they're good at while minimizing any potential friction.

    1. Re:I'd say most are less extreme by Lumpy · · Score: 4, Insightful

      Honestly....

      I dont care how good you are. TAKE A FRICKING SHOWER AND WASH YOUR CLOTHES.

      Really is it that hard to spend 10 minutes in the morning, EVERY MORNING to bathe yourself??

      and honestly, "really good coders" are not worth it. Give me medicore coders that understand business and can do what they are asked to do over a stinky quirky great coder any day.

      --
      Do not look at laser with remaining good eye.
    2. Re:I'd say most are less extreme by Splab · · Score: 1

      It's not hard, but it's not healthy either. (I do shower every day though, wear clean(ish) clothes)

    3. Re:I'd say most are less extreme by Anonymous Coward · · Score: 1, Insightful


      Agreed, I've got extensive real world experience with this. I've both been the quirky developer and now manage multiple quirky developers.

      I was definitely the arrogant whiz kid when I was younger, but my infractions were usually showing up late to work, wearing torn t-shirts, etc. Still, getting away with that stuff and still being fawned over by management makes everyone resent you. The fundamental shift came when I realized that although management viewed me as a great developer, I was never going to get promoted because they didn't trust my social skills at all. After that I put a great deal of effort into developing social skills (which was really hard) and stopped acting as if the rules didn't apply to me. Once that happened my career took off.

      I now hire plenty of the same "whiz kids" as I myself was, because I value their talent. But I do try to indoctrinate them in the ways of the real world. I try to make them have the same epiphany that I had, and show them that IQ and income/career trajectory are not proportional, and having a high IQ and being arrogant about it is a huge dead end. This is not something you can convince them of in one sitting, you have to keep pushing this idea on them for months. If it sinks in, the developer becomes a rock star at work. If not, they stay stuck at the bottom, or if their behavior is egregious enough, I fire them. But their talent is undeniable, so being dismissive of them as a manager is immature and cranky. You have to give them a shot.

    4. Re:I'd say most are less extreme by Rene+S.+Hollan · · Score: 5, Insightful
      Really is it that hard to spend 10 minutes in the morning, EVERY MORNING to bathe yourself??

      Sometimes, when you've spent the past 48-72 hours working to solve some crisis that some moron left and you have to clean up, yes.

      You look like shit, smell about as bad, and have a cranky attitude to match.

      But, shipping on time and avoiding a $250,000/day contract penalty can sometimes justify the hell (Ah, contracts with separate "code complete" and "QA Pass" dates.)

      Some coders don't shower all the time because they haven't gone home.

      --
      In Liberty, Rene
    5. Re:I'd say most are less extreme by Anonymous Coward · · Score: 2, Interesting

      I used to be such a person. Your answer is: Yes, it is that hard.

      You put it as if it is by choice, but in most cases it really isn't. Sometimes I would forget to take a shower or would not remember to brush my teeth. (I'd document the fuck out of everything, though). It was never by choice, and I really wanted to improve myself.

      After about 6 years, I've finally managed to. I designed a rigorous schedule that I follow and must follow to keep "fitting in" so to speak, and despite the fact that I still drop the ball sometimes it has improved my quality of life magnificently.

      I'm not saying you're wrong though, heh. Just that usually, most people aren't doing it by choice (or even aware of it). In most cases it can even be addressed or self-addressed. I think it really comes down to communication in the end.

      My 2c. Take it for what you will.

    6. Re:I'd say most are less extreme by Anonymous Coward · · Score: 0

      Sure, if all you need is mediocre code, then you need mediocre coders. You also need a sharp eye and a steady hand to throw away the crud and tell the mediocre people to try again, to avoid succumbing to the crud.

      If you want a great product, you need great people, and those need a lot of care. If your company cannot provide that, then your company will start to stink, figuratively and literally both.

      Merely providing showers and requiring the stinky people (or everyone) to shower before every meeting is not enough to fix bad management. Remember, it is management's job to make sure each cog, brilliant or less so, sits at the place and does the thing where them doing just that benefits the company most.

    7. Re:I'd say most are less extreme by TheLink · · Score: 1

      D'oh. If that's the only problem, I'll take a great coder over a mediocre coder.

      Just let him work from home. His productivity might even increase.

      But I kinda agree, I'd take a mediocre coder over an asshole who is "a fantastic coder". Because though that asshole could do amazing stuff, half the time you won't be sure whether he is really working for you or not...

      It's like hiring a mercenary. If you hire an excellent asshole mercenary, while he can "headshot" from miles away and the rest can't, he might start headshotting you.

      FWIW, quirky != asshole. Typically it's quirky "mostly harmless". Dealing with that sort of thing is what you hire middle managers are for - making a suboptimal/ragtag team work, because the company can't afford "optimal".

      --
    8. Re:I'd say most are less extreme by fprintf · · Score: 1

      Agreed. And to all my Indian and Pakistani friends, please understand what deodorant is for. You may shower each day to remove the smell of curry, but it doesn't help @ 2pm or 6pm if you don't use deodorant. You will still smell rather badly of body odor, and it is not only annoying but it is incredibly unproductive. It is sometimes hard enough to get our business partners to join us for meetings, but it makes it that much harder when they don't want to come because our department smell of BO.

      Thank you,
      The Management.

      --
      This post brought to you by your friendly neighborhood MBA.
    9. Re:I'd say most are less extreme by brianjlowry · · Score: 1

      I worked for someone like you at a previous job. As a power hungry middle-manager, you took the project in a ridiculous route and played both sides of the management fence to pin bad ideas on the team behind closed doors.

      You said that you would much prefer to have 10 average to sub-par developers that would listen to every dumb idea you had then to have 3 brilliant people that might challenge your assumptions, but inevitably could get the project done faster and smarter and cheaper.

      Because of you, the talent at said company is gone and the project is a year behind schedule.

      And the word is, your days are limited.

    10. Re:I'd say most are less extreme by Anonymous Coward · · Score: 0

      Hooray for you. I'm working on a project right now and I haven't left my hotel room for 2 days. I finally took a 2 hour break just to not lose it completely. I've been going 18 hour days since February and that's only getting worse.

      One week left.

      On the plus side this company is at least fair about it. I'll probably have the whole month of April as vacation with pay to most any location on Earth.

    11. Re:I'd say most are less extreme by jmpareja · · Score: 0

      Depends really on the type of software you write. Sometimes 'mediocre' just wouldn't do. :-) And also, I think these bad side is not the rule for really brilliant coders, but the exception. Most just ignore the noise and let their work do the talking.

    12. Re:I'd say most are less extreme by Anonymous Coward · · Score: 0

      Use of the word 'egregiously' when there is no need for it doesn't make you appear smart.

    13. Re:I'd say most are less extreme by Anonymous Coward · · Score: 0

      Yes, right.

      Those 'coders' would have been more productive and finished the job sooner if they had taken the time off to go home, get some sleep, and recharge. I have never found working 24 hours straight (let alone 48-72 hours) to be a successful strategy. I've solved hard problems better standing in the shower in the morning after a good sleep than almost any other way.

    14. Re:I'd say most are less extreme by Orion+Blastar · · Score: 1

      For me, I bring my own soap and shampoo and washcloth and clean myself up in the bathroom when working those 48/72 hours. Plus deodorant and a spare change of clothes. It does not take any more than 15 minutes to do so, more if you brush your teeth and mouthwash. I had such items in my desk drawer for just such cases to be prepared for anything.

      Nothing like cleaning up a big mess of a genius programmer that management loves, but does not love programming janitors like me or you that take on extra work to make sure it passes QA Testing, which should have been the job of the genius programmer in the first place. But he went to "Happy Hour" with the managers to suck up and schmooze his way into a promotion and pay raise.

      --
      Remember, Slashdot does not have a -1 disagree moderation, and no, troll, flamebait, and overrated are not substitutes.
    15. Re:I'd say most are less extreme by RightSaidFred99 · · Score: 4, Insightful

      Well, it's a myth that these great coders are valuable, as well. High level software development requires more than the ability to manage complexity. You won't find any Josh's developing high quality, vast enterprise applications. You won't find them developing a modern RDBMS, or anything that's _truly_ complex in terms of architecture, scope, and interaction with other systems.

      You'll find Josh's hacking away on some custom application developed by a small or medium sized company and it'll be their one trick pony.

      The reason is simple - to develop a large system it takes many people, you can't have a one-man show on large software products.

    16. Re:I'd say most are less extreme by 91degrees · · Score: 1

      What job do you have where you can maintain productivity working more than 12 hours without a break?

    17. Re:I'd say most are less extreme by GooberToo · · Score: 1

      I don't disagree with your position but I will point out, some "really good coders" are often worth 3-5 "medicore coders" and may only cost 1.5x-2x what of those "medicore coders" cost the company.

      Its often simple economics as to why "Pig Pens" of the world are allowed to exist.

    18. Re:I'd say most are less extreme by infodragon · · Score: 1

      I dont care how good you are. TAKE A FRICKING SHOWER AND WASH YOUR CLOTHES.

      I have Aspegers syndrome which, arguably is a "mild" form of autism. I feel every droplet like a gran of sand when I'm in the shower. A bath is even worse. If I'm having a good day it takes 2-3 hours to recover from said hygienic activity. I do wear deodorant, it took a very long time to find one that did not irritate. Some of the other symptoms are; I cannot stay in a mall for more than 30 minutes, if I wear ear plugs that goes to 4 hours; I see sound and hear color (different sounds produce different "static" in the back ground, red produces a particular type of hum).

      I have no rash, nor is there any physiological explanation for why such activities cause extreme discomfort/pain other than an over sensitivity analogous to the input gain turned way up high.

      I consider myself a *VERY GOOD* developer/engineer. The current software I wrote for executing statistical simulations executes 2000x faster than the fastest competition with the same fidelity. This was done with one other person I was throwing ideas around with. We both have our quirks, but we both are probably near the best in the industry. We both realize that we have quirks and we make room for them. Neither of us are indispensable though, and we know it.

      Before I knew I had Aspergers I didn't understand how people could take a shower and go on with their daily lives like nothing happened (Think getting a light sand blast). After I discovered it researched it, got diagnosed by a professional with adequate experience, I went about modifying my life to manage this disorder. I still stink from time to time, and my wife reminds me and I take a shower... When I'm going to have a meeting with "normal" people I make sure I'm showered 2-3 hours before the meeting and had a good day of rest before.

      It's a cost/benefit. I've sat down and wrote 800 flawless lines of c++ in 2 hours, no copy and past crap, utilizing functors, polymorphism, STL and a few other fun and exciting things. There's never been a problem I couldn't solve, one of my first jobs I was "The Exterminator" because I could find most bugs quickly and fix them. I averaged 40 hours of fixes per day, compared to my team mates, measured by management.

      The point I'm making is many times, and I've met many like me, a shower HURTS and causes severe problems for the remainder of the day. Showering before bed is worse because you don't sleep well.

      Your comment is very short sided and quite Narcissistic as to expect everybody to exist for your comfort (HEAVY SARCASIM THERE)

      You have a good point but before you get FRICKING bent out of shape over some BO, there might be a reason behind it and then again their may not be. Don't be afraid to talk to the person as they may not know they stink (been there done that on both sides)

      --
      If at first you don't succeed, skydiving is not for you.
    19. Re:I'd say most are less extreme by Nick+Ives · · Score: 1

      You should eat more curry. Curry is awesome! It's one of our national dishes here in the UK - Chicken Tikka Masala was actually invented here and exported back to India!

      --
      Nick
    20. Re:I'd say most are less extreme by yttrstein · · Score: 1

      It's not only pretty hard to find really good coders, it's nigh impossible to find brilliant ones; to the tune of "when you catch one, keep it". Whenever I get involved with one of those horrid corporate over-culture places that rewards secret cocaine addiction when combined with expensive suits and pretty much nothing else, I feel nothing but pity for the poor souls who work there, believing that it's their only choice.

    21. Re:I'd say most are less extreme by funaho · · Score: 1

      I guess it depends on how quirky they are. I'm a bit quirky, but I am (at least according to my last review) very productive, helpful and pleasant to be around. My biggest quirk is that to get anything serious done I need long stretches of uninterrupted time, because interruptions completely derail me mentally. My bosses are understanding and they try to make sure they don't stuff me into too many meetings, or at least they try to concentrate them into one or two days a week to minimize my need to stop & start working.

      I have other quirks too, though over the past 15+ years in the job force I've learned to hide and/or work around those on my own.

      And by the way what kind of a geek would insult female coworkers? Sheesh, those are the ones I go out of my way to help! Maybe it's just because all my female coworkers are grad students... :)

    22. Re:I'd say most are less extreme by Anonymous Coward · · Score: 0

      i'd say you've got other problems if your smell is offending others after missing a shower for two days. you're coding at a desk, you're not working in a pulp mill. it may not be roses, but god damn it man, learn to wipe your arse.

    23. Re:I'd say most are less extreme by Trepidity · · Score: 1

      Depends on what you mean by "valuable", I suppose. If the only thing your company needs done is high-level software development of large, complex systems, then sure. But I've never seen a company that didn't have at least a few ad-hoc custom messes sitting around somewhere, also, often needing urgent tending to at just the wrong times.

    24. Re:I'd say most are less extreme by seebs · · Score: 1

      How does that make these people not valuable?

      A ton of software isn't that big and has no reason to be.

      If you can get someone with ten times the productivity of other developers (and yes, ten times is a real performance differential), there's likely to be some project or projects where that person is worth a lot of money.

      --
      My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
    25. Re:I'd say most are less extreme by RightSaidFred99 · · Score: 1

      Yeah, I should have said "always valuable", or just left that sentence off. If you're a poorly run company and want to put all your eggs in one basket, then these people are of course valuable. Let's say the guy isn't even an asshole, what if he gets hit by a beer truck?

    26. Re:I'd say most are less extreme by Rene+S.+Hollan · · Score: 1
      Except, you don't have the luxury of taking the time.

      You have to fix what someone else fskd up.

      It often isn't that much of a matter of re-design, so the lack of "sharpness" after the first 12 hours or so doesn't hurt as much as you'd think. And, the way things are broken is often a clue of how to repair them. It's a question of realizing that it's about two to three days of typing to be done in two to three days of wall time.

      No, you can't debug effectively, except the simplest things in context, but you sure can code the simple missing bits until you drop.

      --
      In Liberty, Rene
    27. Re:I'd say most are less extreme by Rene+S.+Hollan · · Score: 1
      Oh, I didn't say one didn't take breaks. One just doesn't take breaks long enough to sleep or go home.

      Can't do it often, and the second twelve hours are often the worst, but a "second wind" effect kicks in. And, by this time, you usually know everything that is wrong, and it's crystal clear what it will take to make it right -- you just have to code it.

      It's often not hard work, just lots of loose ends to tie up, or reimplement a badly written library, that you could have implemented in a week of wall time, but were too busy, so it was outsourced to someone who did it in a month, and all wrong.

      You "push" because so much context is in your head, that you'd forget it before you could ever document it, and as long as you keep coding, it stays refreshed.

      There's a saying that "the product of the size of the code base and the duration where it will all be crystal clear is a constant". You want that two or three golden days to be the duration when all is crystal clear. It's like being in "the zone" on steroids (or, Jolt, as the case may be).

      Often, at the end, it's far from perfect, but it's good enough to meet this version's reauirements, and you can at least document what remains broken/cruftily implemented.

      --
      In Liberty, Rene
    28. Re:I'd say most are less extreme by Anonymous Coward · · Score: 0

      Well... Bill gates was well known for having poor hygiene... working all night longs... and not going home for days untils things where going as he wished... He was dimmed a genius too...

      The OP can call him and say hin that he is such an asshole that can not be allowed to work in any Corporation....

      Because it's perfectly clear who is more valuable to society...

      Dependable mediocrities, are well... dependable... that make mediocre managers comfortables with them...

      Truly brightness on the other side... could easily end in a mental institution (Think Van Gogh)

      Somebody must fund Leonardo and or Michelangelo (Not the ninja turtles, by the waay) But it will come clear in the centuries to come, not right away...)

      Good luck with your mediocre self...

    29. Re:I'd say most are less extreme by Anonymous Coward · · Score: 0

      True, but this doesn't occur EVERYDAY, while their smell on the other hand ALWAYS seems to make it to work with them.

    30. Re:I'd say most are less extreme by IntlHarvester · · Score: 1

      Well, it's a myth that these great coders are valuable, as well. High level software development requires more than the ability to manage complexity. You won't find any Josh's developing high quality, vast enterprise applications. You won't find them developing a modern RDBMS, or anything that's _truly_ complex in terms of architecture, scope, and interaction with other systems.

      Actually, many established tech companies have a Josh, just that they usually have been promoted out of the way have a fancy title like "Chief Scientist" but no real management responsibility.

      --
      Business. Numbers. Money. People. Computer World.
    31. Re:I'd say most are less extreme by Anonymous Coward · · Score: 0

      We have a shower at work. When I've had to do an all nighter I take three minutes to refresh myself and change my clothes before the 9-5ers get in. Makes me feel almost human again and my productivity definately increases.

    32. Re:I'd say most are less extreme by sfcat · · Score: 1

      No, instead you find an entire team of them. Seriously, go see who works on the Oracle Kernel team and you'll realize just how wrong you are.

      --
      "Those that start by burning books, will end by burning men."
    33. Re:I'd say most are less extreme by dbIII · · Score: 1
      Tell that to emergency room doctors. I think the theory there is that a half asleep doctor that might let someone die by making a mistake is better than having people die in larger numbers becuase there is no doctor on duty. With good management and enough staff you wouldn't have doctors working 16 hours+ or 48 hours on the premises with the occassional nap.

      Now look at a typical US style management company and you have office workers of various types that are not in short supply and are not involved in situations where people will die if you are not there - and you see exactly the same thing. It's a symptom of either a lack of good management, a project that has got out of control, or something needs to be fixed quickly because production is being effected. Usually it's the first case, but in a well run company the second and the third happen.

    34. Re:I'd say most are less extreme by Anonymous Coward · · Score: 0

      'medicore' coders will only ever deliver 'medicore' results.

    35. Re:I'd say most are less extreme by Anonymous Coward · · Score: 0

      "Quirky, brilliant" designers of the type mentioned here are a roll of the dice. While they are cheaper than buying "charismatic, brilliant" workers, they'll hoover resources pretty ferociously, either in budgets or in interpersonal coverage. That said, there's an undeniable chance that they will indeed lay a golden egg, given somewhere to roost. As such, they're not such a bad investment of extra resources, when those exist. Right now, discretionary budgets are pretty tight, and it makes solid sense to show a few of these folks the door. *shrug*

    36. Re:I'd say most are less extreme by libkarl2 · · Score: 1

      The "Josh" character strikes me as an extreme case of Asperger's Syndrom:

      Low self awareness, inability to intuit psychological situations, low empathy, manipulative, ruthless, cunning, flatness of affect but unlike true psychopaths he retains technical skills, is hygienically agnostic, and totally unconcerned with his personal appearance.

      Often, when a particular area of the brain does not function well (if at all), other areas of the brain overdevelop -- in an effort to compensate for the missing brain function. His "genius" could stem from that... he could have an IQ as high as 180, but with no grasp of psychological reality, zero team integration, and a truncated worldview... he is virtually worthless.

      And thats before you let him log in to your cvs server and create downstream mayhem!!!!

      --
      You are where you are at the time you are there.
    37. Re:I'd say most are less extreme by Rene+S.+Hollan · · Score: 1
      Amateur.

      Yeah, after a 10k run, I'd want to shower too.

      Guess what, buckeye, you're running a marathon. 26 miles. 40k.

      The thing is, a break to take a shower at that time, would KILL my productivity.

      Finished the first day, struggled through the next eight to ten hours, we're about at 3:00 AM. Fatigue sets in, but that goes away by 5:00AM or so. By seven or eight, one is comfortably "in the zone", and coding against time. One is oblivious to time, actually, and sees the design clearly in one's mind. If anything, one gets frustrated that one isn't typing as fast as one wants, lest the design start to fade. (You've got not time to document anything -- this is crisis mode -- where you have to replace a horribly defective piece or implement a missing piece NOW.) The code IS the documentation, and you can extract the spec later. After all, you are doing the plumbing now and have the spec in your head. No need to persist it in anything except code just yet.

      Have you ever been "in the zone"? I suspect not. You don't program, actually. Code just flows. It's almost a transcendental, hyptnotic state of extreme productivity. You can go on for another day like this, at least...

      ... as long as you aren't interrupted, espescially for something as mundane as a shower.

      Thing is, if you fall out of "the zone" on a marathon like this, you likely will not get back.

      The other thing is this: this is extremely taxing on the body and mind, and you will likely have to crash for 3-4 days afterward and not be able to repeat the performance for a few months.

      Is the resulting code elegant? Likely not. It represents the extreme compromise of schedule, performance, and correctness within extremely well-defined bounds. Probably does not scale, or is not extensible. Not because it is "bad", but because that flexibility was compromised to meet schedule.

      Would it have been better to do it slowly, and better? Of course, except you're stuck in this hell because (a) some other moron coultn't code correctly even when given ample time, (b) something was forgotten, (c) a late requirement came in. It could be argued that what you produced, in terms of maintainability and extensability, is no better than what said moron would have. But, you've ensured it is (a) correct, (b) on time.

      It's time to stop, reflect, and consider changing jobs if management requires these kind of heroics too often. (IOW, having a fire extinguisher in the explosives factory is a good idea, but not a good place to work if you need to use it often because some moron insists on smoking there.)

      --
      In Liberty, Rene
    38. Re:I'd say most are less extreme by Anonymous Coward · · Score: 0

      Honestly....

      I dont care how good you are. TAKE A FRICKING SHOWER AND WASH YOUR CLOTHES.

      Really is it that hard to spend 10 minutes in the morning, EVERY MORNING to bathe yourself??

      and honestly, "really good coders" are not worth it. Give me medicore coders that understand business and can do what they are asked to do over a stinky quirky great coder any day.

      Ahh, you'll be the guy managing a project that's "mysteriously" far over budget and time. Hiring a bunch of mediocre programmers will get you a bunch of mediocre code. I would think twice about someone like "josh", I would insist he documents and that he doesn't insult the ladies. (T-shirts, I'd generally say don't look at them.) But if you're expecting your programmers to have pressed suits or something, you will not get any decent programmers and that's that.

  13. Why Are They Quirky? by theBraindonor · · Score: 1

    Some developers are quirky because they do someone no one else understand and think they are better than everyone else they work. They go out of their way to be a pain in the ass to work with, and I really don't understand why any manager puts up with it.

    Others, like myself, are quirky because...we just are. No amount of trying to fit in with office life is going to be considered a success. No one minds if I'm quirky so long as I work hard at being a member of the team.

    1. Re:Why Are They Quirky? by Kartoffel · · Score: 1

      That's true. As a mid-career nerd myself, however, I've noticed that our type often presents themselves as a pain in the ass without realizing it.

      People are fickle. If they think you're intentionally being an ass, they'll resent it. For me at least, that means making a conscious effort to spend at time making small talk, attending social stuff, and engaging coworkers on topics besides just work. Getting to know your coworkers isn't just Dilbert teambuilding bullshit. It also (a) covers your ass by helping the mundanes relate positively to you and (b) gives you insights into how your coworkers think, too.

  14. Stop coddling your little genius by Anita+Coney · · Score: 5, Informative

    When kids are recognized as being highly intelligent and gifted, parents, extended family, and teachers go out of their to coddle them. To treat them as special. To give them far greater leniency and independence than kids with normal intelligence.

    Is it any shock that these kids grow up to think the rules don't apply to them?

    --
    If someone says he and his monkey have nothing to hide, they almost certainly do.
    1. Re:Stop coddling your little genius by rolfwind · · Score: 3, Insightful

      When kids are recognized as being highly intelligent and gifted, parents, extended family, and teachers go out of their to coddle them. To treat them as special. To give them far greater leniency and independence than kids with normal intelligence.

      Is it any shock that these kids grow up to think the rules don't apply to them?

      One of the pure group psychology shows I really like watching is Dog Whisperer. It's left unspoken, but I think a lot of it applies to kids and even adults in power situations.

      However, I don't think it's the gifted children that are specifically the problem, I think any type of kid treated with gloves becomes that way. The one that can't perform are merely arrogant losers as adults. While the ones that can become like Josh. The brilliant ones without the anti-social problems don't use their brilliance as a excuse and often don't call attention to it in the first place and may be skipped over as merely above average (which the Josh of the world may be but play it up, afterall, when you aren't hamstringed by stupid bullshit rules, you can do things more freely and eventually do things others never thought of in the box they've been confined in).

      But as a counter, I have to bring in the brilliant George Carlin:
      http://www.youtube.com/watch?v=w7LOCg4uKAg
      http://www.youtube.com/watch?v=izE4_Jd2dOw
      http://www.youtube.com/watch?v=f3XeRCAAkZY

    2. Re:Stop coddling your little genius by Heather+D · · Score: 1

      Agreed. This is damaging to the society they have to live in and to them as well in the long run. Its okay to be quirky, it can even be a good thing sometimes, but it doesn't grant a get out of social responsibilities free card.

    3. Re:Stop coddling your little genius by Anonymous Coward · · Score: 0

      Some parents do. Some parents don't.
      Depends how talented the parents are.

    4. Re:Stop coddling your little genius by Anonymous Coward · · Score: 0

      I am one of those "highly intelligent and gifted" kids and was recognized as such, yet I was never coddled by extended family or teachers. What universe do you live in where this happens?

    5. Re:Stop coddling your little genius by Mr.+Slippery · · Score: 3, Insightful

      When kids are recognized as being highly intelligent and gifted, parents, extended family, and teachers go out of their to coddle them. To treat them as special. To give them far greater leniency and independence than kids with normal intelligence.

      Kids who are highly intelligent and gifted are special, by definition. Teachers and caregivers often find that the rules designed for age-group peers should not be applied, because the assumptions behind the rules don't fit. That's not coddling, especially when you consider the additional pressures of expectation placed on them.

      For example, I remember in elementary school (this is around 1975) it was a rule that kindergarteners could not books out of the school library. After all, reading wasn't taught until first grade, so kindergarteners can't read. When they found two of us who showed up able to read, rather than remove the rule entirely or stunt our learning potential, the rule didn't apply to us.

      Now, this has nothing to do with the sort of developer discussed in the article. A smart developer develops elegant and documented code, and is so proud of their work that they love to explain it to others. Someone who's mastered some arcane bit of technical lore and secretively builds convoluted, undocumented code around it, is neither smart nor talented nor an asset to their team. If they further behave like an asshole (not just quirky, but actively rude and abrasive), the only "special treatment" warranted is a swift kick in the ass.

      --
      Tom Swiss | the infamous tms | my blog
      You cannot wash away blood with blood
    6. Re:Stop coddling your little genius by Anonymous Coward · · Score: 0

      I've seen kids smarter and less smart than me achieve more, and I've seen kids smart and dumb alike grow up to be conceited, spoiled, or downright criminal. IQ has little to do with it.

      That doesn't change that smart kids need smart guidance; guidance very different from ``normal'' kids, just like really retarded kids need to be approached in their own special way.

      As a poster child underachiever I am actually quite happy some countries have seen the light and provide specialised care for the smart end. This doesn't need spoiling, frag no. It usually means the kids work their asses off, and rightfully so. A big brain needs lots of stuff to do or it gets bored. Which is a sad, sad waste.

    7. Re:Stop coddling your little genius by protected_static · · Score: 1

      What BS. There are as many styles of parenting and educating 'gifted' kids as there are 'non-gifted' kids. If anything, the parenting paradigm I see most frequently (as the parent of a 'gifted' 9-year-old) trends towards pushing their kids harder.

    8. Re:Stop coddling your little genius by stevied · · Score: 4, Informative

      There's a fine line, I think. All kids should certainly be taught respect for others and society, regardless of their talents.

      On the other hand, subjecting smart kids to excruciatingly slow tuition along with everybody else because streaming is seen as un-egalitarian is a pretty effective form of torture, as is forcing them to endure bullying while trying to play team sports that they don't understand and are no good at, for example.

      I'm willing to buy into the idea that all people are equal, but not that they are identical, and our culture increasingly cannot cope with people who are not exactly the same as everyone else. People with talent can serve society by developing that talent and using it to help society, if they're given the opportunity: otherwise they just end up broken and resentful.

    9. Re:Stop coddling your little genius by kestasjk · · Score: 1

      The summary seems to suggest that the rules don't apply to them

      --
      // MD_Update(&m,buf,j);
    10. Re:Stop coddling your little genius by Lemmy+Caution · · Score: 1

      I speculate that bad every quirky asshole "genius" there's a kid who had just that experience, and whose shoulder-chip has grown into a cancerous boulder.

    11. Re:Stop coddling your little genius by east+coast · · Score: 1

      Obviously you're not smart enough to realize that you're not the only one.

      --
      Dedicated Cthulhu Cultist since 4523 BC.
    12. Re:Stop coddling your little genius by Edward+Scissorhands · · Score: 1

      I'd mod you down. Did it ever occur to you that maybe the "rules" we apply to "normal" kids is what holds them back? That the bigger, more interesting sandbox we give to more intelligent kids is what helps them grow up to have positive impacts on society with their inventions and perspectives? You're the type of person who thinks that everyone should be treated the same, except you don't realise that not every person actually is the same.

    13. Re:Stop coddling your little genius by Kartoffel · · Score: 1

      Is there any reason the rules for average children *should* apply?

      Every person has special needs, whether they're gifted, average, or dumb as a stump. When you treat all children as if they all have the same abilities they will resent it. They will resent YOU.

      Children should be challenged and rewarded if they succeed. That's not coddling.

    14. Re:Stop coddling your little genius by pnuema · · Score: 1
      I'm a smart guy who really could have benefited from more tracking in my education. My brother is an administrator at one of the best high schools in the city. We once got into a debate on tracking. His response to my arguments really scored:

      Tracking students has huge negatives for the kids who get mapped into the lower track. No matter how dumb they are, they are generally smart enough to figure out they have been lumped in with TEH STOOOPID, and once that happens, it is only a matter of time before they start living up to your expectations; academic performance goes down significantly.

      When I countered that not tracking impacted the smart kids negatively, he fully conceded the point. And here is where he closed the argument once and for all:

      "These kids are smart. They don't need the help. They're going to turn out fine."

    15. Re:Stop coddling your little genius by Mr.+Slippery · · Score: 1

      it was a rule that kindergarteners could not books out of the school library.

      Obviously that precocious youngster who learned to read so young, never learned how to type or proofread his posts so as to prevent the omission of verbs like "check". D'oh.

      --
      Tom Swiss | the infamous tms | my blog
      You cannot wash away blood with blood
    16. Re:Stop coddling your little genius by Draek · · Score: 1

      Is it any shock that these kids grow up to think the rules don't apply to them?

      The thing is, they don't. One thing few people understand is that "rules" aren't God-given mandates that thou shall follow lest ye be cast into the fiery pits of hell, they're simply social conventions made to facilitate interaction with other people and, if the people around you expect something different from you, there's simply no need to give them more than that. For examples, see 'successful politicians'.

      And if this "Josh" was capable of manipulating his boss into letting him take a dump on the company's lobby, well, who are we to say that he shouldn't? not that I'd do such a thing, but still, that's pretty impressive.

      --
      No problem is insoluble in all conceivable circumstances.
    17. Re:Stop coddling your little genius by Atlantis-Rising · · Score: 1

      Your argument does not make much sense, I do not think: Why should a kid who does not understand and is not good at respect for others and society be taught it?

      Well, the obvious answer is because it's necessary, regardless of whether or not they're good at it. And, to a very large extent, it's true.

      But the same thing applies to team sports. The same things applies to mathematics, and science, and reading and writing.

      The truth of it is, there is really no part of schooling that should be skipped in principle. In practice, often that is not the case.

      When I was in elementary school, there were two streams. Both my brother and I qualified to enter the higher stream; both of us left the program after less than a year. The material was not presented any more cogently, nor, in fact, was it any more 'advanced' in any reasonable sense of the term.

      No. More usually, and in this case, there was simply more of it, thrown at a faster pace. Rather than having to do one worksheet per week as in the regular stream, the 'advanced' students had four worksheets per week. The difficulty, of course, was that if you were to separate students into a stream where they were taught faster than the others, there would be very limited mobility between the streams.

      Once the streams divulged, there would be almost no way to jump 'up' a stream- you could jump down, because the level below you would be behind, but because the level above you would be getting further and further ahead as more time passes, it would be almost impossible to jump into the advanced stream.

      And ultimately, learning to deal with boring and slow material is a good lesson as well. The argument that talented people will end up broken and resentful if they feel they are being 'held back' is silly. As a good friend of mine is fond of repeating:

      'Your circumstances dictate your emotions, but you dictate your circumstances. If you don't enjoy what you are doing, change your circumstances. If you are unwilling to change your circumstances, stop whining.'

      The only people who end up 'broken and resentful' because the system is 'holding them back' are the people who are essentially fragile. Their talents come at a significant price in mental stability, and on the whole those people are often not an asset, they are a liability. They don't need to be coddled; they need to be reforged and tempered.

      --
      "It is possible to commit no errors and still lose. That is not a weakness. That is life." -Peak Performance
    18. Re:Stop coddling your little genius by seebs · · Score: 1

      If this were true, you might have a point. It ain't.

      I was recognized as "highly intelligent and gifted" in school, as a result of which... uh... Well, basically, I got treated pretty badly, the closest I got to "coddling" was that my parents got me into a slightly better school.

      This coddling you speak of doesn't exist. Honestly, I'd have settled for coursework that taught me something more than one day in five.

      --
      My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
    19. Re:Stop coddling your little genius by stevied · · Score: 1

      I guess it depends on your ego. I was pretty smart at math and hard sciences (back in the day - have forgotten most of it now!), got pretty frustrated when I was younger, and really enjoyed it when I got older and was in a class with people of similar ability.

      The flip side, though, is that there was plenty of stuff I wasn't particularly good at: languages and PE in particular. I would much rather have been in a group without all the little polyglots for languages, where we could have taken things slower and been treated a bit more with kid gloves (I went to quite a high-achieving private school and some of teachers could be a bit brutal, in a purely verbal sense of course.) And I wouldn't have minded doing exercise so much if it hadn't been competitive, and I wasn't constantly being verbally abused by some meathead on the sidelines who fancied that he was being "encouraging."

      The real problem is a broad social one of course, and it's a bit of a vicious circle. If the smart, hot-housed kids weren't put under such intense parental / teacher pressure to perform (but were still given opportunities to develop), and weren't picked on by the others, they might not become such narcissists. If the goal of the talented kids was not to earn $$$ and climb to the top of the greasy pole, but rather to contribute back to society, then the less talented might not resent them, and might actually be able to engage to a greater extent in the more sophisticated parts of our culture. Plus the talented kids might feel more like coming back into education as teachers, and contribute to the levelling out of all of the differences in the non-genetic aspects of "talent", which I suspect are at least as important as the genetic ones ..

    20. Re:Stop coddling your little genius by stevied · · Score: 1

      I don't see how teaching people to play team sports is anywhere near as important as teaching citizenship. Society doesn't fall apart just because 5% of the kids don't want to play football, but it just might if 5% grow up to be narcissistic, sociopathic solipsists in charge of the banking system :/

      I agree with you that streaming done as you describe sucks. It should be done per subject, because most people are good something, and few are good at everything. And it should focus more on (sorry, buzz-word coming up) "joined up thinking" and not just storing information and performing exercises faster.

      [..] If you are unwilling to change your circumstances, stop whining.'

      I've heard this quite a lot over the years, and the sort of people it comes from are usually people who have started out with some sort of an edge, either their own talents and drive, or family support / money, or just luck (IME, being born into one of the right generations is a big part of that!) Then they like to pull up the drawbridge behind them, either because they've made themselves comfortable and don't like to think about anybody else, or because they're actually still insecure about their position and don't want the competition.

      Yes, maybe people who end up broken are fragile, but that doesn't mean they couldn't have contributed to society at a pretty sophisticated level if they'd been allowed to quietly specialize rather being repeatedly (metaphorically) beaten. I've been "reforged" (nice analogy BTW), and the process has only made me more convinced that the only way modern civilization has a future is if we can treat the next generation substantially differently. Individualism has its limits: money only has value when there's a stable financial system to spend it in, and pretty sea-side holiday homes will disappear under rising sea levels in just the same way that the slums in Bangladesh do..

  15. simple economics by circletimessquare · · Score: 3, Insightful

    i remember a book from the dot com boom days claiming that a company in san francisco hired a network engineer who stipulated in his contract that he:

    1. would only work in the middle of the night
    2. got to work completely nude

    he got away with it, because it was simple economics: his services were needed badly

    any employee who has quirky behavior that is somehow provocative to fellow employees gets away with their oddball offenses to the extent that their services are needed that badly. beginning and ending of issue. you don't have any power or influence over the guy if he is that valuable. you just don't. so accept his behavior. you can moan all you want, but if you want the guy to disappear or act more uniformly, then just hope for a sudden influx of really good programmers from some magical place. thats the only way his behavior becomes a liability

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:simple economics by TheCarp · · Score: 2, Insightful

      Meh I agree and disagree. I don't think you can put a blanket over all behaviour like that.

      The fact is, most of what we see as normal, is people doing prescribed things because its what everyone else does and whats expected of them. Anyone who has spent a few minutes questioning can see how superficial many of our daily activities are.

      I have seen entirely effective and competent entire teams that don't wear suits or even particularly nice clothes. Tshirts and jeanes. That same group, dark offices, loud music.

      Frankly i think most of what people lable as "eccentric" is just mundane difference. You don't really need people to conform in those ways. You don't need everyone to be a 9 to fiver with a collared shirt...

      what you need is the work to get done, and right, and the docs to be written. You need to make the docs part of the task and not fall for the old "the code is the docs" BS.

      What probably helps the most is integrating such people with others more. More positive social interactions, more work interactions where they can see that other people are important and they contribute.

      Assholes are usually assholes because they don't understand the people they are being assholes too. It comes, often, from judging others by the standards of your own myopic world. "I am the sysadmin, you are an idiot by sysadmin standards, your request makes no sense for a sysadmin".... but you arn't a sysadmin, you are with the helpdesk.

      I think to the studies of what happens in situations of authority (like the prison gaurd experiment), and think this is a lot of the issue... people judging and making decisions for others based on their own requirements. If my requirements and world works best when you are docile and do afraid of me and do as I say.... I treat you accordingly. Hence the "Instant asshole, just add badge" syndrome thats seems so common (at least among younger cops as far as I see)

      -Steve

      --
      "I opened my eyes, and everything went dark again"
    2. Re:simple economics by 91degrees · · Score: 1

      Startups are slightly different. You need to get the product out and generating revenue at high speed.

      I still think you want to avoid the primadonnas but you can be a lot more tolerant of bad behaviour. The net result will be that you need to completely restart everything after your launch, but you can do that. At that point you actually have revenue.

      I guess you'd have to promote the genius to "management" or something so he's still around for maintenance and let the developers refactor as they go.

    3. Re:simple economics by Calithulu · · Score: 1

      ...you can moan all you want, but if you want the guy to disappear or act more uniformly, then just hope for a sudden influx of really good programmers from some magical place...

      India?

  16. Dr. House Syndrome by EastCoastSurfer · · Score: 4, Insightful

    Sounds like Dr. House for developers. People think because they are smart and/or great at their craft they can basically do anything they want. This ties back to the /. article about the younger generation being more narcissistic than ever. Shows like 'House' glorify it and apparently make people think it is okay to be an asshole as long as you get the job done.

    1. Re:Dr. House Syndrome by java+killed+the+dino · · Score: 5, Informative

      Shows like 'House' glorify it and apparently make people think it is okay to be an asshole as long as you get the job done.

      It isn't?

    2. Re:Dr. House Syndrome by Anonymous Coward · · Score: 0

      Well, the hospital knows House is an ahole, puts him on a team with other Doctors that are suppose to contain his aholeness. Real problem is that the management there does a poor job of containment. However their decision to keep him saves how many lives? Which is the right thing to do... now the "correct" business decision would be to fire him. We all wish we could work in a place where the right thing wins over the correct business decision...

    3. Re:Dr. House Syndrome by russotto · · Score: 5, Insightful

      Sounds like Dr. House for developers. People think because they are smart and/or great at their craft they can basically do anything they want.

      Right. And that must be stopped. Because extraordinary results shouldn't result in extraordinary rewards. Genius developers who can solve problems in an hour which could take the rest of your team a month or more should get the same cubicles and be subject to the same strictures as everyone else.

      Sorry, I'm not buying it. It's hard to compensate a quirky genius developer. You can pay them well (and usually have to), but that only goes so far -- they generally aren't like CEOs for whom money is the end rather than a means. Perks like an office rather than a cubicle are perfectly reasonable incentives, and so is "slack". If your genius developer doesn't document his code, a lesser developer can document it in far less time it would take any number of lesser developers to write and document it, or at least one of them isn't worth his salt.

      Spiegel has rigged the question by choosing, embellishing, or inventing out of whole cloth a "quirky developer" who Spiegel claims caused most of the problems he solved and went beyond what any company could tolerate (open sexual harassment). But just because his probably-fictional "Josh" wasn't worth the trouble doesn't mean it's a good idea to treat your best developers like interchangable code-monkeys for whom following procedures is more important than brilliance.

    4. Re:Dr. House Syndrome by Joe+the+Lesser · · Score: 5, Funny

      He may be an ass, but I agree with the parent that if you cure cancer I don't care if walk around shirtless and speak in Klingon.

      --
      "I only speak the truth"
      Karma: null(Mostly affected by an unassigned variable)
    5. Re:Dr. House Syndrome by Registered+Coward+v2 · · Score: 1

      Sounds like Dr. House for developers. People think because they are smart and/or great at their craft they can basically do anything they want. This ties back to the /. article about the younger generation being more narcissistic than ever. Shows like 'House' glorify it and apparently make people think it is okay to be an asshole as long as you get the job done.

      What those people don't realize is as soon as the organization perceives their value is less than their douchbaggery they are curt lose. I've seen it happen, an guess what - the organization survives just fine and the rest of the staff is grateful.

      Very few people truly have the rare talents that lets them get away with such crap for an extended period of time.

      While it is nice to have the genius that can perform wonders; the truth is most organizations can be quite successful with a set of bright, hardworking people who like what they do, are rewarded for good work and treated fairly.

      Despite the stereotypes of managers perpetuated on /., many realize that their role is to help their employees succeed and deliver quality work. The really good ones want people on their team that are the brightest and best (and play nice together or at least fake it well); because that makes their job easier and everyone wins.

      --
      I'm a consultant - I convert gibberish into cash-flow.
    6. Re:Dr. House Syndrome by binary+paladin · · Score: 1

      I don't know that House glorifies it. (Maybe something changed in the last two seasons.) However, I've never noticed that the show portrays him as a terribly happy person or someone you'd want to be.

      However, I'll take an asshole who gets the job done over 95% of the people that have worked in any office I've ever worked in. I don't need to be coddled, I need the job done! It's not necessarily about being narcissistic, it's about trying to do some REAL work and not have to worry about the cover sheet on TPS reports.

    7. Re:Dr. House Syndrome by Anonymous Coward · · Score: 0

      Recently I wound up yelling at my boss, literally, after a 24 hour clean up marathon because the developers took out the production servers by basically ignoring the set policies.

      He pretty much told me that it's people who really believe in their work who are willing to yell when necessary.

      So yeah, I can be a mini House now and then, but it's really tough not to be a jerk when the people around you are morons.

      (I also fixed a server with duct tape 5 mins before a demo that got the company a major contract, that might be part of why they put up with my occasional rant)

    8. Re:Dr. House Syndrome by thhamm · · Score: 1

      Real problem is that the management there does a poor job of containment.
      but the management is cute. dang. rrr cuddy. :P nice legs.

    9. Re:Dr. House Syndrome by ultranova · · Score: 3, Insightful

      Genius developers who can solve problems in an hour which could take the rest of your team a month or more should get the same cubicles and be subject to the same strictures as everyone else.

      Genius developers like that should be employed as designers, not coders. By the time you start writing code, there should be no problems left that take even an afternoon, much less a month, to solve. Besides, to put it bluntly, I sincerely doubt you are more than 160 times more productive than an average developer. Finally, dunno about the article, but the summary didn't talk about someone getting rewarded, it talked about someone going out of his way to be an asshole; and that should never be tolerated, since it will lower everyone's productivity.

      If your genius developer doesn't document his code, a lesser developer can document it in far less time it would take any number of lesser developers to write and document it, or at least one of them isn't worth his salt.

      Except it's more difficult to understand someone else's code than to write it in the first place. This is especially true if the code is "brillant" - meaning it has hacks and abuse of language features that make strong men cry - and even more so if it's actually brilliant, since that means it uses concepts and solutions the lesser developer could never even imagine.

      The smarter the original developer is, the more important it is that he properly documents his code, since it's less likely that your average coder will understand the underlaying idea and be able to produce meaningful documentation.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    10. Re:Dr. House Syndrome by PMuse · · Score: 1

      ...if you cure cancer I don't care if [you] walk around shirtless and speak in Klingon.

      But, you should care. Let's suppose that the guy could, even with his inability to cooperate with anyone, cure cancer. If we could have gotten him to work with others, maybe he could have cured aging.

      Great talent can be hard to coach, particularly because it can do pretty well without cooperation or discipline, but it can do even more with them.

      Have we got a guy who can keep our network from crumbling? Great. But maybe he could be inventing the next bittorrent or HTML if we weren't letting him lose his focus by being a jerk.

      --
      "We reject as false the choice between our safety and our ideals." --The American President (20.1.2009)
    11. Re:Dr. House Syndrome by radtea · · Score: 3, Interesting

      It isn't?

      If you're being an ass, you are not getting the job done. Basic civility is part of any reasonable job description. Generally an implicit one, which people with no social skills are unfortunately too crippled to understand.

      --
      Blasphemy is a human right. Blasphemophobia kills.
    12. Re:Dr. House Syndrome by Maxo-Texas · · Score: 1

      I find cuddy to be infinitely hotter than 13 or Cameron.
      She's just so pneumatic.

      Pistons of a Ferrari, indeed.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    13. Re:Dr. House Syndrome by hal2814 · · Score: 1

      "However their decision to keep him saves how many lives?"

      Their decision to keep House and tie up a staff of 3-4 other doctors will have saved about 110 people by the end of Season 5. That's a rough count. There have been episodes where House saves more than one person and at least two where a lesser team probably might've solved the problem and House's team missed something simple. 110 people in 5 years payrolling a staff of 4-5 of the best and brightest doctors out there. What else could those doctors have been doing in that time (or other doctors being paid from the same funding)? I don't see a contradiction between the "correct business decision" and the "right thing" in House's case.

    14. Re:Dr. House Syndrome by Anonymous Coward · · Score: 0

      I've yet to see an episode where House drops a deuce in the pot plants. Just sayin.

    15. Re:Dr. House Syndrome by Anonymous Coward · · Score: 0

      Extraordinary results shouldn't result in extraordinary rewards. Genius developers who can solve problems in an hour which could take the rest of your team a month or more should get the same cubicles and be subject to the same strictures as everyone else.

      If you advocate for the same for managers (managers should be put in the same cubicles and be subject to the same stricture as everyone else) then at least you're consistent.

      But for some reason I think you're just another hypocrite who can't swallow it that somebody actually *might* do something that is *worth* to get recognized by e.g. giving that guy a bigger room to work in.

      There is a reason good work gets rewarded. The reason is commonly called 'motivation'.

    16. Re:Dr. House Syndrome by stevied · · Score: 1

      It rather depends where you draw the boundaries of "job." Producing genius code is good, but being able to maintain a product long-term is what actually earns the $$$ for the company (in a sane economy.)

      On the subject of House: do you think in real life that the hospital wouldn't simply have been bankrupted by lawsuits years ago?

      Of course, one of the other ideas House conveys is that is possible to manage the mavericks. I would like to think that there are people out there who admire talent and are prepared to put up with (a certain level of) insanity in order be that talent's "interface" to the outside world..

    17. Re:Dr. House Syndrome by java+killed+the+dino · · Score: 0

      If you're being an ass, you are not getting the job done.

      Sometimes you are an ass because other people are incompetent and interfere. So in that case, you're being an ass because other people don't get the job done.

    18. Re:Dr. House Syndrome by thhamm · · Score: 2, Interesting

      I find cuddy to be infinitely hotter than 13 or Cameron.

      absofsckinglutely.

    19. Re:Dr. House Syndrome by TheCarp · · Score: 1

      I dunno.... havn't people been complaining the younger generation is worst than every in every way imaginable since the dawn of language?

      I have personally read accounts over 200 years old of how "young people today just want to stay up all night, listen to loud music, and disrespect their elders"

      -Steve

      --
      "I opened my eyes, and everything went dark again"
    20. Re:Dr. House Syndrome by russotto · · Score: 1

      If you advocate for the same for managers (managers should be put in the same cubicles and be subject to the same stricture as everyone else) then at least you're consistent.

      Can we have a WHOOSH for the AC?

    21. Re:Dr. House Syndrome by riegel · · Score: 1

      If the guy saved you millions then hire a few guys to help document what he did. Remember ... he saved you millions, so there should be some spare money now.

      Uh... Errr... Ohhh... I see... you got a bonus and so did a lot of the management team, and the savings is almost gone now. Ohhh... yeah fire the guy.

      --
      http://p8ste.com - Web based Clipboard
    22. Re:Dr. House Syndrome by Anonymous Coward · · Score: 0

      People tell me I am one of the quirky ones. I guess I am. However plays nice with others does go a long way.

      I started showing people how to fix things. It doesnt take much time. But it is 1000000 times worth it in the long run. If you just swoop in fix it and run off they will ALWAYS be coming to you. If you swoop in and SHOW them how to fix it and make them fix it they learn how. More than likely they will not ask again as they do not need to. Then they start bringing you more and more interesting problems. As they 'solve' the 'easy' ones for themselves.

      'why do you take the time to show everyone how to do your job?'
      'Honestly I am lazy, so I do not have to do it at their whim, I do it at my desk working on my assignments, not in some lab or at a customer site, that is their job I show them how to be more effective at it. Also if they are coming to me because of something in my code I have failed already.'

      I usually show people how to do things. Then when I am done 'show others they need it too, I will be around if you need me'.

      If I can make an army of ME I can write some bad ass stuff... To pull this off you need to play nicely with others...

      Also eventually what will happen is another 'guru' will be hired that is nicer and the prima donna is swept to the side. I have seen it dozens of times.

      You sound like you are one of the 'prima donnas' who think they are better than the others. But I will take someone who can crank code and plays nice with others than someone who gets only can crank code. Its a skill that is learned. Learn it now you will not regret it. Even from the 'morons' you will learn something.

      The quirky dev is probably not an invention. I have worked with my share. Nothing is more interesting than ones who just came out of the armed forces. Talk about INTERESTING quirks...

      If you have 1 guy who 'does all the work' and terrorizes the other 20 and they 'dont get anything done'. Maybe they dont get anything done because the 1 guy is too busy acting like an ass to them. Perhaps you should dig into the matter. It sounds like everyone involved was too chicken shit to ask what the hell is going on. Then when the CEO got involved (wtf right there...) he just ups and disappears?! No big loss there. He wouldnt tell people how to use things that he invented (another wtf). Then would bully them when they asked (another wtf).

      It sounds like he invented a crap system and was moonlighting. This is not that big of a stretch it happens a LOT. Of course he was able to show up and fix something in 20 mins, and it took a couple of days for someone else to look at it. He understood the system and was hording the knowledge of how to do anything in it. This is also common.

    23. Re:Dr. House Syndrome by jollyreaper · · Score: 1

      Shows like 'House' glorify it and apparently make people think it is okay to be an asshole as long as you get the job done.

      It isn't?

      If you're really that good they'll keep you around but be willing to chuck you the first time a viable replacement comes around. Few people like an asshole.

      I think they made up the crapping in the pot story here but the craziest one I ever heard of was a coworker who told me about his pipeline uncle up in Alaska. This guy lived on whiskey and ciggies and had to be drinking his way into an early grave. He was the kind of alcoholic at this point who was fucked up if he wasn't fucked up, would get the shakes and all. But he was the best welder they had, could do the stuff nobody else even wanted to risk. So he got to stay in the cab of the truck and drink his ass off until it was time to do the weld and then he'd come out, do it, then crawl back into the cab for more booze.

      In the situations like this I've personally seen, it's not so much that the asshole in question is the greatest whatever he does ever, it's just that nobody else knows what he does and can't be bothered to learn. Just like you have the petty tyrant situation evolve amongst IT geeks, you get the Glengarry guys who amp it up with the testosterone and freak out. The biggest exception for this is in sales roles where a guy is bringing the company in millions in hard cash and so all manner of behavior is tolerated. He's probably still respectful and polite to his superiors and equals but is a monster to those lower on the ladder.

      The thing I laugh about in these situations is the person whose cache happens to be specialized knowledge useful only to the company they are in. An asshole like a House could presumably work in any hospital he wants but someone whose head is full of institutional knowledge would bring little of value to a new employer. If a petty tyrant like that were to lose his perch, he'd be back to square one.

      From what I've seen, it's inadvisable for companies to tolerate people like this in their ranks but most companies don't operate in a fashion people would be proud to emulate. In most places it seems to be "I know this isn't how we should be doing things but this is the way we are." It could be from a lack of budget, poor leadership, politics, whatever. The thing I would caution anyone about is a towering asshole who has remained at a company for a long, long time probably has protection. Even if he is an asshole, if you get in a fight with him on something, you're likely to be the one coming out with a hurting. Doesn't matter whether you're right or wrong, you're outta there. I saw this very thing happen with a marketing director the owners thought pooped gold. In fact he pooped glowing nuclear waste and contaminated the entire company but the owners were slow on the uptake. People who got into conflicts with the guy got canned. He came into conflict with me but I didn't rise to the bait and did appropriate CYA and IT did not come under his jurisdiction so I was safe until he quit. It was only then that the owners found out about his transuranic turds.

      --
      Kwisatz Haderach
      Sell the spice to CHOAM
      This Mahdi took Shaddam's Throne
    24. Re:Dr. House Syndrome by Joe+the+Lesser · · Score: 1

      I'm not saying he's the ideal, but a flawed genius is sometimes better than no genius. That's why supporting the genius to help him communicate his ideas is also a respectable job, like extracting the nectar from a tricky plant.

      You say he's losing his focus by being a jerk, but it's possible the two are connected. If he had to spend time worrying about what people thought he might be distracted from his real work.

      Obviously this doesn't mean you must always keep your hands off, but more geniuses are crushed than nurtured because they behave differently.

      --
      "I only speak the truth"
      Karma: null(Mostly affected by an unassigned variable)
    25. Re:Dr. House Syndrome by kbielefe · · Score: 1

      I heard that sometimes in a TV season they don't show all 8760 hours of what happens to those characters in a year.

      --
      This space intentionally left blank.
    26. Re:Dr. House Syndrome by khallow · · Score: 1

      Besides, to put it bluntly, I sincerely doubt you are more than 160 times more productive than an average developer.

      There are two things to remember. First, a good programmer can often code more than ten times faster than an average programmer. That's almost half the necessary speed up (logarithm-wise) right there. Then consider that one developer can skip the bureaucracy and communication issues that would ensnare a large team. There is IMHO a huge leverage to a top notch programmer who has awareness and control of a large share of the codebase. I don't see the speed up claim as being unreasonable.

    27. Re:Dr. House Syndrome by iPaul · · Score: 1

      It does you no good to have a genius developer if he's the only person that can work on the code. Just because Josh solves something quickly, how do you know his solution is tested, reliable, or doesn't introduce new bugs? I've worked with Josh types and generally they don't produce quality code. They produce a lot of code and they produce it quickly, with little thought.

      More often than not, once you actually start to look at the code it's rife with other problems. Sure, they fixed the one issue or added that one feature, but they did it at the cost of a some other, perhaps even more serious, issues. Of course, that's once you get past the fact they rely on XYZ undocumented "feature" that got patched, which caused the hack to break 3 months after Josh left, which is why you're now reviewing Josh's code.

      But let's assume Josh wrote good code and everyone else was just too dumb to follow it. From the company's perspective this is almost as bad as not having Josh in the first place. Now, if Josh were to leave, they would face the problem of not being able to maintain their code until they find another Josh. (Who will probably s**t all over the work of the first Josh in order to prove how smart he is.)

      In other words, if you can't play well with others then you are not an asset to the company. Your value to the company is less than someone who, although not as smart, documents their work and explains it to other team members. A "genius" developer like Josh shouldn't have a corner office because you don't merit it any more than the guy who can't code to save his life. Although Josh looks good in the short term, eventually he will become the bottleneck since only he can maintain his own code.

      I've met guys who are insanely productive but almost always can explain what they're doing and why they're doing it. You could step into their code with little or no trouble. Those guys are worth the big bucks because what they do is not a one-off solution or a quick hack. Those are highly productive, high-value engineers. They're also much more rare than often self-appointed hacks that claim to be genius developers. The tough part for companies is to find these guys, reward them, and keep them. Most companies, however, get dazzled by Josh or by Jack (the popular guy that doesn't seem to do any work but everyone likes).

      The sign you have a snake oil salesman like Josh is that once people start to question what they do, they bolt. Once their scam comes due, and it always does, they realize people will start to really evaluate their value. If they bolt early on, while their reputation is still intact, they might be able to continue their scam at the next company.

      --
      Leave the gun, take the cannoli -- Clemenza, The Godfather
    28. Re:Dr. House Syndrome by javilon · · Score: 1

      Genius developers like that should be employed as designers, not coders.

      You seem to work in a big, bureaucratic company, but in my experience, almost every coder I have come across has many design calls to make, at different levels of detail from the ones a typical designer or software architect would.

      So yes, being a good developer makes a big difference and yes, a good developer can be 5 times as productive as a bad developer, so a genius developer can help the company by being a genius developer and not a designer, especially when by designer probably you mean business analyst.

      --


      When his defense asked, "Which computer has Jon Johansen trespassed upon?" the answer was: "His own."
    29. Re:Dr. House Syndrome by Anonymous Coward · · Score: 0

      I have stepped in a few times after a mediocre developer has been banging their head against some problem for a week and most of the time can solve whatever it is in 5-10 minutes and in a couple of hours in the rest of the cases. But part of what makes a great developer great is that they don't just solve the problem, they try to impart enough knowledge that they don't have to deal with the problem again. I don't know (and don't care) about 160 times but I can see how a series of these kinds of thing can add up. See also Joel on Software WRT to "hitting the high notes".

      I can't remember the source, but I remember reading somewhere that one of the big differences between good developers and great developers is that while both solve problems elegantly great developers do so in a way that is easy to understand. Their code is clever, but not overly so, concise, and easy to read. Maybe if you don't understand some basics (e.g. templates) you will have trouble but a competent developer should be able to understand what is going on quickly and perhaps learn something along the way. If what you consider "great code" doesn't have this attribute it isn't.

    30. Re:Dr. House Syndrome by Dragoness+Eclectic · · Score: 1

      *Only* 200 years old? Read the Satires of Juvenal, where he's mocking the deviant behavior of young people those days, during the height of the Roman Empire.

      You can go further back to some Greek whose name I forget who was complaining about long-haired, disrespectful youths back in 400 B.C. or so.

      I think there's some ancient Egyptian texts surviving from the First Intermediate Period where the writer is lamenting how much things suck compared to "the old days" (The Old Kingdom).

      No matter when you are, the old days were better, unless the old days were during the height of the Black Death.

      --
      ---dragoness
    31. Re:Dr. House Syndrome by roman_mir · · Score: 1

      160 seems very high. I calculated on practice however, that in some cases I am as productive as 99 other developers where I am right now. How do I calculate that? Well, if 3 people deliver a project in 6 months, but then they disappear and maintenance is a nightmare, I take a look and write a tool in 4 days that generates that exact project from the list of 162 (similar number here is just an actual coincidence) XSDs and a data model, and now maintenance is easy: a modified XSD or a modified data model is just used to re-generate the entire project in under 2 minutes, well, let's count: 3 x 6 = 18 man months. At 22 days per month that's 396 man days. 396/4 is 99. Ok, so there is also some extra time (another 2 days) for actual documentation (which wasn't there in the original project) and an extra day for ant task generator. Ok, so it's 56 times.

      However considering that 3 people were employed for 6 months, I wouldn't call their work 'stupid', just purposefully inefficient, so I don't really know if I really did that well, however if you don't pay attention to such details, then yes, in our field one person can be dozens, even a hundred times as efficient as the next person.

    32. Re:Dr. House Syndrome by hal2814 · · Score: 1

      No, but it's made pretty plain that these doctors work only on the one or two cases House takes at a time (with the notable exception of Foreman's clinical trial and the occasional clinic duty) and that there are sometimes large gaps between the last patient and the next one where the doctors do little to nothing.

    33. Re:Dr. House Syndrome by dodobh · · Score: 1

      Genius developers like that should be employed as designers, not coders. By the time you start writing code, there should be no problems left that take even an afternoon, much less a month, to solve.

      Except that the code is the design, and wasting time doing too much design upfront is also stupid.

      You need to do some design, write code to validate that design, run it by the users to check that it does what they need, and then repeat the cycle.

      Good code doesn't need much documentation at the code level, but it does need documentation in the interplay of larger parts. An decent developer will be able to convey that level of documentation in minutes to another developer.

      --
      I can throw myself at the ground, and miss.
    34. Re:Dr. House Syndrome by Anonymous Coward · · Score: 0

      Amen

    35. Re:Dr. House Syndrome by deadweight · · Score: 1

      I'd fire House on his second day for sure. The multi-millions in legal expenses and settlements he would cause in a given year would be too much for my budget.

    36. Re:Dr. House Syndrome by Anonymous Coward · · Score: 0

      If the house has more developers on staff, who are not at Josh's level, then they should document his code after he churns it out. The documentation should include purpose and reasoning on how it works.

      That way, they can learn by figuring out what Josh did, and Josh can run ahead and do what needs to be done.

      I've deployed a similar model for programmers working for me and they loved it. If you had less than 1 year of experience working as a programmer and/or in our systems, you were the documenter. You sat in on all design discussions and team meetings, and you documented the code. For the next year or two it was a mixed bag according to the relative skills of the person involved. After 3 years, if they were still in this phase then they fell to the 10% annual turnover policy the company had and were replaced by someone generally fresh out of college. Those who made it to three years and showed proficiency became the teachers, and documentation fell to those lower on the totem pole.

    37. Re:Dr. House Syndrome by seebs · · Score: 1

      Genius developers like that should be employed as designers, not coders. By the time you start writing code, there should be no problems left that take even an afternoon, much less a month, to solve.

      This just ain't so. The notion that everything should be in design and code should be done by interchangeable monkeys doesn't work. It is really popular with people who want a more predictable world, but wishing don't make it so. In the real world, the programming work can be genuinely hard, not because the design is flawed, but because the underlying task requires some amount of coherent thought.

      Your assumption that "brilliant" code is badly-written is unsupported. Brilliant code need not be hard to understand; in fact, it's often simple to understand. What's hard is realizing that there's an easy-to-understand way to do something complicated.

      Basically, it sounds to me like you've either never seen, or never understood, actual genius-level work. It isn't the same stuff, only faster. While the factor of 160 sounds a bit high, there are certainly plenty of cases of brilliant developers being able to trim days or weeks off of project schedules by finding elegant solutions to problems which looked like they would require a long and painful slog.

      --
      My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
    38. Re:Dr. House Syndrome by AchilleTalon · · Score: 1

      I love this one. The bigest assholes are probably those running the companies in first place. See them at work live in Wall Street. What shareholders are asking them is results, no matter how much assholes they are and it pays. Are shareholders assholes as well for asking them to focus on profits alone?

      --
      Achille Talon
      Hop!
    39. Re:Dr. House Syndrome by pla · · Score: 1

      If we could have gotten him to work with others, maybe he could have cured aging.

      A great line of PC BS, but in practice, rarely true.

      History contains almost nothing but one-man miracles. The "team" sweeps the floor and packages the the semiconductor laser as a cool new type of record player, but without the genius, they'd just sweep the floor.

    40. Re:Dr. House Syndrome by Dhalka226 · · Score: 1

      maybe he could be inventing the next bittorrent or HTML if we weren't letting him lose his focus by being a jerk.

      It doesn't seem likely. In fact it may do more harm than good trying.

      In my experience, these jerky genius types rarely go out of their way to be a jerk. Most of the time they're a jerk because people are getting in the way of them accomplishing what they're setting out to accomplish. They're annoyed by somebody constantly coming over to ask what they consider to be a stupid question, or by having to write 100 emails letting 37 managers know what's going on before they can write a line of code. He's not losing his focus by being a jerk; he's being a jerk because he's being forced to lose his focus. For those who are truly more onto the anti-social side, they may be annoyed by or horrendously uncomfortable with just the regular office niceities that most people suck up. (I don't think I'm rude to anybody, but I tend to be uncomfortable with that "small talk" sort of thing too.) They just want to be left alone to do their work.

      If you force these people into a team environment, you're very likely to lose everything good you had and gain nothing in return. He's not likely to stop being a jerk; he's just going to now have a constant stream of "inferior" people he has to tolerate daily. You're institutionalizing the very things that make the person act that way. So he's going to be annoyed and even more jerky, getting even less done than he would have if you just tucked him away in his own little corner of the world and let him go about his business. His co-workers are going to be even less productive than they would ordinarily be because they're going to be delayed by teamwork in general, delayed by his jerkiness and thus obstructionism specifically, and probably affected by the constant exposure to somebody they'd likely rather run away screaming from.

      The specific instance in the summary is retarded; if somebody really is crapping in the lobby, they have severe mental problems and should probably be locked in a therapists office and on disability for the rest of their lives. These people are not tolerable in a workplace regardless of what they do. Harrassing female employees probably isn't either, if for no other reason than the millions he saves your company in development costs can very easily be siphoned away by a single lawsuit by any of those employees. If we're just talking about somebody not being social, I don't consider that a grave sin.

      Now, admittedly, there are some environments where this person simply never works well. Sometimes the things going on are all too collaborative to just let him off on his own to do what he does best, and that's not going to be a company that works for him and thus he's not going to be an employee that works for the company. Absent that, I agree with what somebody else said whole-heartedly: Use a person's strengths. If you have a guy who's a rockstar coder but bad at the social things and documentation, do what you can to keep as much of that as possible off his desk. If somebody works best in teams, put them with teams as much as possible.

      Trying to ram a round peg into a square hole is much more likely to be a great way to shatter them both than it is a method of making a circle square.

    41. Re:Dr. House Syndrome by pugugly · · Score: 1

      I despise that stupid show.
      "House - because people aren't sufficiently programmed to believe smart people are assholes that hold them in contemt!"

      Fuck House. I'm a geek, statistically there are 300 people on the planet smarter than me, and dammit I'm a nice guy that recognizes that being smart is both an important thing and not the only important thing.

      Pug

      --
      An Invisible Entity of Vast Power whose existence must be taken on faith alone: Liberal Media
    42. Re:Dr. House Syndrome by Anonymous Coward · · Score: 0

      First of all, your "efficiency" did not rake in a buttload of cash for the company, their inefficiency did.

      Second of all, they are that much closer to paying off their kids' mortgages than you are, after a shitload of overtime charged to the project.

      Third of all, the "management" who were told what was going on and too afraid & stupid to do anything about it should be lined up and shot in the crotch. This world doesn't need anymore snivelling idiot cowards.

      So stop patting yourself on the back, and start getting wise and charging lots of otime ;)

    43. Re:Dr. House Syndrome by AceofSpades19 · · Score: 1

      Sounds like Dr. House for developers. People think because they are smart and/or great at their craft they can basically do anything they want.

      Right. And that must be stopped. Because extraordinary results shouldn't result in extraordinary rewards. Genius developers who can solve problems in an hour which could take the rest of your team a month or more should get the same cubicles and be subject to the same strictures as everyone else.

      Sorry, I'm not buying it. It's hard to compensate a quirky genius developer. You can pay them well (and usually have to), but that only goes so far -- they generally aren't like CEOs for whom money is the end rather than a means. Perks like an office rather than a cubicle are perfectly reasonable incentives, and so is "slack".

      What the GP means is that just because you are smart doesn't mean you don't have to follow the rules. Sure if you do something thats genius, you should get compensated for it, but that doesn't mean you can do whatever you want, you still have to work hard and show up every day

      If your genius developer doesn't document his code, a lesser developer can document it in far less time it would take any number of lesser developers to write and document it, or at least one of them isn't worth his salt.

      Except when the "lesser-developer" takes a few days just to understand a couple lines of code

    44. Re:Dr. House Syndrome by pla · · Score: 1

      Besides, to put it bluntly, I sincerely doubt you are more than 160 times more productive than an average developer.

      For the most part, we agree. But there, you missed the point.

      You can't measure the true genius coder (which I don't claim myself as, but I've known one) in terms of "x times more productive". They don't (just) churn out code faster, they solve problems in ways no one else would ever even consider.


      Einstein didn't do math "faster" than Maxwell, he made a massive jump in reasoning that made the idea of the "aether" or even a rest frame completely irrelevant.

    45. Re:Dr. House Syndrome by scotch · · Score: 1

      Maybe the don't show every case? I can't believe you actually analysed the business case for this fictional show. Amazing because it's a recurring theme whether it is worth it to keep Dr. House from several perspectives: business, ethical, social, etc. So if you read between the lines and assume the full existence of the universe the show portrays, then your analysis comes up short some how. Based on the logic in your analysis, he's saved 110 people in 110 hours.

      --
      XML causes global warming.
    46. Re:Dr. House Syndrome by SoupIsGoodFood_42 · · Score: 1

      Perhaps you haven't been watching the same show as I have. This point comes up often and the writer seems to be saying that it's not OK and anyone who isn't full of themselves can see that, too. And when it comes to software development, rather than helping to save lives...

    47. Re:Dr. House Syndrome by ultranova · · Score: 1

      You can't measure the true genius coder (which I don't claim myself as, but I've known one) in terms of "x times more productive". They don't (just) churn out code faster, they solve problems in ways no one else would ever even consider.

      That's nice. Do these solutions consistently perform over 160 times better than the solutions made by average programmers? Because unless they do, firing the asshole is still the correct move.

      The thing is, we're talking about justifying keeping an abhorrent human being on staff. Someone who's making everyone else suffer, and thus less productive. The only justification, from a business point of view, is if that evil genius is worth more than the total worth of productivity lost by everyone else. And that pretty much requires comparing his productivity with theirs.

      And then there's the consideration that, being a psychopathic asshole, he certainly wouldn't feel any bangs of conscience selling your trade secrets to your competitors...

      Einstein didn't do math "faster" than Maxwell, he made a massive jump in reasoning that made the idea of the "aether" or even a rest frame completely irrelevant.

      Einstein was a scientist, while a coder is an engineer. Sure, an engineer might come up with a new type of bridge; but unless that makes the company more money, why should that engineer be preferred over any other?

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    48. Re:Dr. House Syndrome by dkf · · Score: 1

      Genius developers like that should be employed as designers, not coders. By the time you start writing code, there should be no problems left that take even an afternoon, much less a month, to solve.

      This just ain't so. The notion that everything should be in design and code should be done by interchangeable monkeys doesn't work. It is really popular with people who want a more predictable world, but wishing don't make it so. In the real world, the programming work can be genuinely hard, not because the design is flawed, but because the underlying task requires some amount of coherent thought.

      Or rather, if it is true, the program is really already written at the design level and what you've got below that is - or ought to be - mechanical translation. I don't normally worry myself over how my compiler works, after all.

      Your assumption that "brilliant" code is badly-written is unsupported. Brilliant code need not be hard to understand; in fact, it's often simple to understand. What's hard is realizing that there's an easy-to-understand way to do something complicated.

      Well, depends on whether you're talking about brilliant code or "brilliant" code. The former makes a tough job trivial and clear and can even change how other people think about the original problem, and it will either be well documented or so clear that it doesn't need it. The latter is what the Joshes of the world produce...

      Basically, it sounds to me like you've either never seen, or never understood, actual genius-level work. It isn't the same stuff, only faster. While the factor of 160 sounds a bit high, there are certainly plenty of cases of brilliant developers being able to trim days or weeks off of project schedules by finding elegant solutions to problems which looked like they would require a long and painful slog.

      The other indicator of real genius-level stuff is that it enables something previously thought impossible or utterly impractical. The first compiler was an example of a genius-level change, no matter how obvious it seems now.

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    49. Re:Dr. House Syndrome by Anonymous Coward · · Score: 0

      Genius developers like that should be employed as designers, not coders.

      I really hate it when people keep making that distinction between designers and coders. You really can't design if you don't code or code if you don't design.

      By the time you start writing code, there should be no problems left that take even an afternoon, much less a month, to solve.

      Easy to say, *very* hard to do, probably even impossible for sufficiently large projects(basically anything produced by software companies). Top-down design never (fully) works. Though designing is important, so is implementing even in the early stages of design. Implementing a design will catch design flaws early on in the process when correcting such mistakes is still relatively cheap.

    50. Re:Dr. House Syndrome by radtea · · Score: 1

      Sometimes you are an ass because other people are incompetent and interfere.

      Sorry, no. You can be bluntly, objectively critical of a co-worker, subordinate or manager without being an ass. I've done it a lot, and it is far more effective than letting your emotions get the better of you, which is something best constrained to /.

      The trick is to stay as objective as possible. "I was not able to get this done because X did not deliver Y by date Z. This has been a persistent problem, and I'd like to discuss with X how we can ensure it happens less often in future, or my schedule estimates will in future reflect these delays, which have now become routine. Here are the data on the promised and actual delivery dates from X in the past six months."

      You'll be amazed at how effective that kind of fact-based response can be.

      --
      Blasphemy is a human right. Blasphemophobia kills.
    51. Re:Dr. House Syndrome by java+killed+the+dino · · Score: 1

      I am never an ass to the people I work with. I'm a really nice guy. And I shower, wear normal clothes, and I don't shit in flower pots. But -- I have been subordinate to people who were assholes, and had quirks. They were some of the best people to work for because they cared more about getting the job done than people's feelings. Because their attitude wasn't just about their ego (though it certainly in part was); it was about motivating their subordinates. They don't put up with incompetence or laziness.

  17. Who asks such a stupid question? by Anonymous Coward · · Score: 0

    Got nothing better to do you grass mud elephant!

  18. Stop generalizing!!! by Anonymous Coward · · Score: 0

    That guy sounds like a douche bag, glad I didn't have to work with him.

    That said, I've worked with many brilliant developers who this persons direct oposite (not including programming skills)

    Don't think everyone is like him, stop generalizing. Its like saying most blondes are stupid...

  19. Classical developer example... by ccguy · · Score: 1

    These stories always make up a developer with a bad attitude.

    Well, you should tolerate such an employee the same you would tolerate him if he was a great salesman than drove everyone else crazy.

    Apparently bad attitude is worse when it comes from a developer, why?

    1. Re:Classical developer example... by Yaur · · Score: 1

      That is an easy one. With a sales person you can draw a direct line between the person with a bad attitude and the dollars they are generating. With a developer the value of putting up with the bad attitude is more abstract. The first line manager might understand the value, but as you move up the food chain you get too people that are increasingly less likely to understand the value add.

    2. Re:Classical developer example... by hypergreatthing · · Score: 1

      Because developers are a dime a dozen!

      Lets get something straight here. Everyone has quirks. You aren't special because you conform less than others. The problem at hand is people being asses. That doesn't stop and end at developers. I would say it's a bigger problem in management and upper management as they can and do get away with anything they want.

      Developers get a bad rap because a lot of them know their personal skills suck. Why do you think they're in front of their monitors all day long instead of talking to people? They also know that they're gifted more than the average person, and that's why they're at a computer instead of doing some other type of work.

  20. Football on Slashdot? by bytethese · · Score: 4, Interesting

    To make an analogy here, he sounds like the TO of coding...

    1. Re:Football on Slashdot? by Anonymous Coward · · Score: 0

      And you've lost many Slashdotters. At least the smug, vocal minority that must tell you at every opportunity that they don't value athletic competition. (Obligatory)

    2. Re:Football on Slashdot? by cffrost · · Score: 1

      Football on Slashdot?

      No.

      --
      Thank you, Edward Snowden.

      "Arguments from authority are worthless." —Carl Sagan
  21. I knew a "Josh" by OzPeter · · Score: 1
    Except his name was Robert, and he was best bud's with the company owner as they had gone to school together.

    One experience I had with him was that Robert (working remotely) broke the system one day which affected my work and when I mentioned this to the owner, rather than him speaking to Robert, the owner went and quietly fixed the issue himself.

    It was things like that that pissed me off and eventually led to me quitting.

    --
    I am Slashdot. Are you Slashdot as well?
    1. Re:I knew a "Josh" by Yaur · · Score: 1

      Was "Robert" a genius or just incompetent with connections to the boss? There is a big difference. If he wasn't willing or able to fix what he broke it sounds more like the latter.

    2. Re:I knew a "Josh" by Anonymous Coward · · Score: 0

      Why didn't you speak directly to Robert?

    3. Re:I knew a "Josh" by OzPeter · · Score: 1

      Because I had dealt with him before and if you attempted any sort of conversation with him and he wasn't interested in talking with you he would just ignore you.

      --
      I am Slashdot. Are you Slashdot as well?
    4. Re:I knew a "Josh" by OzPeter · · Score: 1

      Robert was a one of the smartest people I knew in terms of programming. But it was all about him

      --
      I am Slashdot. Are you Slashdot as well?
  22. right tool by trb · · Score: 5, Insightful

    If you need to cut, there's no tool as good as a sharp knife. If you need to turn a screw, a sharp knife probably isn't the right tool. If you have a guy who's a sharp knife, and you're using him to turn screws, maybe the problem isn't him. Maybe the problem is you.

    1. Re:right tool by Bieeanda · · Score: 1

      Or maybe Josh needs to find himself a nice silverware drawer where he can sparkle.

    2. Re:right tool by Lumpy · · Score: 3, Insightful

      but my knife does not stink, mumble loudly, have action figures cluttering TWO cubicle spaces and refuses to empty that festering experiment of a mini fridge under his desk.

      My knife looks good and does it's job without offending all the other tools.

      --
      Do not look at laser with remaining good eye.
    3. Re:right tool by Burdell · · Score: 2, Funny

      Thanks Bob, Bob. I'll get right on those TPS reports now.

    4. Re:right tool by Anonymous Coward · · Score: 0

      The only time I managed to get my tools to talk to me was after a decent amount of alcohol. Turns out my cable stripper is a total bitch.

      You do make a valid point though, I will give you that. It is one thing to be working so many hours straight and not have the time to go home and clean up. It's another thing entirely when you simply have the time but refuse to take a damned shower.

    5. Re:right tool by Anonymous Coward · · Score: 0

      ...right up until you break your knife because turning screws isn't what it's for.

    6. Re:right tool by Anonymous Coward · · Score: 0

      Yes, we are all tools. We get it.

  23. Amazing by WindBourne · · Score: 2, Interesting

    "Josh" is the kind of guy that develops Googles, Yahoo, etc. This idiot is obviously one of those guys who is jealous of any who show better skills then themselves. That does not mean that "Josh" should not be encouraged to change for the better, but a lot of that is simple maturity. OTH, this poster will never be a better coder.

    --
    I prefer the "u" in honour as it seems to be missing these days.
    1. Re:Amazing by Bieeanda · · Score: 3, Insightful

      "Josh" is the kind of guy who thinks he can develop the next Google, and that the shit he's taking in the lobby planter smells just like the rest of the roses. He's already missed the boat if he's in the workplace and still hasn't figured how to network himself properly.

    2. Re:Amazing by INeededALogin · · Score: 1

      OTH, this poster will never be a better coder.

      Exactly. The poster would be outsourced. Josh would be left as the head of research or something. Regardless... this whole topic is moot because now it is nothing but the anti-Joshs posting against the Joshs. Unfortunately their are a lot more of anti-Josh.

    3. Re:Amazing by AKAImBatman · · Score: 0

      "Josh" is the kind of guy that develops Googles, Yahoo, etc.

      No he's not. I've worked with this type before. The ones who never check in their code (or check it in several versions behind current), are the darlings of management, and appear to get everything done faster than everyone else.

      I personally went head to head with someone like this "Josh", though he was a bit more personable and hygienic than the described individual. Management loved him because they could walk up to his desk, ask him for code, and it would get hacked out in no time flat. Of course, no one could maintain the code except him (it was a mess), the code was not scalable, it was usually the source of most of our problems, and the guy wasn't nearly as smart as he was made out to be. His "gifted abilities" were little more than a matter of controlling the situation well enough to make himself look like a miracle worker.

      Don't get me wrong. Unlike the author of the article, I didn't have any personal issues with the guy. We started in different areas of the company's infrastructure and only came into collision because I was pulling off many of the same miracles, but in a team environment, with good documentation, and with strong communication. At one point our areas of responsibility started to overlap and it became clear who was and who wasn't the team player. Management still felt a lot of loyalty to him, but he began to fall out of favor as my team and I continued to open up our systems and re-architect them for scalability and maintainability.

      This idiot is obviously one of those guys who is jealous of any who show better skills then themselves.

      While I may not agree with your specific statements, I agree with the sentiment. The author generalizes this specific case so much that you have to wonder if he's really run into that many people like "Josh", or if he simply has a problem with people who are good at programming. I can certainly believe the latter, even if it's not intentional on the part of the author. Strong programmers are not all instances of Pigpen, but we're not exactly social mavens either. There are more than enough people who read too much into our social ineptitude and take offense where none is intended.

      I can't speak for everyone in these positions, but I do my best to manage these situations and address the perceived offenses head-on. Sometimes we can come to an understanding and everyone benefits as we move forward. Sometimes we don't.

      I always feel horrible about the latter. I continuously wonder if there's something more I could have done to resolve the situation. As a personal goal, I've continued looking for ways to better reach these individuals. But over time I've come to understand that there are some people who I can not reach out to. They have made up their minds and will continue to take offense, usually to their own detriment. I'm probably not responsible for their inevitable departures, but I still feel it's a personal failure when it happens. :-(

    4. Re:Amazing by Anonymous Coward · · Score: 0

      Amen to that. He's written other posts attacking so-called "genius coders" and it seems to be becoming a hobby for him.

      Where I work, there are a couple of us who are very talented, a couple more who are ok but no great shakes, and several telephone support people who share space with us.

      The phone support types are insanely jealous of our salaries, and don't understand what we do that they cannot. Because they deal with fools all day on the phone, they think they're technical sophisticates. Also, they're taking community college courses at night and are VERY impressed with themselves since they've taken an "intro to SQL" course. One of them was bothering me for a while with quirky little SQL statements, to see if I could figure them out (I got fed up with it, and started telling her "No idea, go away"). Meanwhile, we DBAs and programmers are regularly debugging 10,000 line PL-SQL procedures (trust me, there's a reason for it, but it ain't no picnic).

      I swear, if I never hear another phone jockey whining about my "management salary" it'll be too soon. Why the HELL aren't we on a different floor? With locked doors? And guard dogs?

    5. Re:Amazing by Hozza · · Score: 1

      "Josh" is the kind of guy that develops Googles, Yahoo, etc.

      Because Google runs on undocumented spaghetti code, right?

      Or, alternatively, "Josh" is the kind of guy who wouldn't even get an interview at Google, Yahoo, etc.

    6. Re:Amazing by Anonymous Coward · · Score: 0

      "Josh" is the kind of guy that develops Googles, Yahoo, etc. This idiot is obviously one of those guys who is jealous of any who show better skills then themselves. That does not mean that "Josh" should not be encouraged to change for the better, but a lot of that is simple maturity. OTH, this poster will never be a better coder.

      Are you saying Sergey Brin takes dumps in the lobby flowerpots at Google HQ?

    7. Re:Amazing by nomadic · · Score: 1

      "Josh" is the kind of guy that develops Googles, Yahoo, etc.

      You have no idea if that's true. If the author of the article had mentioned which company "Josh" worked for we could look at the actual work product. It's entirely possible, and more than likely, that "Josh" is just a better-than-average programmer who doesn't have the ability to work at the truly elite developers.

    8. Re:Amazing by mcvos · · Score: 2, Insightful

      "Josh" is the kind of guy that develops Googles, Yahoo, etc.

      No he isn't. Well, I don't know about Yahoo, but Google invests in smart, maintainable code. Josh writes convoluted code that nobody else can maintain, and he's unable to work with others. You can't build a company out of that.

      And there are far better coders out there who write self-documenting code that the other coders, the "average" ones, are able to maintain and fix.

    9. Re:Amazing by mcvos · · Score: 1

      Exactly. The poster would be outsourced. Josh would be left as the head of research or something. Regardless... this whole topic is moot because now it is nothing but the anti-Joshs posting against the Joshs. Unfortunately their are a lot more of anti-Josh.

      Why would you admire an anti-social asshole who only pretends he's a good programmer? I admire quirky genius programmers, but Josh doesn't sound like one of them.

    10. Re:Amazing by jmpareja · · Score: 0

      I totally agree with you. That's the first thing that came to my mind that the poster is just plain jealous that he doesn't have the skills. As for me, when I meet people like 'Josh', I try to learn and better my self. Make this person my bar and realize that even after the many software you have written, I still can learn more.

    11. Re:Amazing by WindBourne · · Score: 1

      want to bet what the ORIGINAL google code that was developed PRIOR TO INVESTORS look like? THink that PRIVATE code from some students was commented, let alone heavily documented?

      --
      I prefer the "u" in honour as it seems to be missing these days.
    12. Re:Amazing by KeithIrwin · · Score: 1

      "Josh" is the kind of guy that develops Googles, Yahoo, etc.

      Umm, no. Unlike the parent, I actually know some of the people who have done big things. Not to name-drop, but I know Joshua Schachter (del.icio.us) and Bram Cohen (BitTorrent). They're nice, friendly, personable people. They have good personal hygiene. They document their code.

      People with poor habits (be they coding habits, hygiene habits, interpersonal relationship habits) rarely get amazing things done no matter how smart they are. So, no, the "Josh" from the story isn't the sort of person who would create the next Yahoo or Google.

    13. Re:Amazing by IntlHarvester · · Score: 1

      You're probably right, but only 1 out of 100,000 academic experiments ever become venture capital-backed firms.

      In my experience, Joshes usually have some largely useless "product" that didn't become the next Google, so they wedged it into a business application where it ends up doing more harm that good.

      In some alternate universe, Sergey Brin is stinking up some small-time consulting firm and everyone is complaining about his buggy homebrew database.

      --
      Business. Numbers. Money. People. Computer World.
  24. team player ? by artg · · Score: 3, Interesting

    It's up to management to apportion work to where it's done best. Some people work well in teams, some better as individuals. Make use of people's strengths and give them the work that suits them. Rudeness is not necessarily an offence (though harrassment of e.g. female coworkers is) - it's just part of the price. If it's not worth the cost, then don't employ him. Similarly with obscure code and prima-donna behaviour: if the overall cost of writing and maintenance is lower when it's all done by easily-managed people, then that's who you should employ. And make sure the same test is applied to the CEO.

    1. Re:team player ? by Anonymous Coward · · Score: 0

      . Rudeness is not necessarily an offence (though harrassment of e.g. female coworkers is)

      Yep, being rude to women is an offence: welcome to women's rights: the majority rule and they are women.

    2. Re:team player ? by Synn · · Score: 1

      Being rude to co-workers on a regular basis is a pretty serious offense IMO.

      It creates a hostile work environment for them and any new employees. That will brain drain your company more than firing a single genius would.

  25. They do exist by Maximum+Prophet · · Score: 5, Interesting

    I worked for a small company that severely underpaid it's employees. As a result, most were people who were just out of college (me), couldn't get a job elsewhere, or didn't want to move because of family connections in the area. Many employees quit right after a spouse graduated from the nearby University.

    One of the programmers was brilliant, but actually insane. He could look over your shoulder and debug the page on your terminal in a few seconds. That is, when his meds were working. He would check himself into the local mental hospital for weeks at time, during which he was truly unavailable. They kept him around because they couldn't afford to hire real programmers.

    --
    All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
    1. Re:They do exist by Quiet_Desperation · · Score: 1

      That is, when his meds were working. He would check himself into the local mental hospital for weeks at time, during which he was truly unavailable. They kept him around because they couldn't afford to hire real programmers.

      Dang, what company was that?

      Are they hiring by any chance?

      Sweet! Meds and weeks of bed rest. Were the nurses at the mental hospital hot?

    2. Re:They do exist by Anonymous Coward · · Score: 0

      Were the nurses at the mental hospital hot?

      I guess, if you like 6'6" guys built like brick shithouses...

    3. Re:They do exist by Anonymous Coward · · Score: 0

      The company is Applied Micro Circuits Corporation. (amcc.com)

      Anonymous for obvious reasons.

    4. Re:They do exist by mdielmann · · Score: 1

      Were the nurses at the mental hospital hot?

      Maybe there were also nursing students. They gotta learn how to do sponge baths somewhere...

      --
      Sure I'm paranoid, but am I paranoid enough?
    5. Re:They do exist by roman_mir · · Score: 1

      Anyone can debug code by looking over the shoulder, it's just not everyone will get it to work as intended.

      Consider that by looking over someone's shoulder you don't get the picture of what the entire thing is supposed to do. Maybe the entire code-base fits on a single screen? Then it shouldn't take a 'genius' to fix it.

      Now if you know already what the code is supposed to do because you are familiar with at least the business case that is being solved (whether it is a device driver or an ordering system, there is some business case there) and you you are looking over someone's shoulder, then I still don't see how you should be a 'genius' programmer to do the fix.

      In yet another scenario, the code on the screen is a common algorithm that really can be understood from a single screen and the person in front of the screen doesn't see the obvious. Then anyone, who fixes the obvious code from behind the shoulder would look like a 'genius', and in reality they just may be a programmer, who is experienced enough, educated enough to do just that.

      Third case (last one, the way I see it), the person in front of a computer is tired. He has no attention left, he is burned out and the problem on the screen is just bloody obvious to anyone behind the shoulder, still no 'genius' here.

      ---

      My point is that any sufficiently educated/experienced/motivated coder could fix something from behind someone's back on a single terminal as long as they understand the context of the problem, otherwise they will be just as useless as the next guy. Also people need rest. 'Genius' programmers? I think most of them are just quick/educated/experienced/motivated. Now, great designers - this is where you really want someone with that extra quirk maybe, as long as their documentation is useful (don't underestimate just how much I am implying in my definition of 'useful').

    6. Re:They do exist by swb · · Score: 1

      Were the nurses at the mental hospital hot?

      I'm sure they are. The bad news is that its a teaching hospital and they use the mental patients to practice urinary tract catheterization.

      "Ooops, I'm sorry, let me try this again..."

    7. Re:They do exist by Anonymous Coward · · Score: 0

      Oh wow, I made it to the slashdot comments section.

      I don't know if you didn't like me, but please understand that I really never meant to be an asshole (mentally ill and asshole are not necessarily concomitant). I'm truly sorry if I pissed you off at any time.

      Generally the check ins weren't weeks at a time. Like in one case I checked myself in and was there for 1 1/2 weeks, but then I ended up being involuntarily brought back for another 2 week stay. And something like only happened on other time on the following year.

      I was also doing my UG degree work at the time while still working and did end up in the psych ward once more.

      If this place you're talking about wasn't upstate NY, well then I'm probably not the same guy. But, I thought it might be possible :)

  26. Anyone can be replaced by iamflimflam1 · · Score: 1

    These myths of one coder being so valuable that he/she can't be replaced are just untrue. When they are gone people either pick up the code they left behind or if it's incomprehensible it gets rewritten. If you really feel as a manager that you have to keep someone on your team who can't play nicely with other people then it's your responsibility to make sure they don't do any damage to the company or their coworkers.

    --
    "Some days even my lucky rocketship underpants don't help."
    1. Re:Anyone can be replaced by mcvos · · Score: 1

      These myths of one coder being so valuable that he/she can't be replaced are just untrue.

      If the one coder is really that good, and the others are crap, then those myths can definitely be true. A single quality programmer who writes maintainable code and shares his knowledge can keep an entire team on track. Someone like that would be worth his weight in gold. Josh from the article doesn't really sound all that good, however.

    2. Re:Anyone can be replaced by Anonymous Coward · · Score: 0

      My thought exactly! The personality traits are believable (if not probably exaggerated, unless this Josh is the perfect storm), but the professional philosophy makes it sound like Josh doesn't understand much about producing software.

  27. management doesn't enable him, they fear him. by DragonTHC · · Score: 1

    The "Josh" you're referring to has management pissing in their pants.

    They let him get away without documenting one program and he'll keep his job forever.

    He purposely obfuscates his work to prevent anyone else from doing it. Management knows he holds the keys and they are scared of him.

    Management doesn't know much about programming.

    On the flip-side, should you really maintain documentation that will make it easier for someone else to do your job? Professionally, yes. But the way employers treat programmers, I'd say Josh was ensuring his job security.

    --
    They're using their grammar skills there.
    1. Re:management doesn't enable him, they fear him. by Pope · · Score: 1

      "Job security" my ass. If he's actually that good, he can go anywhere he wants to. This "Josh" sounds like a thoroughbred prima-donna jackass.

      --
      It doesn't mean much now, it's built for the future.
    2. Re:management doesn't enable him, they fear him. by Maximum+Prophet · · Score: 1

      Perhaps programmers should develop a secure repository of documentation that only the anointed will be allowed to access. If a company does anything to offend the guild, that company would be cut off from any and all documentation related to computers.

      --
      All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
    3. Re:management doesn't enable him, they fear him. by Registered+Coward+v2 · · Score: 1

      The "Josh" you're referring to has management pissing in their pants.

      They let him get away without documenting one program and he'll keep his job forever.

      He purposely obfuscates his work to prevent anyone else from doing it. Management knows he holds the keys and they are scared of him.

      Management doesn't know much about programming.

      On the flip-side, should you really maintain documentation that will make it easier for someone else to do your job? Professionally, yes. But the way employers treat programmers, I'd say Josh was ensuring his job security.

      Maybe, but it also means the first chance they have to fire him they will; and nobody will argue he should be kept.

      If he is in fact harassing other employees they may find it necessary to fire him just to avoid a lawsuit.

      --
      I'm a consultant - I convert gibberish into cash-flow.
    4. Re:management doesn't enable him, they fear him. by Mantrid · · Score: 1

      And we should wear robes, with hoods! And carry staffs...glowy ones (maybe wifi enabled?)

    5. Re:management doesn't enable him, they fear him. by LearnToSpell · · Score: 2, Funny

      I put on my robe and wizard hat.

    6. Re:management doesn't enable him, they fear him. by Nick+Ives · · Score: 1

      I think the point is that he isn't that good, he's an insecure prima donna who knows how to bully people into thinking that he's a genius via crap, undocumented code.

      --
      Nick
  28. Oh, I've met a few of them... by BlueBoxSW.com · · Score: 4, Insightful

    ... but they always seem to self-destruct on their own.

    They either:

    1) Take of too much work because they never know how to balance things, and burn themselves out.

    2) Stop working on needed projects, and only focus on the fun ones, which loses their value in the company

    3) Get Hooked on drugs and/or alchohol, and mess up their own future (MODERATION, people, moderation).

    4) Piss off management by sh!tting one to many times in the lobby.

    5) Get shown-up by some newbie coder who knows less than them, but is willing to learn new things (Josh doesn't like to learn new things, because it would imply that he wasn't a master of everything in the universe).

  29. why is it or by d-r0ck · · Score: 1

    They can be both or neither. It really depends. But they are definitely quirky.

  30. Rent-seeking by Baldrson · · Score: 5, Insightful
    "What documentation?"

    The story ends there. "Josh" is no coding genius. He's a business genius. He understands that business nowadays is all about rent-seeking. Rent-seeking is looking for a parasitic niche from which you can milk the system with impunity, until the system collapses.

    How could anyone learn any other lesson from the goings-on in Washington, D.C. and Wall St. nowadays?

    1. Re:Rent-seeking by Heather+D · · Score: 1

      This is very likely. For every genius there are dozens of two-bit con men.

    2. Re:Rent-seeking by Bocaj · · Score: 1

      I think this comic from user friendly sums it up:
      http://ars.userfriendly.org/cartoons/?id=20010703
      Any developer who's given enough freedom to write undocumented code has the potential to become a "genius" by designing something only he/she can comprehend.

      Even if they truly do produce valuable product, is it worth it? What say you if we have a developer that writes code so fast we could finish multi-billion dollar projects in only weeks instead of years? Only catch is he's a psychopath and we need to secretly provide him with victims and then cover it up. Yes, I'm way over the line, but only to prove the line exists. Where is your company's line?

    3. Re:Rent-seeking by javilon · · Score: 1

      "What documentation?"

      What is funny is that if you remove the personal hygiene references, what this guy is doing is what your regular salespeople and middle management will try to achieve. They will try to get some valuable piece of information that is necessary for the company to run (business contacts, working procedures, whatever) and lock it away so only them control it. At that point they are irreplaceable for the company and they sit down and enjoy an easy job.

      --


      When his defense asked, "Which computer has Jon Johansen trespassed upon?" the answer was: "His own."
    4. Re:Rent-seeking by bar-agent · · Score: 1

      What is funny is that if you remove the personal hygiene references, what this guy is doing is what your regular salespeople and middle management will try to achieve. They will try to get some valuable piece of information that is necessary for the company to run (business contacts, working procedures, whatever) and lock it away so only them control it. At that point they are irreplaceable for the company and they sit down and enjoy an easy job.

      Yes. And I don't approve of them, either.

      I don't know how they get away with it. Why is this sort of thing permitted in sales & management but not in development?

      --
      i'd hit it so hard, if you pulled me out you'd be the king of britain [bash.org]
  31. One sided story by oneiros27 · · Score: 4, Interesting

    I've been pushed hard on projects before -- and been told that documentation wasn't a priority, that getting the code out was. (I had a sign on my wall that said 'Documentation is Phase 2', a direct quote from my manager).

    Now, "Josh" seems like he has some personality issues, sure, but don't bitch about the documentation thing. If anything, I find that documentation can be harmful (if it's not kept updated as the code is), and that it's often best when it's written by someone _other_ than the coder who already knows everything (so they don't bother documenting all of the 'obvious' stuff that's only really obvious to them).

    If this "Josh" were worth the cost of 4+ "normal" programmers, assign someone extra to follow behind his commits and document what's going on. The lack of documentation is a company problem, not just one programmer's.

    --
    Build it, and they will come^Hplain.
    1. Re:One sided story by Anonymous Coward · · Score: 0

      Poor documentation works both ways.

      I was contracting for a company years ago that wanted a bunch of changes right at the end of the contract. This was at a time when we agreed that I would be spending documenting and cleaning up the code and getting ready to pass it off to one of their permanent staff.

      Anyway, no one cared about the documentation when the time came. Despite my protests they wanted new features literally up to the last minute of my work with them.

      So, what happened? Well, I can only assume that they have had lots of problems with the code when they needed to update things, and likely blame me for it. Updated documentation would have helped them. Now, I'm sure they forgot their previous decisions to rush new features in and lay the blame at the feet of the contractor when things aren't clear or the code is "convoluted".

      It's really too bad for me too. There is a potential client that I lost because I trusted that we would stick to our contract. Live and learn...

    2. Re:One sided story by PrescriptionWarning · · Score: 1

      I agree with having a separate person do the documentation, if only because we coders can often write it assuming the audience is ourselves, rather than another person.

      however the one thing that really annoyed me in this case was the lack of writing coherent code and proper use of comments. I tend to write my comments with the knowledge that I'm very likely going to have to tread back in the same code months later and it can take much longer to look through uncommented code to redetermine the function and how to fix/improve it.

    3. Re:One sided story by coaxial · · Score: 1

      You know it really isn't that hard to document code as it's being written. Seriously. Just put four or five lines at the top of the function saying what it does, what it takes, and what it returns. A single line before each "paragraph" of code does wonders.

      Putting it off later not only makes the documentation harder (stale code is hard to read), but all but ensures that it will never happen.

      Honestly, it takes 5 seconds.

    4. Re:One sided story by kimvette · · Score: 1

      How about this? Hold weekly code reviews, and assign one developer to document another developer's code. Devote 10% to 20% of the time to code reviews and documentation and chances are unit testing will improve, lessening the load on QA and you'll actually have a hope of shipping a product with zero fatal defects on time, and only a handful of less severe but noticeable defects. Quality assurance should NOT begin with the QA department, but should be implemented throughout the process, from requirements through deployment and maintenance. The end result is usually actually less costly than the balls-to-the-wall approach and results in repeat customers who will purchase at each upgrade cycle.

      Also, having code documentation in place helps your release engineer produce builds on time because then build failures are more easily fixed at 7:00am by the release engineer without having to wait until the developer rolls in at the crack of noon to find out where the missing parenthesis belongs in your spaghetti code of an algorithm.

      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    5. Re:One sided story by jmpareja · · Score: 0

      Very true. And instead of finding faults of this 'Josh', management should look at themselves because they are part of the problem. I believe in small sub-groups and code ownership in software projects. Only then you can truly have a 'team' in software development.

    6. Re:One sided story by nomadic · · Score: 1

      I've been pushed hard on projects before -- and been told that documentation wasn't a priority, that getting the code out was. (I had a sign on my wall that said 'Documentation is Phase 2', a direct quote from my manager).

      But "Josh" seems to have decided on the no documentation idea himself. Which means he isn't really doing his job.

    7. Re:One sided story by Anonymous Coward · · Score: 0

      Bonus: the follow-behind documenter is also secretly in training to become the quirky asshole's replacement.

  32. Wrong choice of words by vlm · · Score: 3, Insightful

    What a piece of journalism.

    Quirky = rare habits and/or rare hobbies and/or rare background/culture that bring a smile to co workers faces or make them interesting to talk to, at least compared to an average drone.

    vs

    guy in the article = a-hole that everyone hates but has the redeeming characteristic of being somewhat productive (at the cost of ruining everyone elses productivity)

    --
    "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
  33. Digital Equipment Company by Maximum+Prophet · · Score: 1

    The head of DEC, Ken Olson, has been famously quoted as saying, "We don't have any geniuses at DEC." Where are they now?

    --
    All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
    1. Re:Digital Equipment Company by Anonymous Coward · · Score: 0

      The head of DEC, Ken Olson, has been famously quoted as saying, "We don't have any geniuses at DEC." Where are they now?

      The same place as Netscape.

    2. Re:Digital Equipment Company by Lilith's+Heart-shape · · Score: 1

      Isn't that the same guy who thought that UNIX was nothing but snake oil? I guess there weren't any geniuses in DEC's management.

  34. Work from home by jlebrech · · Score: 2, Interesting

    wouldn't he be more producetive if he worked from home?

    You now have a performance benchmark, due to him having previous work done in the office.

    1. Re:Work from home by DaveV1.0 · · Score: 1

      He might be more productive, but what about the people who have to work with and maintain his undocumented spaghetti code?

      --
      There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  35. Weighed in the balance. by LaminatorX · · Score: 1

    Everone should be evaluated in terms of (benefit to the company)-(hassle to deal with+cost of employment+replacement costs). If the result is positive, stay the course. If negative, cut your losses. If borderline, try to work with the person to push towards posative.

  36. Troll by oldhack · · Score: 0, Troll

    The dude's an ass, like Taco pulling this troll, not "quirky" - look up the bloody dictionary sometime.

    --
    Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
    1. Re:Troll by oldhack · · Score: 1

      Whoever modded me troll, maybe I was being "quirky". Did you ever think of that? Bloody illiterate.

      --
      Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
  37. Not likely to change by JerryLove · · Score: 1

    Successful salesmen and executives get the same treatement (better?)

  38. Perhaps both, or perhaps not... by Millennium · · Score: 1

    The quirky developers tend to be brilliant: it's how they get hired.

    Are they dangerous? That depends on a lot of factors. Most, frankly, are not; the quirks are minor, harmless affairs that can and probably should be overlooked, especially if they do not violate any company policies. Happy coders are better coders.

    Dangerous coders do exist, however, just like in any other profession, and it sounds like the article's Josh is one of them. It's tough to argue with his code, but his other behaviors are causing a lot of harm and risking even worse. This is a point where stepping in would be appropriate.

  39. At first I agreed... by Shads · · Score: 1

    I kinda agreed about Josh when I read the article... then I read some of this guys other stuff, about Tyler, and a few of his other articles.

    Basically it boils down to he wants cogs in a machine at any cost.

    Being different is fine, being a complete and total douche like Josh, no. Josh needed to revise his attitude and this guys needs to revise his also, unthinking cogs are useful in some situations, original thinkers are useful in some situations also.

    --
    Shadus
    1. Re:At first I agreed... by mcvos · · Score: 1

      I kinda agreed about Josh when I read the article... then I read some of this guys other stuff, about Tyler, and a few of his other articles.

      Basically it boils down to he wants cogs in a machine at any cost.

      I also read the Tyler article, and that's not quite what happened there. He didn't want Tyler to be a cog, he wanted him to be a mentor, a guru perhaps. Lift the others up instead of putting them down, which is what Tyler had been doing before.

      A genius programmer who can't work with others isn't anywhere near as valuable as one who can.

  40. Dangerous to MANAGEMENT by redelm · · Score: 1
    Yes, talent is dangerous. Often to itself, but that is a different question. But all talent is challenging to everyone who works with it. Most challenging to management who have the responsibility and duty of managing it, and most specifically for covering and backfilling gaps.

    You see, the matter is _NOT_ to complain of what the talent is missing, but to be grateful for what it provides and to identify and try to backfill the missing areas.

    Glass half empty? Or half-full?

    Most unfortunately many managers are there because the want to be. That is, they enjoy the power and do not see the responsibility. Often they simply cannot understand people who are not like them. A singular disqualification for anyone who pretends to manage others.

  41. Well, most blondes are stupid by Anonymous Coward · · Score: 0

    Male and female (et al.) It's a genetic thing that persists because, obviously, people like screwing blondes.

    1. Re:Well, most blondes are stupid by Anonymous Coward · · Score: 0

      Funny I must have been left out that loop... Blonde: Check. Screw much: Not so check

    2. Re:Well, most blondes are stupid by Anonymous Coward · · Score: 0

      Oh Man, you are missing out then... I love being blonde :P

  42. Do you need these people? by Yaur · · Score: 1
    Most of the development superstars that I've worked with all have their eccentricities... some of which are irritating and some of which aren't. My belief is that most mediocre developers have to get rid of these to stay employed, but the best don't.

    If you are building something new and innovative you need them and have to work around their quirks if you want to keep them. There are obviously limits, though it doesn't sound like you are the one that gets to set them. Where those limits are depends on the project and how badly it needs star developers.

  43. Too many ideas by Kupfernigk · · Score: 1
    I suspect one reason some of these people are difficult is simply that they have a big brain which makes lots of connections and has lots of ideas, but have to apply it in a very narrow field. Perhaps the quirkiness is partly due to outlying areas of the brain (whole hemispheres?) having nothing to do all day, just like dogs get destructive when they are bored.

    I'm putting this forward partly because I know my own boredom threshold is close to zero, but I've been lucky enough to have a portmanteau career - hardware, software, some metallurgy and a ten year spell in management. As a result, I've never got to the top in anything, but I've only twice been bored for very long (and both times I did, I changed jobs.)

    The antisocial stuff is a different matter. A lot of (mainly men) get like that when they feel in a position of power. Our own lovely Tony Blair apparently liked to demonstrate his power over civil servants by having meetings with them dressed only in his underpants - look at me, I can go around like this but you have to wear a suit. Other alpha males just like to scream and thump their chests at people while hurling excrement at them, and I believe some non-human primates do this as well.

    As a counter example, look at Richard Feynman, who was interested in all kinds of things and had a very varied career. He did quirky things but in a nice way, asuch as giving evidence in court that all kinds of "respectable" people frequented topless bars, because he didn't care that people knew that he did, or exposing the poor security at Los Alamos diplomatically by safebreaking. Robert Oppenheimer too had a very wide variety of interests, which probably helped him retain his sanity when he was persecuted by Strauss and the McCarthyites. Oppenheimer was also tolerant of diversity as a manager, which helped even if it annoyed the military.

    So, my 2c worth; what these people need may be to be included, but to be encouraged to widen their interests.

    --
    From scarped cliff or quarried stone she cries "A thousand types are gone, I care for nothing, no not one."
    1. Re:Too many ideas by CFTM · · Score: 1

      The very process of creation requires absolute freedom and a safe environment where colossus mistakes can be made.

      It is not a big brain thing, it's a creative process thing.

      And coding done at the highest level, is like any creative art form.

    2. Re:Too many ideas by johndoejersey · · Score: 1

      Tony Blair apparently liked to demonstrate his power over civil servants by having meetings with them dressed only in his underpants

      WTF?
      Source?

  44. Josh the lone IU by pohl · · Score: 3, Interesting

    Since the article was written from the perspective of someone who is upset with Josh, and therefore prone to paint him in a negative light, I'd like to offer some words that may balance the perspective. I'm no fan of people like Josh, so the following is the devil's advocate perspective:

    By way of metaphor, it seems like Josh is the only Integer Unit in a CPU burdened with processing lots of integer-heavy code. He is a resource for which there is a lot of contention. Someone tried to have someone else on the team (say a floating point unit) solve an integer problem, and all they could muster was to go to the Integer Unit, who is already bogged down, and beg for help. Apparently, in this organization, Integer arithmetic is deep voodoo that nobody else can do. Everything flows through Josh. The odds that someone will relieve him of his duties long enough to generate a HowTo on adding two ints are pretty small.

    Odds are that the project managers around him aren't thinking in terms of resource contention and how to alleviate it. They may make noises that sound like they understand that task B, with a lower priority than task A, will be starved until A is completed - but then tomorrow they'll still be asking why B isn't done, knowing full well that A is still in queue and they set the priorities themselves.

    Even if they do understand priorities, they'll probably constantly adjust priorities eating Josh's productivity with lots of context switching and pipeline stalls.

    They need more people who can do what Josh can do. Once he's no longer the only Integer Unit, he won't be able to afford to be a douche-nozzle. If this outcome is worth it to them, they'll pay for it. If it isn't, they'll whine in an editorial.

    --

    The "cue the foo posts in 3, 2, 1..." posts will commence with no subsequent foo posts in 3, 2, 1...

    1. Re:Josh the lone IU by DaveV1.0 · · Score: 1

      No. Josh is an arrogant asshole and used his ability and position to prevent to protect himself from the consequences of his behavior and attitude.

      The Joshes of the world need to be fired until they learn the world does not revolve around them and that working with others is a good thing.

      --
      There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
    2. Re:Josh the lone IU by pohl · · Score: 1

      I agree with "Josh is an arrogant assole" and "the Joshes of the world need to be fired".

      I'm not sure I understand the "No," however, because none of that seems to contradict anything I wrote.

      --

      The "cue the foo posts in 3, 2, 1..." posts will commence with no subsequent foo posts in 3, 2, 1...

    3. Re:Josh the lone IU by internerdj · · Score: 1

      From reading the article looks like the company needs 3 or 4 Joshes because Josh is overloaded. If the company actually hired 3 or 4 Joshes then Josh wouldn't be so mission critical and they could fire him for sexual harassment or not showing for work. Now the existing Josh should be fired no doubt for being a bad employee, but your typical company won't hire a group at Josh's level because they can pile 400 hours of work a week on Josh and leave the rest for the interns. Alternatively they could hire a much larger group of developers to replace Josh (who will dress in ties and won't demand the office space which should rightfully be given to the deserving managers who can't even handle such a large problem as Josh) and redo Josh's code next time in breaks, but then again that's expensive.

    4. Re:Josh the lone IU by Speare · · Score: 1

      By way of metaphor, it seems like Josh is the only Integer Unit in a CPU burdened with processing lots of integer-heavy code.

      Sorry, I didn't understand what you said there. Can you explain interoffice politics in terms of a carburetor, windshield washer pump, or an overhead cam?

      --
      [ .sig file not found ]
    5. Re:Josh the lone IU by Anonymous Coward · · Score: 0

      You swing a mighty pair, Sir. That's announcing, in the Pittsburgh Steelers' locker room, that you need football explained in terms of badminton.

    6. Re:Josh the lone IU by colinrichardday · · Score: 1

      Your analogy might be better if you made Josh the only floating-point unit, as floating point is generally harder than integer.

    7. Re:Josh the lone IU by pohl · · Score: 1

      Yeah, I kicked myself a bit shortly after submitting.

      --

      The "cue the foo posts in 3, 2, 1..." posts will commence with no subsequent foo posts in 3, 2, 1...

  45. You're talking about Linus, right? by meist3r · · Score: 1

    I'm a big Linux fan and I appreciate the man's work on the Kernel and git but his antics sometimes let the asshole part of him slip out a bit too far. Confidence makes you cocky if there is no one to restrain you ever.

    Back to "Josh":
    A douchebag like that will take the entire project down with him once he snaps. No documentation and an attitude that would prevent proper inheritable code writing from the onset makes this a bad deal. Basically I'd guess they're useful if kept in check, reaally dangerous when you let them do whatever. Much like nuclear power plants really.

    1. Re:You're talking about Linus, right? by riegel · · Score: 1

      I always laugh when people criticize Linus Torvalds, or unmentioned so far Dan Bernstein, or other brilliant individuals.

      Then they proceed as if we are to accept these criticisms as somehow authoritative without any evidence to back it up.

      And when you challenge them for evidence it usually goes along these lines.

      1. Someone pointed out an error in [arrogant person's] code.
      2. I thought [arrogant person's] response was arrogant.
      3. Turns out [arrogant person's] was right but I still think [arrogant person's] is arrogant.

      I would respectfully submit that meist3r and the like are demonstrating the very thing they are accusing others of having

      And then you people like Reiser get a pass, when we have compelling evidence of their arrogance.

      --
      http://p8ste.com - Web based Clipboard
    2. Re:You're talking about Linus, right? by riegel · · Score: 1

      oops, above should have said...

      And then you HAVE people like Reiser WHO get a pass, when we have compelling evidence of their arrogance.

      --
      http://p8ste.com - Web based Clipboard
    3. Re:You're talking about Linus, right? by meist3r · · Score: 1

      I don't have a single clue what you are on about but watch the talk Linus gave for Google about git:
      http://www.youtube.com/watch?v=4XpnKHJAok8

      If that doesn't demonstrate arrogance or douchebaggery for you then I don't know what you'd call arrogant. How would you categorize me for arrogant after reading one single post of which you ignored all of the important bits? Like I said I admire the guys work but there's a difference between being good and being a dick about it.

    4. Re:You're talking about Linus, right? by Anonymous Coward · · Score: 0

      I'm a big Linux fan and I appreciate the man's work on the Kernel and git but his antics sometimes let the asshole part of him slip out a bit too far. Confidence makes yo

      Maybe Theo "The Rat".

      In the big scheme of things Linus the gold standard of Open Source project management. The flaming is just part of the act.

    5. Re:You're talking about Linus, right? by JohnFluxx · · Score: 1

      Heh, all it demonstrates is that you have no sense of humour. He's funny and take friendly jabs at the svn developers.

    6. Re:You're talking about Linus, right? by meist3r · · Score: 1

      Heh, all it demonstrates is that you have no sense of humour.

      Yeah right, you know me pal. Because it's me who's defending a programmer dude that was just wayyy to cocky at that talk. Friendly jabs end after the third time. Making a joke is one thing, rubbing it in something else. One is funny, the other just isn't. I have no reason to defend cvs or svn at any point. Neither do I have reason to advertise git. I use all of them now and again with mixed results across the board. The way he was constantly being a bitch about everything else sucks and only he and his genius web of trust friends can audit proper code was just ... well ... cocky. There's a fine line between talent and obnoxious arrogance and he clearly tread over it this time.

      Good thing though your definition of humor derived from my single post nobody read 'til the end is the penultimate truth. HarrHarr

    7. Re:You're talking about Linus, right? by JohnFluxx · · Score: 1

      Hum, I watched it again. I'd watched it ages ago when he first did the talk. I'd forgotten just how bad it was.

      I agree that he was really quite an ass in the video, although I hope that it was just a bad judgement call and regrets it now.

  46. Like a former boss said: by dargaud · · Score: 1
    "Whenever you think of a clever programming trick... forget it !"

    And I see his point: other people will need to maintain the code afterwards.

    --
    Non-Linux Penguins ?
    1. Re:Like a former boss said: by mark-t · · Score: 2, Insightful

      There's nothing wrong with clever programming tricks, as long as they are documented so that other people can understand them.

  47. no longer acceptable by Anonymous Coward · · Score: 0

    These so called brilliant people are more of a liability than a benefit. Sure, they can do in one hour
    what teams takes days to, but at what cost?

    Inappropriate behavior with female colleagues == sexual harassment suit

    Too much access == segegation of duties issues (your internal/external audit functions will haunt you with this)

    The "what happens if he gets hit by a bus" scenario
    Lack of standardization: sorry, Josh likes to use XYZ for his development environment, because he says it's better,
    so he's not using a standard environment. What do you do when he decides he's had enough and quits? Who will
    be able to continue working on the mental-diarrhea left behind?

    Is there a wonder why these folks tend to gravitate more and more towards job based consulting gigs and are more and more moving away from the corporate standard?

    No documentation? Are you kidding me? This in the day of ITIL, CobiT, best practices, post-Enron/9-11/Sarbanes-Oxley/Compliance-gone-mad era? Are you fucking shitting me? No documentation? The cowboy days of the early 1990s -- editing a live binary running in memory on production systems during prime time -- are LONG gone.

    Time to adapt.

    If you don't, get the hell out, you are a problem waiting to happen.

  48. prima donna by Jodka · · Score: 1

    prima donna - noun 1. the chief female singer in an opera or opera company 2. a very temperamental person with an inflated view of their own talent or importance.

    --
    Ceci n'est pas une signature.
  49. Rings a bell... by CFBMoo1 · · Score: 1

    And reminds me of what happened at my first job, though the guy from my experience wasn't that bad. He still did indicate to me one day that the code was the documentation. The good thing was he was more helpful with me figuring it out.

    --
    ~~ Behold the flying cow with a rail gun! ~~
  50. Trust? by ZenDragon · · Score: 1

    The problem with these types of people is not so much their own problem but a management problem. Entrusting too much to any one person is dangerous. Proper project management would componentize the workload and have this "quirky" guy working on one small component at a time, you NEVER trust a guy like this with the entire project. These people have a useful skill, but its up to management to utilize that skill in a manner that is conducive to the goals of the company as a whole. If you (as management) have a guy like this running lose in your office deficating in flower pots, and insulting the women because he thinks he is irreplacable: it is YOUR problem, and your responsibility to keep him in check if you feel he is a valuable asset to the company. If you cant rope this guy back in remember rule number one of IT; there is ALWAYS somebody smarter out there somewhere. If you want a master coder with social skills be prepared to cough up the big bucks, otherwise deal with the smelly garage coder with some common sense as a manager.

  51. breaking a lance by e**(i+pi)-1 · · Score: 1

    An innovative company probably needs both: quirky people with unconventional work habits but who have ideas and can break a lance. If they are not particularly good at documenting things, it should be easy to have this done by others who are good at learning, absorbing, cleaning and improving a good idea.

  52. Not worth it by squoozer · · Score: 3, Informative

    I started on the software coal fact many years ago and have slowly worked my way up to the point where I now employ programmers and right from day one I've found the Josh type developer to be nothing but a pain in the neck and generally not worth it. They might be great developers but in my team (at least) that alone is not good enough. I need people that can communicate and get on with others as well. I need people that I can take to customers occasionally. In my experience Josh types are also loose cannons that can't be trusted to do what they are asked to do, they go off mission because they think they know better. Unfortunately they rarely do see the whole picture and end up causing problems further down the road.

    My view of this type of programmer is probably rather skewed because one of them actually managed to bankrupt a company I was working for by promising far more than he could actually deliver. Management just kept lapping up the promises despite warnings right up to the end when they noticed how much they had spent and what they actually had got in return.

    --
    I used to have a better sig but it broke.
    1. Re:Not worth it by riegel · · Score: 1

      My view of this type of programmer is probably rather skewed because one of them actually managed to bankrupt a company I was working for...

      Probably is as the posted indicated this Josh saved them millions

      Depending on the size of the company millions may have different hues, but in my book thats a lot.

      --
      http://p8ste.com - Web based Clipboard
    2. Re:Not worth it by squoozer · · Score: 1

      I'm guessing that sometimes it works out and sometimes it doesn't. I've seen it go wrong a lot more than I've seen it go right hence my opinion that they are probably not worth it. I'd take a team of moderate, well adjusted, programmers over a maverick and a bunch of brow-beaten devs any day.

      --
      I used to have a better sig but it broke.
  53. Not nice? by mgf64 · · Score: 1

    Maybe he had red Do Nice Engineers Finish Last in Tough Times? by the same author http://itmanagement.earthweb.com/features/article.php/3796861/Do-Nice-Engineers-Finish-Last-in-Tough-Times.htm and chose not to be too nice, uh?

  54. Sucking Productivity from Other Coders by dcollins · · Score: 4, Interesting

    The couple of "hero" coders like this I've seen in the past are, to a large degree, sucking productivity directly from other coders. Their complete lack of documentation, zero time spent naming variables/functions with whatever gobbledygook ran through their head momentarily, etc., winds up bringing other coders' work to a complete screeching halt. Intentionally or unintentionally, they arrange it so they're the only person who can manipulate the codebase. So the whole "hero worth millions" idea is really just a facade.

    Example from this month's Game Developer Magazine: Near the end of a production cycle, one game is way over memory budget. Entire staff (engineers, artists) spend weeks cutting stuff out: reducing polygons on models, downgrading textures, etc. Everyone sweats it out and comes up 1.5 MB short. On the last day a senior coder goes in to where he'd hidden a 2MB string allocation at project start (completely unused), snips out the one line, and is hailed by everyone as having "saved" the project at the last minute. That's the kind of bullshit going on with these sociopath coders.

    --
    We know where leadership by an anti-intellectual "strongman" who scapegoats minorities and likes boisterous rallies goes
    1. Re:Sucking Productivity from Other Coders by Orion+Blastar · · Score: 1

      Agreed, this happened to me a few places that I worked at. Not only did I have to do my work, but the work of three other coders to fix their messes. The extra stress made me sick and I developed schizoaffective disorder and got too sick to work. Therefore; I have been out of work since 2002 due to disabilities like high blood pressure (I had a few mini-strokes) that damaged my stomach and colon and put me on short-term disability. When I returned all of my doctors' notes got lost and I was put on probation, and then two weeks later fired because I got so sick I threw up into a trashcan and it bothered my coworkers to hear me throw up. So I was fired on the spot.

      --
      Remember, Slashdot does not have a -1 disagree moderation, and no, troll, flamebait, and overrated are not substitutes.
    2. Re:Sucking Productivity from Other Coders by Reziac · · Score: 1

      Makes you wonder what else Senior Coder had hidden in the project, don't it??

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    3. Re:Sucking Productivity from Other Coders by seebs · · Score: 1

      So you're saying you can't tell real geniuses from fake ones?

      Sorry, but I don't buy it. The "hero" programmers I've seen make other programmers more productive. If they aren't doing that, they're obviously not really "hero" programmers, they're just talking a lot.

      I certainly wrote unmaintainable code back when I was in college. These days, the stuff I produce is mostly intended to be fairly simple and clearly documented. It's not 100% simple-and-self-documenting, but if I do anything remotely tricky, I explain what it is, how it works, and why it's a good fit for the problem. I'm still fast. :)

      --
      My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
  55. The company needs to grow some balls.... by mark-t · · Score: 1

    ... and fire the guy for not documenting his code. Most companies have documentation standards in their policies... not following company policy is actually a quite reasonable reason to be fired, even where I live and I don't even live in a an "at-will" jurisdiction.

  56. I had a "House" ENT do my sinus surgery by Anonymous Coward · · Score: 0

    he was a royal 1st-class pr1ck who (among other things) cussed me out after I coughed up blood when he took the packing out (evidently I was supposed to "swallow" - not going there...). almost six yrs later I'm still night & day better so while his behavior was extremely unprofessional putting up w/him for a few post-op visits was a small price to pay for the outcome...

    1. Re:I had a "House" ENT do my sinus surgery by java+killed+the+dino · · Score: 1

      I actually had the same thing happen. I had sinus problems - severe pain - for years, went through several doctors. My last ENT was a dick and had me in and out of surgery one week after my first appointment. I haven't had any problems since. I'd much rather have someone who gets the job done than someone who is tactful.

    2. Re:I had a "House" ENT do my sinus surgery by kbielefe · · Score: 1

      I'd much rather have someone who gets the job done than someone who is tactful.

      False choice, people. The vast, vast majority of competent doctors I know (and I know a lot) are both effective and tactful. If a doctor like that told me I needed surgery, I would fire him and shop around for a well-mannered surgeon.

      --
      This space intentionally left blank.
    3. Re:I had a "House" ENT do my sinus surgery by java+killed+the+dino · · Score: 1

      "I'd rather" does not imply mutual exclusivity. Allow me to rephrase: Given the choice, I would prefer someone who gets the job done over someone who is tactful. My last ENT was exclusively the former, and the others (as far as I am concerned) were exclusively the latter.

      It isn't mutually exclusive for developers either, but given the choice, I think getting the job done should be more highly regarded.

    4. Re:I had a "House" ENT do my sinus surgery by LihTox · · Score: 1

      Let's put it this way, then: we've got this guy who's a jerk, but who is also highly skilled in medicine. Can we really afford to not use his brain, to tell him to go home and twiddle his thumbs because he's just not nice enough? It's not like we have a glut of geniuses; sure there are nice brilliant people, but they can only handle so many cases.

    5. Re:I had a "House" ENT do my sinus surgery by kbielefe · · Score: 1

      You're acting like how one behaves towards others is set in stone. Geniuses are more than capable of pretending to be nice.

      --
      This space intentionally left blank.
    6. Re:I had a "House" ENT do my sinus surgery by LihTox · · Score: 1

      It's impossible to know just how difficult it is for any given person to change their behavior: for some people, pretending to be nice might require constant concentration and render them unable to do anything else. Who can say?

      There's probably a happy medium: smack the guy down for really over-the-top behavior, and ignore the snide comments etc.

  57. Managers Job by edivad · · Score: 2, Insightful

    It's managers job to give the right amount of freedom to talented individuals. Individuals with well over the average IQ, with passion for the job, and that are no afraid to spend extra hours on the task. If it were for me, I'd give up ten of the 9-to-5, dumb, lazy a$$es, weasels, that are unfortunately the fabric of most of US companies, for one talented engineer. You wonder and cry because he has extra privileges than you? Meritocracy, comes not only in form of extra salary, my friend.

  58. Saved the company millions by slim · · Score: 1

    If, as the summary says, this guy churns out code that 'saves the company millions', that seems to justify what he does.

    To offset that, you've got to demonstrate that his deficiencies cost the company millions. Lack of documentation; personal abuse in the workplace; those mount up.

    He probably doesn't save millions after all.

    1. Re:saved the company millions by swordgeek · · Score: 1

      No. No no no no no!

      Perks for good staff? Yes. Quirks? Sure. Kid gloves and tolerance of anti-social behaviour? No. Behave like a reasonable adult, or get the hell out of my company! I don't care if you're the best programmer on planet earth--if you can't work with others, you should be working for yourself, in a yurt in outer Mongolia, and not bothering the rest of the world with your crappy attitude.

      In short, juvenile delinquents shouldn't be employed. Hire grown-ups.

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
    2. Re:Saved the company millions by E.+Edward+Grey · · Score: 1

      Mod parent up! The "Josh"es of the world aren't saving anyone money if the company is spending money to fix the problems he creates.

      Switch him to design work. If he's such a genius, he can easily envision what's to be done architecturally and transmit that vision to coders. If he can't do that, then his career is at a brick wall anyway.

      --

      ---don't make me break out my red pen.

  59. Quirky developers by youngdev · · Score: 0

    In the case presented (which seems extreme even for the cowboy coding shops I have been in), "josh" is not as dangerous the manager who tolerates such behavior. A good manager recognizes brilliance and will allocate certain liberties based on productivity. There will be a point though where sexual harassment lawsuits eat up and profits gained by productivity at which point a good manager will say "It is cheaper to get 2 mediocre programmers who are reliable and polite that deal with another one of this asshole's liabilities." I mean, we are not talking about linus torvalds here. It's some asshole named "josh". On the other hand, antisocial talent can usually picked up pretty cheap if they have a reputation. Then the question becomes "Am I desperate enough to babysit this egomaniac or would I be better off with a X% loss in productivity in exchange for a smooth running work place?"

  60. Brilliant & Dangerous - Use it to your advanta by ashraya · · Score: 1

    15 years back, When I was younger, I would have probably fallen into that category. However, I had an ingenious manager who turned it into the companys advantage - He assigned and encouraged others to work around me, and do the mundane things around / for me, so that as a team we were successful. Eventually, he taught me to work within a structure, and not feel that structures limit productivity.
    I am very grateful to him, and today when I see some one like that, I try to emulate that formula. Works sometimes.

    Ashraya

  61. Management problem by turbotroll · · Score: 1

    The fact this guy gets away with being a downright asshole is purely a management issue at the company. The management either decided to ignore the problem, or tolerate him as he is for whatever reason.

    I stumbled upon a couple of such people at my jobs, except they were by no means above average and even had no excuse for similar behavior. Fighting them makes no sense, usually. My advice is to ignore them and focus on doing your job. If it becomes unbearable, change your job.

    P.S. Somebody who gets insulted by a slogan on somebody else's T-shirt has a serious issue with himself, I would say.

  62. At a large Canadian bank ... by Dragged+Down+by+the · · Score: 0, Troll

    I worked at a large Canadian bank where they had a programmer like this guy. They let him come in at noon and work 'til whenever he wanted. He had the long hair and the smell and he named all his computers (he had four servers at his desk) after planets. It took me 1 microsecond to figure out he was an a$$hole. I was sent to learn how to install this Windows service he had developed some years earlier - he obviously didn't want me to know how it worked. It was installed on every single system that talked to the mainframe at this bank. He proceeded to try to confuse me by rolling his chair from one server to the next while he ran through this complicated installation of products (it relied on a bunch of other, properly configured software). Unfortunately for Dingus, I'm a pretty darned good shoulder surfer, having worked with Aholes like him before. Five minutes later, I walked out of his hovel, he with a smile on his face thinking he'd confused me and that I'd be back, me with the knowledge of how his software worked. A couple of days later, I showed my manager how his software was logging the userid and passwords (in the Windows Event Log) of every supervisory user who logged on to the systems that made use of his software. The excrement hit the fan!

    1. Re:At a large Canadian bank ... by mevets · · Score: 1

      Nice Story; kinda like penthouse-forum for geeks.

  63. I am irreplaceable by Anonymous Coward · · Score: 0

    Some of us are irreplaceable. My previous employer took advantage of my generous nature, underpaid me and was hosing my dear friend in an emotionally abusive relationship. I finally was head hunted away. He is now out of business. Some of his failure is independent of me leaving, but due primarily to the reduction in clients who were loyal to me, not who I work for.
    So, note to owners / managers, treat your stars like stars. A company car and meager expense account will go a long way to making us loyal to our customers and then to you.

    1. Re:I am irreplaceable by houghi · · Score: 1

      Some of his failure is independent of me leaving

      Perhaps you were the last mail, but he would have failed regardless of you. Nobody is irreplaceable and especially not those who think they are.

      --
      Don't fight for your country, if your country does not fight for you.
    2. Re:I am irreplaceable by omnichad · · Score: 1

      Depends on how small of a town you live in. It's really hard to get talented people to be willing to move to a small town - especially a small town without a good ISP.

      I myself feel irreplaceable, and I don't want to be. I want to be free to leave without hard feelings if opportunity arises.

  64. I prefer to say by br00tus · · Score: 1

    The code IS the documentation.

  65. Ignore... by autocracy · · Score: 2, Insightful

    Drop down menus should come with an ok button. Undoing "overrated," which should have been "funny."

    --
    SIG: HUP
    1. Re:Ignore... by Gldm · · Score: 1

      Interfaces are often overrated like that.

      --

      Introducing the new Occam Fusion! Now with sqrt(-1) fewer blades!

  66. What genius? by Salamander · · Score: 1

    According to the story, the bug was in Josh's code. Where I come from, you don't get much credit for fixing a bug you created, especially if it took two days of eroding customer perception before you did it. Further, the description of the convoluted code and missing documentation suggest that such problems should have been expected. This is not a guy who wrote great code and then demonstrated brilliance fixing a customer problem. It's a guy who wrote crappy code and then fixed it later than he should have.

    OK, so it's a bad example, but that doesn't necessarily invalidate the whole line of inquiry. There's still a real phenomenon of brilliant programmers who are also disruptive. The solution is to tell the person that they can't rely on history, that every single instance of flouting the rules will be evaluated on its own merits. If they're right every single time that their actions are justified by creating an overall good for the company, they'll be OK. If they're wrong just once and it's an action that would lead to anyone else being fired then they'll be fired too. If they're not capable of working through the implications of that simple policy and modifying their behavior accordingly, then they're really not that smart after all and you're better off without them. We are all responsible not only for our own individual deliverables but for the effect we have on others around us. Reward people for the good things that they do, and penalize them for the bad things. If they're rational, they'll adjust.

    --
    Slashdot - News for Herds. Stuff that Splatters.
  67. and see what it gets them. by RoverDaddy · · Score: 1

    From TFA: Eventually customer issues reach the breaking point and CEO steps in. Josh is called to the carpet, so like the child he is, he picks up his ball and goes home. Company suffers. All goes to show that management ought to nip the problem in the bud before it ever gets this bad.

    --
    RETURN without GOSUB in line 1050
  68. Conditionally OK by Quiet_Desperation · · Score: 1

    I'd say it's fine, but I'd also turn a blind eye to any of the female coworkers who kick him in the balls.

  69. The stupidest people possible by Demonantis · · Score: 1

    These people have to be the stupidest people alive. A company doesn't care about performance entirely if they want to promote you to management. They care how you represent the company. If I could churn gorgeous code out, I still only get paid the $65510/year that everyone else does. Management gets paid in around six figures. If your really that good that means you get $35 000 just for putting on a dress shirt and pants every work day. I for one would do that.

  70. Re: Seems ridiculous to me as well. by guidryp · · Score: 4, Informative

    I would say for every "freak" like this there must be a thousand+ that can code as well and are great to work with. This is just a egregious stereotype that would be quite hard to find in most modern Dev shops.

    I have been doing SW dev for a living for about 15 years. Most of it large scale teams. I never saw anyone remotely close to this description and I have worked with some brilliant people. The best were humble, normal down to earth people. There has been a touch of arrogance, by some, but nothing like this.

    I don't think the described person would last a week in the environments I work in.

    Only in a small shop run by an idiot who won't pay for quality developers that are both talented and decent to work with, would you get this kind of freak and any dependency on him.

  71. Compensation by Anonymous Coward · · Score: 0
    Tolerating assholishness is a form of compensation. If he is worth the tolerance, keep him on. If he's not worth the cost of keeping him employed, let him go.

    This is the way business works! If value > cost, go for it!

    It sounds like he's still a net win. If he doesn't document his code, maybe it's more valuable to hire someone else to document after the fact than it is to let this guy go.

    This is assuming that there is no middle ground, that you can't convince him to be a "better" (in your opinion) employee.

    Have you considered that the problem is you? I've noticed that I get along with some people at my job very, very well. They know their stuff, they execute quickly, they get things done. Other people -- even other whole teams -- are very frustrating for me, and I come off as an asshole from their perspective. I try to be nice, but I always end up sending an email saying "Please fix this bug that I filed many months ago", and they take it personally. But when you ask for a fairly simple feature and it takes 8 months to implement, maybe the problem isn't the guy who does the asking.

    So you may want to ask yourself, before you bitch too much about this guy, whether it's everyone who has a problem with him, or if it's just some people who have a problem. And if the people who don't have a problem with him tend to be the very productive ones, maybe the problem isn't him.

    Or maybe he is really just a jerk. Depending on the offensiveness of the T-shirts and the types of the insults, he may be a liability to have in the office, and you need to get rid of him. But if he wears T-shirts saying "FSCK YOU" and gets frustrated with employees (male or female) that take it as insulting, maybe he's not the problem. It's hard to tell from vague descriptions.

  72. Not just software by cirby · · Score: 3, Interesting

    A while back, I worked in a video production place where the lead engineer was an asshole. He was rude to everyone, and made a point of telling everyone how irreplaceable he was in every way.

    Meanwhile, he spent most of his day sitting in his office, looking through hardware catalogs - and never bought anything useful. Once in a while, some computer or video box would arrive, he'd have me unpack it and set it up, and then he'd berate the poor people who had to use them for not knowing how (he bought a really cool SGI workstation and dumped it on a girl who had never even seen one - she was a Photoshop artist).

    He used to set really long schedules for simple things, too - he told me I had to come in for a couple of months on weekends to put connectors and labels on a bunch of prerun video cables. It took me four hours. So he got mad, and told me I had to come in anyway, because he'd already set the schedule, and it was my fault for working too fast (and he also complained about paying me overtime, instead of thanking me for doing it fast and correctly).

    Yes, these people do exist...

  73. House by blueforce · · Score: 1

    If we didn't enable these people then we wouldn't have Dr. House.

    Man, crazy people always wanting to cut off the nose to spite the face.

    --
    If you do what you always did, you get what you always got.
  74. A much larger cohort... by Anonymous Coward · · Score: 1, Insightful

    I think the number of brilliant genius delicate hothouse flowers of programming genius are pretty rare. So rare, in fact, that it isn't even worth discussing (sorry Taco).

    I think a FAR larger cohort of programmers fall into a category of people who have been in one place a long time, know the systems (AND business processes) really well and have done little to no documentation.

    These people have you by the balls (as evidenced by me posting AC). If they leave you have to, in a lot of ways, start at square one. One can easily acknowledge that this was a management problem but even IF you try to institute best practices NOW these people will resist it because they know they hold power as operators of the Black Box. Every line of documentation removes a little bit of their power and leverage and it is the rare (and perhaps stupid) person who does that voluntarily.

    Yes, I suppose the ubercoders are a problem too but I think it is a much smaller, and different, problem than the one I described. If a company is depending on a coding wunderkind then they are probably on the cutting edge of SOMEthing and bad documentation is something of an expectation in that arena.

  75. Don't waste your money... by ntimid8 · · Score: 1

    Unfortunately our team has experienced this at the cost of possibly not making our project schedule. We finally discovered that 2 or 3 moderately talented developers cost the same as a one blowhard, pain in the ass developer and can typically accomplish the same things under budget and on time. I would also point out the history of Google and its many quirky developers and the worthless products they have produced in the past few years.

  76. The door swings both ways... by RogueWarrior65 · · Score: 1

    In my experience, management can and often does attempt to reign in talented people because they feel their own inferiority and the fact that while they will be stuck where they are for the rest of their career, the talented ones will eventually realize that they are getting the sh*t end of the stick and leave to start their own companies.

  77. The Capabilities Pool by Fringe · · Score: 1

    Too many of you think that you can train or fix developers. Some of us are well-rounded, but stop and think for a moment... the same things that CREATE great developers - utter focus on logic and machines, great spatial/coding skills, analysis, concentration to the exclusion of all physical - also creates anti-social people. If these guys had social skills and rewarding interactions with normal people to begin with, they wouldn't have become great developers. 'Josh' is hyperbolistic, but I've had a hard time teaching some of my programmers that showering regularly and not picking their nostrils in a meeting are important. They listen, but they can't really implement it. And then they wonder why they are career-ladder-limited. But if we keep them away from the other kind of people, it's all okay. Spiegel screwed up; the trick isn't to fix Josh, but to hire a team better able to work in the realm between Josh and the customers. Even Spiegel admits that losing him cost the company a lot of time and money. Maybe the company should have dumped Spiegel and found someone willing to work between Josh and the humans.

    1. Re:The Capabilities Pool by geekoid · · Score: 1

      "the same things that CREATE great developers - utter focus on logic and machines, great spatial/coding skills, analysis, concentration to the exclusion of all physical - also creates anti-social people. "

      No.

      Sorry, to many great developers have had social skills that fit someoqwhere in the expect sociatal sopcial skills.

      Also, to many peopel who don't create are anti-social people.

      There 'smarts' isn't really a factor.
      This sums it up:
      "Some people are fuck wads."

      I ahve worked with some actual geniuses. Most had a reasonable degree of social awareness. The exception where ones whose IQs are off the charts and they were assholes, they just couldn't communicate well.
      This wasn't a problem becasue they all had 'handlers'.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  78. Real geniuses aren't arseholes by David+Gerard · · Score: 5, Informative

    In my continued and repeated experience, the real geniuses aren't arseholes. They may be socially inept, but they aren't contemptuous about it.

    Paul Graham talks about this in How to start a startup:

    For programmers we had three additional tests. Was the person genuinely smart? If so, could they actually get things done? And finally, since a few good hackers have unbearable personalities, could we stand to have them around?

    That last test filters out surprisingly few people. We could bear any amount of nerdiness if someone was truly smart. What we couldn't stand were people with a lot of attitude. But most of those weren't truly smart, so our third test was largely a restatement of the first.

    When nerds are unbearable it's usually because they're trying too hard to seem smart. But the smarter they are, the less pressure they feel to act smart. So as a rule you can recognize genuinely smart people by their ability to say things like "I don't know," "Maybe you're right," and "I don't understand x well enough."

    This technique doesn't always work, because people can be influenced by their environment. In the MIT CS department, there seems to be a tradition of acting like a brusque know-it-all. I'm told it derives ultimately from Marvin Minsky, in the same way the classic airline pilot manner is said to derive from Chuck Yeager. Even genuinely smart people start to act this way there, so you have to make allowances.

    It helped us to have Robert Morris, who is one of the readiest to say "I don't know" of anyone I've met. (At least, he was before he became a professor at MIT.) No one dared put on attitude around Robert, because he was obviously smarter than they were and yet had zero attitude himself.

    --
    http://rocknerd.co.uk
    1. Re:Real geniuses aren't arseholes by T.E.D. · · Score: 1

      I've been a professional developer for about 20 years now, and that is exactly right.

      Posters going off on this need to realise TFA was written by a manager to other managers. While "Josh" doesn't resemble any real developer I have ever met, he is a great representation of what a typical pointy-haired manger thinks all developers are like.

      In the real world, the only a-holes I have ever met down in the trenches are the kiss-up types. Plenty of managers are jerks though. At least to their subordinates. Excrement flows downhill.

    2. Re:Real geniuses aren't arseholes by pugugly · · Score: 1

      Thank - Good Article, and seems pretty on point to me.

      Pug

      --
      An Invisible Entity of Vast Power whose existence must be taken on faith alone: Liberal Media
  79. Balance by m509272 · · Score: 1

    I've been doing this for 30 years now, nearly 20 as a consultant/contractor. I don't like to write documentation but I whip stuff out faster than most and do the work of most 3-5 person teams. I'm extremely loyal and committed to my job. I'm very gracious to all and don't smell. I obviously save my employers a huge amount of money even though I am being paid at premium rates. So what should be happening here? Take some of the money they saved and hire a documentation writer even if this is on a part-time basis. They are relatively cheap, they might even like writing documentation. I have no problem communicating with someone performing this function. After all they are doing something I don't want to do but should be done. As for rude, smelly, obnoxious, uncooperative, etc. There's just no place for those people. I was the replacement for someone like this. That was 10 years ago.

  80. watch out for too much "independence" by Anonymous Coward · · Score: 0

    There's a fine line between being a simple axx-hole and being a dangerous sociopath. I hired a guy who could be nice, but very strange, and he actually killed his wife and chopped her up in small pieces (over a major disagreement). Hiring people who can fit in with the team as well as being bright should be the high priority. Not either, but both. You need a sign that says "refusing to document your code is the first sentence of your termination letter."
    name with held

  81. Green Programmers by Ukab+the+Great · · Score: 1

    Shitting in a flower pot has the distinct advantages of:

    1. Saving management money on fertilizer.
    2. Reducing carbon emissions required to produce and transport said fertilizer.
    3. Lessening the solid waste that will end up leaking into our watershed.

    According to Gartner, more and more IT departments concerned with eco-friendliness are having their programmers shit in flowerpots every day. I'm surprised you haven't heard of this.

  82. Some Quirks Needed by DivineEquality · · Score: 1

    I think this guy is the extreme, but for the most part we as programmers are quirky (especially to Non-It people). At least the good ones..lol

  83. I must say... by SGDarkKnight · · Score: 1

    I've never met an employer that would tolerate anything near what "Josh" was doing; No documentation for code that is designed for a customer, so that you make yourself the only one that can fix any potential problems or needed updates = no job for the individual responsible and that code would never make it into the customers hands. I had worked with one such person, who was hired on as a developer, tried to have code sent out with no documentation (maybe he was hoping for job security by doing that, who knows), the code never made it out, and shortly after he was on his way out.

    There was only 1 time I ever had to use obscure code that nobody else could understand... that was when i was in college to ensure nobody could steal my code and hand it in as their own.

    --

    ...A no smoking section in a restaurant is like having a no peeing section in a swimming pool...
    1. Re:I must say... by geekoid · · Score: 1

      most developers don't document becasue they are lazy*, there ego is too big, or they are under an unreasonable time line.
      Very few think far enough a head to do it for job security.
      If you were doing looking at job security, you would still document....just not let anyone know where it is. That way you can get tagged as a genius when you fix a problem in 5 year old code in about an hour. well 5 minutes, but they don't need to know~

      You know, you could just have had the compiler embed a code in the final product that indicates it's your when you look at the hex, you could still have written clean code.

      *contrary to what you may have read,, lazy is BAD for a developer.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  84. Wasn't me! by JoshDM · · Score: 2, Funny

    I take showers.

  85. Or if the programmer IS the "good" one. by Kabuthunk · · Score: 1

    Or failing that, why does it always fall on the "quirky, socially-inept programmer" to be the "bad" person in the office?

    I mean, has anyone ever SEEN some of the office politics that take place in most companies? Holy jesus hell, I've worked in places where I would have KILLED to be socially-inept and ignored by everyone!

    --
    Planet Zebeth - Metroid with a twist
  86. Symptom or cause? by Anonymous Coward · · Score: 0

    The article seems to borrow a lot from the typical dorky programmer stereotypes. A bit too much to be believable IMHO.

    I've dealt with a lot of anti-social programmers in my time, and they all had some of the characteristics. They only however had one common symptom that is not mentioned: they were overworked, and were bad at delegating, and other programmers and managers systematically abused and reinforced that.

    To me that was always a stronger cause than the rest, which were mostly considered stress symptoms (and quite often a job-change cleared those up)

  87. Peter principle? by Anonymous Coward · · Score: 0

    From reading your post, it seems that you are probably a perfect example of the peter principle.

    1. Re:Peter principle? by Maxo-Texas · · Score: 4, Interesting

      I will be if I get promoted one more time.

      The two levels above me have no clue (they were reorganized over our department but really don't know who anyone is or what anyone is doing or what is important and what is trivial).

      I was always a leader type (lead sports team, lead online guilds, organized groups) so being a low level manager is fun. I was a solid intuitive maintenance programmer. I was not a brilliant developer but after loading the code, I could figure out problems in a non-logical fashion.

      I'm solid at building morale, coaching programmers how to game the system better so they get promotions and raises, and running programmers and projects so they arrive on time without the programmers having to work overtime.

      And I have carpal tunnel so I can't do head's down coding any more.

      I'm good at where i am- but if I were moved another level up, I'd be another clueless manager.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    2. Re:Peter principle? by infonography · · Score: 1

      by that you mean they are a bunch of pricks?

      Well the same could be said for the managers who don't have a single clue what the programmers are doing and just using them to pad their dept. The more difficulty a project the more levels of management from the top will require to translate tech speak into management speak. This is what happens when you hire jerks out of college with MBA degrees and a society that thinks people in Suits are better then T-shirts. for fricks sake they are making techs wear ties in some companies. The part in Matrix where Neo is talked down to is a businessman's wet dream.

      We need to make sure the company we work for has a clue before we sign on. If no then its going to be hell and they deserve the no docs approach.

      --
      Sorry about the writing. Robot fingers, you know? Cliff Steele in DOOM PATROL #23
    3. Re:Peter principle? by setagllib · · Score: 1

      Urgh, that was not an alliteration at all. Allow me.

      Your post poses probable perfect Peter Principle patrondom.

      --
      Sam ty sig.
    4. Re:Peter principle? by Maxo-Texas · · Score: 1

      Parent post poses probably perfect Peter Principle patrondom. :-)

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    5. Re:Peter principle? by setagllib · · Score: 1

      Ooh. Ok, I bow out.

      --
      Sam ty sig.
    6. Re:Peter principle? by Maxo-Texas · · Score: 1

      Nah, these are decent people with 5 to 10 years with the company. But they are business people with no clue about programmers or the programs they have been put over.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    7. Re:Peter principle? by Maxo-Texas · · Score: 1

      I was standing on the shoulders of giants. I only added one word.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
  88. Dangerous and quirky? by WoollyMittens · · Score: 1

    There can be no progress without risk.

  89. Brilliant doesn't have to be dangerous. by crovira · · Score: 5, Funny

    I used to comment my code's 'intent' and document what I was trying to make it accomplish. (Instead of, and I kid you not, writing shit like "C = C + 1; /* add one to C */" [What was C counting, you fucking butt munch? There's terse and then there's stupid.] )

    Then and only then, after documenting the intent, would I feel free to write the code.

    I ended up giving courses to the other programmers because I was doing things in CICS Command Level COBOL that they had never heard of (like dynamic memory allocation to take a data structure and stand it on its ear.)

    There were two ways to approach the problem.

    I choose NOT to be a cock-biting ass-hole about it.

    --
    MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
    1. Re:Brilliant doesn't have to be dangerous. by Beardo+the+Bearded · · Score: 5, Interesting

      I once wrote a coder / decoder for control messages for a radio system.

      The code itself was about 30 lines. With comments explaining WTF was going on, it was about 150. There were backsteps, cycling through arrays, multiple search trees, etc. Part of the comments included basic theory on the decoding mechanism.

      There was no way good variable names or "self-explanatory" code would have worked there.

      --

      ---
      ECHELON is a government program to find words like bomb, jihad, plutonium, assassinate, and anarchy.
    2. Re:Brilliant doesn't have to be dangerous. by Anonymous Coward · · Score: 2, Insightful

      mh, true and false. a pseudo code for a fast Fourier transform would be undocumentable - extracting radix: wtf is a radix? but a clean call to a method called fft() with a one liner pointing at the algorithm (eg Cooley-Tukey implementation of a fast Fourier transform) would change the mess in a functional block easily testable, replaceable and maintainable

    3. Re:Brilliant doesn't have to be dangerous. by Beardo+the+Bearded · · Score: 4, Insightful

      It's not 1985. Comment space is cheap.

      First, most functionality should be in functions (or methods, depending on your language). You wouldn't put stuff inline because that's a nightmare. However, at some point, you're going to have to write code that actually performs some kind of operation upon the data.

      If you called the function fast_fourier_transform() or fastFourierTransform() (depending on your coding style) it would make it a lot easier on the maintainers and cost you nothing.

      No matter what you called it, you'd still have to document the transforming function so that if you'd made a mistake in it, the next person looking at the code would be able to say, "oh, hey, this is supposed to be multiplied by -1 here"

      --

      ---
      ECHELON is a government program to find words like bomb, jihad, plutonium, assassinate, and anarchy.
    4. Re:Brilliant doesn't have to be dangerous. by Anonymous Coward · · Score: 0

      There was no way good variable names or "self-explanatory" code would have worked there.

      You probably still would have needed some comments, but the idea behind self-explanatory code is that you're structuring your code in such a way that it reads like a bunch of comments.

      It sounds like the code you wrote was a very dense 30 lines, which may have been necessary given performance requirements or what-not. However, it's entirely possible that if you had been willing or able to break it up into, say, 30 small functions, it could have largely documented itself.

      Not to say self-documenting code is a panacea and makes comments superfluous in all cases, but:

      There were backsteps, cycling through arrays, multiple search trees, etc.

      makes it sound like it may have been structured poorly for legibility. For example, a self-documenting approach would have created functions with descriptive names to wrap those array references, rather than use them naked.

    5. Re:Brilliant doesn't have to be dangerous. by Beardo+the+Bearded · · Score: 1

      Ah, sorry, I wasn't clear.

      The comments were placed throughout the code, explaining each line as it went along. The comments at the beginning were just the standard headers.

      The code was intricate because it's an intricate operation that required fuzzy logic to complete correctly.

      --

      ---
      ECHELON is a government program to find words like bomb, jihad, plutonium, assassinate, and anarchy.
    6. Re:Brilliant doesn't have to be dangerous. by Anonymous Coward · · Score: 0

      Then and only then, after documenting the intent, would I feel free to write the code.

      Absolutely. Thats how I've been doing it since 1983, using various languages. Incredible that so many people still don't get that the writing out of your thoughts before you code really pulls a lot of the flaws out and sometimes forces a different approach.

      And of course the benefit is that afterwards, the comments tell you what the code should do (which hopefully is what it does do).

      Productive? Very. Much more so than the laughable "self documenting" code, which is nothing of the sort (it only documents what it does, not what it should do).

    7. Re:Brilliant doesn't have to be dangerous. by Tubal-Cain · · Score: 1

      [What was C counting? There's terse and then there's stupid.]

      Speed of light. Duh.

    8. Re:Brilliant doesn't have to be dangerous. by Gldm · · Score: 1

      Having dealt with the very specific headache of having to use and modify an FFT function before, one problem that is difficult to avoid is the fact that most coders who write math libraries and things like FFT functions tend to write them in math terminology. I.e. there are lots and lots and lots of confusing little single letter variables that are obvious in purpose to a math major (or someone who's done the math for engineering/physics/CS) but completely obscure to anyone else. Sometimes x or w or n or k as a variable choice is just a lazy programmer. Other times it's mathematically significant. And if you don't have the experience to know it's the latter and not the former, especially since many math programmers are very lazy about documentation since they assume everyone will either know the math or go look up the math, it can turn into a real headache real fast. And if you're somehow in the position of having to deal with functions written by programmers from different scientific disciplines (math + physics for example) you can just forget about consistent and descriptive variable naming. Because to them a single letter IS descriptive and not obscure at all, but to anyone else it's not, and the systems are not consistent to each other (too few letters for that).

      --

      Introducing the new Occam Fusion! Now with sqrt(-1) fewer blades!

  90. Brilliant programmers by Anonymous Coward · · Score: 0

    are dime a dozen. Fire the guy. And fire any management who thinks that their Golden Boy is not to be found anywhere else. More Stupid Management being played like a cheap violin.

    Nothing new here, move along.

  91. I've read the "Stuart" story before. by MarkvW · · Score: 1

    I've read the "Stuart" story (referenced in the article) before--probably on Slashdot.

    These articles appear to be a higher level of troll. From my experience, the Slashdot editors stir the pot with extreme articles every now and then to stimulate responses.

  92. Both IT and health care value autonomy highly. by ndru82 · · Score: 1

    It's interesting to see this debate happening here on Slashdot. I spend my life immersed in the world of health care, and a large part of my job is trying to figure out ways to deal with folks like Dr. House. It's a big, big cultural transformation, or at least it is in health care. One of the reasons that it's so hard to deal with is because in "fixing" a problem like Dr. House you run the risk of treading on people's autonomy. And part of the reason that folks like this get as far as they do is because of all the places in our broad culture where autonomy reigns supreme as a guiding value. Now don't get me wrong, I support autonomy in a big way! I'm just saying that we need to think of some of the unintended side effects that brings along when we perhaps push the dose a bit too much. Ironically, I often use the analogy of an open-source software community to help people envision what health care might look like if we did a good job of improving its culture. If only hospitals had a modding system that allowed flame-bait to be identified and screened out in policy debates!

    1. Re:Both IT and health care value autonomy highly. by ndru82 · · Score: 1

      Here's an interesting article that you might also enjoy, by one of the foremost thinkers in the field. His theory is that smart people don't experience enough failure: they're too often right, and they're right immediately. If you don't seem so sure of yourself immediately, you have a better chance of attracting collaborators. It's a little like agile development, where you release stuff that you know isn't exactly "it" but it's a good start, works, and makes a meaningful improvement in people's lives. If you've always succeeded in "brilliant loner" or "cathedral" style development, you don't know how to function in the bazaar. http://www.velinperformance.com/downloads/chris_argyris_learning.pdf

    2. Re:Both IT and health care value autonomy highly. by TheRaven64 · · Score: 1

      Sounds like good advice. I really hate letting anyone see my work-in-progress stuff, but I've found that when I do then I can incorporate their feedback and get a better final product. Code review is the same. No one likes to be told that their code isn't perfect, but going through the process helps you, as well as your collaborators. They learn about what you are doing, and you learn how to avoid the mistakes you made the next time around.

      Very few programmers, if any, write perfect code all of the time. Even fewer are willing to admit it.

      --
      I am TheRaven on Soylent News
  93. Come again? by smcdow · · Score: 1

    Sure, he was whipsmart and could churn out code that saved the company millions, but can we please stop enabling these people?"

    Let me get this straight -- you'd rather prevent someone from saving your company millions of dollars?

    If I were a manager, I'm pretty sure you'd have a hard time justifying this idea.

    --
    In the course of every project, it will become necessary to shoot the scientists and begin production.
  94. Josh, stand up by gzipped_tar · · Score: 1

    Do you really think that Josh is the kind of person who don't read /. ?

    --
    Colorless green Cthulhu waits dreaming furiously.
  95. Just say it in ONE word by Provocateur · · Score: 1

    Divaloper.

    --
    WARNING: Smartphones have side effects--most of them undocumented.
  96. It's a theoretical issue by ClosedSource · · Score: 1

    No single coder has saved a company "millions of dollars".

    1. Re:It's a theoretical issue by 91degrees · · Score: 1

      I spotted a bug in our software that would have prevented it from ever being released.

      Someone else would have spotted it if I hadn't, so they would have saved the company millions of dollars, but perhaps "Josh" is better at self promotion.

  97. simple, really by Tom · · Score: 3, Insightful

    There's absolutely nothing specific to developers here. You have the same kind of people in every other job.

    The one question you need to find an answer to is this: Teamwork or solo heroes?

    If, for whatever reason, your project needs a team to work, say you want to support it for years to come and can not 100% guarantee that the one developer is still on board by then, or it is simply so large that you need more than one person to do it, then you absolutely can not use asocial people. Any and all attempts to somehow fit them into the team, or build the project around this inherent conflict will fail. You can't go faster than the speed of light, it really is that simple.

    However, there are projects where you need a lone hero. A crash project that needs to be done with next week, and can be shut down the week later, but it absolutely must be there during that time, and there's absolutely no way you can get it done while following procedure. Or - the more common case - you inherited a project that only this one dude even understands, and you don't have the manpower to replace it or reverse-engineer it. And sometimes, you have a project you want to fail spectacularily, and absolutely no team will give you the same show for your money that a fanatical lone hero can bring.

    So if you need a hero, then enable him, empower them, and suck it up. If you need a team, kick out the hero and make sure your team knows who to thank for it. Just don't try to have both. You can't. Been there, survived it, and I did, in fact, get a T-Shirt.

    --
    Assorted stuff I do sometimes: Lemuria.org
    1. Re:simple, really by jeffc128ca · · Score: 1

      "There's absolutely nothing specific to developers here. You have the same kind of people in every other job."

      I disagree completely. There are certain skilled jobs that allow the skilled employee to hold others hostage. As a programmer myself I have seen this countless times in several companies. Employee X is the only one that knows some system that is mission critical. It's difficult, even for other system developers, to jump in and understand how something works to replace employee X. It could take 6 months to a year. This doesn't work with secretaries, salesmen, accountants, managers (who are completely expendable), and "business analysts".

      Besides programmers, you can count mechanics, doctors, electricians, and network technicians as having a special hold over their clients when they gain intimate knowledge of their daily jobs. Because of this they have special bargaining power that the normal managers and administrative assistants don't have.

    2. Re:simple, really by Tom · · Score: 1

      There are certain skilled jobs that allow the skilled employee to hold others hostage.

      Agreed, it isn't every other job. But it is a lot more than you'd think at first glance.

      I've met people like that in the legal and HR departments, in marketing, in networking and in sales. And I dare say that some secretaries know a lot more and are a lot more important to the company, than their bosses. I know how dumb I occasionally look when mine's on holiday. :-)

      --
      Assorted stuff I do sometimes: Lemuria.org
  98. That's not true. by tjstork · · Score: 1

    There was the single coder that ported, without authorization, Windows 286 to Windows 386. He got enough of it to work that he demo'd it up the chain until Ballmer took a look at it, threw a chair, and said "f---- you just killed OS/2!"

    They threw some more developers on it, and the rest, as they say, is history. A single developer laid the groundwork for Windows 3.1.

    --
    This is my sig.
    1. Re:That's not true. by ClosedSource · · Score: 1

      Actually Windows 386 and Windows 3.1 were separate products. If your point is that there would be no version of Windows beyond Windows 286 if not for this guy I don't buy it.

    2. Re:That's not true. by IntlHarvester · · Score: 1

      No, his point is that a skunkworks effort allowed Microsoft to more aggressively market Windows and therefore dump OS/2.

      If Windows 3.0 came out a year after OS/2 2.0 instead of a year before, the world might be a different place.

      --
      Business. Numbers. Money. People. Computer World.
    3. Re:That's not true. by SuiteSisterMary · · Score: 1

      The punchline to the story is kinda funny, too.
      Programmer We should port Windows to protected mode.
      Techie Manager Can't be done.
      Programmer It's running downstairs.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
  99. Are quirky developers brilliant or dangerous? by TheCreeep · · Score: 1

    Yes.

  100. Remind him that he's not *that* smart by RevWaldo · · Score: 1

    It was a running gag back in engineering college. A bright-eyed student would start his engineering major (electrical, chemical, etc.), get his ass handed to him, and then switch to computer science.

    While there's certainly a steep learning curve in becoming a developer, at the end of the day its just a matter of hands-on experience. Fold flap A into slot B enough times and you eventually get the hang of it.

    But most of the concepts are understandable to the everyday human. In business development, the mathematics involve rarely involve anything beyond some complicated algebra. If homeboy was a *real* genius he'd be in game physics or data compression or quantitative analysis or some other programming field where calculus and other brain-bending forms of math raise their ugly head.

    I've found that there's a big difference between "clever" and "smart". The smart guys figure out how to store 100GB of information on a 3.5" disk. The clever guys come up with microblogging. Most developers fall into the clever category.

    1. Re:Remind him that he's not *that* smart by buddyglass · · Score: 1

      While there's certainly a steep learning curve in becoming a developer, at the end of the day its just a matter of hands-on experience. Fold flap A into slot B enough times and you eventually get the hang of it.

      I can't disagree more with this statement. IMO there's a certain aesthetic element to coding that most developers just don't "get". You're designing something with moving parts that fit together in a certain way, etc. You want it to be fast, but you also want it to be as "simple" as possible. You want it to be easily extended. Etc. From what I've seen, this isn't something people just "pick up through experience" or learn from a book.

      The gag about EE folks moving to CS also existed at my University, mainly because the Engineering college made you "apply" to finish the degree after your first two years, whereas CS was open to anyone. As someone who earned undergraduate degrees in CS and Math, I'll say that the Math students similarly looked down on the Engineering students as being devoid of intellectual curiosity. There was some truth to that stereotype.

  101. "No? Then you're sacked!" by Anonymous Coward · · Score: 0

    Bummer.

    1. Re:"No? Then you're sacked!" by RMH101 · · Score: 1

      And if production has an issue that can't be fixed due to poor documentation and an MIA developer, the responsibility for that falls on the PHB. This is why in the long run, no documentation = not finished.

  102. You can be a nice genius... by tjstork · · Score: 1

    I mean, if you are a genius, why wouldn't you be nice... if you are better than everyone else, then, take ownership of the team, put the project on your back and just do it. That's what you were meant to do. No need to be a dick about it. If its so hard, maybe you aren't so smart!

    --
    This is my sig.
    1. Re:You can be a nice genius... by pugugly · · Score: 1

      There *is* a tendency for the corporate world to not recognize a genius *unless* he's also a complete ass.

      Pug

      --
      An Invisible Entity of Vast Power whose existence must be taken on faith alone: Liberal Media
    2. Re:You can be a nice genius... by tjstork · · Score: 1

      There *is* a tendency for the corporate world to not recognize a genius *unless* he's also a complete ass.

      You have to network in the corporate world, and constantly differentiate yourself so that everyone sees what you are doing is vital to the firm. The thing is, though, unless your project is a new product, that brings money into the firm, then, you aren't likely to get attention.

      --
      This is my sig.
  103. Both! by ErichTheRed · · Score: 1

    Being a systems guy, I've worked a lot with quirky developers. I also work an industry that is a haven for crazy proprietary standards. The description of "Josh" in the article is very close to some people I've had experience with. The "extreme niche" of my industry makes things worse -- newbies are useless for months until they can begin picking up how things work. Once they learn, they're highly-prized, which makes it really hard to get rid of lousy developers.

    At least for the present and in the past, IT work has been all about being a hero and pulling insane hours to fix something. I've always been a fan of doing the engineering and documentation up front rather than staying up all night messing around with a problem. For every one of me, there's 10 Joshes. And since Josh is constantly fixing the mistakes as they appear, he's the one that ends up the hero. Management declares Josh the wunderkind, and the rest of the IT staff ends up second-class citizens.

    Does that sound bitter? Not in my mind. I actually don't mind going along and doing my work. However, companies that embrace Joshes set themselves up for a big problem later on. What happens when Josh leaves (and he will)? The rest of your IT staff now has to pick through his undocumented code and figure out what he did. Also, if Josh is an offensive jerk, no one is going to want to talk to him, which makes the problem of no documentation worse.

    Companies do need really smart developers. However, management needs to realize that parts of IT naturally attract "socially challenged" but really smart people. They need to keep on top of what they're doing and set appropriate limits.

    The next generation of IT work *may* limit the appeal of the lone wolf/nerd brilliant developer, but I don't see that happening anytime soon. Until then, I have to put Josh's untested code into production because he doesn't need any QA people looking over his shoulder. :-)

  104. Or they just might not be "all that" after all by onyxruby · · Score: 1
    I'm presently working a consultant for a company that had 4 people doing a single function. Management was previously convinced that they knew the product (SQL based) better than the the products manufacturer. Meanwhile the company (15,000 seats) decides to outsource all IT to another company as they were in desperate need of help. Other company has no such pre-conceptions and brings in me to look at what they had going.

    I get on site, the previous four administrators are now gone. I check things out and discover things like the architecture is fundamentally flawed, documentation is wrong and must now be discarded on face value and redeveloped from scratch, security holes big enough to drive a truck through and a complete lack of best practices. Meanwhile I must undo their previous three-four years work, re-architect, document, upgrade and migrate everything.

    The previous employees were incompetent, management didn't know better and now it will cost a fair bit of money to fix everything.

    1. Re:Or they just might not be "all that" after all by geekoid · · Score: 1

      Perhaps they7 where incompetent, I'm not there I don't know. Bear in mind that those are also symptoms of bad managements using poor indicators to determine deadlines.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  105. Re: brilliant and dangerous? by fugue · · Score: 5, Insightful

    People like Josh, on the other hand, should be fired on the spot.

    I don't think so. They can just be recognised for what they are, and treated accordingly. Think of him as a fire extinguisher--a pain in the ass to clean up after, but from time to time invaluable. Sometimes you need a solution NOW, and you will have time to clean it up (or re-implement it more carefully) later. Perhaps your expectations for him were too high. Understand your resources and learn to use them appropriately.

    --
    "The biggest problem with communication is the illusion that it has taken place."
  106. pot meet kettle by dna_(c)(tm)(r) · · Score: 1

    "Is mediocre management searching to blame lacking cat herding skills on cats?"

    See? I can make insightful headlines too.

  107. I read the article by br00tus · · Score: 2, Insightful
    First of all, the writer talks about how the coder was not "businesslike", but then goes on to describe him and others as "quirky...weirdest...weird...quirky...prima donna...he was truly crazy...his appearance was like Pig Pen...smells...'offensive' t-shirts...inappropriate...dark, cave office...quirky, crazy, irrational". Now how "businesslike" is it to describe someone like this? He is just slinging mud trying to bias me against this person instead of giving examples of what he has done. So what if his office is darker than the rest of the floor, it's his office, I've had to sit in cubicles where we are practically blinded by the light. And it's his private office, this guy seems to think he's a big boss and can tell people what the lighting level of their own private office is. If he is offended by someone not having a global warming causing office, I wonder what he finds offensive on a T-shirt, "Vote Obama"?

    Amidst all of this mud-slinging, we hear some actual examples of what Josh's supposed failings are. The first one is a developer on his team, who is responsible for implementing and patching version 1.0 of the code, decides to not do his work, and goes to Josh, who is writing version 2.0 of the code, and sounds like the head developer on that, and have Josh do his work for him. Josh tells him to fuck off as he is busy, on a deadline to write 2.0. Then Spiegel walks in. Spiegel is there to reprimand Josh for not pulling off his tight developed schedule, and deal immediately (without scheduling it) with a problem that his own incompetent developer can't deal with. Spiegel is shocked Josh isn't obsequious in the face of this demand. Josh's paycheck is dependent on him getting version 2.0 on time, why should he spend more than the 50, 60, 70 hours a week than he's currently working to dump everything immediately and go deal with a problem due to an incompetent developer who can't handle the work?

    So the story is Spiegel has an incompetent developer on his team who can't figure out code and how to do his job, so the bad guy is the coder who everyone including his manager says is the best, most brilliant coder, who won't drop everything immediately and go work on Spiegel's problem. After which Josh will either miss his deadline or have to work even more hours than he has to, and Spiegel looks like a star for fixing his problem. As far as curtness, I wonder if Josh worked 40 hour weeks, had things scheduled far ahead with reasonable deadlines and a full and competent support staff in place? Why do I have a feeling that was not the case? Spiegel had a developer on his team and mentions the 2.0 team Josh is on. So why didn't his own developer or someone else on the 2.0 team look at it? Because Spiegel wants the star of the 2.0 team to drop everything and fix his problem.

  108. It "depends" on your CEO more than that by Anonymous Coward · · Score: 2, Interesting

    and that seems to be A-OK, doesn't it.

    I mean, that's why he gets ~50x the salary of the workers and a bonus in the millions, yes? Because you MUST HAVE HIM!

    Strange isn't it, that when it comes to executive or director pay, your company pays top dollar "because we must have the best", but when it comes to the people who actually DO the work you sell, it's all "it's a competitive market and we can't afford to spend too much on salary or we'll lose customers".

    1. Re:It "depends" on your CEO more than that by Angostura · · Score: 1

      Nope. CEOs leave all the the time - and when they leave people don't sit around going 'shit he didn't document the business strategy, anyone know how the company is meant to work?'. Dependency on the CEO and dependency on a maverick developer are quite different.

  109. Josh is payed to do his job, not to be a great guy by Otis_INF · · Score: 2, Funny

    i.o.w.: josh isn't payed to go hold your hand, share funny stories or go to the mall with you and your kids, he's payed to get the job done, whatever it takes.

    If that makes life hell for his co-workers, the company should make a decision: what are we: an organization which purpose is to keep some group of people off the streets or a business? If it's the former, Josh has to go, as he'll force the rest of his coworkers to go back to the streets, however if it's the latter, the rest should either shutup or do their work as well, as they too aren't payed to babble for hours at the watercooler.

    --
    Never underestimate the relief of true separation of Religion and State.
  110. No documentation = not done by fdrebin · · Score: 2, Insightful

    I have a simple policy, for myself and for people who work for me.
    If it isn't fully documented, it isn't done. There are no excuses, period.
    /F

    --
    Stupidity... has a habit of getting its way.
  111. The whole point of your post... by Anonymous Coward · · Score: 0

    was to get this sentence out of your keyboard without appearing to boast, "I spend a good deal of every day helping people that may be not as quick or sharp as me..."

    Trouble is it didn't work.

  112. Re:These guys are all right. by somersault · · Score: 2, Insightful

    perhaps brilliant people are angry because life sucks.

    You poor fools who die boring, polite and pointless never realized the tragedy of it all.

    Funny how what you think of as the boring and polite people don't actually think life sucks, eh? I get frustrated at the attitude of some sheeple too, but there is something to be said for being happy.

    Sometimes these people are not actually boring either, just respectful. Speak to them in an informal situation and they might not be as boring as you had previously thought. You don't have to be a jerk to have fun.

    --
    which is totally what she said
  113. You need to wean the company off him by 91degrees · · Score: 1

    This guy's only important skill is that he understands how his own code works. That's all. You can hire smart specialists in any other field that he's good at. Maybe they'll be a little more specialised, but they'll be able to help the rest of the team develop and they'll be replacable.

    Aside from that he creates code that only he understands, making the company more dependent on him.

    The main problem is that by giving him more work, you end up becoming more dependent on him because he produces more code that only he understands. The other problem is that you can't easily get rid of him. The only thing to do is give him a nominally impossible make-work project, while other people work to clean up and rewrite his unreadable code. Then make him expendible enough that you can discipline him without repercussions.

  114. The problem with irreplacable... by PinkyDead · · Score: 2, Interesting

    You can be an idiot and be irreplaceable - and of lot of these guys are.

    One clown I came across deleted all the test code, because he thought testing was a waste of time. He was gone a good 8 months when that shit hit the inevitable fan.

    The problem is that they write shit hot amazing code that does the job and impresses the PHBs, but if it is unmaintainable by a team then:
    (a) It's not scalable (in terms of growing the product)
    (b) It's long-term useless

    This is the equivalent of a teenager thinking they are super drivers because they can speed at 130mph with their eyes closed. An experienced driver knows that deer can jump into the road.

    --
    Genesis 1:32 And God typed :wq!
  115. There's quirky, and then there's narcissistic by rlk · · Score: 1

    To me, "quirky" means someone who eats offbeat food for lunch, or works particularly strange hours, or wears ripped T-shirts and cutoffs in the dead of winter, or wears a suit and tie when not visiting a customer, or who consistently underestimates schedules by the same amount each time. These can either be ignored or worked around (the person who consistently underestimates his schedule by a factor of 3 is easy to plan around, just triple his time estimates and caution other people to do the same thing). That's harmless.

    The prima donna is someone with mildly narcissistic tendencies whose ego needs some stroking, but who will get things done in a fashion that allows others to understand what's going on. I can handle that, up to a point. If when push really comes to shove the person works well with the team, OK, he or she is fundamentally a good person but has some insecurities. If the person insists on taking all the credit for a team effort, that's getting destructive.

    A real narcissist is another matter altogether. Someone whose code is impenetrable, who refuses to document anything or tell anyone what they're doing, or who deliberately and maliciously offends people (wearing offensive T-shirts...I don't simply mean less than stellar personal hygiene) is another matter altogether. Doesn't matter how brilliant the person is, someone like this will destroy a team, and however clever their work, it's not going to be usable if anything changes.

  116. Re:Josh is payed to do his job, not to be a great by taustin · · Score: 2, Insightful

    The first job responsibility in our employee handbook is that we have to get along with other employees. In other words, yes, it is my job (and everyone else's job) to not piss people off. Unless Josh can literally do every job in the company, he's not worth losing other employees over. No matter how productive he is, he's not the entire company.

    Plus, creating a hostile work environment is illegal.

    Any company that tolerates assholes like this will have no other competent employees.

  117. I've known several people like this by davidwr · · Score: 1

    If I inherited a dept. and got someone like this, I'd look at a few things:

    *If he was making a net negative contribution, it's an urgent problem that requires fixing now, otherwise it's "just" an opportunity for improvement

    *Is the person's personality such that he will "never" be "normal," that he's as socially adept as he will ever be?

    *Is the person's personality such that he isn't open to change right now but with some maturity he might be in a few years?

    *Where is the best place for him in the company right now?

    *What can we as a company do to help him mature so he can really shine?

    After looking at all of these questions and more, I'll have a good idea if he's someone we want to keep on the staff or not.

    If we do keep him on the staff, then I'll probably isolate him. There are good programmers out there who enjoy working around such "eccentric geniuses" and are more than eager to be the "public face" of a 2-man team, or even manage a team of such people.

    --
    When I was at University I met several nutty-professor-in-training-types who I thought "I'd never want someone like this on a team, but I'd love to put them in a closet and throw work at them to make me a boatload of money, and they would love it too."

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  118. Re: brilliant and dangerous? by Dionysus · · Score: 5, Insightful

    Sometimes you need a solution NOW, and you will have time to clean it up (or re-implement it more carefully) later.

    Except, cleanup (or re-implementation) never happens. What will happen is layer upon layer to work around bugs and problems. Because you can (almost) never justify to upper management that you need to reimplement something that works and the finish product is basically the same you started out with (with cleaner code, maybe).

    --
    Je ne parle pas francais.
  119. Re: brilliant and dangerous? by jellomizer · · Score: 5, Insightful

    Um no.
    Because there are a lot of good people who can do the work and better and be a company player too. You are assuming that Josh's skills are irreplaceable. And that a good employee cannot do what he does. I am sorry, he is replaceable, and you can get a more professional guy to so the same job just as well, if not better because he is not so high on himself. I too have cleaned up messes after people like him. And let me tell you I have never seen any work by these guys that make me go wow this guy is my superior, in programming. Usually after a couple week I figure out the flow and I am just as productive as the guy was before, except people are willing to talk to me. Ask questions and raise problems that the other guy made them to afraid to mention.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  120. My personal experiences with Cowboy Coding by jockeys · · Score: 1

    I've been in the development business for a while now, and I've been on both ends of this mess.

    As a cocky young prick^h^h^h^h^h developer right out of school, I would frequently go off on my own and do things that I thought were cool and clever. Occasionally, they actually were. Never really thought much of it, in those days of 80 hour weeks, but one day I got sick and stayed home. Much to my dismay, I got phone calls all day long because of how needlessly complicated and unfamiliar my shit was. From then on, I started to see how it wasn't that cool.

    Fast forward a few years and I'm the project lead on a pretty ambitious (couple million lines) web project. One of my direct reports was a Cowboy Coder like I had been. He did a lot of the same things, and I understood why: it was faster. He understood the codebase better than anyone, and so he could fix problems in an hour or two. Other devs struggled to do the same in days. In the end, I had to make a policy that everyone would take a few hours each week and teach their job to someone else. That way, if one of them got hit by a truck or something, the project wouldn't sink. There was a lot of bitching at first, but when devs realized it meant they wouldn't be getting nagging calls on sick days and vacation, they were a lot less pissed.

    In the end, it's about the team. I'm not writing the code for myself, I'm not managing the project for myself. It's for my employer (assuming I'm not self-employed) and I have to consider what is best, in the long run, for them. Yes, bringing the whole team (or at least a few other people) up to speed on stuff is expensive, time-wise. But it totally pays off in the end.

    --

    In Soviet Russia jokes are formulaic and decidedly non-humorous.
  121. Unmaintainable by WED+Fan · · Score: 4, Insightful

    My local "Josh" is a genius, has gone from Athiest to American Indian to Christian to converted Jew (the last because he doesn't believe the miracles that Christians talk about), has a habit of telling the most inappropriate jokes, shows up when he wants, leaves when he wants, cannot/will not explain his code, will not code with others, insists the DB be designed to his standards, and produces code that does the job very well, but is utterly unmaintainable.

    He also collects the bonuses and gets the trips and training money. (The last, training trips and seminars that he usually ends up walking out of because they don't go along his lines of thinking.)

    --
    Politics is the art of looking for trouble, finding it everywhere, diagnosing it incorrectly and applying the wrong fix.
    1. Re:Unmaintainable by mabhatter654 · · Score: 1

      the trouble is that management likes these people. They get invited to the meetings, the get called first, so they get things "done". They are also careful to make sure THEY get training, and THEY get invited to meetings first and carefully control that others don't get invited. Their opinions get heard first and get heard loudest.. and they know who to cry to, and what things to threaten to get their way.

    2. Re:Unmaintainable by kalirion · · Score: 1

      has gone from Athiest to American Indian

      "American Indian" is a religion now? Or is Atheism an ethnicity?

    3. Re:Unmaintainable by obarel · · Score: 1

      Sounds like a movie to me... maybe the sequel to American Ninja?

  122. I really want to thank Josh by bugs2squash · · Score: 2

    I rarely shower, wear worn-out filthy clothes, neglect anti-perspirant and have defecated on countless lobby plants as a career building move.

    Now my co-workers consider me a genius because they have been conditioned by people like Josh to presume that only a genius could get away with these things.

    The fact that I can't code worth a crap does not enter into the equation. Perception is reality.

    --
    Nullius in verba
    1. Re:I really want to thank Josh by Anonymous Coward · · Score: 0

      I rarely shower, wear worn-out filthy clothes, neglect anti-perspirant and have defecated on countless lobby plants as a career building move.

      Tom, is that you?

  123. Exaggeration? by MBGMorden · · Score: 3, Insightful

    I wonder to what degree "Josh" here is an exaggeration. I'll say that I'm probably the "Josh" of our office - to some degree. I don't wear offensive t-shirts, but I don't normally do suit/tie (normally a polo and jeans - though often the polo is untucked). I am regarded as one of the few "people persons" in IT though (contrary to the "Josh" example).

    But, I am the odd ball out at work. I typically embrace new versions of software much quicker compared to many of our older workers who must be dragged kicking and screaming into an upgrade. I'll code stuff in whatever language I feel suits my mood and the requirements of a particular problem. I keep up to date with the latest technology trends.

    The "documentation" thing is one that I hear a lot. I try to document what I do. But some people can be unreasonable. For instance, I setup an amavisd-new email filter. Now, amavisd-new is a well known open source tool. It's ALREADY documented. Is that enough? Nope. I'm expected to write NEW documentation for the tool so that the rest of the IT department (who doesn't understand much Unix) can use it. I don't mean a diagram as in "here's how I setup the system", as in I'm expected to produce documentation on "How to release a quarantined message" when it already exists.

    Not to mention that when you look at how some of these people code and/or setup systems/databases, it's obvious just WHY they need so much documentation. The darned things don't make any sense. Without some ancient codex you can't make heads or tails of the system. So rather than do a clean and logical implementation, they'll do something that makes no sense and then go about it as if everything is OK so long as there's a written explanation of the kludge on file somewhere.

    I think far too often "Josh" might simply be getting mud slung his way due to the shortcomings of his peers.

    --
    "People who think they know everything are very annoying to those of us who do."-Mark Twain
    1. Re:Exaggeration? by CherniyVolk · · Score: 1

      The only reasonable post yet.

    2. Re:Exaggeration? by geekoid · · Score: 1

      You are looking at it wrong.

      Not every one has your experience, and your experiences aren't the only legitimate ones.

      IN your example, just web crawl this:
      http://www.ijs.si/software/amavisd/amavisd-new-docs.html
        Bam, documenting is done.

      While documenting can be held to an unreasonable standard, your example is not it.

      For example, developers should never do end user documentation. Hire a professional becasue users need it laid out differently then developers, and most developers aren't trained to think that way.

      "Not to mention that when you look at how some of these people code and/or setup systems/databases, it's obvious just WHY they need so much documentation. The darned things don't make any sense. Without some ancient codex you can't make heads or tails of the system."

      That explains a lot.

      When you do it it's obvious and everyone should know, but when 'they' do it it's not obvious.
      You need to think about your ego and expectations a little. It will do you good.

      "I think far too often "Josh" might simply be getting mud slung his way due to him being an ass."
      There, fixed that for you.

      Sorry, couldn't resist after reading your sig.
      Yeah, and I am scared of being 'Dealt with' from someone like you~

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  124. Really. by tthomas48 · · Score: 1

    I don't think this is a "quirky" developer. A "quirky" developer is one who talks obsessively about Pokemon or has trouble making eye contact. Then again, I've met my share of sociopath managers too, so I don't think development is the only place you find them. Let's not confuse "quirkiness" with severe personality disorders.

  125. DRM by TheLink · · Score: 1

    Yeah, maybe Consultants should add DRM to documentation, so that customers can only have one copy and it's only viewable in a DRM infested viewer.

    And trying to break/bypass the DRM gets you slapped with the DMCA.

    --
    1. Re:DRM by egcagrac0 · · Score: 1

      That's a disturbingly sick idea that I'd love to milk.

  126. Even Medicine Involves Teaching and Standards by Parker51 · · Score: 1
    Of course, one of the other ideas House conveys is that is possible to manage the mavericks.

    Also:

    • Medicine is a complex, experience-dependent, field where you learn how to be a good doctor by doing actual clinical medicine and collaborating with others. Even quirky experts are expected to teach, show, and actively involve the next generation of interns.
    • Medicine has overarching professional standards, including stringent practices for safety, hygiene, and record-keeping, that no one is above, not even the quirky experts.
    • Even the mavericks understand that the goal is not feeding your own ego and sense of self-importance, or just working on intellectual exercises that interest you, but looking out first for the health and welfare of the patients (i.e., the customers).
  127. Reiser Drop down menus should've had an OK button by davidwr · · Score: 2, Funny

    Drop down menus should come with an ok button

    Slashdot doesn't allow pictures, but this is what I imagine is one of the drop-down menus on Reiser's last computer:

    Action->
    *Open sandbox for ReiserFS improvements
    *Edit documentation
    *Kill wife

    He meant to edit the docs but his finger slipped.

    An OK button would've really helped a lot here.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  128. That's a con man by Animats · · Score: 1

    There were times when they were the only ones who could solve a problem that could have cost the company millions of dollars. Of course, most of those times were the result of code they designed or influenced in the first place.

    That's not one of the "great developers". That's a con man. Obnoxiousness when challenged is typical con man behavior. It's a manipulation tool.

    In a long career, I've met many of the "great developers"; including many big names that are in the textbooks, and dozens of others at the top of the field. None of them act like assholes. I'm talking about MIT/Stanford/CMU/Apple/Sony/IBM Research people. Some can be difficult to deal with, and a few have real trouble explaining their work because they get too wrapped up in their own theoretical niche. Some of them don't suffer fools gladly. But none of them are jerks.

  129. Programmer needs to grow up, business needs a pair by drmike0099 · · Score: 1

    We have a couple of programmers like this, and I can tell you, they pretty much all wind up like Josh if they're bad enough. The problem is that their antisocial behavior results in huge sections of code, even within a "group" project, that only they understand. Over time, that means they become more "valuable" only because they're the only ones who know the code, and as such they tend to develop seniority, which makes them even more dangerous as they implement their craziness elsewhere. They also drive away other more reasonable and often just as competent developers, who themselves can't tolerate how mgmt tolerates the crazy in their midst, and elevates them despite them not doing the right thing. It's a vicious cycle.

    In other words, both the developer and their manager are at fault. If that dev, at the age of 22 fresh out of college, had been told within a month of their first job that they could change their behavior or be unemployed, most would have changed. The ones who wouldn't or couldn't would be (and should be) unemployed, and living in their parents' basement working on some open source project. Not doing so is the classic short-term gain at a long-term cost, and managers need to look at it in that sense in order to make the proper business decision. Sometimes that makes sense, but most times it doesn't.

  130. False assumptions. by kumma · · Score: 1

    I have not experienced any correlation between ingeniousness, quirkiness and the behavior of the management.

    1. Re:False assumptions. by gx5000 · · Score: 1

      Ditto...

      Assuming you believe all the hype from a few stories, most oddballs are just that.
      Most of the brilliant ones can pass any etiquette test, and knows a salad spoon from a spork.
      But assuming management bears them out ?! surely you jest. Isolated cases...

      --
      End of Line.
  131. Re:Josh is payed to do his job, not to be a great by DaveV1.0 · · Score: 2, Insightful

    Josh is paid to do his job. Part of the job of a programmer is to work with others. Part of most people's job description includes things about hygiene, appropriate work behavior, teamwork, etc.

    If Josh's coding results in ten thousand lines of spaghetti code with no documentation and riddled with single and double character variable names that result in other people not being able to do their jobs, then Josh is not doing his job.
    If Josh and his office smell like a pile of garbage, he is not doing his job.
    If Josh is saying offensive things to people, he is not doing his job.

    In other words, Josh is not doing his job.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  132. We all have a bit of Josh by SpaghettiPattern · · Score: 1

    Here on /. we probably all have a bit of Josh in us. In the way that we know more stuff than others because we probably care and because we can be arsed to read a manual once in a while.

    Nothing bad in that. Except that the Josh in you should grow up and accept that documentation HAS to be written. Eventually you might wind up actually documenting by default, generating man pages, Javadoc and understanding/writing technical architecture documents.

    Regardless how brilliant you are, tedious things like documenting you'll have to learn.

    Rudeness is a symptom of hiding insecurity. (Then even brilliancy may be driven by insecurity.) Rudeness is IMHO never excusable. I take the Josh in TA isn't likely to be rude to his bosses.

    I bet the outfit Josh is working for doesn't give dick about a tiny bit of quality (write doc, know where they are, know who should be informed, check documenting is actually done, etc...) That's probably because quality costs. I take a long shot in saying that management most likely knows they are not paying for quality and that eventually when Josh leaves they'll get a new Josh.

    In Josh'es defense: Some time your coworkers don't even know how to read basic documentation and even if everything is around they still find something to complain.

    More likely though, if you start digging into his code you'll find it's horrible and that you shouldn't touch the system with a barge pole.

    --

    I hadn't the slightest objection to his spending his time planning massacres for the bourgeoisie... (P.G. Wodehouse)
  133. OutsideTheBox by Anonymous Coward · · Score: 0

    "and could churn out code that saved the company millions, but can we please stop enabling these people?"

    LMAO! Stop enabling them? They save the company millions, fuel our economy, and make our world a better place. It's fools like you who are the problem. You don't STOP ENABLING brillant. You help them. You surround them with people who can take care of all of that tedious garbage. Get them a GOOD manager and a team-mate or lackey.

    A good manager will ensure that that brillant coder isn't wasting his time filling out time-cards, going to company staff meetings, or documenting his code. He'll make sure all that's taken care of by SOMEONE ELSE. I know it drives all you in-the-box detail-oriented, task-driven, order-mongers crazy, but some of us actually thrive on a bit of chaos.

    Suggest you go check out Meyers-Briggs. We wouldn't get much of anything accomplished without some order....but it wouldn't be any fun without some chaos. You take care of everything "in-the-box", we've got the rest covered. My wife pays our bills, makes sure the trash can goes down on whatever day is trashday, that I remember to go to work, and that I actually wear pants when I go. I do brillant stuff that earns big money and try to remember to eat.

    We aren't "quirky", we just think differently than you do. I'm lucky enough to have some people that value my skills and thought processes enough to make some accommodations, just as I do my best to try to accommodate their "quirks"...like believing:

    1. that you need to answer a phone just because it rings
    2. that it's ok to interrupt a thought process just because you want to go to lunch
    3. that the amount of time spent on a thought has some correlation to its value
    4. that shoes are somehow necessary
    5. that pointing out inconsistencies or lies is rude
    6. that a person in a position of authority has some inherent right to greater respect than anyone else
    7. and finally, that if it is inside of one of your boxes, a thing is inherently "good", while anything that is outside one of your boxes is inherently "bad".

    Ask a in-the-box what he wants for lunch, and he'll pick a choice from his list.
    Ask a outside-the-box what he wants for lunch, and he'll tell you the thing he doesn't want. Everything else is still on the table.

    STOP trying to stuff us in your little box.

  134. Shoe: other foot by Anonymous Coward · · Score: 0

    Pfft. This myopic BS never fails to cracks me up.

    If you do some research you see Mr Speigel's firm is a Microsoft certified partner.

    Fsck be me backwards. Microsoft was FOUNDED by a "Josh".

  135. it would have been humorous... by buddyglass · · Score: 1

    If he'd chosen the pseudonym "Joel" instead.

    1. Re:it would have been humorous... by Anonymous Coward · · Score: 0

      And accurate.

      The universes biggest douches, in order:
      John Edward
      Joel.
      Douche.

  136. And they all work here by Anonymous Coward · · Score: 0

    Wow - we have a jar full of nuts where I work.

    Now, I'm not completely brilliant, nor am I 100%, but you can bring me out into public.

    This is opposed to:
    1) NRA guy. You know him - he's the lifer with the NRA. He's the guy who thinks that if you can't kill and process your own meat, you're worthless. He's also the one who wants to see anarchy reign.
    2) Testicle grabbing guy. He can't keep his hands off of his junk.
    2a) Itchy Testicle guy. This guy is famous, for he's mentioned in Cube Farm. He once humped a 1/2 wall in front of a co-worker.
    3) ADD guy. This is the guy who will interrupt a conversation to type something into his IM session, or pick up the phone, or send an email.
    4) Jackass guy. You can't TALK to this guy without getting insulted. He's so brilliant, he's not afraid to tell you. We have a bunch of those guys here. Thing is, they just aren't that bright - it's more through sheer force of will that they get stuff done.

    Ugh. This is why work sucks.

    I wish more CEOs read 'The No Asshole Rule.' Perhaps we'd get more things done.

    Until then, I'm
    6) Keeping my head down and trying to be invisible guy. Contribute, just don't get caught.

  137. Re:These guys are all right. by Weaselmancer · · Score: 5, Insightful

    Yeah, I was all angsty in my 20's too. I had long frizzled hair and wore an army jacket with patches all over it, and hated the world and all the stupid morons in it.

    I'm now in my 40's. I have a haircut, I'm sitting in an office cube wearing a polo shirt.

    And I've got some news for you. It's *all* pointless. The end is the same for everybody. We're all worm food. Doesn't matter if you rage against the machine or oil its gears. In a hundred years, I promise you it won't matter one whit.

    What does matter is what you do with the time your have. And I'll say this - I'm happier now at 40 with a nice job, nice house, nice car and a family I love dearly - however boring and polite it may be - than I *ever* was at 20 running around rebelling against everything mocking the stupid sheeple.

    My advice would be to take whatever brilliance you may have and apply it to your own life, if you're able. Solve your own problems. Find whatever happiness you can. Because sitting around picking at your own wounds to keep them fresh doesn't do a single bit of good.

    I have friends who never "sold out". They're miserable. Most are too poor to fix their missing teeth. If you sit around and tend a harvest of misery your whole life, then that will be your reward.

    To sum up, life only sucks if you work at making it suck. Let it go.

    --
    Weaselmancer
    rediculous.
  138. Re: brilliant and dangerous? by Greg_D · · Score: 4, Insightful

    They should be recognized as douchebags and fired on the spot.

    Proper management and planning means you don't need a Josh on your team. The guy should have been fired before he was ever allowed to become so integral to their solutions that getting rid of him would mean pain for the group.

    There are very few irreplaceable workers in this world, and none of them work on code.

  139. Workers Unite! by mediis · · Score: 1

    So an individual who vastly outperforms all other workers, and who is solely responsible for making that company money, is kicked out the door because of what? Because others can't read code? Not for work performance, which is what he was hired for, but for smelling bad and having a bad attitude? If that was such a problem why wasn't it in the dress code? I thought we were supposed to tolerate diversity in the workplace? This is another example of the left wing liberal commutarians destroying the individual's ability to function!

  140. Re:These guys are all right. by Eunuchswear · · Score: 2, Insightful

    Only sheeple use the word sheeple.

    Baaa.

    --
    Watch this Heartland Institute video
  141. thoughts on Josh the Example by wardk · · Score: 1

    1. he was NOT the genius they thought he was, just because he knows more than his customers doesn't make him anything more than smarter than non-techies

    2. looks like he wrote shitty code

    3. he's an asshole

    Josh and his company needed one thing to happen so be successful, fire his ass at the first sign of idiocy. refuse to help your team, gone. treat a customer like shit, gone.

    the problem with this story is clueless and spineless management letting a bad situation escalate.

    Josh was a moron, not a genius. rename the thread appropriately.

  142. Sounds like a few of my ex-coworkers by Orion+Blastar · · Score: 1, Interesting

    except I was the one that debugged their "sloppy" and "crappy" code that while brilliant, had crashed the PCs and servers 12 times a day.

    Eventually the extra stress of working on spaghetti code with no comments or documentation or flowcharts gave me a lot of stress and I got sick on the job, and then eventually fired for being sick.

    Now I don't have a job since 2002 and the Brilliant but sloppy and crappy coders still have their jobs and promotions and pay raises.

    Why does management like them? Because it takes one to know one, jerks like or love other jerks. In order to break into management, one has to become a jerk to their coworkers and underlings, or else they cannot manipulate them into doing work. Then when they offload the hard work to their coworkers, they are considered to be delegating work. All I got was insane puzzles to figure out from coworkers who were considered brilliant, but didn't know how to do quality control, secure programming, or even standard programming. Just sloppy code, crappy code, that was one big mess that coworkers like me had to clean up after.

    --
    Remember, Slashdot does not have a -1 disagree moderation, and no, troll, flamebait, and overrated are not substitutes.
  143. The real issue is productivity by iPaul · · Score: 1

    If there's anything that most business fail to do well, is realize who is a productive engineer. If an engineer does it in a couple of days, but only he understands the solution, is he more productive? What if the engineer takes two weeks but then any other engineer in the department knows exactly what they did and can maintain their work?

    What about the engineer who is a framework guru that needs six weeks to build the frameworks for the project, so they need to only spend two weeks on actual problem specific coding? Is that more productive than the engineer that looks at the same problem as a "one-off" and does it in three weeks without building the frameworks?

    So Josh is productive, but what happens what Josh leaves? We used to use a metric called the bus count. How many people would have to get hit by a bus before we lost all institutional knowledge of how something works. The bus count of 1 means you are up s**t creek if the one developer leaves.

    I've met people who were rock stars and could document everything they did. They could play well with others and be smart. Having someone with serious skillz but unable to communicate and work with others (keeping the bus count at 1) is about as useful as a likable person that can't code.

    The difference is that we tend to, on a gut level, respect competence more than incompetence, but working with others is a kind of competence. So, at some level, we have more sympathy for someone like Josh, as does management. In the long run, however, Josh can't fix all the problems, Josh can get hit by a bus, or Josh could just decide to go off and do his own thing. In any case, letting Josh get that much control was a management, not Josh's, failure.

    --
    Leave the gun, take the cannoli -- Clemenza, The Godfather
  144. Are crappy programmers who are assholes quirky, or by wardk · · Score: 1

    just assholes?

  145. Bureaucracies and software development by coats · · Score: 2, Interesting
    Qualifications: I'm a software systems architect with over twenty years experience in environmental supercomputing. In that time, I've seen a lot of screwed-up code and screwed-up systems.

    In that time, the worst screw-ups have been exclusively codes developed in bureaucratic organizations.

    It seems to me there is a personality type that is in love with structure: it doesn't matter whether the structure is appropriate or not, just that it proliferate. This leads to codes that are not merely baroque, but positively rococo. And this is the personality type that flourishes in bureaucratic environments.

    The first principle of software engineering is Occam's Razor, more flippantly stated nowadays as "Keep it Simple, Stupid."

    My experience says that the lessons Kernighan and Pike teach in The Practice of Programming are de-valued in development-bureaucracies. And DeMarco was right-on in The Deadline about that subject, too.

    --
    "My opinions are my own, and I've got *lots* of them!"
  146. saved the company millions by l3v1 · · Score: 1

    can we please stop enabling these people?"

    Uhmm, no? It's millions. What's a few perks in comparison? One just needs to find the right place for them, to be at hand, should such problems arise again.

    --
    I am putting myself to the fullest possible use, which is all I can think that any conscious entity can ever hope to do.
  147. Writing... by EddyPearson · · Score: 1

    ...genius code is not that hard.

    It's very easy to use your own style for eveything and reimplement every existing toolset because "you know best". You can heavily over-engineer every library you write. You could do something outlandish like creating a custom scriping language for you business logic. Academically clever it may be, but it's totally wasted in any production environment.

    What's hard is writing good, clean, concise (yet not obfuscated) code. It must well structured and sensibly designed. Not just so that you can maintain it, but that everybody can. The kind of code that'll convince subsequent devs follow YOUR example, rather than come up with their very own individual "clever" style and fuck it up for the next generation.

    "Genius" code isn't that clever. Genius devs write code that that even the least talented there can comprehend.

    --
    You feel sleepy. Close your eyes. The opinions stated above are yours. You cannot imagine why you ever felt otherwise.
  148. Code comments as documentation by justfred · · Score: 1

    You're right, but the thing is, you can see the value most developers put in comments, in the quality and emphasis that programming languages put on comments. At best they're an afterthought, implementing what other languages have done before. I've never seen comments done "right" so I end up doing it myself.

    I currently write in html, php, javascript, css, perl, sql, and command line script. Comments are supported differently in each. CSS is particularly awful, only supporting /* */ and including it in code-weight.

    (mini-rant)
    There are many types of comments.

    To begin with, there's code-header comments - program name, change date, inputs and outputs, platform, etc. I used to program in COBOL and these were mandatory. In some languages this can be used to autodocument.

    There are declarative comments - the kind you usually expect. They tell what a function or program section should do.

    There are temporary notes and to do comments - "remember to change this so that it won't fail if we get a negative", etc. I use #! and #? for these (or /* #!yaddayadda */ if # isn't supported).

    Then there's comment-out: places where I leave the previous code in for a while so I can see what I changed. If I can I put the # in the left column for these; wish there was a whole different symbol for it.

    Finally, there's well-formed/best practices code as its own "self-documenting" - but that does not substitute for good comments.

    (here's my blog rant)
    http://www.obtainium.org/index.php?option=com_content&view=article&id=234:250&catid=7:programming&Itemid=2

    1. Re:Code comments as documentation by tedrlord · · Score: 1

      Self-documenting code is ideal, as long as it also includes comments.

      --
      [insert witty quote here]
  149. One causes the other by MythoBeast · · Score: 1

    These people wouldn't be dangerous if they weren't brilliant. It's something called "the aura effect". When someone does something well, everyone starts to think that they do everything well.

    I've seen people like that ruin entire departments. They can code like a demon and produce spectacular and extremely functional software. They do great things and then move on to the next project. They start to form a following, which adds to their notoriety. Small religions form around them.

    And then some poor schmuck is handed last year's effort to make a few minor adjustments and finds that it's thoroughly undocumented and uncommented. The call structure averages thirty functions deep, there are more interfaces than there are classes and as many classes as there are functions. Everything is extremely efficient because there is no segmentation of functionality, and subsections have no clear interface boundaries. But because this person is such a great corporate asset, said poor schmuck has absolutely no traction with management in terms of calling attention to this.

    More years go by while the superstar wraps entire departments around their coding habits. Great chunks of the company's IP are written in this person's style because he's become a shining example of how things should be done. Maintenance costs go through the roof until enough software engineers with a clue point out these problems and insist on policies that address these problems, and major projects have to be initiated to rewrite huge chunks of existing incomprehensible spaghetti code.

    At which point our shining primadonna takes his experience and awards and goes and finds a job with a fat salary in some other poor company.

    --
    Wake up - the future is arriving faster than you think.
  150. Re:Football on Slashdot? TO? by fleebait · · Score: 1

    Ok, I'll bite, what's a TO -- sounds like someplace to send e-mail

    (this should probably be rated -2)

  151. Sounds like Darl McBride, doesn't it. by Anonymous Coward · · Score: 0

    But it's only the rank and file that are egomaniacs that must be replaced.

  152. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  153. Documentation Lacking? by kenp2002 · · Score: 1

    Developers are becoming resistant to documentation as the lack of documentation affords more job security. Better documentation = easier to replace the original coder.

    It really is that simple.

    --
    -=[ Who Is John Galt? ]=-
    1. Re:Documentation Lacking? by swordgeek · · Score: 1

      This is a sign of inexperienced and/or paranoid developers.

      Good developers will know that writing good code and documenting it correctly is job security of another sort--companies who WANT to keep you or hire you, not companies who are forced to do so. Ultimately, undocumented code will be rewritten from scratch by someone else, and the original programmer will be fired.

      Do your job to the best of your abilities--always.

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
    2. Re:Documentation Lacking? by kenp2002 · · Score: 1

      Nonsense. Absolute nonsense.

      "Good developers will know that writing good code and documenting it correctly is job security of another sort--companies who WANT to keep you or hire you, not companies who are forced to do so. Ultimately, undocumented code will be rewritten from scratch by someone else, and the original programmer will be fired"

      You are making the assumption they'd keep the original coders around for maintenance. I've never seen a senior developer retained for maintenance programming. They're converted to consultants and I have never had to call back an original coder when the documentation is good. So much for job security. I hate to break it to you but businesses pay people to WORK not sit around. No work, no pay. I sure as hell wouldn't pay someone 74 grand a year to put in 40 hours of maintenance per quarter. Once the first release is done he's either going to head a new project or he's out the door. Man where do you work? They have money to burn?

      I hate to break it to you but there are plently, in fact a GLUT, of good programmers. Being a great programmer with good documentation skills means you get brought in to code the first release then promptly shown the door once it's gone into maintenance phase.

      Programmers are a dime a dozen now. Thanks to open source their free now too.

      I can bring in a "great programmer" on a project at $74-76 grand a year. I keep him for 6 months, make damn sure he does great documentation and after the second quarterly release I show him the door and hire two new grads at $31k a year to maintain the code and save myself $10 grand. At 3% annual raises I still come out ahead by notkeeping the original programmer around very long and I get 2 people instead of one. A few years later when they head the next project, out the door they go and wash rinse repeat.

      The smart programmers do good documentation but not enough to make it too easy for the maintenance programmers. That way at least they can squeeze some consulting time out.

      If your logic held fast cars would last for 30 years and toasters would last a lifetime. It cutthroat out there and it's only going to get worse for programmers. Hell I have a niece that already learned C++ and she's in the 8th grade. The bar is getting pretty high now for programmers. It's almost on the verge of being a basic skill (programming in at least 1 language).

      Programmer, meet Mr. TV repair man. You have a lot in common now and say hi to the Help Desk folks when they get in.

      Employees are an investment.

      Mr. $75 grand a year will get 5% more productive but will want at least a 3% raise. I'm only getting a 2% return on investment.

      Mr. $31 grand a year will get 15% more productive, take 4 years to be as good as Mr. 75 but with a 3% raise I'm getting a 12% return on investment.

      You keep senior people because you have to, not because you want to (Barring personal feels etc.). Productivity gains taper off and factoring inflation you have to be ruthless in looking at productivity or your gonna get buried. It's why we outsource. Better return on investment in an employee.

      I can go to some locations and get a damn good programmer for $1.88 an hour making him wealthy in his home country. He's not as good as the local guy, in fact he's twice as slow BUT the local guy is $44 an hour. I can hire 8 of the cheap guys putting me time table wise ahead by 4 fold, still under 1/2 the cost and know I've help 8 people become wealthy by thier local standards. In 4 years they'll be as good as the local guy and I've gotten a massive return of investment in my labor. Then I cut them loose and start over.

      Job securty is the result of necessity not some idealogical committment to excellence. The mantra is Better, Faster, Cheaper. If you are not NEEDED, you aren't. Business doesn't deal with WANTED, we deal with NEEDED. We hire people and keep people because we NEED them, we don't hire people because we feel like it, we hire people because we NEED them.

      BETTER: Employees are investments, you want a good return
      FAST: If a project takes 2000 hours, you need more people working 8 hours each to get it done faster. That means they have to be cheaper.
      CHEAPER: Withou compromising BETTER and FASTER it needs to be cheaper.

      --
      -=[ Who Is John Galt? ]=-
  154. Really? by gillbates · · Score: 1

    I sincerely doubt you are more than 160 times more productive than an average developer...

    Perhaps he's not managed by the *average* large-corporation manager. Trust me, I've seen changes that would have taken me a day to complete end up stretched over six months because management is clueless and obstructive. You can take my personal experience with a grain of salt if you'd like, but there's probably a 10 to 1 ratio of performance between coders in the same organization. Combine this with the fact that management can obstruct or enable productivity by two orders of magnitude (again, personal experience), and it is easy to see how some developers are 1,000 times more productive than others. For the GP to be 160 times more productive than average, he needs be nothing more than a lower 20% coder in a company with good management practices.

    --
    The society for a thought-free internet welcomes you.
  155. Re: brilliant and dangerous? by Kell+Bengal · · Score: 5, Insightful
    I've been in exactly this situation: we were an custom GPS electronics company where one very talented electrical engineer built the hardware from the ground up (and he and a whole team of software guys did the code). I signed on as his lackey to do additional electronics development on the side because his time was 'so valuable' and they needed more stuff done besides

    .

    The -very- first thing they had me do when I arrived was produce page after page of documentation on how the hardware actually worked so that the software guys could understand it. It wasn't ground-breaking design, it wasn't super complicated, but it was subtle and you couldn't get the whole idea of what was going on without being able to speak Engineer (specifically the EE dialect). A lot of people in the company were terrified that he'd walk out one day and get hit by a bus and the company would have to spend a fortune it didn't have for a team of engineers to come in and tell everyone else how their own system worked.

    When I asked him why there was no documentation (or very poor documentation when there was) the answer was a combination of "You shouldn't need documentation" and "I'm not paid to document things."

    Well, actually... you are.

    A few early experiences counseled me very strongly to enforce good documentation practices in my code and hardware design. Any design more complicated than a blinking LED (the hardware equivalent of 'Hello World') requires it - if you aren't documenting, you're not doing what you're paid to do. As TFA says, End of Story.

    --
    Scientists point out problems, engineers fix them
    altslashdot.org: The future of slashdot.
  156. If he is an asshole, fire him. by master_p · · Score: 1

    And never hire assholes again. It's that easy.

  157. I feel like there is a basic truth missing... by mykepredko · · Score: 1

    I've come across several Josh's in my career and they have been labeled as geniuses simply because they did something first in a company. All it takes to be recognized as a genius is to get a product off the ground and "good enough" that somebody will buy it.

    From there comes the rewards and the swelled head and the feeling that they are geniuses. The rewards come from PHBs that don't understand that what they did was all that special.

    Right now, my team is rewriting an application written by a "genius" that is not documented, no comments, variable names were written in Hungarian (the guy who wrote the code is in Mississauga, Ontario, Canada), what does work is crappy and there is a lot of functionality left out (with the comment saying that he has shown the way so we can replicate it for the missing features). The code looks like a drunken monkey wrote it with no regard to conventional (or even consistent) indenting and spacing. Asking for questions just gets a reply like "Josh" and complaints from his manager demanding why we can't hire competent developers because he is too critical to the business to support us.

    The one genius I have met from a start up, made sure that there were coding standards, insisted on documenting everything and put in place test requirements. When he left, nobody had anything but good things to say about him - and his peers (the people who matter in the long run) regard him as a genius.

    myke

    1. Re:I feel like there is a basic truth missing... by SuiteSisterMary · · Score: 1

      I think I know who you're talking about.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
  158. *sigh* It doesn't have to be that way. by seebs · · Score: 1

    I'm one of those fairly bright, fairly quirky, sorts.

    A while back, one of the managers explained to me in engineering terms how it is useful to other people if I explain what's up, give them status information, warn them about possible deadline problems, and so on. And I spent some time reading about, and writing about, usability. Net result? I'm still weird, I still occasionally say things that are offensive -- but my coworkers appear to like me and I cooperate well with others.

    So far as I can tell, the problem is often simply that no one has explained why this matters. Seriously, it's not always obvious. I have warned my coworkers that I have a clinical diagnosis of a mental disorder, and that if I say something offensive it's probably not intentionally-offensive, and they cut me a bit of slack -- but I do make an effort to avoid offending, because it's just common courtesy and all that.

    --
    My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
  159. Re:Not worth it - for the developer either by Anonymous Coward · · Score: 0

    As a developer, being this person (thoughts about hygiene aside) is no great deal either. I've been the position far too many times where I'm the go-to guy for a system that I worked on / lead the development of. Initially it's flattering because being that guy means that people recognize that you know what you're doing and can perform when it comes down to crunch time or when stuff hits the fan. After a while of getting pinged after hours or on weekends, your perspective changes and you make sure that you've got a back-up who can share the wealth. Can honestly say I've always put together decent documentation and worked with others on the implementation to make sure that everyone has a good feel for the system (that's part of my job) but now it's more of a focus to make sure that I'm not the only one whose cell phone rings in the middle of the night.

  160. Re: brilliant and dangerous? by Dark+Coder · · Score: 2, Interesting

    Try hiring ANY decent coder that works with my former boss's highly impossible deadlines.

    I'm with previous parents. A good fire extinguisher (Asperger's) is handy to have. Deadline gets met, even though the end-result (support and maintenance) sucks.

    Most start-ups are in it for a quick and lucrative exit strategy (post IPO-sale).

  161. I use to be a josh by ghinckley68 · · Score: 1

    Yes I was and still am. I did learn some people skills though along the way. But let me tell you there are coders and then there are programmers. Josh and my self or the latter. 99% of coders out there could not program there self out of a box with 3 of its sides missing. Its not an insult it is just that they can not see the logic in there head. That is why they need to flowchart/entity diagram/what ever the problem is to death and then sit around and discuss it with a team.
    Programmer like me and josh just sit down and start typing.
    Yes there is a place for us. We are the clutch player the guy you go to in the endzone with 35 seconds left on the clock for the win in the supper bowl who are inches from the sideline but stick the catch and keep both feet in bonds.
    We are not the guy you go to on second an short on the 50.
    Are we premodans yes, one company I worked for made me and engraved sign that said "Go Away Programing" and sent a memo out that all employees had to sign say that if the sign was on my office door they were to leave me alone. Hell the owner of the company though twice about bugging me.

    Any way in any field you need people who you go to when it absolutely has to get done. This is why we have navy seals, doctors like House and yes they exist, and Santonio Holmes. Are we irreplaceable no, but we are less replaceable than most.

    Josh/Glen

    --
    Linux modi 2.6.26-2-parisc
  162. Re: brilliant and dangerous? by fugue · · Score: 3, Insightful

    Because there are a lot of good people who can do the work and better and be a company player too.

    Um no.

    The article was about someone who can do an incredible amount of coding in a very short time. Indeed, more coding in less time than most anyone else.

    It isn't that they weren't smart. In every case, these "great" developers were the most talented in the group. Their intellectual abilities and problem solving capabilities were unparalleled.

    Obviously, if there are a lot of people who are equally fast and one can't work with teammates, then fire the asshole. But that wasn't the question. The question was how to deal with one asshole who can churn out more code faster than everyone else. You can tell me you're as good as anyone else until you're blue in the face--in which case your employer is lucky to have you--but that's not what the article was about. It was about someone who was much better than you (for a certain very circumscribed--but potentially useful--definition of "better").

    Sure, if you spent sufficient time and money, you could find someone better than Josh. And ideally you do. There's always someone better on the market, out there, somewhere--especially in this economy. But if you have a limited budget for finding and hiring the best of the best, then an acceptable compromise is learning how to use the people you have. Understand what he is, and isn't, good for, and offer him what he's worth to the company. And learn to use him wisely.

    --
    "The biggest problem with communication is the illusion that it has taken place."
  163. A sad story by kilodelta · · Score: 1

    At my last job we in I.T. were getting deluged with requests that weren't normal help desk issues, like db design, web apps, etc.

    One day when my director was lamenting this I asked if we could meet up later on.

    I told him about project management. He seized on the idea and we put together a great process.

    If a help desk ticket was to take more than 4 hours to resolve, it became a project. Project ID was the help desk ticket ID.

    We then would go out and get the requirements and then develop from that. Tracked everything in dotProject.

    More to the point we got senior management buy-in by letting them prioritize.

    That all ended when a new administration came in, and I left 9 months later.

  164. It's also about understanding how to use people by Anonymous Coward · · Score: 0

    My brother is something of a genius programmer with a number of Josh like qualities, but is still very useful to a team. Part of the trick is to understand how to use people like this:

    Don't expect the geniuses to slow down to the average speed. At one job, when he tried to quit because he wasn't learning enough, but his boss talked him into coming in one afternoon a week to talk to the other people about their work, for the same pay. The office started organizing itself around his visits. If someone was stuck on a problem, after thinking about it for a week they now understood it well enough to talk about it at his level. If someone had a general design, his review and okay was enough to convince people that the design was sound and allow them to move forward confidently. According to his boss, the office had never been more productive.

    Measure the output if you really want to understand if someone is worth the hassle. At one job he went missing while trying to think through a problem so I ended up talking to his boss who told me that this type of thing made him "worse than useless", to which I simply replied that it wasn't true or we wouldn't be having this conversation. Two weeks later when he returned he had finished designing a system which took him less than a day to code, and is still the only part of the code that has been kept in four complete rewrites of the rest of the system. By his bosses own admission that code, which can do things that none of their competitors can, has made the company many million dollars.

    Never rely on a genius -- accept that lightning doesn't always strike and plan projects so that brilliant solutions can be dropped in. At his current job he gets given projects that involve making dramatic improvements on the current state of the art (or in some cases the theoretical limits), but always as a well defined component of a larger project. If the interfaces are well defined, no one else needs to understand how the black box works. Pushing the limits means that you don't have a safety net to rely on, so failures will happen -- either accept the occasional failure (and plan accordingly) or accept constant mediocrity (like most business do).

    For documentation, the trick that works for him is to not do it, instead follows a few rules:
        Define the interfaces well and enforce them (asserts are a great tool when trying to prove to someone that what you passed was correct, but what they returned wasn't).
        Make sure every function clearly describes its function (ideally in its name, but in comments if necessary).
        Code everything in the simplest possible way first and don't care about efficiency.
        Write progressively more clever and efficient versions of each function.
        Leave all the earlier versions of the code in place as the documentation for the more clever functions.
        If in the future someone really can't figure out the assembler, then let them comment it out and go back to an earlier C version.

  165. Fixed it for ya by DevConcepts · · Score: 1

    In short... it is only mutually exclusive if you are in a room full of a bunch of business MBAs who apparently as a whole still think that solutions come out of some magic hat somewhere...

    room full of a bunch of business MBAs who apparently as a whole still think that solutions come out of some magic asshat somewhere...

  166. Brilliance is a three-edged sword? by fugue · · Score: 4, Informative

    They should be recognized as douchebags and fired on the spot.

    Sounds like you want him fired because you don't get along with him. Perhaps you're jealous of his ability, such as it is? You needn't be--a good coder who can work with people is generally far more useful than a great one who can't.

    Proper management and planning means you don't need a Josh on your team.

    Proper planning means you'll anticipate every eventuality and be ready for it, which is of course impossible given that outside factors are basically random.

    The guy should have been fired before he was ever allowed to become so integral to their solutions that getting rid of him would mean pain for the group.

    You're confusing two issues here. He should clearly not have been allowed to become so integral to a sustainable solution, since he fucked up any hope of that. Firing him is one way to keep him from becoming integral to long-term solutions.

    You might just as well advocate firing any manager who lets a Josh become involved in long-term projects. That would be just as correct. Clearly there are things Josh shouldn't be doing. A good manager will see that.

    Actually, I like the idea of keeping Josh around just in order to test new managers. If they can't figure out how to use him effectively, fire them. He could be a truly invaluable resource to the company even if not a single piece of his code ever gets executed.

    --
    "The biggest problem with communication is the illusion that it has taken place."
    1. Re:Brilliance is a three-edged sword? by ukyoCE · · Score: 1

      re: Planning, the claim here and perpetuated by the article is that there are OMG RIGHT THIS INSTANT problems in programming. There aren't, unless you're a small programming shop that doesn't follow relatively basic practices like version control and QA'd releases.

      re: Managers, I would advocate firing anyone who hired a Josh. And if I came into a company, I'd also advocate firing any managers who let a Josh stick around pulling this kind of crap. In my experience having Joshes around depends on having clueless managers who believe the kind of bullshit a Josh spouts. Or, even worse, a Josh got promoted to manager and likes to hire more Joshes (i've seen this first-hand)

    2. Re:Brilliance is a three-edged sword? by fugue · · Score: 1

      re: Planning, the claim here and perpetuated by the article is that there are OMG RIGHT THIS INSTANT problems in programming. There aren't, unless you're a small programming shop that doesn't follow relatively basic practices like version control and QA'd releases.

      If your QA team is perfect, then OMG problems are constrained to things like "our biggest customer needs this prototyped by yesterday". Stupid, but it does happen. Or do you advocate firing any client who makes such patently idiotic and shortsighted requests? :)

      re: Managers, I would advocate firing anyone who hired a Josh.

      Sounds like your experience is not with companies that could have put him to good use. I believe that that makes you lucky. I'd hate to deal with him, for sure. And a company with a Josh but without a manager who can keep him from doing damage is indeed screwed.

      --
      "The biggest problem with communication is the illusion that it has taken place."
    3. Re:Brilliance is a three-edged sword? by YeeHaW_Jelte · · Score: 1

      Preferably, keep him available as freelancer, or have a freelancing 'Josh' available.

      That way, you can quickly have something to show if you're competing with another company for a contract or if you're doing a one-off 'yes-we're-very-sure-we-won't-have-to-maintanence-this-ever'.

      However, if you're a small to medium sized company and you have need of a 'Josh' fulltime, you have a problem with planning and realistic deadlines and the need for Joshes is only a symptom.

      --

      ---
      "The chances of a demonic possession spreading are remote -- relax."
    4. Re:Brilliance is a three-edged sword? by Anonymous Coward · · Score: 0

      Proper planning means you'll anticipate every eventuality and be ready for it, which is of course impossible given that outside factors are basically random.

      So proper planning doesn't exist.

      Actually, I like the idea of keeping Josh around just in order to test new managers. If they can't figure out how to use him effectively, fire them. He could be a truly invaluable resource to the company even if not a single piece of his code ever gets executed.

      Or they could just hire me to replace Josh. I'm not a dick like he is. I'm very easy to work with. But with a little heads-up and maybe a company-paid lunch I can *act* like a dick to test the new managers.

      By the way, you are fired.

  167. Re: brilliant and dangerous? by trvd1707 · · Score: 1

    Usually after a couple week I figure out the flow and I am just as productive as the guy was before, except people are willing to talk to me. Ask questions and raise problems that the other guy made them to afraid to mention.

    Would you be able to figure out the flow after a couples of weeks if you didn't have Josh's code to look at?

  168. Maby the problem isn't them? by Steauengeglase · · Score: 1

    OK, first there was the story about the delusional college student and now the weirdo. What next, the annoying guy who keeps talking about last night's episode of The Office or the ungrateful Russian intern who won't go out with you? Maybe we could move on to the guy whose resume didn't quite match yours, but his charisma is obviously blinding your coworkers except when you guys are having a drink at the bar and chicks come over to talk to him.

    Seriously, what is with all of the "get off my lawn" or iron clad conformity stories on Slashdot? It does take all kinds.

    1. Re:Maby the problem isn't them? by DaveV1.0 · · Score: 1

      No, it doesn't take all kinds and this is not about "iron clad conformity". It is about basic civility, common courtesy, professionalism, and hygiene.

      If you believe it takes all kinds, then, by definition, you believe it also takes child molesters, rapists, and murders as they are part of "all kinds".

      --
      There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
    2. Re:Maby the problem isn't them? by Steauengeglase · · Score: 1

      There is a big gap between Jimmy smells bad and has serious social anxiety issues and Jimmy killed 3 people on the way to work and sexually assaulted a 9 year old boy in the hallway. If someone has problems like that I'm sure the cops will be in long before HR.

    3. Re:Maby the problem isn't them? by DaveV1.0 · · Score: 1

      That is not what you said. You said "It takes all kinds". Now, you are changing your mind and saying it doesn't take all kinds. So, I guess you were wrong and it doesn't take all kinds now does it?

      --
      There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
    4. Re:Maby the problem isn't them? by Steauengeglase · · Score: 1

      Fine, you win.

  169. Re: brilliant and dangerous? by jellomizer · · Score: 5, Insightful

    Having Asperger's isn't a good excuse to do a poor job or to be anti-social, or unprofessional. Yes you may have hard time following the right non-verbal queues. But things such as dressing appropriately for work, using the bathroom in the right spots, and a lot of the quarks that happen are due to bad behavior that people even with serious Asperger's can work one and minimize and be at a professional level. I don't take the idea, that I have a disability so you need to deal with my Crap mentality, it is basically reinforcing that they can behave badly, without having them work on improving themselves.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  170. I depends on their manager by trvd1707 · · Score: 1

    They can be brilliant, dangerous, dull, dumb or all together. If the manager is skillful enough, the whole team can benefit from the assets that everyone bring to the group

  171. Re: brilliant and dangerous? by shutdown+-p+now · · Score: 4, Insightful

    Except, cleanup (or re-implementation) never happens. What will happen is layer upon layer to work around bugs and problems. Because you can (almost) never justify to upper management that you need to reimplement something that works and the finish product is basically the same you started out with (with cleaner code, maybe).

    Agreed; which is why this statement from TFS: "... could churn out code that saved the company millions" - is nonsense. It may look that way on the surface, but when accounting for all the code maintenance pains that inevitably follow, I've yet to see a single such "genius" that wasn't a net loss. What's worse, the expenses are quietly swept under the rug, or, even worse, shouldered by the rest of the team who gets flak when they can't keep up with the "genius" (because they're cleaning up after him).

  172. Everyone has a place by mkcmkc · · Score: 1

    I sure as hell wouldn't want to ride in an airplane running Josh's avionics software, but if I was on a plane that was plummeting to earth due to avionics problems and Josh was on board, he might be the best candidate to try to save the plane.

    --
    "Not an actor, but he plays one on TV."
  173. we should al wear what we want. by cdpage · · Score: 1

    NO we can't/shouldn't. Stop trying to change people!

    Formal wear has no place in a 'working' environment.

    big business meetings included. you can tell a lot more about a person about what they wear... Think about it.

    1. Re:we should al wear what we want. by geekoid · · Score: 1

      NO you can't.

      Your just using dress to shove people into your misconceptions.

      Clue:
      A suit is not formal wear, a Tuxedo is.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  174. Re: brilliant and dangerous? by jellomizer · · Score: 1

    Yes. As if I didn't have his code When there was a problem I would have to rewrite from scratch every time something broke, or create a workaround for it. But for the most part as the users of the software has the process down it makes it easier to remake such software. Yes it will take a bit longer then a couple of weeks but it is doable.

    Having his code even if it is an utter mess and obfuscated to a massive amount will save time as I have something to work off of. But I have never came to a situation where when a "Josh" leaves I couldn't keep the company/software running, then improve it over time.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  175. Re:Football on Slashdot? TO? by bytethese · · Score: 1

    TO = Terrel Owens. Great player, but is such a hassle to have on a team he keeps getting dropped from teams he plays for.

  176. Re: brilliant and dangerous? by Anonymous Coward · · Score: 0

    "You are assuming that Josh's skills are irreplaceable." ... And that chess move is blocked by a previous post, ... i.e. "I'm always amazed by people who think that writing impenetrable code is "advanced""

    Its not "advanced", but it is (job) protection through obscurity. (I'm not suggesting thats a good or bad thing to do). More to the point, its not simply good or bad. Its not mutually exclusive. Rightly or wrongly it can be used (and I've seen it used) to help protect a programmer from redundancy (in the shorter term) as they are *seen by non-technical management* as indispensable in maintaining the code. Of course from a longer term perspective of code maintenance, they are building a house of cards, which becomes ever harder to maintain. Over the years, I've found not all programmers are as idealistic as I oftan am, with their work methodology or even their work ethics, but I can see why they do these things even if I don't always agree with their methods.

  177. Re: brilliant and dangerous? by jellomizer · · Score: 4, Interesting

    Software development is 40% technical and 60% people. Even though he my get twice as much technical done his bad people skills are affecting his usefulness, and still needs at least 20% people skills to be useful, however to balance him you will need to hire someone who is like 10% technical and 90% people skills just to support him. So you are in essence paying twice as much to get slightly less then twice output. You are better off with 2 people who can do 40/60 balance. As you will get twice the output without the risk.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  178. Brilliance != Obscurity by BountyX · · Score: 1

    I have a high IQ and this "Josh" is not brilliant. He is exploiting misconceptions of intelligence. I myself am not "brilliant" despite my IQ. All my life people had expectations that I would achieve all these grand things and that everything I touched was a "stroke of genius". Teachers and administrators always treated me as though I was "special". Students thought I would pass tests without studying, magically. Far from it. If anything, I learned how little intelligence really matters, especially when everything is instantly accessible.

    First of all, brilliance is not obtained through obscurity. Sure some obscurities may be brilliant, but not many are. Think about this mathematically for a second and you will understand how confounding it is. This brings us back to what intelligence actually is. Intelligence represents how fast a person is able to learn. This is DIFFERENT than knowledge, which is information retained through experience.

    In the case of computer programming, many of the tasks are repetitive; thus, great intelligence is not as important as having the knowledge, but still important in HOW you approach and analyze your problems. In this case, we see what happens when you have someone with lots of knowledge, but little intelligence. "Josh" indulges in the obscurities of his own knowledge but lacks the intelligence to quickly identify problems associated in a larger construct of connected factors ("the big picture"). He makes a number of assumptions that are based on his obscurity, not intelligence (or "relearn- ability"). Focusing on intelligence would mean focusing on making the learning process more efficient for himself at the benefit of others.

    He can create obscurities, but how fast can he find them? How fast can he put the puzzle together to get the big picture? How fast can he learn that his obscurity is creating problems, not solving them. He is just a failed rationality that represents how very little, we as a race, understand our own intelligence. An assumption that correlation is causation is the culprit here since his behaviors are correlated with intelligence, but he fails to obtain. This goes beyond "josh", we (as individuals) should challenge our perception of intelligence.

    --
    Trying to install linux on my microwave, but keep getting a kernel panic...
  179. code written for support by Anonymous Coward · · Score: 0

    I know of a successful software company that has saved much $$$ in support people wages by simply requiring programmers to 1) comment in plain english, such that anyone can follow the code without knowing the code language, and 2) limiting use of complicated-to-understand verbs.

  180. Re: brilliant and dangerous? by julesh · · Score: 3, Interesting

    Agreed; which is why this statement from TFS: "... could churn out code that saved the company millions" - is nonsense. It may look that way on the surface, but when accounting for all the code maintenance pains that inevitably follow, I've yet to see a single such "genius" that wasn't a net loss.

    The folks who do extreme programming have a metaphor for this; they call it "technical debt", and point out that if you don't pay your debt down pretty quickly after running it up, you're going to get into trouble. Generating technical debt, they say, is an inevitable consequence of programming. But good programmers immediately clean up at least most of that debt as soon as they've finished implementing whatever they're working on.

    The metaphor works. Managers are quite able to understand it, and it does seem to help in explaining what it is that's wrong with the kind of programmer we're talking about.

    (They also have something else that might help in this situation: pair programming)

  181. huh? by cat_jesus · · Score: 1

    What I mean is, yes, I'd rather have someone working for me who says, "I can get this project done in 2-9 weeks" and gets it done in < 9 weeks then, someone who says, "I can get it done in 16 weeks" and gets it done in 16 weeks exactly. 9 weeks is shorter, that's an easy call.

    Why would you have two people doing the same project, one after the other? That's really dumb.

  182. Re: brilliant and dangerous? by nabsltd · · Score: 1

    Except, cleanup (or re-implementation) never happens.

    And, then, if it does, nobody bothers to even think of asking for help from the guy who implemented the emergency fix.

    In one case, I was the guy that had to code like mad to get a database app finished. It was client-server before the web really existed, so it used a custom app on the client. When it was re-implemented later using ASP.NET, nobody even bothered to ask me anything about it.

  183. Wow, let it all out! by elloGov · · Score: 0

    LOL. This conversation has clearly become one big venting session for all that have dealt with that jerk of a Josh. When venting however, don't let it overtake logic and rational. Let's not hate good programmers :)

  184. Treat them right by sce7mjm · · Score: 1

    That is to say let them be brilliant and congratulate them on it, Especially when they've got you out of a tight fix with some rapid coding.
    Afterward when the dust has settled get them to go through their code and comment until another member of staff can understand it. Most people quite like explaining to other people how simple/elegant their solution is.
    It will encourage them to comment as they code so they spend less time explaining it to other people later, and let them get back to what they do best.
    Everyone wins.

  185. Viable companies by Maximum+Prophet · · Score: 1

    if you are running a viable business in the long-term.

    You've hit the nail on the head. The company in the story is probably not viable in the long term. Most of the people adding to this discussion seem to just want to tell everyone in the company, "Go home, your company is fubar." Real people won't give up on a sinking ship until it's too late. Management will stay with this asshole until he's dead or gone, and there's a good chance the company will fail after that.

    --
    All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
  186. Re: brilliant and dangerous? by 91degrees · · Score: 5, Insightful

    The article was about someone who can do an incredible amount of coding in a very short time. Indeed, more coding in less time than most anyone else.

    Because all he was doing was writing code. He took an hour to solve a problem that took the team 2 days. "The team" must have been at least 3 people. So that's occupying 6 programmer days. 40-45 hours. It would have taken him less than an hour to document or explain what the solution was. Is he really worth 40-45 times as much as the other programmers?

    If the guy produces a lot of unmaintainable code then he's costing almost as much as he's making for the company. His personality problems will increase staff turnover, and he will eventually leave. Nobody lasts forever. When he leaves everything that he wrote will have to be documented or replaced at considerable cost.

    Most programmers will be able to do most tasks. There are some highly specialised tasks that will require an expert in that area, but you can always find the appropriate expert. Anything else can be learned. You'll lose a developer for a few days while he learns but you'll gain a developer with extra knowledge, and the half decent ones will be happy to stick with a company that allows them to develop.

  187. i sit next too him by mr_musan · · Score: 0

    i can very much relate too this, one developer is a complete arss hole but he writes most of the code and is very smart so we alow him his ways as he too an extent allows us ours, but talk to him on monday and you had better have a spare head to replace the one bitten off

  188. All kinds of people by GWBasic · · Score: 1

    It takes a variety of people to accomplish large tasks. Often this requires putting up with peoples' shortcomings in order to take advantage of their talents. Management typically has to figure out how to work around each team members' shortcomings and/or how to improve on these shortcomings.

    I know I can be quirky at times; and I've had to work with quirky people. In all cases, it requires patience and empathy from all people involved. I've always told my teammates that the success or failure of a project ultimately depends on the quality of management; and not the quality of the individual team members. This is because management needs to guide interactions among team members; if the quirky guy is so bad that he's wearing offensive T-Shirts and taking dumps in the lobby flowerpots; it's just as much a failure of management as a failure of the quirky guy. The same can be said if "normal" engineers just can't write working code; it's a failure of management to recognize and rectify the situation.

    Why do I say this? Every member of a team has its faults. Quality management knows when to say, "dude, you need to brush up on your SOAP skills," just like it knows when to say, "dude, you need to bathe with soap before coming to work."

  189. Re:These guys are all right. by squozzer · · Score: 1

    > In a hundred years, I promise you it won't matter one whit. Unless you're John Connor...

  190. There are two distinct classes of this by melted · · Score: 1

    There are two distinct classes of this phenomenon:

    1. People who just appear "brilliant" due to being good at obfuscation and self promotion. There are tons of these in any big company. They talk the good talk and move on shortly before management discovers they aren't all they're pretending they are.

    2. People who ARE so brilliant, that bringing them to the lowest common denominator would be hugely unproductive and they'd probably just leave rather than comply. I've met a few folks like this when I was at Microsoft. It was a humbling experience.

    So I say beat #1 into submission and let #2 do whatever the heck they want. The trick is to get your average front-line manager to figure out which is which. The distinctions that are obvious to a grunt in the trenches aren't all that obvious to them.

  191. Fire him *now* by jstott · · Score: 1

    ... insults female co-workers and ...

    I don't care if he's brilliant, this guy's a legal liability and he needs an ultimatum: if you ever single out your female co-workers again, you're fired.

    He may be good, but he's not worth a sexual-harassment lawsuit.

    -JS

    --
    Vanity of vanities, all is vanity...
    1. Re:Fire him *now* by geekoid · · Score: 1

      No ultimatum, you can't trust this guy at all. Fire him, be done.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  192. Re: brilliant and dangerous? by illegalcortex · · Score: 1

    When I asked him why there was no documentation (or very poor documentation when there was) the answer was a combination of "You shouldn't need documentation" and "I'm not paid to document things."

    Well, actually... you are.

    So he didn't document things, right? And management knew this, right? Did he continue receiving paychecks?

    The fact that they hired you shows that he was right, at least on the reality of the situation.

  193. Re: brilliant and dangerous? by spiffmastercow · · Score: 1

    That's all well and good unless you're expected to meet unreasonable deadlines to begin with. If I have to get something done in a short period of time, documentation is not a priority. Of course, I'm the only programmer at my work, so its not like anyone else has to look at it anyway.

  194. Re: brilliant and dangerous? by noidentity · · Score: 2, Insightful

    Being required to produce documentation along with one's design often makes the design better, because it encourages a design that's easy to document clearly. The lazyness principle makes you want to avoid tricky things that take pages of documentation. So even if you think the documentation as some crap that goes along with your nice, clean design, think of the task of writing it as no different than a unit test or other QA; it exposes problems you might not otherwise notice.

  195. Re: brilliant and dangerous? by JoeMerchant · · Score: 3, Insightful

    Sometimes you need a solution NOW, and you will have time to clean it up (or re-implement it more carefully) later.

    Except, cleanup (or re-implementation) never happens.

    I'd say that's clearly not Josh's fault. If you hire a team of paratroopers to build you a bridge, then you try to use it as critical infrastructure for the next 30 years, it won't be the paratroopers' fault when a bunch of trucks fall in the river.

  196. Alternate solution by egcagrac0 · · Score: 1

    If Prima Donna's skills are essential (or highly desired), hire an assistant to deal with the mundane niceties that Prima Donna isn't willing to deal with.

    Flatter Prima Donna a bit, say "Look, what you do is amazing, but nobody else can keep up with you without documentation. We've hired Leroy here to fetch your coffee, screen your phone calls, and document your code. Just put a few notes in at the top and pass it off to him, and try to answer his few questions so you can get back to churning out code and reading xkcd."

    Suddenly, Prima Donna has a lot fewer reasons to venture out of the cave and offend the female staff, and the code gets better, and in a year or two, Leroy will be so fluent in the code that Prima Donna can be replaced (if necessary) without significant hangup.

    TLDR: PFY can be useful, as can PHB for providing PFY.

  197. you sir win at the intarwebs ;-)

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  198. Re: brilliant and dangerous? by JoeMerchant · · Score: 1

    "I'm not paid to document things."

    Well, actually... you are.

    Depends on your contract - not just the paper one with a job description written 12 years ago by a manager who only worked for the company for 6 months - but the social contract you develop with your co-workers as the relationships evolve.

    I think most people here are pissed at "Josh" because they let him get away with "his crap" for so long that they can't imagine how to fix things without firing him.

  199. Re:These guys are all right. by computational+super · · Score: 1
    I'm sitting in an office cube wearing a polo shirt.

    A polo shirt!? Get a button down, you damned hippie.

    --
    Proud neuron in the Slashdot hivemind since 2002.
  200. Josh isn't smart by GWBasic · · Score: 1

    After reading the article; my conclusion is that Josh isn't as smart as the manager thought he was. His manager was just deluded into thinking he was smart. I've had to clean up messes from developers like this guy; and it's shocking when I realize that it's a manager's delusion that the quirky guy is writing brilliant code that is what made a particular project fail.

  201. Re: brilliant and dangerous? by fugue · · Score: 1

    Software development is 40% technical and 60% people. [citation needed]

    There, fixed that for you. How do you even measure those things quantitatively? That's nothing more than a way of saying "people skills matter too" and yet you're parroting it like it's a law of physics.

    Even assuming those numbers are correct in general (to two significant figures, even), do you think that there's no variation? Do you think that you can measure an average and then insist that the real world must match the average in every case? Precisely enough that you can do that sort of math?

    however to balance him you will need to hire someone who is like 10% technical and 90% people skills just to support him.

    What does this mean?? It's not even wrong. Firstly, 10% technical and 90% people sounds like a manager or enabler, you need those anyway, and one of them can support a lot more than one 90/10 like a Josh. Secondly, are you suggesting that the company as a whole needs to add up the raw ability scores of all of its employees and make sure that the average is upheld? Methinks you've been playing too much D&D!

    And you're still ignoring the first law of hiring: figure out what the person is worth to you and offer him that. If he wants more, then you can fire him. Again, another inexact science, but not so bad...

    --
    "The biggest problem with communication is the illusion that it has taken place."
  202. More people to be encoraged to be like Josh by strangeattraction · · Score: 1
    I've worked with my share of plant shitters, conference room table shitters and garbage can shitters in my time and they aren't limited to your typical software types either. CEO, CFO, VP, shitters are prevalent and just once in my career I worked with a Human Resource shitter at a major SV company (that will remain nameless) that would take a dump in the executive's office whenever he would ask to get someone fired.

    I have to admit my experiences haven't been entirely negative.

  203. Meh. by Anonymous Coward · · Score: 0

    I generally set my own hours (aside from pesky deployments) and get to work without pants.

    Usually I wear pants anyway, but it's nice knowing the option is there. Of course, I telecommute, so I guess I could not wear pants even if the option hadn't been put on the table when I was hired.

    Work for a startup company. If you can manage to survive the first few years without becoming absolutely batshit insane, there are some great and weird perks, to be sure.

  204. Re: brilliant and dangerous? by Jherico · · Score: 3, Insightful

    Agreed; which is why this statement from TFS: "... could churn out code that saved the company millions" - is nonsense. It may look that way on the surface, but when accounting for all the code maintenance pains that inevitably follow, I've yet to see a single such "genius" that wasn't a net loss

    First off, sometimes there is a time basis that cannot be avoided and a solution, however dirty, is required right away in order to complete a contract or open a web storefront or the like. In these cases the original statement is literally true, millions could be made or lost depending on whether you can flip the on switch tommorow or next week. At that point, you're making money in the long term, regardless of whether you have to reimplement.

    Of course companies are usually, imo, too focused on the here and now results anyway and this is a double edged sword. It can get you to market quicker, but I have time and again seen companies shopping for development libraries or other similar tools go against the selection of one vendor by EVERYONE who was going to use the product and go for another cheaper vendor that no one liked because it saves the company 100k right now, even though the cost of developing locally all the missing functionality from the cheaper solution will easily end up costing more that the saved amount in the long run.

    --

    Jherico

    What can the average user can do to ensure his security? "Nothing, you're screwed"

  205. Re: brilliant and dangerous? by mooingyak · · Score: 1

    Sometimes you need a solution NOW, and you will have time to clean it up (or re-implement it more carefully) later.

    Except, cleanup (or re-implementation) never happens. What will happen is layer upon layer to work around bugs and problems. Because you can (almost) never justify to upper management that you need to reimplement something that works and the finish product is basically the same you started out with (with cleaner code, maybe).

    Not just that, but I *can* come up with something less than ideal on the spot when it's necessary. I don't need some guy just for those situations, all the more so because most of the rest of my time is dedicated towards preventing that scenario anyway.

    --
    William of Ockham had no beard. The most likely explanation is that it was chewed off by squirrels every morning.
  206. Re:These guys are all right. by cromar · · Score: 4, Insightful
    Overall, I agree, but saying that

    It's *all* pointless. The end is the same for everybody. We're all worm food.

    is a great plan for mediocrity. There are struggles that are worthwhile and there are struggles that are pointless, but to say that no struggle matters is speaking from both ignorance and arrogance. I mean no offense, we're all ignorant and arrogant to some extent.

    Doesn't matter if you rage against the machine or oil its gears. In a hundred years, I promise you it won't matter one whit.

    I'll just give a few examples of why this isn't true: Martin Luther King, the Buddha, Jesus, Krishna (to whatever extent those last three are flesh and blood historical figures), Ghandi, US founding fathers, those who participated in the Tiannamen square incident, etc., etc., etc. All these people have had and will continue to affect life for humanity.

    So, while it's true that blindly "raging against the machine" is pointless, just because you have

    a nice job, nice house, nice car and a family I love dearly

    doesn't make you any better or make your life more worthwhile or valueable than someone who can't afford to fix their teeth. Their pain and alienation may be far more meaningful than your "boring life" (your words).

    All I'm saying is you don't have to settle for assimilation, blind hate, futility, alienation, mediocrity or ambivalence or comfort. Do something with your life and make the world a better place, but don't "sell out" or become so bitter that you are divorced from the world. It's not worth it for you or anybody else.

  207. Brilliant is good, quirky is fine, obnoxious not by rbunker · · Score: 1
    It is certainly true that there are super-programmers out there. They are worth not just two or three of the rest of us, but more productive than 100 or so normal humans. A company is really lucky to have some of them.

    The thing is, there is zero correlation between being this good, and being an asshat.

    Now, sometimes there will be a bad programmer who acts like this, and they just get fired fast. Nobody worries about them.

    But when the stars mis-align and you get someone actually talented, who is also a jerk, some inexperienced managers will feel stress about the obvious decision.

    But the easy, obvious decision is to fire the asshat. You can go out there and find someone just as talented who is not obnoxious. I promise, you can. Do it.

    The rest of the team will have a party when the obnoxious one leaves. Overall morale will increase, people will be only too glad to jump in and fill the gap (until you replace him/her and the replacement comes up to speed). Everyone will respect management more, and they will see that treating coworkers with respect is really important, not just lip service.

    By the way, the same holds true for the great salesperson, etc.

  208. I have Asperger's Syndrome by Anonymous Coward · · Score: 0

    Yeah, everyone knows around me knows that I'm EXTREMELY intelligent. That's half of my problem really, trying to slow down so I'm on the same page everyone around me is on.

    The other half is that I'm completely focused on what is currently triggering my focus and that's not usually the task at hand.

    When I was a kid, all my teachers thought I should be in the gifted program. I spent most of that time bashing my head against the wall during class to make myself 'Dumber' so I could fit in.

    I couldn't handle school the way they have it set up though, I just think too differently than most folks. I never had great grades because homework was always counted as a huge percentage of the grade. I never found time to defuse from school AND do homework without getting completely futzed from anxiety. Had I been graded on test scores alone I probably would have had a B- average.

    As it stands I never graduated and only picked up a G.E.D. a few years later.

    What really changed my life? Finding out that I have Asperger's Syndrome. That single thing has allowed me to identify and eliminate 80% of the issues that have plaugued me my entire life.

    I can say that it's no excuse for me to treat people like I'm an asshole or something.

    I've met "Josh" characters before and yeah, the more intelligent and quirky weird we are, the more difficult it is for us to hang on to what other people call 'reality'.

    It's difficult holding a screaming engine back from the brink all day AND putting up with people that don't understand how our reality is fundamentally different than theirs. The difficulty there is that we're often not aware that we're doing any of this at all. I didn't find out until age 30+ that I have Asperger's Syndrome. By that time, all the frustrations that I've identified were just one big mass of background noise. I constant state of upset that wasn't readily apparent to me. Very weird state to come out of, that's for sure. :)

    All in all, life is F'n awesome, even with all the years of frustration and crap I put up with before I found out how my brain works.

    Enjoy!

    1. Re:I have Asperger's Syndrome by Anonymous Coward · · Score: 0

      People who have any sort of unusual talent but some handicaps when it comes to "normal business social behavior" need understanding managers in order to be productive; otherwise, the business can lose out on what that person has to offer.

      That doesn't mean the subordinate employee should abuse their power, like Josh in TFA.

      Everybody is different, Asperger's or not. A good manager can utilize their subordinate employees' talents without putting the business in a precarious position, putting undue burden on their subordinates or their own supervisor, or letting a subordinate employee abuse their position (intentionally or not). Obviously, good managers are few and far between. I've found that good managers, at least those who manage programmers, are people who have a few exceptional talents of their own and get extremely focused on some things they're working on (so they can understand when an employee has some of the common quirks associated with programmers); is exceptionally good at communication *and* empathy (so they learn how to talk to their employees rather than expecting their employees to learn how to talk to them); and is patient without being self-defeating (they'll take as much as time as they need to get quirky employees into the best, most productive place/state-of-mind possible, without letting people like Josh learn to walk all over them).

      I think programming teams need the right kind of managers, and, yes, sometimes those managers may need to defend their subordinate employees from other managers who are very business-oriented and have extremely different managing styles... doesn't excuse Josh's behavior...

      Oh, and sorry about taking a dump in the flower pot. Next time, I'll take a dump in the big ceramic pot in the lobby that the fancy miniature tree is in... unless, of course, I get an extra six weeks of vacation this year with no penalty.

  209. Re: brilliant and dangerous? by Ralish · · Score: 1

    Where exactly is the conclusion being drawn that this guy even had Asperger's, or any disability? It's all just hypotheticals by armchair psychologists.

    It's probably worth pointing out as well that most people with Asperger's are somewhat socially inept, but there's a difference between being socially awkward and just being an arsehole. The guy in the article comes across as the latter.

    Some people are just genuinely brilliant without the "benefit" of a disability, some are just genuinely quirky, and some are just genuinely arseholes. Not every trait out there requires a mental disability or condition to explain it.

  210. Re: brilliant and dangerous? by fleco · · Score: 0

    People like Josh, on the other hand, should be fired on the spot.

    I don't think so. They can just be recognised for what they are, and treated accordingly. Think of him as a fire extinguisher--a pain in the ass to clean up after, but from time to time invaluable.

    The problem is that management will go for the fire extinguisher most of the time. And "later" means that it will never be re-implemented carefully.

  211. Re: brilliant and dangerous? by Kell+Bengal · · Score: 5, Insightful
    Well, he was employee #1 in the company (both value-wise and chornologically). Since he didn't document at the start, it was much cheaper to hire a post-grad than spare a more expensive employee from actual development work.

    I wonder if perhaps there's an argument for pairing senior employees who do the critical design work with fresh hires to document the what and why of it. That way, the higher-up engineers don't have to write anything down and the junior engineers get to absorb some of their insight by osmosis.

    --
    Scientists point out problems, engineers fix them
    altslashdot.org: The future of slashdot.
  212. Rick found a cure for cancer. He was arrested by Anonymous Coward · · Score: 0

    News flash!

    Guy creates cancer cure and gives it away. Feds arrest fellow because the cure has cannabis in it.
    All research completely destroyed by our wonderful political system that keeps cannabis illegal through dishonesty.

  213. Re: brilliant and dangerous? by fugue · · Score: 1

    If the guy produces a lot of unmaintainable code then he's costing almost as much as he's making for the company.

    Maybe. Depends on how they use him. Read my post again.

    --
    "The biggest problem with communication is the illusion that it has taken place."
  214. imma jerk by Anonymous Coward · · Score: 0

    I like josh. I'd hire josh. I'm like josh.

    If doc's don't exist then when you go to "read the code a year later" your better off coming up with a new solution. Most of the time creating documentation for a quick and dirty solution is useless.

    You get used to no documentation and become a better coder by being able to read code. ( I go through open source all the time, most of the time there are no docs, and/or the docs are out of date with the code) l2hack

    "Sure, he was whipsmart and could churn out code that saved the company millions, but can we please stop enabling these people?"

    He saved the company millions?? Buy that man a gold flower pot! Josh probably has to deal with mac users,mcse monkeys, and people that use the word empower.

    Josh probably doesn't belong in the public sector. He'd be better off in a private dev house with similar ppl. imo.

  215. Not a team player: Josh or the author by charlieo88 · · Score: 1

    A manager goes to talk to another manager's employee without first talking to the employee's manager. Add to that an employee with which the author clearly had many issues, ie dress, deportment, hygiene.

    The talk, that the author can't recall, possibly with shame, a talk that deteriorates to the point that "Josh" quits and never comes back?

    Sounds like maybe "Josh" wasn't the only one that wasn't a team player.

  216. "Real programmers" and psychiatric illnesses by kurisuto · · Score: 1

    One of the programmers was brilliant, but actually insane. ... They kept him around because they couldn't afford to hire real programmers.

    Having a psychiatric illness doesn't make you any less a "real programmer".

    I'm sure there's a fair number of us here who have been treated for psychiatric conditions at one point or another and are still perfectly competent programmers.

    Suppose your colleague's disability were physical rather than psychiatric. If he used a wheelchair, would that mean that he is not a "real programmer"?

    Psychiatric illnesses are classified as disabilities under the Americans with Disabilities Act. If the condition can be reasonably accommodated by the employer, then it is against the law to discriminate on the basis of that disability. If your employer got to the point where they could afford "real programmers" and ended your colleague's employment because of his psychiatric illness (assuming it's a case where reasonable accommodation is possible), then your colleague could take the employer to court under the ADA.

  217. Not just developers by Anonymous Coward · · Score: 0

    It's not just software developers that this happens with.

    I've seen companies look the other way when project managers, departmental managers, and even executives do stuff that would get the normal worker fired.

    We used to have a project manager that would come to work drunk, use obscene language in nearly every sentence he ever uttered, and he would file his travel expenses on an annual basis (even though the company policy was to submit them within two weeks of the end of the trip). He got away with this for years.

    He finally left only when some incompetent HR person forgot to file his immigration paperwork on time. Yes, he was a foreign national working in the US largely illegally. They'd send him out of the country every couple of months so he could come back in on a vacation visa.

  218. Working for the wrong company by Anonymous Coward · · Score: 0

    I've obviously been working for the wrong companies for the last 25 years. They would prefer that a project definitely takes 1 week.

    Evidently you're not that bad off. Where I am, they prefer it be done two weeks prior to the need being apparent and the project being created and assigned.

  219. Neither by Anonymous Coward · · Score: 0

    Quirky developers are quirky, possibly dangerous.

    Brilliant developers are brilliant.

    Poor management confuses quirky with brilliant, and gives credit for brilliance where it is not present.

  220. Terry Childs anyone? by Dogbertius · · Score: 1

    Does the Terry Childs incident ring any bells?

  221. Learn to tolerate other people. by Anonymous Coward · · Score: 0

    Different people are different. Everyone has their own priorities. We just need to learn to appreciate different kind of people. If you're quirky, it's a strenght that can be used to make the team perform better. Should learn to tolerate differences in people and find advantages from every behaviour you encounter.

    Any suggestion that quirky or any other kind of people should be fired for wearing a t-shirt is outrageous. Everyone deserves to have a job. Everyone is different.

    Some people do not tolerate people wearing a t-shirt. This is a strength too. Make them check customer relations team t-shirts. If your company cannot rearrange cubicles when finding out that two team members do not like what the other is doing, then the company needs to really think how they deal with employees.

    Good companies respect all kinds of people. Quirky employees have their own strenghts and weaknesses. Good managers can make team work well recardless of what kind of people they started with. You just need to know what kind of employees you have, and adjust your process.

    Your programmers didn't write documentation? Blame the process. Once you can shift the blame from individual people to the process, it can be improved. Usually there is a good reason why your programmer didn't write the documentation. Maybe your process constantly reminds the programmers that documentation is missing, and your programmers are already tired of it. Anyway, there is some reason for every behaviour your employees are doing. The process is broken.

    It's everyone's job to improve the process. Wearing a t-shirt is one way to improve the process. Find a flaw? It's your job to fix it. It takes lot's of effort to make the process perfect. But there are rules. You're not allowed to change other people. If you can't tolerate t-shirt of someone else, ask managers to rearrange cubicles or reorganize the work.

    Real change happens when people want to do it. Not when some external outside force makes them do it. Some of your employees is a bitch and insults people? They're already sick of your work environment and your process failed. This is a warning sign. Learn to read them. Next week you'll have 20 more people with the same problem, unless you start a change in the process. Do it immediately. Do not wait. It can take years to fix, but it'll be worth the effort. Blaming individual people for your process problems gets you nowhere.

    We're in this for most of our lives. Many things happens in that long time. People get bored of doing the same thing thousands of times. Some people learn bad habbits from outside of their work. This is just life. Your process must be prepared for all kinds of events. Builds break, your customers will shout at you, you lose millions of dollars because of flaw in the product. It will happen to you. Process be praised.

  222. Re: brilliant and dangerous? by Thaelon · · Score: 2, Insightful

    If my code takes more than a few seconds to figure out what it's doing, I keep rewriting it until it doesn't.

    The golden rule of being a truly good programmer is that you write the code that you wish other people would write.

    Write code that is self documenting by way of having very descriptive method and variable names. Because while it may take longer to write, you'll invariably end up reading it ten or more times more than you'll be editing it. So time making it readable & grokable is time exceedingly well spent.

    here's a quick sample of what I mean:

    Instead of this

            if (thingy.getLastTime() - thingy.getCurrentTime() > 3600000) {
                    for (Calendar calendar : thingy.getCalendars()) {
                            calendar.update();
                    }
            }

    write this:

            boolean isChangingTimeZones = hasChangedTimezones(thingy);
            if (hasChangedTimeZones) {
                    updateAllCalendarsWithTimeZoneChange(thingy);
            }

    It's debugger friendly (you can see the value of isChangingTimeZones before you step into the if-then-block, and the logic is described via the variable name which has a corresponding method that can be easily unit tested) and all the names are descriptive as hell. Not to mention the action is decoupled from the logic, and could easily be more so. Either could be modified without ever changing that particular code. And yes, the boolean method should use a constant for that magic number. You can probably infer what that constant is, but why waste people's time making them infer when you can very easily tell them explicitly?

    --

    Question everything

  223. Re: brilliant and dangerous? by bwcbwc · · Score: 1

    How many sexual/racial harrassment lawsuits would this guy be worth to your company? Definitely creating the proverbial "hostile work environment" and if your managers don't do anything about it, the whole company becomes liable.

    --
    We are the 198 proof..
  224. Speaking for some Joshs by J05H · · Score: 1

    Personally i've never taken a dump in a potted plant or otherwise fuxxored my coworkers/office. Perhaps the difference is that I'm a regular Subgenius Josh and not your brilliant Assburger Josh. The distinguishing characteristic is whether you are ninja, pirate or jackass.

    (shouts to the Joshs that don't give us a bad name)

    --
    gigantino.tv - Heavy but weighs nothing.
  225. Re: brilliant and dangerous? by sfcat · · Score: 2, Insightful
    And you are 100% wrong. Programming is 100% technical. Working in an IT shop might be 40% technical and 60% people but that just means that you only spend 40% of your time programming.

    But here's the catch, someone must write the code in the end. And someone must maintain it. And the code that is written is of varying quality. If someone is simply a better, faster programming, then their code will be cheaper to maintain because it will break less often and scale better (or whatever your metrics are for code quality). I find that a "nice programmer" might be easier to work with, but those Saturday night production outages make me hate that person all the same. And I'm much more likely to fire him at that point because I think that person is unlikely to have to skills to keep the code working.

    Finally, I think this entire argument is a bit of a crutch. I've seen people who match Josh's description, but usually the best programmers are just crabby because so much of the work falls to them. Then they get painted with "Josh's brush" and labeled as having bad people skills. When really, they are just tired and overworked. If the people with "people skills" had to deal with even 1/10th the work, they would go on a killing spree within a week.

    --
    "Those that start by burning books, will end by burning men."
  226. Genius is the most important part. by Anonymous Coward · · Score: 0

    People seem to forget that if not for individual genius we would still be wondering how to start fire. Where would physics be without Einstein, or Newton? Similarly, where would computer science be without Turing, Knuth, or Neumann?

  227. Re:These guys are all right. by mrcaseyj · · Score: 1

    >And I've got some news for you. It's *all* pointless. The end is the same for everybody. We're all worm food. Doesn't matter if you rage against the machine or oil its gears. In a hundred years, I promise you it won't matter one whit.

    At the rate that molecular biology is advancing, aging will likely (or at least possibly) be cured within the lifetime of many people alive today, especially children who can expect to live at least another 80 years. Think about what kind of medical technology we'll have in 80 years. We can already look at the atoms that make our cells work, there is nothing smaller that we need to be able to see. There are just a lot of little parts that will take a while to figure out how they go together. It's amazing what we've figured out already. With improved computers and microscopes, we'll surely make huge progress over the next 80 years. The old saying that everybody dies someday is no longer certain.

    But what I think will happen before an aging cure, is a massively more powerful, possibly molecular, computer technology. Super computers are just now reaching power levels comparable to the human brain, so it might not even require a breakthrough new technology to create intelligence that will make Einstein look like an idiot.

  228. Assholes can be managed by Anonymous Coward · · Score: 0

    Assholes should be kicked out of any team, because no matter how bright they are, they won't be able to compensate for the lowered productivity of everyone else who has to waste their time and energy to deal with their little power games. As an added bonus, it makes every other employee happy, thus making the world a bit better place. Profitable and morally right, firing assholes is a win-win situation. Even the asshole might benefit from the wake-up call.

    But sometimes their skills are critical and they just need to be managed. If they are that profitable to keep, you just hire a babysitter. They can be socially isolated (work from home). They can even be successfully counseled. But if they are violent or sexually aggressive, then all bets are off because of the liability. And don't even think about covering that up. It surfaces years later to bite you in the ass.

    On second though -- fsck 'em.

  229. Re: brilliant and dangerous? by burris · · Score: 1

    If you're selling necessary refactoring as an independent project then you're doing it wrong. Take a hint from Congress, bundle refactoring in with the new features that depend on it. An experienced legislator knows you bury the pork in a bill that the opposition would not dare obstruct.

  230. Good career move by zooblethorpe · · Score: 1

    I can't say that I enjoy working with assholes, though.

    I can certainly see why you didn't go into proctology. Though sometimes it sure seems like a good field to know a bit about, no matter what industry you might work in...

    Cheers,

    --
    "What in the name of Fats Waller is that?"
    "A four-foot prune."
  231. Re: brilliant and dangerous? by rs79 · · Score: 1

    " Software development is 40% technical and 60% people."

    For some definition of "software development".

    Funny thing about poeple skills, you put them in a chip and the CPU won't execute them. I'll cede some sw jobs require people skills.

    Funny thing about comments and documenation too: when presented with what it costs to PROPERLY document stuff (2x what it cost to develop it) nobody ever wants to pay for it.

    This is besides the obvious "Comments lie. Code never lies." thing.

    --
    Need Mercedes parts ?
  232. I myself am a quirky yet briliant programmer by MichaelCrawford · · Score: 5, Interesting
    I have been a software engineer for twenty-one years, at one time having the role of "Debug Meister" as a system software engineer at Apple Computer - this because I'm a wizard at assembly debugging and reverse engineering.

    For example, I was once able to give Microsoft the exact byte offset in Word's binary where their bug lay, that would cause a very rare, difficult to reproduce system crash - this was way before Mac OS X, so application faults would hang the whole machine.

    I have Bipolar-Type Schizoaffective Disorder. Because it's just like being manic depressive and schizophrenic at the same time, it is one of the very worst mental illnesses that one can have.

    It is very rare, poorly understood and notoriously difficult to treat. My symptoms include depression, which has been suicidal at times - I've attempted in a serious way twice - a profoundly euphoric state called mania, auditory hallucinations and, in my case, visual hallucinations that coordinate with a profound paranoia that leads me to believe that a shadowy, secret law enforcement agency I call The Thought Police are coming, not to arrest me, but to kill me.

    I call them The Thought Police because they are The Police Inside My Head. You see, I know very well that they're not real. Unfortunately, just knowing that one is paranoid doesn't make the paranoia go away. When I look directly at my attackers, I can see that they're not there, but when I turn away I can feel their presence again.

    But Wait, There's More!

    There are Five Axes of psychiatric diagnosis. That is, one's Madness is a point in a sort of five-dimensional vector space.

    Schizoaffective disorder, schizophrenia and manic depression are all biochemical axis diseases; they are caused by screwed up brain chemistry. They are thought to be genetic, although there is some evidence that schizophrenia can be caused by infectious disease when one is either in the womb or very young.

    Biochemical axis illnesses are generally incurable, but their symptoms can often be relieved with medication. I know very well what would happen to me should I ever weary of my life on the run and decide to turn myself in to The Thought Police - and so I am very diligent at taking my daily dose of the powerful, expensive, mind-altering drug which gives me the comfort of staying a step - but just a step - ahead of Them.

    There is also a neurotic axis. Neuroses are purely psychological in origin and are usually caused by some kind of unresolved trauma, usually experienced as a child such as sexual abuse, but it can arise in adults too, as with the war veteran's Post-Traumatic Stress Disorder.

    Ironically, many neurosis originate as adaptive strategies, that enable the neurotic to survive their terrible ordeal. Thus the soldier who learns to dive for cover at every sharp sound survives the war, but is unable to return to civilian life after returning home - because he still feels the need to dive for that safety.

    The little girl who survives her pedophile by imagining his advances to be courtship by a handsome prince my not find her Castle in the Sky such a wonderful place to live when she grows up, gets married and has children of her own.

    The neurotic axis illnesses can all be cured, and through "talk therapy" alone, without the use of any drugs - in fact, using drugs to relieve one's symptoms can actually relieve one of the need to ever get better.

    Unfortunately, the cure generally takes many years and is collossally expensive. In my case I estimate that I paid just one therapist sixty thousand dollars for thirteen years of weekly psychotherapy sessions.

    --
    Request your free CD of my piano music.
    1. Re:I myself am a quirky yet briliant programmer by SoupIsGoodFood_42 · · Score: 1

      Does the neurotic axis even exist anymore? There have been so many studies recently show all sorts of physical neurological differences (which would fit on the biochemical axis) in people with "neurosis" that I have to wonder. Same goes for the biochemical axis, since the brain is quite plastic, thoughts can have a real effect in this area. But then again this is psychiatry and they often seem to be many decades behind the times.

    2. Re:I myself am a quirky yet briliant programmer by Anonymous Coward · · Score: 0

      "..Microsoft the exact byte offset in Word's binary where their bug lay,... "

      So? reverse engineering and debugging are the easiest things that can be done in software. Hell, good QA is much harder.

      "I've attempted in a serious way twice"

      No you didn't. If you had you would be dead.
      I know for a fact there is a bridge you can get to.

      "...but just a step - ahead of Them."

      We are all just a step ahead of them. Just look at how easy people fall prey to Cults, and make believe medicine.

      60K of 13 years isn't that bad.

      Again, debugging is damn easy. It's just time and tools.

      Your not special, you are just broken. Seek help, be well but stop going on about it as an excuse to flaunt your ego.

  233. My (dev/ops/manager/wearerofmanyhats) take by forgottenusername · · Score: 1

    Keeping "Josh" types around is wrong, and any company who does that is almost invariably ignorant. Lemme explain why.

    Take amount of time it takes to write a particular piece of software and compare it to how long it can be in service. You'll quickly see why writing clean, easily maintainable code is so much more important than churning crap out to meet a deadline.

    Which, realistically, is the root of the problem. Business is like a blind, hungry animal with no knowledge of the future, and complete ignorance of the past.

    When you couple that with most business folks complete lack of understanding of tech fundamentals, you end up with a dangerous situation.

    I can't count the number of jobs I've worked at that has had subpar dev/ops members that are as highly regarded as "Josh". They are usually highly protective of their "turf", and unwilling to share info. In my experience, that is one of two things; either total incompetence and they are wanting to protect their ego and company standing, or they want job security. In reality, these "brilliant" people are usually supbar employees who are viewed as heroes when they fix problems that _they caused_. Business not knowing tech or how to tell if a tech employee is good, ends up praising the worst possible employee behavior and loves the worst quality employee. Comically sad.

    Intelligent people eventually realize that job security by claiming turf & not sharing info means that their life eventually becomes a living hell of their own creation as they are now chained to this crappy software or project that is probably breaking all the time, a beast to maintain, and if that project goes away, likely so will they.

    Another point - no single dev is going to be as productive or useful as a well integrated dev team. In sane orgs, there's a flow of dev -> qa -> ops moving through various environments. That's a lot of hands touching code, having to understand and test it, having to support it. If there is no clean handoff, documentation, or willingness to help/defend/explain their code, it is not supportable for the business. You might meet a few deadlines but you will lose out every single time in the long haul.

    Dev teams have to integrate code. How many devs have had to work with reticent, subpar coders who don't provide documentation or clean integration paths, with unreadable code? It just wastes valuable time on the project, frustrates your entire dev team and leads to inferior quality products.

    Your business will _fail_ if you foster "heroes" like Josh. You will never have a maintainable code base, scalability, or supportable code in the most important environment, production. Which is another important point; no other environment matters but production. Everything else is to support a clean, supportable, scalable production environment.

    No single team member should be indispensable. It's an indication that your hiring practices are flawed, or the company is not willing to staff up enough to provide redundancy. Having been that "indispensable" employee several times, I can tell you that it sucks balls and any sane person will fight like hell to get out of it. It means you can never go on vacation without being bothered.

    Specific to "Josh" - immediate firing is in order. Are his (negative) contributions in light of his flawed methodologies worth the amount of money a sexual harassment lawsuit would cost?

    Time to wake up. The myth of the reticent superhacker who saves corporate is beyond stupid. It's criminally negligent on behalf of hiring managers because of the long term problems it brings.

    If your company is a small startup, it's workable in the beginning, but you really need to be careful that best practices are instituted as it makes sense, with the eventual goal being a clean SLDC or similar process that provides clean, well maintained, supportable production environments and applications.

    Engineer to business; grow up and get a clue. We have to understand your world when costing things, you need to understand what constitutes a good tech employee and a bad one.

  234. The fundamentals of being a good engineer by DomainDominator · · Score: 3, Informative

    1. knowing the theories and technologies 2. being able to communicate your ideas effectively to your team If you fail at either of these you don't belong in any company. Josh fails at #2.

  235. Re:These guys are all right. by Weaselmancer · · Score: 2, Interesting

    There are struggles that are worthwhile and there are struggles that are pointless, but to say that no struggle matters is speaking from both ignorance and arrogance. I mean no offense, we're all ignorant and arrogant to some extent.

    None taken.

    I'm not suggesting that no struggle matters - quite the contrary. What I am saying is that there are struggles that can make a difference to you, and there are those that can't. Being a perpetual outsider because the whole world sucks is an example of just such a pointless struggle.

    doesn't make you any better or make your life more worthwhile or valueable than someone who can't afford to fix their teeth. Their pain and alienation may be far more meaningful than your "boring life" (your words).

    Boring was from the OP, I was quoting. I'm happy with my lot.

    I'm not placing more value on my life than anyone else's. In the end, we're all just about twenty bucks worth of water and salt anyways.

    What I am saying is that using pain and alienation to make your life meaningful is a waste. Stop carving My Chemical Romance lyrics up your arms up and enjoy what you've got.

    Life ends. Surprisingly quickly, too. So make the most of what you have.

    All I'm saying is you don't have to settle for assimilation, blind hate, futility, alienation, mediocrity or ambivalence or comfort. Do something with your life and make the world a better place, but don't "sell out" or become so bitter that you are divorced from the world. It's not worth it for you or anybody else.

    I'm not even vaguely bitter - I think we're arguing at cross purposes here. I'm saying be happy because life is short. Too short to waste it with useless meaningless teenaged angst. I have friends in their late 40's who are still clinging to it. All it buys them is suffering. There isn't any meaning to it. There isn't any point to it. Or any beauty or truth either. It's just pain and you don't need it.

    If you want to go out and help people, do it. If you want to grow roses, do that. Do whatever you can to wring as much joy out of your short years as possible. What worked for me was to stop fighting things and join the human race.

    I have never been as happy and fulfilled as I am right now. When I look down my street and see people going about their lives I don't see drones, or sell-outs, or mindless zombies. I see people who are probably as happy and blessed as I am. And rather than cook up a list of reasons why they suck, nowadays I think they're probably a lot like me. And hopefully just as happy, too.

    --
    Weaselmancer
    rediculous.
  236. Re: brilliant and dangerous? by virmaior · · Score: 1

    while i see your point... often you aren't paid to document things. At least, I am not. I am told, get this out by yesterday. That doesn't include any time to document things.

  237. Re: brilliant and dangerous? by turbidostato · · Score: 1

    "Since he didn't document at the start, it was much cheaper to hire a post-grad than spare a more expensive employee from actual development work."

    That's part of the problem. /* This is intended to do foo by means of algorithm bar which was selected because this and that */

    is as much code as

    void main()

    Misunderstanding this fact is what puts us into these troubles to begin with.

    "I wonder if perhaps there's an argument for pairing senior employees who do the critical design work with fresh hires to document the what and why of it."

    Being that such documentation is there mainly for those fresh hires can understand the "whys" of the former developers (or the developer himself in a future incarnation), that makes as much sense as mandating users of a product the burden of developing user manuals instead of the makers.

  238. Danger == You by Anonymous Coward · · Score: 0

    You as a manager are responsible to make him write documentation. If he hasn't made them his work isn't done. It's that simple.

    Many people don't like documentation. And one of the hardest things is to keep code and documentation in sync. So it's the team leaders resposibility to verify that documentation is written and that "this thing about that requirement we fixed last week" has also been documented.

    If Mr. Josh then refuses he will simply be missing his deliverables.

    If he keeps that up it will be of no suprise to him that he is receiving bad reviews and eventualy the sack. But at least you have a objective measurement of his performance and Josh has a clear indication of what is expected of him. This gives him the possibility to correct... or not.

    Just my 2c.

  239. Bullsh*t by Brandybuck · · Score: 1

    Sure, he was whipsmart and could churn out code that saved the company millions

    I call bullshit on this one. For every dollar he saves for the company, he's losing two. He should have been fired with the first crude teeshirt and harassed female. Undocumented code is bad code and it loses you money in the long run. Insulting coworkers and refusing to bathe drives productive employees elsewhere, and you lose money. There is no excuse for putting up with assholes in today's economic climate. If you feel sorry for him because he's never been laid, send him down to the mailroom to learn some humility.

    --
    Don't blame me, I didn't vote for either of them!
    1. Re:Bullsh*t by geekoid · · Score: 1

      unless you company hinges on some sort of brilliant RnD effort, there is no need for that person in any economic climate.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  240. stick to your policy by Anonymous Coward · · Score: 0

    Every employee should be FIRED who intentionally violates or habitually behaves in a way that conflicts with your company's code of conduct regardless of position.

    If any employee is not expendable, then you should hire an employee to shadow and document his work to ensure that he is expendable.

    I would suggest you fire any employee who writes code that is not documented and cannot be understood by any other programmer. As this is far too much risk to the corporation should he need to be fired or leave the company for any reason.

    Firing may be avoided by employees who learn to comply and understand the value of working as a team.

    Personally: I work as a programmer and like many large applications, we have a section of code that is very complex and undocumented. It's great when it runs through data as originally designed, but code modifications have been difficult. Without proper documentation or access to the author... we cannot easily determine the difference between a bug and an intentional exception to the flow process.

    Please encourage management to fire these employees.

    ALSO: please look into the testing process. Forcing a programmer to write a testing suite for his code will assist future programming changes long after the original designer is gone.

  241. Re: brilliant and dangerous? by shermo · · Score: 1

    That was a 90% technical arguement for a 90% people problem.

    --
    Insanity: voting in the same two parties over and over again and expecting different results
  242. "If you don't have time to do it "right" now... by kosty · · Score: 1

    What makes you think you'll have time to come back and fix it later?"

    [Anyone have an attribution for this [probably inexact] quote? TIA.]

    --
    "Democracy." It's just a slogan.
  243. hostaging by Anonymous Coward · · Score: 0

    Whether they're smart or the code is good is beside the point.

    These people hold others hostage by convincing the powers-that-be that what they are doing is essential. Like most abusers, they control what people know and how they think -- whether it's through the latest techno-babble or special access to decision makers doesn't really matter.

    They persist even in the face of people saying their systems are screwed up because they get the decision-makers to put themselves on the line for it. It's easy to say "get rid of him", but he's kept because people feel they don't have a choice. The first sign of such a relationship: you feel like you don't have a choice.

    If you are a truth-teller, you think you're doing management a favor by pointing out how wrong this guy is; but because they've staked themselves on it, you're in the position of embarrassing the decision-makers. You give them a choice: (a) go with the truth, and lose their credibility; (b) (i) suppress or (ii) destroy you; or (c) get out of the situation by declaring victory and moving on. In my experience (and somewhat to their credit), they usually suppress you long enough to pass the buck.

    The worst thing you can do is to think it's about technology or the abuser's bad behavior. Both are distractions they deploy in order to suck up all the discontent around their control, and to prove to themselves that others aren't worth considering and they are in fact superior. If you fight them on those grounds, you lose. You won't convince someone they have a choice if you don't address their own investment in being constrained, and that has nothing to do with the bad behavior or technology you complain about.

    The way to win is (sorry to say) bureaucracy: make decisions more procedural and with more decision-makers. This gives the offending managers cover for changing their minds and makes it difficult for the abuser to hostage particular decision-makers. You might thank your lucky stars for the manager with the balls to can someone, but that's just another abusive situation waiting to happen.

  244. Re:These guys are all right. by relguj9 · · Score: 1

    I agree, if you want to be a brilliant ass hole, do it on your own time, do some code projects at home or maybe even help with some open source projects.

    If you're working for a corporation, you're working with a team and you're only a small cog in the process. They likely have the money to hire someone to replace you and they SHOULD if you're a jerk like the guy described in the OP. The code you write is also probably going to be around long after you're gone, so documenting it is going to save more than scoffing at documentation.

    I bet the guy described in the OP never had to do bug fixing of other people's code at the start of his career, went right into development. That would explain the ineptitude.

    I think quirky is perfectly acceptable to a point though, everyone's quirky it makes you human. The OP guy just sounds like an ass.

    That is, unless he's working for some firm that requires some incredibly complex algorithms to improve efficiency and he's putting together brilliant critical sections that really requires a genius to figure out. From the sound of it, he's just working for a regular joe firm and he's just figured out a good way of doing some mundane task that any code monkey could figure out with X amount of time.

  245. Re: brilliant and dangerous? by Kell+Bengal · · Score: 1

    Most users, however, do not have the advantage of talking to the product designer face to face in order to understand the material in the first place. What I propose is more like getting the alpha-testers to write the manual; they can talk to the designers directly, record what they feel is important for people of their skill level to understand how to use the product, add to it form their own experience with the product and then this documentation can then be disseminated to all subsequent users of the product.

    --
    Scientists point out problems, engineers fix them
    altslashdot.org: The future of slashdot.
  246. Re: brilliant and dangerous? by kyliaar · · Score: 1

    I agree... you need to learn how to use your resources.

    If you, as a peer, find someone on a team that is unsufferable for these sort of generic reasons, you would be served best to do things and opening your mouth to lambast them.

    A) People often scream most loudly at others for those crimes that they themselves are committing. Before you scream at Josh, take a look at your habits. Are you just jealous because he is better at 'bullying others into compliance'?

    B) Look at the business you are in and take a hard objective look at what he brings to the table and understand that upper management looks at the current bottom line and will never get too caught up in details, like documentation.

    So, this sort of stuff boils down to how a team is managed. If there is still a justifiable grievance, take it up with the team manager or lead. No one starts off as a perfect team member but villianizing them only makes it harder for the team to form as you are busily choosing sides for people.

    Finally, keep in mind A above. If your sole intention is to make Josh pay for his sloppiness and don't really care too much about team building, you are probably in that category.

  247. Re: brilliant and dangerous? by Kell+Bengal · · Score: 1

    Oops - I fail. Reply is below your comment.

    --
    Scientists point out problems, engineers fix them
    altslashdot.org: The future of slashdot.
  248. Then he should do that by snowwrestler · · Score: 1

    This is actually a really insightful post--the best place for a quirky, brilliant asshole is in an early-stage startup, preferably their own. There's a much higher premium placed on quick coding and clever solutions, and a much lower premium placed on documentation and management. And when you're the company founder you can dress however you like and be a jerk to someone if you want (see: Steve Jobs).

    The problem is when someone thinks they should get these perks as the employee of a mature corporation with a steady salary, health benefits, sick days, paid vacations, etc. Sorry, you have to trade something for security and yes, it is freedom and immaturity. If you want the benefits of playing for a solid team you need to be a solid team player.

    So geniuses: put your money where your mouth is. Start the next Google or Yahoo and I guarantee people will line up to kiss your unwashed feet.

    --
    Build a man a fire, he's warm for one night. Set him on fire, and he's warm for the rest of his life.
  249. I've actually been in that situation.... by Zapotek · · Score: 1

    ...when I were younger.
    I had written a complex bitmask hack if I recall to determine return values of a function after
    encountering a number of errors or something like that.

    The manager called me to his office and politely told me to change the code so that the rest will understand.

    It wasn't a big deal so I changed the code, it did take x10 LoC but I didn't care.
    I'm not the team player kind by any means and I have lots of pounds of
    several weirdness on me as well but never have I reacted like that, I think the article just blows things out of proportion....

    Maybe that "Josh" guy was just a jerk...

  250. while I got the idea by BitterAndDrunk · · Score: 1
    You screwed your code up. :) You used a method name for your If evaluation, rather than the boolean you'd assigned the method result.

    I.e.

    if (isChangingTimeZones) vs if (hasChangedTimeZones)

    But the compiler would catch that anyhow ;)

    --
    You better watch out, there may be dogs about . . .
    1. Re:while I got the idea by Glonoinha · · Score: 1

      Maybe he was making a point you missed.

      Code :
      [ ]pretty
      [ ]cheap
      [ ]correct

      Pick two.

      --
      Glonoinha the MebiByte Slayer
    2. Re:while I got the idea by Anonymous Coward · · Score: 0

      Off-topic, but your list made me think of something like this:

      Women:
      []pretty
      []cheap
      []female

      Pick two.

    3. Re:while I got the idea by artsrc · · Score: 0

      If he was making that point then it would take more than a few seconds to figure it out, so he should have made it more clear.

  251. Re: brilliant and dangerous? by paulgrant · · Score: 1

    pay them more to keep them and stay out of their way. then you dont have to pay the "cleanup" costs. Its not hard, I dont hear anyone bitching about executive pay or perks. If their code is so useful in the first place (and it is by virtue of the fact that most companies would rather hire one talented developer than several mediocre ones), why not ensure they stay?

    By way of disclosure I am one of those developers - and I argue to have things taken off of my plate (documented, designed etc) outside of my scope specifically because I dont know what will happen tomorrow (hit by a bus, food poisoning etc) and a team of people like u most likely will take over. The number of times I've told management "yes its possible but do you really want me to responsible for the well-being of your company, if I drop dead where will that leave you?" cannot be counted. But if you are coding with fools (and yes, I've worked with my fair share of body-shop consultants), no amount of documentation will suffice. They are simply not qualified in what should be their area of expertise.

    I lost a employment opportunity specifically because I told the CEO in the interview -- "{I can do what you want...} just dont stick me with someone stupid {as a coworker}" -- the reason why I didn't get the job? The ceo knew his employees were crap. And to be perfectly blunt, he did both of us a favor ;) I've worked with brilliant people (and it is the finest pleasure I've known), and I've worked with average people (cutting wrists!), and the pleasure of *not* having to explain for the umpteenth time how 2+2=4 is incalculable.

    Brilliance is the ability to *not* have to deal with stupidity, office politics, societal constraints that are harebrained, etc.
    The paycheck is almost incidental. Freedom to operate and innovate is not. Instead of resenting it, aspire to it.
    Or at the very least, stay out of our way.

    My apologies its a bit more personal than I intended but in the end, it is personal :P
    Your requirements for (excessive) documentation is a direct transfer from my finite amount
    of time available on this earth (solving problems) subsidizing your mediocrity. GROW!

  252. Re:These guys are all right. by cromar · · Score: 1

    I kind of figured that's how you felt; I think it's important to explain it to people a bit though. I know there were times in my life when it would have been good to have heard someone tell me how futile those kinds of thoughts can be, basically what you said, but it can be hard to communicate the whole picture to someone that feels that way.

    About the "settle for assimilation, blind hate, futility, alienation, mediocrity or ambivalence or comfort" bit, it was meant for both of you, or anyone who thinks they have to settle in life. We can't necessarily have everything we want in life - but that doesn't mean we have to "settle." On the contrary, the power that comes with the knowledge that one can make decisions to move towards ones goals is astounding. If you hate the world, people, try to fix it and shape your life around that goal - there's no other worthwhile outlet for those feelings. Also, the world sorely needs more rose-growers ;-)

  253. Re: brilliant and dangerous? by will_die · · Score: 1

    That fire the highly knowledgeable tech worker thinking has been a message in many management books for a few years. the basic idea is that you do have a wide range in the knowledge of people and if you grow dependent on a a single person and they leave you will be in really big trouble. Instead get as much documentation from them as possible then fire them.

  254. Re:These guys are all right. by Parallax48 · · Score: 1

    Wicked post dude. +1 Inspirational

    Focus your attention and passion on what really counts.

  255. Re: brilliant and dangerous? by pla · · Score: 1

    Sometimes you need a solution NOW, and you will have time to clean it up (or re-implement it more carefully) later.

    At most companies, you always need a solution "NOW", and time to do anything but deal with the next now" never comes. Thus, "Josh" will benefit most companies more than he harms them.

    In part, though, that forms a self-perpetuating cycle - You'll never escape damage-control mode as long as you work in damage-control mode. On the flip side of that, however, I would encourage most people to ask themselves, honestly, what tediously documenting every step really buys you.

    First of all, most "solutions" become irrelevant long before they break. We've all heard about the woes of 40-year old payroll systems that no one can upgrade, or even the Y2K fears dealing with legacy code... But those situations fall into an extreme minority. We work in a world where most software counts as "venerably ancient" if it sees five years.

    Second, "cleaning up later" only matters if Josh leaves... Which he eventually will, but good luck selling that as a problem to Josh. I don't mean that as necessarily a lack of care on his part, BTW, so much as a simple statement of the fact that true superstars honestly don't think in terms of "the team" - Except as baggage they have to drag along for the ride.

    Finally, even with good documentation, even on a codebase still retaining some relevance, would a semi-clean reimplementation better suit present needs (and possibly take less time thanks to newer dev tools) than trying to keep patching holes in a well-known but crumbling dike?

    In particular, on that last point, I certainly don't count as a superstar, but I've made that exact argument myself. I can personally reimplement quite a lot from scratch faster than I can understand even a well-documented preexisting project. That might not always exist as an option, but more often than not, your "2000 human-years invested" legacy project only really contains perhaps six months worth of chewy goodness for a single decent programmer, with countless years worth of "Patching holes in a wall-known but crumbling dike".

  256. What happened to "Diversity?" by Virtucon · · Score: 2, Funny

    After reading this I thought "humbug." What ever happened to "Diversity" and accepting people for who they are. Most brilliant programmers I've come across in my career weren't very sociable. Some could be jerks but at times aren't we all? I worked with a guy like that who was involved in some of the early days of computing, eclectic yes, arrogant, sometimes...

    Or is it that we only pay lip service to "Diversity" just to be inclusive of race or sexual preference so companies can push us to the lowest common denominator? Ahh yes, strive for mediocrity, that's what the MBAs want. Don't stir the pot, sit down and shut up.

    --
    Harrison's Postulate - "For every action there is an equal and opposite criticism"
  257. Re: brilliant and dangerous? by shutdown+-p+now · · Score: 2, Interesting

    I dont hear anyone bitching about executive pay or perks.

    You've got to be kidding...

    If their code is so useful in the first place (and it is by virtue of the fact that most companies would rather hire one talented developer than several mediocre ones), why not ensure they stay?

    Because it is usually quite possible to hire developers that are just as good, but that are not jerks. They may be slightly less brilliant, but they make up for it because they can actually work well in a team.

    By way of disclosure I am one of those developers - and I argue to have things taken off of my plate (documented, designed etc) outside of my scope specifically because I dont know what will happen tomorrow (hit by a bus, food poisoning etc) and a team of people like u most likely will take over.

    First of all, you assume that I'm one of the "rank and file" devs. In practice, I had been in the role of "star developer" in my division in the past, so I know how that works from the other side. But note that we aren't talking about this phenomenon in general, but about a very specific subset of such people, who are "good" (for some definition of it) on the technical side, but are arrogant and uncooperative with other people whom they perceive to be lesser.

    The number of times I've told management "yes its possible but do you really want me to responsible for the well-being of your company, if I drop dead where will that leave you?" cannot be counted.

    See now, if you ever told that sort of thing to your manager, TFA is not about you, and neither are any of my comments above. You seem to understand the bigger picture, which isn't just about you.

    Your requirements for (excessive) documentation is a direct transfer from my finite amount
    of time available on this earth (solving problems) subsidizing your mediocrity. GROW!

    Why do you assume that I require "excessive" documentation? When I say "bad docs", I mean stuff like 50 kLoC of code that has not a single comment in it; not forgetting to fill in the "detailed description" in the documentation comment for a private method!

    By the way, regarding the "finite amount of time" - that's all well and good when you solve problems for your own sake. But when you're at work, the time is not "yours", really - it's bought by the company you work for, and you should use it in a way that's more efficient for the company. Sometimes that means being more patient when it comes to dealing with abilities of people around you, even when they're lower.

    I was in that position as a senior dev who got promoted to lead very fast, and had to learn to manage a small team of my own. I had to struggle with that "if you want to do things right, do it yourself" attitude. Yes, I could do it better than my juniors could, and faster as well. But you know what? Once I've learnt to delegate appropriate tasks, and, when coding, to keep in mind that I may later want to assign the mainenance of that bit of code to one of the juniors, and dumb things down sometimes, or at least comment the "smarter" pieces even when they would be obvious for myself, I've found that the overall productivity of the team increased - precisely because I could offload those maintenance tasks to them, and keep working on new code that truly required more knowledge and experience to be done right.

    If you keep writing more and more code that only you can maintain, then, eventually, you'll end up doing nothing but maintaining that code - and that is usually not fun (and at that point, people often pack up and leave to find a more "fun" place to work at, and start writing "fun" code there as well... and cycle repeats - and the old place is left with unmaintainable "smart" code, and no-one able to deal with it). And it doesn't matter whether it's because you're being too much of a smartass, or because the people around you are truly idiots - the end result is the same. Worth keeping that in mind for one's own sake.

  258. Fire them! by Anonymous Coward · · Score: 0

    I've worked with these types before and totally agree that firing them is the right thing to do. Allowing them to continue this behavior is the same as bad parenting which in some cases the root cause of their problem..

  259. And this is why.. by magamiako1 · · Score: 2, Funny

    Reading these comments make me realize the sad state of the tech industry.

    Look, who gives a damn if the guy is a "people person" or not. When they come to you and say that they're not paid to document or be a people person, that's correct. They did not go to school, spend their lives learning how to "be a social butterfly", they went to school for coding.

    Their job description, in this case, says "programmer" not "social worker".

    I'm sure if you took the time to ask "Josh" about what he's doing he would be more than willing to tell you, but only if you're not sitting there trying to derail the conversation to bullshit about fantasy football the whole time.

    I should know..I'm this type of person. I'm not the crazy genius that many people here have been discussing, but I'm "that guy". I've always pretty much been "that guy".

    That doesn't mean I'm "that guy" for every computer-related incident, but I certainly know my shit and far more than most of my peers.

    1. Re:And this is why.. by ztransform · · Score: 1

      They did not go to school, spend their lives learning how to "be a social butterfly", they went to school for coding.

      Err.. no one goes to school to learn how to code.. that's something they do in their lunchtimes in the library escaping the bullies that will deck them for being too "smart".

      If you didn't endure some level of suffering to get where you are then you are weak, not elite.

      I certainly know my sh** and far more than most of my peers.

      The problem is that your peers can't back that up with evidence; when your peers don't understand your code and find you unwilling to explain why you did what you did then they have no reason to believe you know what you're doing.

      Everyone knows that if you can't explain a concept to a child then you clearly don't understand the subject yourself. If you won't then people wonder what you have to fear from being made accountable for your actions.

      In my experience in dealing with anti-social contractors I've found them all to be wanting in their technical abilities. Their greatest problem is that they consider themselves to be an expert which almost always means they know very little. The saying "the more you learn, the more you realise how little you know" applies.

      All developers should be asking questions.. "is there a better way of doing this? Of the many ways of doing this which is best for everyone?" Those who say "this is the only way to do it", or "you're stupid if you don't know MY way" clearly have not been around long enough to realise there's rarely one holy solution to a problem.

      I do my best not to be "that guy". I try to document, communicate. I try to leave a company in confidence that they won't need me back, but very much want me back. I've had men come to me at Christmas parties and tell me I'm the smartest guy they've met - though I'm pretty sure they got that wrong.

      If you treat people with respect and educate them then they will respect you and the overall productivity in the team will increase by multiples. Communication is increased and overall morale improves.

      Taking pride in being "that guy" is something to be ashamed of - and should I ever be a software manager I'd have you dismissed without hesitation.

    2. Re:And this is why.. by geekoid · · Score: 1

      Wrong.

      There are certain expected social norms from all people.

      Not shitting in the flowers is one of them. We aren't talking about being the life of the party, or knowing everyone's name. We are talking about basic sane social behavior.
      Your doctor doesn't go to school to be a social butterfly either, but you don't want him insulting you and crapping in your yard.

      And yes, if you are a programmers, documentation is part of your job, just like it's pretty much part of every professionals job to some degree. If you school did not teach you that(doubtful) then your school failed you and you are not prepared to be in the real world.
      I a not talking about end user documentation, but basic coding documentation.

      I'm that guy as well. I don't know jack about the local sports, and I focus on the job and the BS part about work is something that takes an efforts to do.

      "...but I certainly know my shit and far more than most of my peers."

      Doubtful.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    3. Re:And this is why.. by geekoid · · Score: 1

      "If you didn't endure some level of suffering to get where you are then you are weak, not elite."
      WTF does that mean?

      It seems to me you are around the wrong people.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  260. OFF TOPIC by Anonymous Coward · · Score: 0

    Re: Your sig...

    How is it that a government BY the people and FOR the people is afraid OF the people?

    It is because they can remember from whence they came...

  261. Re:These guys are all right. by Weaselmancer · · Score: 1

    I kind of figured that's how you felt; I think it's important to explain it to people a bit though.

    Sorry for being unclear, and thanks for calling me out on the carpet and making me clarify my position a bit.

    On the contrary, the power that comes with the knowledge that one can make decisions to move towards ones goals is astounding.

    Oh, absolutely. For me it came by accident but the end result was the same. I started off like the original AC's post. Angry and angst ridden. What you don't know when you live your life that way is that you're hurting yourself. The anger is yours. Maybe you didn't start it, but you're the one cultivating it years down the road. If you let it go, things improve almost overnight. Did for me anyways.

    I feel bad when I run into my friends from back then. I've been called a sell-out by people who can't afford basic health care. It's mind boggling.

    I guess what I'm trying to say is that the "boring, polite and pointless" life the original poster was railing against is actually full of freedom and joy. They might see an office cube where I have to sit for 8 hours a day, but instead I see a lifetime of health care, paid bills, and hugs from my kid. I gain everything, and all I had to do was give up hating everyone for "being normal".

    --
    Weaselmancer
    rediculous.
  262. The customer viewpoint by Anonymous Coward · · Score: 0

    I am a customer. I don't write code, I write requirements, vet contracts, and authorize expenditure of money.
    You bid on one of my contracts and there will ALWAYS be a documentation clause in there. And a QA clause, and a separate acceptance test clause, and milestones and so on.
    You don't deliver properly documented software, you and your team will be on the pointy end of my bright red acrylic fingernail, and your company will be doing it out of pocket.
    Just sayin' the customer that lets a company put 'documentation in phase 2' deserves the pilin' steam of unmaintainable crap they get for a product at the end of the day.

    (And the guy who makes trouble just so they can 'fix' it later, they're easy to spot, they're the ones that with hold information from their own team, don't document meetings, and refuse to respond to email....I'm lucky, I'm old enough that I learned shorthand in high school, I keep contemporaneous records of conversations with these buzzards, they never cross me twice)

  263. Irreplaceable + Hostile = Not Usable by billstewart · · Score: 1

    If the guy's irreplaceable, you not only have to worry about him getting pissed off and leaving, you need to worry about him getting hit by a bus (or cancer or heart attack or a better offer from some startup company.) If he's not only irreplaceable, but a hostile troll, you need to worry about him getting shot in a fight in some bar because he pissed off somebody else who had no social skills either.

    On the other hand, if he said he didn't document what he did because he had a deadline, his manager needs to whack him with a clue bat about deadlines and priorities, and about modular programming with well-defined interfaces even if the modules themselves may be opaque. That doesn't mean there isn't a place for people whose real skill is finding problems and telling people what to fix, but you want production code built in ways that can be used.

    And the fact that Josh stayed at the company as long as he did meant that Janet either didn't take the job there or didn't stick around, which cost them a lot of money that they didn't know how to measure because they only saw the HR costs of trying to hire her, not the value of the work she didn't do because she'd left.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  264. Brillant, definitely. by Anonymous Coward · · Score: 0

    Brillant

    - Paula

  265. It's a Cost/Benefit thing by pugugly · · Score: 1

    My problem with this comes from both ends.

    A: The Management team that gets involved in a co-dependent relationship with *one* person on the team, and treats the rest as disposable.

    If that one person is the reason you can't keep other people, then you need to verify - is this guy *really* worth any three other programmers you have. And if so, is there a reason you can't get somebody as good that *not* a personality problem - since evidently that would be worth six other programmers - him and the three he's been costing you.

    B: I've seen a lot of people that bitch and complain about the corporate 'fit all pegs into round holes', right until they're in a corporation that actually allows people some individuality and recognizes that, even in the same job, people have different strengths.

    Turns out, you're not always the star, and the company may go further for somebody else with unique strengths. In which case, the problem is obviously that the company lets themselves get co-dependent with these people - not that they were *actually* worth it.

    Unfortunately, both of these cases sound the same when the co-worker is grumbling about it after work.

    Pug

    --
    An Invisible Entity of Vast Power whose existence must be taken on faith alone: Liberal Media
  266. A-holes are a-holes by al0ha · · Score: 1

    Whether they be developers, managers, janitors or CEOs. There is no good reason to be an a-hole and those who are should not be tolerated for any reason.

    --
    Did you ever wake up in the morning, with a Zombie Woof behind your eyes? -- FZ
  267. Re: brilliant and dangerous? by 91degrees · · Score: 1

    Yes. Ultimately, I think I value someone who can churn out clever code quickly less than you.

    I mean I'm sure they have their uses, but most companies just aren't so innovative.

  268. why should we do that? by Anonymous Coward · · Score: 0

    we enable the niggers....

    at least josh is useful

  269. Re: brilliant and dangerous? by Anonymous Coward · · Score: 0

    Parent anon has an excellent point. I used to have a boss that did exactly this. He developed databases in this obscure program barely even used in the US and obfuscated his code purely because he thought that he would guarantee he'd have a job forever. It worked for awhile but now he is a *former* boss. Even worse he's had a hell of a time getting another job since no one else wants to hire someone who programs in an obscure db program.

  270. As a Josh by Anonymous Coward · · Score: 0

    I demand you keep enabling me or I will leave the company with the million lines of undocumented spaghetti code I created!

  271. Re: brilliant and dangerous? by ukyoCE · · Score: 1

    It's unfortunate that a lot of companies let engineers get away with "speaking engineer" and claiming themselves to be Rodney McKay-esque geniuses doing the impossible and not having time to document or explain it to anyone.

    It always ends badly. I'd bet a lot of these companies go under before they figure out how much more productive they would have been with engineers who could work well on a team and document+QA their work.

    I've seen a lot of examples play out where the "lone genius coder" finally gets forced to have a bunch of underlings hired to work with him. And that's when the underlings start realizing that the guy isn't a "genius", he's just a jerk who treats people like crap, writes bad code, and doesn't understand the most basic good software practices. Like testing - of any sort.

    Either the organization is structured such that the underlings can get across the Lone Genius's stupidity and get him fired (or demoted to a position where he's forced to work well). Or the organization is structured such that the underlings all get frustrated and quit.

  272. Re: brilliant and dangerous? by gamefreak1450 · · Score: 1

    Having Asperger's isn't a good excuse to do a poor job or to be anti-social, or unprofessional. [snip] I don't take the idea, that I have a disability so you need to deal with my Crap mentality, it is basically reinforcing that they can behave badly, without having them work on improving themselves.

    With all due respect, Asperger's is not a choice for those who have it - it's them. They can't control who they are or what they do any more than the severely autistic can see their own situation or you can drastically change who you are (even though your personality may be a little more socially acceptable). If you were arguing against hiring autistic adults, perhaps there is an objective argument there. But, please, do not expect miracles from people with untreatable medical conditions.

  273. Re: brilliant and dangerous? by ukyoCE · · Score: 1

    Exactly.

    One of the problem's with these Lone Coders is that no matter how hard they work, and how much code they churn out, odds are they aren't even solving the right problem. To solve the right problem you have to talk to the business.

    More often than not once you get a real development team with competent leadership, the Lone Coder's work is going to be almost entirely replaced over time by refactoring. And note that I said refactoring, not trying to rewrite a massive app in one fell swoop while the business continues ramming its head for months (or years) against all of the problems "unworthy" of the Lone Coder's time to fix.

  274. Easy solution. by Anonymous Coward · · Score: 0

    Don't let this guy work around other people. They don't like other people anyway, so they will be thankful. Other people don't like that guy so they will be thankful.

    Make him develop something and throw it over the wall to someone else to be cleaned up and maintained. Locate and train others to high standards and then fire him once you don't need him anymore.

  275. I fired a Josh... by Anonymous Coward · · Score: 0

    To make a long story short, the team lived.

    It's not just the code, though. People like this warp the dynamics of the team, often not letting others thrive in the environment. Short term, it can hurt. Long term, getting rid of them is a good thing.

    Of course, if they're just a fool with an over-rated sense of their own skills, it's not even that hard of a decision.

  276. There is exactly one strategy. by drolli · · Score: 1

    Ty to replace him silently ASAP by hiring sbdy else. There are a lot of good and a moderate amount of excellent programmers around who aren't assholes. Making insulting remarks to female coworkers can bring the company directly in front of a court. Undocumented code/coding prodecures can make you/your customers loose certain certifications (thing about automobile industry, medical devices etc.)/not pass such certifications when required. Not team working is costing the company money. And anyway, as the story points out you cant rely on him.

    So, find a replacment and on day one give Josh two minutes to pack his things, then throw him out, dont expect that he cooperates in anything, so make the decision to clean up the mess he left.

    1. Re:There is exactly one strategy. by geekoid · · Score: 1

      Be sure he is walked out by two uniformed security guards.
      March him out at about 2 on a Thursday, when most people will see that the company is taking care of it.

      Be prepared to hire a couple of temporary contractors to sit down and just figure out what he was doing. Not the details, just his actually tasks.

      I would wager 100 bucks it's not nearly as much as they think he is doing.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    2. Re:There is exactly one strategy. by drolli · · Score: 1

      > I would wager 100 bucks it's not nearly as much as they think he is doing.

      And i would not bet against that.

      As a matter of fact, i once had the ungrateful task to supervise some Josh in something (writing a master thesis) which was not exactly on his line of talent (he was a brilliant engineer who decided life is too boring and studying another subject would be a remedy for that), and he grossly underperformed due to his unwillingness to accept a good advice before the shit hit the fan and his opinion that he is so brilliant that de does not have to learn something. Somehow when the shit finally hit the fan, he made it sound like it was not his fault not to listen to the advice (actually with an accusation in the undertone that I had not been insisting enough in convincing him to listen; Bystanders working in the same room usually had the impression that my attempts to steer him took a little bit too long); the usual sentence was "who could have known that?". When i think about it, he also made diminishing comments about the work of a female co-master student who was undoubtedly the best we ever had in the chair (measured by all scales available, grades, prices, publications and also personal opinion). It finally cumulated in him skipping me as his direct supervisor and talking directly to the professor whenever he did want to do some task actually was necessary for his thesis (I did not load him with anything additionally).

    3. Re:There is exactly one strategy. by drolli · · Score: 1

      That is a "did *not* want to do some task" in the last line...

  277. Re: brilliant and dangerous? by EriDay · · Score: 1

    "The major problems of our work are not so much technological as sociological in nature."

    Peopleware - Productive Projects and Teams by Demarco and Lister.

  278. Re: brilliant and dangerous? by Anonymous Coward · · Score: 0

    I've run into two interesting things about documentation and convoluted code.

    Number One:

    First, when coding on Microsoft Foundation Classes about 7 years ago, I hit *so many* broken things that could only be made to work if they were done in a convoluted, nonintuitive manner. Sometimes I would have several lines of ugly code followed by 30 or 40 lines of comments explaining (1) how this should have been written, but can't be because MFC is broken, (2) briefly, why the ugly mess is the only way this can be done, (3) what this code actually does, and (4) if changes need to be made, where to start in order to understand what to do.

    It was a temporary position, and I knew I was going to have to hand over my code to someone else who wasn't familiar with the many ways MFC would fail without returning an error, return bogus errors when nothing went wrong, returned pointers/handles that pointed to random addresses, crash when passing in a perfectly valid set of arguments, require you to re-cast classes in an incorrect way, not inherit things that were supposed to be inherited, .... the list goes on and on. Anyway, I knew I would have to hand over the code, and if someone tried to clean up the code by eliminating what looked like unnecessary complexity or strange ways of casting things and invoking methods that disagreed with the official MFC documentation, things were going to start breaking in strange ways (there were plenty of things in MFC that, if done as the official documentation says, would work in Debug but break in Release, or vice versa).

    The situation was similar for some Matlab code I had written, and the person who was going to take over the project was actually intimately familiar with Matlab; unfortunately, new features introduced in the new version of Matlab (which we had to start using because a 3rd-party product was not going to be supported any more unless we moved to a new version of it, which required upgrading Matlab) broke some code that they should not have broken, sometimes in very frustrating ways. One problem was that some things that worked in the interpreter would behave differently when using the Matlab compiler to convert the M-files to C++, and start returning different data or returning error conditions for things that worked in the interpreter. Since the debugging options were limited with the Matlab compiler at the time (it's much better now), compiled Matlab code did not have any sort of embedded mini-interpreter (now it can), and several restrictions (both from licensing and IT policy standpoints (only "developers" were allowed to have anything with "compiler" in the product name, and developers were put on a segregated network as a matter of security policy)) meant that we absolutely had to have our code work when compiled. Another problem was that some functions which were the recommended way of doing certain types of file I/O in the last version had become officially unsupported and would lose some functionality in the next release, and they had been replaced by a compatibility layer that called the new functions -- sort of. They actually called a lower-level part of the API that was subject to change from version to version; it was the same API used by the new functions that were supposed to be used for those types of file I/O, but in that version, the new functions did not yet support some things that could be done with the old functions. So, the old code worked, but we knew it would break in the next version of Matlab; the new functions would not do what we needed, and we did not know when Matlab would have that functionality; the lower-level API would handle it, but that would probably change within a few releases. The only feasible option (since we weren't just going to sit around for a year to see what the next couple releases of Matlab supported -- not to mention that licensing Matlab and the Matlab compiler for each new release cost money and had to be approved, and since the IT department was in the process of being outsourced

  279. I think that's by BitterAndDrunk · · Score: 1
    • Cheap
    • Fast
    • Correct

    Pick Two.

    --
    You better watch out, there may be dogs about . . .
  280. WATCH OUT FOR THAT BUS! by Anonymous Coward · · Score: 0

    In one of my jobs I was asked to document all my procedures and code I had written. I was told the reason for this was that if I was "Hit by a bus" than my job could be performed.

    Three months later I was laid off and replaced by a college student. The replacement was clueless and a few months later decided not to show up.

    I was left with a subconscious fear of buses.

  281. Re: brilliant and dangerous? by coxymla · · Score: 1

    I've been in exactly this situation: we were an custom GPS electronics company where one very talented electrical engineer built the hardware from the ground up ... I signed on as his lackey ... because his time was 'so valuable' ... The -very- first thing they had me do when I arrived was produce page after page of documentation on how the hardware actually worked

    When I asked him why there was no documentation (or very poor documentation when there was) the answer was a combination of "You shouldn't need documentation" and "I'm not paid to document things."

    Well, actually... you are.

    No offense, but it sounds to me like no, he wasn't paid to write documentation. You were. The company thought for good or ill that this super-engineer's time was better off spent doing what he did best, and a cheaper hire was found to do other cleanup work like writing docs and sharing/storing knowledge. Nothing wrong with that.

  282. Re: brilliant and dangerous? by Anonymous Coward · · Score: 0

    Yeah, and there was nothing in the article about him taking a dump in the lobby flowerpot either!

  283. This sort of thinking... by gbutler69 · · Score: 1

    ...is absolutely foolish! Think about what you are saying. "I don't want to have to ever eat crow and explain why something took longer than originally thought. I'd rather always get an overly long estimate and stick to it that way I don't have to look stupid/incompetent or like I can't manage." Grow a pair loser. Learn how to set expectation and how to communicate when those expectations change and why. All the whining so called managers make about "expectations" shows them to be completely useless and that they have nothing to contribute to the overall process (this from a Project Manager). Most PM's I've met are completely useless and have nothing of value to contribute. Most are in their positions, like executives and managers of any stripe, because they have charisma (symetrical features, tall, etc) and know how to tow the company line. They couldn't bring a project to fruition without the people actually doing the work if they're life depended on it. MBA's are a total fucking joke. Look what these fucktards have managed to do to the economy and society. They're a bunch of fucking shills that need to be put up against the wall and shot!

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  284. Damn! by gbutler69 · · Score: 1

    Too bad the switch to turn on the Freezer is on the other side of the lake and we don't have a boat. Shit! If only we had someone who could walk on water (or swim)!

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  285. Re: brilliant and dangerous? by Nefarious+Wheel · · Score: 3, Informative

    Pair programming sucks.

    Remember that scene in Amadeus where young Wolfie was composing using the billiard table as a desk? All those symphonies in his head, interrupted when someone came in and broke his concentration. The music stopped.

    Programming can be an extraordinarily complex, involving activity that works best when you're concentrating, producing and on a roll. It only takes one prick to break the bubble of concentration. And yes, you may extend that metaphor.

    If you really want to do the armpit-to-armpit teamwork go back to Yourdon's original structured programming team. You had a senior guy, a junior guy, and a librarian. Today that would be senior guy, junior guy, and documentor. It works in threes, but not in twos for some reason. I think it has something to do with allowing intelligent people to lead design, rather than have to check around to see if what they're doing is ok. In pair programming you have no leader. With no leader you have no direction and thus no progress.

    Ok, I may be out of touch -- the half-million lines of code I delivered was a good few years back. But I can't think when people are shouting around me, and I get paid to think.

    --
    Do not mock my vision of impractical footwear
  286. Re:Reiser Drop down menus should've had an OK butt by Anonymous Coward · · Score: 0

    You have *pictures* of Reiser killing his wife?

    Hold on for a sec while I make a phone call...

  287. Re: brilliant and dangerous? by Nicolay77 · · Score: 1

    Come on, my standard response time to implement a feature in my current job is 15 minutes. When I was in college I was always the first or at least the second finishing the exams, about an hour earlier than anybody else.

    But I can talk to people, I'm nice to coworkers and clients.

    It doesn't mean I was the best, a classmate was faster than me by about 20% consistently. But he also was very sociable and could work very well in a team.

    If someone doesn't document, and is harsh with coworkers and clients, I don't want him in my team. Period.

    AFAIC, he can go and fund a startup or something.

    --
    We are Turing O-Machines. The Oracle is out there.
  288. Re: brilliant and dangerous? by Anonymous Coward · · Score: 0

    Bullshit. The business sets my priorities. Where is the documentation? OK, remember when I gave you that estimate and you cut it in half? The half you cut is where the documentation would have been. Not my fault, never was. The business made that decision. That's why I laughed in your face when you asked for it.

  289. Re: brilliant and dangerous? by paulgrant · · Score: 1

    >If their code is so useful in the first place (and it is by virtue of the fact that most companies would rather hire one talented developer than several mediocre ones), why not ensure they stay?
    >>Because it is usually quite possible to hire developers that are just as good, but that are not jerks. They may be slightly less brilliant, but they make up for it because they can actually work well in a team.

    Presuming your original assertion is correct. I'm not convinced that brilliance is mutually exclusive of teamwork; else how do you explain Oppenheimer and the Manhattan Project? Personally I've always felt that
    a true measure of a man is not his dick-size, wallet, girlfriend, car or what have you, but rather his ability to work with others to accomplish a goal -- note there is no presumption of liking a person built into that
    statement. I've worked with people for years I would have cheerfully beaten to a bloody pulp and paid for the privilege.

    >By way of disclosure I am one of those developers - and I argue to have things taken off of my plate (documented, designed etc) outside of my scope specifically because I dont know what will happen tomorrow (hit by a bus, food poisoning etc) and a team of people like u most likely will take over.
    >>First of all, you assume that I'm one of the "rank and file" devs. In practice, I had been in the role of "star developer" in my division in the past, so I know how that works from the other side. But note that we aren't talking about this phenomenon in general, but about a very specific subset of such people, who are "good" (for some definition of it) on the technical side, but are arrogant and uncooperative with other people whom they perceive to be lesser.

    I get arrogant all the time; I'm also the person people come to when they're having: a) legal problems b) medical problems c) life problems d) work-related problems e) loans f) cheering up. Arrogance (as a word) is nothing more than someone's description who knows their shit cold *and knows it*. I dont presume to know everything; I do presume to know that *what I do know*, I know *well*. I am extremely uncooperative when it comes to bullshit. I am *extremely* cooperative when it comes to solving business issues including employee quality-of-life. I fit the articles profile quite well, and I am sick of hearing about it -- y'all are venting, which I understand - this is merely my response (that if you brought this up in front of said coworkers, they would undoubtedly mirror) -- GROW UP, GET A THICKER SKIN and READ/LEARN OUTSIDE OF WORK.

    >Your requirements for (excessive) documentation is a direct transfer from my finite amount
    of time available on this earth (solving problems) subsidizing your mediocrity. GROW!
    >>Why do you assume that I require "excessive" documentation? When I say "bad docs", I mean stuff like 50 kLoC of code that has not a single comment in it; not forgetting to fill in the "detailed description" in the documentation comment for a private method!

    When someone usually bitches about documentation, its generally because they want every function documented with fancy descriptions & uml. write your code small, modular, with unit tests. its not rocket science.
    If you do something tricky (like using a GPU to calculate veroni diagrams) then include a link to a paper, or a psuedocode overview of the algorithm/engine in question; assumptions on input, same. todo/suggestion for improvement, same. other than that the code should pretty much speak for itself.

    >>By the way, regarding the "finite amount of time" - that's all well and good when you solve problems for your own sake.

    I would say stop right there ;) I own my time, regardless of compensation, agreement or anything else other than involuntary incarceration. Anyone that forgets that (including the bulls) learns otherwise *quickly*.

    >>But when you're at work, the time is not "yours", really - it's bought by the company you w

  290. Joshettes? by spaceyhackerlady · · Score: 1

    I've met a few "Josh" type in my life, but have never met the female version. Do they exist?

    I've known some frighteningly smart women, and am pretty handy with a C compiler myself. But somehow women do not get in to this mode, apparently having only minor issues with personal hygiene, working with others, and so on. Why?

    ...laura, who has her eccentricities, but nothing like Josh

  291. Oh, I read that wrong... by DamnStupidElf · · Score: 1

    Eric Spiegel tells of one such Josh, who wears T-shirts with offensive slogans, insults female co-workers and, when asked about documentation, smirks, "What documentation?' Sure, he was whipsmart and could churn out code that saved the company millions, but can we please stop enabling these people?"

    For a second I thought they were starting to describe their CEO or other high level manager who instead of saving millions of dollars, was raking in millions of dollars in salary.

    The bottom line demands that Offensive Josh the brilliant coder be retained, and the senior management trashing the company be fired. Won't somebody *please* think of big business's bottom line?

  292. Re: brilliant and dangerous? by mdwh2 · · Score: 1

    But that's not really what we're talking about - the problem is that Josh didn't build the bridge he was asked to (refusing to write documentation etc). It's like them building you a bridge, but it requires them to continue to maintain it, because no one else can. And one day, they're gone, and the bridge falls apart. If they were asked to build a bridge, and everyone else is capable of building a bridge that stays up like they were told, yes that's their fault.

  293. Loser programmers by EmperorOfCanada · · Score: 1

    I find that this argument tends to also be used by loser programmers against the brilliant people who try to simplify as much as those psudo-geniuses who make things more complex. I had this happen years ago when I pointed out that we didn't need to reprogram the Linux Kernel to filter packets and could build a plug-in for a firewall to do the same thing. I have also seen this happen to people who wanted to implement complex ideas like source control, backups, modern OSs. "He's out of control and had no respect for process."

  294. I was Josh. by Wargames · · Score: 1

    When I was younger, I was Josh. Well, I may have been the Josh in the story, except for two things, I wrote clean well-documented code, and I generally friendly to people. Some brilliant people place a high value on beautiful code (code that works and reads well and is maintainable). I admit, my people skills were not (and still are not) up there with my tech skills but then I found Toastmasters, but that's another story...

    Anyhow, I was there that Friday night. There was a dev staff meeting. There was a problem. I had a crazy idea that I was sure would work, the rest worked on a conservative approach that would have been 36 hours of hell for the entire staff. The customer (AT&T) needed time and cost sensitive international routing up on their switch before the Mother's day weekend.

    I wrote a program that in turn wrote a 300K line program from a 250K line spreadsheet that saved the day and perhaps our business from that customer. It took about an hour, and I was very happy to have had the opportunity to have solved the problem and I may have hurt some feelings with my exuberence. --There are not many that get to brag about writing 300K lines of well documented working code in an hour!

    I wanted to make one more point. I think the correlation between Brilliant (technically) and Quirky is going to be high for one major reason. Brilliant people get bored easy in the public schools, where brilliancy (and the brilliant ideas it puts in your head) is often rewarded by getting the crap beaten out of you. I suppose getting the crap beaten out of you can cause you to get quirky too.

    When you become an adult, and find that your brilliacy is now rewarded (50K a year will buy a boatload of beer!) you can easily become like-a-superstar arrogant, to a certain extent. I got away with the leave-without-coming-back-for-a-few-days thing and I did the poor hygiene stint. And I did wear whatever t-shirt I wanted, and I played Black Flag and Dead Kennedy's loud from my office. And I helped make my employers rich too. Drinking 50K worth of beer can also make you quirky. Then I found hashers, but that's another story too...

    I also was amongst the first group to get laid off when the going got rough when the telecom market busted. I can identify with Josh. I'm sure my lack of people skills contributed, or it may have been the quirkyness.

    I'd like to think I am not Josh anymore.

    In answer to the original question, brilliant people can be dangerous and make you rich like Bill Gates.

    --
    -- Each tock of the Planck clock is a new world and here we are still life. --
  295. Re: brilliant and dangerous? by TapeCutter · · Score: 1

    No there is "nothing wrong with that" but I doubt that is the case in TFS. What you're thinking of is a technical writer, they are not particularly cheap and you only really see them in projects a tad larger than the two person operation described in TFS. In my experience people who understand the development lifcycle (the new guy in TFS) are more expensive than the 'genius' who grows something useful in their cubicle that ends up taking more time than they have got to maintain. IMHO the 'genius' in TFS sounds threatened by someone "doing it right" and simply doesn't want to know about it.

    In other words: The "super-engineer's" baby is growing up, wether he likes it or not.

    Note that due to the diversity in the scale and percieved importance of any particular project there is no magic "one shoe fits all" recipie for what "doing it right" actually means, although the main ingedients are common knowledge amoungst "good" practitioners.

    --
    And did you exchange a walk on part in the war for a lead role in a cage? - Pink Floyd.
  296. Re: brilliant and dangerous? by sgt_doom · · Score: 1

    Bravo! The very best documentation exemplifies brilliance. The first great documentation I came across was the Perkin-Elmer 8/32 processor manual. Absolutely brilliant.....

  297. Re: brilliant and dangerous? by JoeMerchant · · Score: 1

    "Josh" is clearly not the ideal employee, but if you've hired him and you accept the way he works, you get what you deserve.

    I've seen more than one company hire in a cowboy to "fix things" whether in code, or processes, or whatever, they might be a consultant, or even a new Director, but whatever the case, they come in and screw things up for 6 months to a year, take their fat compensation package and head for the horizon. People bitch about them for years, but it's really the morons who hired them that deserve all the credit.

  298. Two Words by Anonymous Coward · · Score: 0

    Blanket Party

  299. Hitting the nail on the head by EmbeddedJanitor · · Score: 1
    If you rely on a Josh you're fucked!

    Sure, it is handy to have a Josh that miraculously saves your project, but the fact that you needed that Josh in the first place says that you don't have the right staff/skill sets. Needing Josh is a sign to management that there are some serious shortages that need addressing.

    Sure, all companies sometimes need firefighting, but the REAL firefighters are those that not just put out fires, but help to prevent there being other fire call outs. Really effective fire-fighters help mentor others and, in essence, make themselves redundant. [Aside, firefighters (of the thermal sort) actually spend a lot of their time doing fire safety inspections etc for this very reason].

    Those Joshes that code so cryptically that they are needed forever are essentially blackmailers and saboteurs. They force you into a position where you have to put up with them to keep functioning. Make a plan to dump them and replace them.

    I've worked with a few Joshes in my time. The one was brilliant, but it took the next three most productive engineers to clean up after him and quite a few almost as clever people just quit because they could not work with him. When you realised that the cost of having him around was not just his remuneration, but also the opportunity cost of the next three engineers too, then he didn't look as valuable.

    --
    Engineering is the art of compromise.
    1. Re:Hitting the nail on the head by obarel · · Score: 1

      I'm not sure real fire fighters like this analogy...

      "Of course we follow procedures when we fight fires. Of course it's all documented. Of course we have to prepare a full report about what happened any why it happened. Of course we train other people. Of course we're nice and helpful to anyone we meet, just because we're fire fighters doesn't mean that we're arrogant bastards."

  300. Re:Football on Slashdot? TO? by colinrichardday · · Score: 1

    Most recently, from the Dallas Cowboys. He was then picked up by the Buffalo Bills.

  301. Re: brilliant and dangerous? by fugue · · Score: 1

    It's been a while so I don't have a reference at hand, but I thought that pair programming had been pretty rigorously shown to improve code output (by some measure that eludes me, but involving quality and production rate) under a wide range of circumstances? Perhaps not "always", but "more often than not". I know people complain about it, and I know what you mean about the concentration bubble, but the numbers don't lie. If, that is, I'm remembering them correctly, the experiments were well-controlled, the pairs were typical, etc...?

    --
    "The biggest problem with communication is the illusion that it has taken place."
  302. quiet but quirky is sometimes a prob. by Teunis · · Score: 1

    I've been told I'm like that (a little). I like being sociable, I think documentation is necessary - and helpful to people outside of developers.... but I have PTSD and occasionally have troubles because of it. (made far worse at my last job because russian ex-military "programmer" threatened my life at work)
    it's been a while since I've worked. I miss it. I'm apparently really bloody good at what I do - but apparently I undervalue myself.
    (yes, some people still do that)

    I just need some quite ethically nice (relatively) job again. (I'm not that picky - but I can't work with spammers)

  303. Never too soon to fire someone by efalk · · Score: 1

    A CEO friend of mine once said "It's never too soon to fire someone".

    A person like "Josh", no matter how brilliant they are, can actually produce negative work as a side-effect of the chaos they sew. They may be productive as hell, but their impact on the productivity of the people around them can cause more harm than good.

    My friend had to fire a number of people over the years who caused big problems. He never regretted firing someone, but he often regretted not doing it sooner.

    Oh, and by the way, writing "clever" code just produces code your peers (and you, six months later) can't maintain. I'll bet Josh's bosses regret not requiring code reviews.

  304. Re: brilliant and dangerous? by wrook · · Score: 2, Interesting

    Programming can be an extraordinarily complex

    Sometimes this is true. If you have to do a lot of math, for instance, it can be true. But, if I look back on my career of 20 years of application programming I can think of only 1 or 2 instances where the problem I was working on was difficult. The rest of the time it was the code that was difficult.

    If you find that programming is extraordinarily complex a substantial amount of the time, then you have some problems. It's only that way because you or your team have created complexity when you really don't need it. Pair programming with somebody who is extremely good at refactoring can help you learn how to improve.

    I know this is hard to believe. Especially when you are used to being the superstar programmer on the team. You are able to deliver when others can't. And your code is probably better than other code you've seen, so you think it must be really good.

    But there's a whole new level you can get to. I'm not saying this to put you down. I'm still working hard to improve myself. But with the approach you are taking, you'll hit a glass ceiling pretty quickly where you can't get any better (from the sounds of it, you've already hit it). I just want to encourage you to look at other methods so that you can break through the place you're in now.

    When you do get through it, you'll find that programming extraordinarily simple, but that "good taste" is difficult to refine. And that refinement requires conversations with other programmers (both in code and in human speech). These conversations require give and take, not leadership; learning and sharing, not enforcing direction. I hope that helps (but even if it doesn't, good luck anyway :-) )

  305. Re: brilliant and dangerous? by stephanruby · · Score: 3, Insightful

    If you really want to do the armpit-to-armpit teamwork go back to Yourdon's original structured programming team. You had a senior guy, a junior guy, and a librarian. Today that would be senior guy, junior guy, and documentor. It works in threes, but not in twos for some reason. I think it has something to do with allowing intelligent people to lead design, rather than have to check around to see if what they're doing is ok. In pair programming you have no leader. With no leader you have no direction and thus no progress.

    That metaphor can be extended to a surgical team, where you have one chief surgeon and everyone else around the table has a specific role and is there to assist. Or it could be extended to the 911 phone operators, where there is usually one operator on the line, and two assistant operators listening on the call and following the directions of the first (although, that part is almost never shown on 911 reenactments).

    Personally, I have no problem letting another programmer take the lead when pair programming, my only two requirements are that we set some time aside for debriefing each other beforehand (so that I know where we're going) and that we set some time aside for debriefing each other afterward. I don't usually interrupt (unless I have to), and besides I take copious notes when sitting shotgun -- this is a trick I use to keep on paying attention -- while keeping the things I say to a bare minimum until later.

    I find it also helps to let the person typing make their own mistakes, a typo, or what have you. Usually the guy typing will correct himself without interruption needed on my part. So if I see an error, I take a quick note of it in the margin of my notebook, and it's only after 10 or 15 seconds or just before the compile cycle, that I'll point out the errors as tactfully as I can.

    That being said, that Amadeus reference you cited scares me. Most programmers are not at the Amadeus-level, and yet most programmers think that they are. And I can't tell you the number of times I've had to stop a fellow programmer from coding because he had no clue where he was going, and no clue on how to get there, he just wanted to make himself feel better by coding something -- anything -- right away.

  306. No you can't by ZeroNullVoid · · Score: 1

    "...but can we please stop enabling these people?"

    Nope, if you do they will leave and take your business elsewhere.

    If you do not fuel them, they will grow bored and find another job, even a completely different project or job and excel at it.

    Same reason a skater will stop doing things if people stop enabling them.

    This is just my opinion, but why not encourage them other ways.

    Same reason your child will stop making A's in school and join the classes for numbskulls, if you stop praising them.

    If you don't enable them, they will find something else and the only people who will suffer is the location that stopped enabling them.

  307. I've got a better story. by mightyhe · · Score: 1

    So now the self-promoting guy who spends his time writing blogs about how bad the smart programmers smell gets the job done better? Yea, right.

    The article reads like a typical journalistic straw man. Strange cave dwelling programmer is rude, smelly, and not at all chivalrous. Bad programmer (if you're not convinced yet that our antagonist is bad, the story will add other irrelevant, and probably untrue details to help persuade you, generally by trying to conjure an image of someone that's done you wrong). Wouldn't it be nice to be rid of them? (duh!) *sigh*, if only they weren't so in with the establishment (a set up for bringing down the expert). Something happens to show that programmer was just mediocre (hooray!). The brave consultant/knight saves the day. And they lived happily ever after.

    This story is pure rubbish. First of all, there are plenty of talented, polite folks that bring the whole package to the table. I don't claim to be one, but I am fortunate enough to work with a few. Also, the consultant rarely succeeds in doing anything other than screwing things up while they firmly attach themselves to the money mammaries of whatever company they are milking.

    Fortunately, the reverse story is generally true. Evil snake-oil consultant is latched on like a lamprey. Smart, humble, articulate, lemon scented programmer saves the day with a elegantly simple technical solution. Other programmers rejoice at their new found freedom. The new knowledge spreads through the technical ranks, elevating everyone's game.

  308. All mostly incompetent, useless, idiots by Anonymous Coward · · Score: 0

    If we built bridges by allowing stupid people to claim their brilliance; that think Ruby, Python, are 'great', and otherwise allowed opinion to replace engineering for things that might fall down, then we would all be dead.

    99% of programming is pathetic, and Linux is just an example of how some small amount of good engineering - things like kernels - get hijacked by mediocre morons. After that layer we get GUIs that f**k up all the time, applications that sit on top of them such that 'stalled' is the most common result of a copy, and.. oh why go on.

    While the moron who hijacks this culture to try and make themselves 'look better' is moron indeed, the main problem is that 99% of people reading here should not be programming in the first place.

    Who said that programming is for the masses and that the problem is we need easier programming languages? We need to go back to assembly language and.. arrrgh f**k it, I can't be bothered explaining and everyone will just self justify anyway.

  309. Re: brilliant and dangerous? by mabhatter654 · · Score: 1

    except that the job of documentation is seen as a "junior" job, something important people don't have to do. Then the whole engineering department is focused on "getting out of" documentation. The peons are expendable and the seniors "just expect" the documentation to appear without working for it and blaming their underlings.

  310. Re: brilliant and dangerous? by oftenwrongsoong · · Score: 1

    You're absolutely right in what you say. Our lead programmer some years back was supposedly the biggest baddest programming genius on the planet. He didn't poop in the lobby or harass the women but he was definitely the person you did *not* want to talk to. He was cranky in the morning. He was cranky during lunch. He was cranky in the afternoon. Hell, come to think of it, he was always cranky! He pushed everybody away so that heaven forbid, you wouldn't touch the sections of code that he determined were for his magic touch only. Those were obviously the most critical sections of the code, in technical *and* in business terms.

    Fast forward a few years. (Actually rewind because this is in the past.) He was let go. The company damn nearly fell apart because that software, the flagship product, was totally unreliable and customers were fuming. And it was because of the software. Somehow we survived, and along with several other people, I was put in charge of going through the code to determine what it would take to fix it. We looked through it and decided it would be better to commit suicide than to try to fix this thing.

    Let me tell you a little about it. First of all, there was no organization. Unrelated functions would be located together, while closely related functions were strewn about across many translation units. Nothing was declared static. Many of the function prototypes and extern declarations did not match the actual definitions. But this is only the very minor stuff. Things that could be done in a single line of code were implemented in the most retarded way possible. (Think Rube Goldberg machine, only in software.) Error checking? Sometimes, and even then, wrong. Every imaginable problem related to the use of pointers, multithreading, files, you name it. And the worst part? He did not use any form of version control, so other than the current bleeding edge sources (what you would call the head of the trunk), there was no source for any other version.

    And this guy was some kind of genius? NO! He didn't push us all away so we wouldn't "mess up" his perfect work. He did that so nobody would discover that his work was shit. Pure shit. It worked, this software. That's the miracle. But it only worked somewhat.

    We described the situation to management and everyone promptly decided to throw the whole damn thing away and start over. The new system is just fine.

    Somebody once pointed out to me that the cemeteries are full of irreplaceable people. In other words, in a world full of billions and billions of people, where to use computer related jobs as an example, so many people work in this sector that the small subset that participates in open source development is so enormous that you can find *any* kind of software in open source, and most of it is pretty damn clever *and* well documented, you can't convince me that there is nobody else who can do some programming job or another, even if the job is something outrageously complicated. You think skyscrapers, airplanes, hell why go that far, the computer hardware itself, you think all that got built because there doesn't exist another person on this planet smarter than irreplaceable Josh or our grumpy idiot programmer? I'm sorry but every single person in the world is irreplaceable. And yet we're all going to die one day. The certainty of that is just below the certainty of your taxes going up every year. When you have some jack ass like that working for you, you weigh all the options like a responsible businessman and then promptly get rid of him. As many here have already said, it's more important to be a pleasant person who can write software than some supposedly genius who nearly (or completely) destroys the whole company.

  311. Re: brilliant and dangerous? by fractoid · · Score: 1

    I don't know what you were coding with MFC, so maybe you were far beyond my (admittedly rather simple) usage of it back then... but almost every time I thought I'd found a case where MFC was actually broken, it turned out to be my not using it correctly.

    Your experience with Matlab bears this out a little - either you're a very advanced user or (more likely, IMO, for the average AC, although of course you, sir, are not that ;) you're doin' it wrong. Of course, the very rare occasion when it IS the compiler/OS/API that's broken, this will drive you insane... :P

    In general, I apply the same philosophy to big, very-widely-used APIs that I apply to compilers: If there's a problem, it's your fault, not the API/compiler/etc's fault.

    --
    Rampant carbon sequestration destroyed the Dinosaurs' tropical paradise. I'm here to help repair the damage.
  312. Re: brilliant and dangerous? by fractoid · · Score: 4, Funny

    That's because while you're pair programming, you spend 80% of your time programming and 20% of your time talking about it. When you're solo programming, you spend 80% of your time reading slashdot and 20% of your time programming.

    --
    Rampant carbon sequestration destroyed the Dinosaurs' tropical paradise. I'm here to help repair the damage.
  313. Note worth the total cost by terryjamesduffy · · Score: 1

    Programmers like Josh always cost more than they are worth because eventually someone has to maintain their code. The mistake that managers who employ Josh's make is they only cost the initial development of the brilliant code, which if it never needed changing would be correct. We live in a changing world. Who has ever encounted code that never needed changing ? The true cost of code must include maintenace of that code and that is where using the Josh's of this world really costs you because their code is, more often than not, unmaintainable and then what will you do, redevelop using another Josh.

  314. By Neruos by Anonymous Coward · · Score: 0

    Missing the point...

    Intelligence in the area of business is dependant on many things but mostly on two things, Greed or Accomplishment. Greed can be anything the intelligent person is trying to reach and it just so happens his intelligences enables him to reach it. You can not STOP enabling this class of people, as it will most doubtfully, cost you money and a business is nothing without profit. Welcome to capitialism.

    Like greed, accomplishment can push a intelligent person to achieve high expectations, but unlike greed it has a personal goal higher then money, deadlines, milestones or pleasing the higher ups. It is the personal satisfaction that a intelligent person is granted when they are thrown into a difficult, complex, creative or even unordinary situation. The feeling of climbing over and resolving the task is the high they long for.

    Now we have broke out and explained a little about these two areas, some are asking the "what does that really have to do with business?" question. Here is the answer, Business is about profit, no arguement there, business is also about results and good results with a small sacrafice is business as usual. The problem most people outside the intelligent persons class is only seeing the superficial area that directly or indirectly effects them.

    I could go on, but I will give you an example.

    A Business wants a software package.
    The Quirky Dev person proposes that he/she can do it for 15,000$ and 3 months.
    The Consultant person proposes that he/she can do it for 30,000$ and 4 months.

    Do you see the higher up mentality?

  315. Re:These guys are all right. by Anonymous Coward · · Score: 0

    Gandhi not Ghandi...I have no idea why so many Westerners misspell Gandhi.

  316. Not document = Longterm costs by Anonymous Coward · · Score: 0

    Not documenting is a long-term cost. To any serious company with long-term plans; Such an employee is worthless. Too bad most companies aren't serious long-term planners.

  317. Re: Seems ridiculous to me as well. by Anonymous Coward · · Score: 0

    I don't think the described person would last a week in the environments I work in.

    Same thought here. I am not a quirky genius. I'm just quirky. So I would probably beat Josh to death in the parking lot after a few days.

  318. Re: brilliant and dangerous? by Anonymous Coward · · Score: 0

    I get arrogant all the time; I'm also the person people come to when they're having: a) legal problems b) medical problems c) life problems d) work-related problems e) loans f) cheering up... GROW UP, GET A THICKER SKIN and READ/LEARN OUTSIDE OF WORK.

    I think that you're pretty much a liar. You're painting yourself as not just a great developer but an all-round superman, yet all I hear is the dime-a-dozen coder giving one of his usual stream of consciousness rants. You are so laughably confident in yourself, convinced that you know what makes for good development practice and for general progress, and so sure about what's good and what's bad in others.

    And yet the hallmark of your message is, "my way or fuck off!" No, documentation for paulgrant is just a sign of bad coding; if an algorithm is complex, why "link to a paper"! Do you regularly precisely implement algorithms from academic papers, paulgrant? And yet your scenario is always so similar to the likely theoretical one in the paper that you never need to make any deviations, any optimisations, any improvements? I am led to think that you do quite a poor job, paulgrant! You have the rudimentary notions of how to make progress, but you don't really know how to advance. You got your basic degree, thought you were hot shit, and you've been basking in this stasis of self-confidence for years since - perhaps decades?

    Tell me, who are you? What great things have you achieved? Why should I listen to you over hundreds of brilliant mathematicians and scientists since the Renaissance who have kept in relative obscurity those who have posthumously shown to be great thinkers but contributed little toward scholarship because they were awful communicators? Even if you were Fermat - and there's no doubt that you are not - you would still never be Euler.

  319. Reading comprehension by Legion303 · · Score: 1

    The smirky "what documentation?" guy was the author's co-worker, not the deranged douche he was writing about.

    And related to the "aspergers" tag, if someone makes a "You don't have Aspergers, you're just a fuckhead" T-shirt I'd wear it.

  320. It is not "josh" who said there was no docs by Anonymous Coward · · Score: 0

    My guy went on to explain that although he tried to step through the code that was causing the errors, it was so convoluted he couldnâ(TM)t figure it out. I asked about documentation and he rolled his eyes and smirked, "What documentation?"

    It is the article writer's "guy" who smirked at the absence of documentation.

    But of course, this is slashdot, nobody RTFA.

  321. "says the resident English Ph D (minus Ph D)" by Anonymous Coward · · Score: 0

    Says the self-appointed "resident expert in writing" (in his own mind @ least), minus his Ph D in English of course, complete with his ADHD &/or dyslexia addled brain, lol...

    (&, it's always the same with you 'resident writing critics' (no degrees in English to certify you as an 'expert' in writing this language & yet your kind sees fit to act as the resident gurus)).

    Funny how you understood what I wrote though, and responded to each point I had made though (seeing as how you said my writing was unintelligible etc.)

    APK

    1. Re:"says the resident English Ph D (minus Ph D)" by Anonymous Coward · · Score: 0

      I don't need to be a certified expert in English to tell you that your original post was a nonsensical ramble. You lose.

    2. Re:"says the resident English Ph D (minus Ph D)" by Anonymous Coward · · Score: 0

      "I don't need to be a certified expert in English to tell you that your original post was a nonsensical ramble. You lose." - by Anonymous Coward on Tuesday March 17, @11:04AM (#27225429)

      First of all: Nobody will listen to you as some authority in the English language because you have nothing to back it up that you are in fact, an expert in it!

      (And it seems you responded to my points on that well enough via your double-talk (despite your stating my words are "unintelligble" & what-not)).

      So, answer the 1 question of mine that you keep avoiding -> Is this the "english writing section" of this website?

      ANSWER - No, it's not. You're OFF TOPIC, no questions asked (& apparently, you cannot read, because this is not "the english grammar" section now, is it?)

      APK

      P.S.=> You're just another clearly OFF TOPIC TROLL, who I get to amuse myself with, by watching you avoid simple questions like the bolded one above... apk

    3. Re:"says the resident English Ph D (minus Ph D)" by Anonymous Coward · · Score: 0

      Wow... you've discovered parentheticals, too.

      Why don't you just admit that your first post was a vague & uninteresting diatribe, and rewrite it so that people can understand what your point was?

      One last time: you lose. Stop trying to argue this point - it's not one you can win. Instead, try posting something that is meaningful, clear, and concise.

  322. lets get it straight by Anonymous Coward · · Score: 0

    Come on guys this is unacceptable, just think that 2 people with half this person's abilities can do a MUCH better work in less time. And then of course comes arrogance which is the top of the cake, I personally have a laugh discussing these people cause they are extremely "one-sided" persons and totally INFLEXIBLE (useless for serious development and teamwork). Instead if they would understand that their abilities in some areas are better and then try to compensate on others such as social, teamwork, documentation or whatever then they would shine much better.

  323. Re: brilliant and dangerous? by Aceticon · · Score: 1

    On any non-trivial piece of software most of the man-hour spend on it are spent during maintenance, not coding it.

    - Support
    - Bug-fixing
    - Enhancements
    - Third party component upgrades
    are the bits that eat up most time - the initial coding is trivial in comparison.

    Another thing to take in account is that true performance in IT is not measured by amounts of code: it's measured by function points implemented (for example, requirement use cases finished and delivered matching the wishes/needs of the client). In other words, results not the artifacts of the method used to achieve said results.

    Putting things together:
    - Somebody that can produce lots of code (but not necessarily results) in the coding stages of a project while sacrificing future performance on all other stages of a project is a liability, not an asset.

    Having been one such person in the early stages of my career (and having worked with other such people), I can confirm that with experience and hindsight I can now see how being a bright, fast, hard-core lone wolf coder was actually not that great in terms of long term results (not to mention being very amateurish and not at all professional).

    This kind of people are only "elevated" and "celebrated" in environments where Management is fully short-term oriented and incapable or unwilling to measure and evaluate longer term negative side-effects - usually because manager bonuses are calculated from short-term, visible and easy to measure actions which are deemed positive.
    (This kind of mis-aligned incentives is what caused all the problems with Credit Derivatives: traders were "elevated" and "celebrated" for using lent money to pile-up into CDs for short term results while accumulating huge long term risks).

  324. This is not English writing section here by Anonymous Coward · · Score: 0

    Why are you avoiding the 2nd question of "Is this the English writing critique section of slashdot?"

    (Would that be because there is no such section here, and that makes you off topic??)

    Between your clearly lacking a Ph D in English on YOUR part, and your outright avoidance of that question above as well??? You don't appear too credible now, do you troll????

    (Although you see fit to criticize others' writing, all the while, in appointing yourself the "resident grammar checker" here (who clearly is not an expert in that arena by any means or certifications we can see that he can produce that qualify you to be such a critic))?

    APK

    P.S.=> Making you look like a fool that contradicts himself and that also avoids questions here, it is just TOO EASY to do!

    Especially considering you answered points of mine each time well enough though you stated my writing was unintelligble etc.

    (Skimming on your part doesn't look good, and neither does outright avoiding BOTH of my questions to you)

    Your responses also clearly indicated that you do indeed understand what I wrote (but you avoid that 2nd question of mine like mad though, lol)... apk

  325. Re: brilliant and dangerous? by swilver · · Score: 1

    Way too verbose for me. If there's one thing I hate, it's variables being declared and assigned, and then only used once. Add a comment if you want to make it clearer, but please no "isThereASolarEclipseSomewhereInTheNextCentury" fields/methods.

  326. Re: Seems ridiculous to me as well. by julesh · · Score: 1

    I would say for every "freak" like this there must be a thousand+ that can code as well and are great to work with. [...] I have been doing SW dev for a living for about 15 years. Most of it large scale teams. I never saw anyone remotely close to this description and I have worked with some brilliant people.

    I imagine the environment you work in has a selection bias away from this type of person. Put yourself in "Josh"'s shoes: do you want to work in a large team? Or by yourself? I'd guess the ideal position for Josh is one where he's the only programmer in the entire company.

  327. Re: brilliant and dangerous? by paulgrant · · Score: 1

    >>I get arrogant all the time; I'm also the person people come to when they're having: a) legal problems b) medical problems c) life problems d) work-related problems e) loans f) cheering up... GROW UP, GET A THICKER SKIN and READ/LEARN OUTSIDE OF WORK.

    >I think that you're pretty much a liar. You're painting yourself as not just a great developer but an all-round superman, yet all I hear is the dime-a-dozen coder giving one of his usual stream of consciousness rants. You are so laughably confident in yourself, convinced that you know what makes for good development practice and for general progress, and so sure about what's good and what's bad in others. ... said the anonymous user... lol ;)

    >And yet the hallmark of your message is, "my way or fuck off!"

    and its my business - so it is *my way* or fuck off. I've never had a problem enforcing it, either at my business
    or any other business I've worked for.

    >No, documentation for paulgrant is just a sign of bad coding; if an algorithm is complex, why "link to a paper"!

    If an algorithm is tricky is what I said (as in subtle) - where you need to understand the *theory* of it; thats
    why you would link to a paper. Of course if all you're coding is bubblesort, certes I could understand why you
    consider that un-natural and useless.

    >Do you regularly precisely implement algorithms from academic papers, paulgrant?

    Unique algorithms are by definition unique, and usually presented in academic papers... If it wasn't, I wouldn't be using
    their paper, now would I? There are many ways to skin a cat but always one way to do it optimally. A paper is nothing more
    than a useful way of documenting a non-trivial algorithm. And if as a developer, you cant read an academic paper detailing
    an algorithm and code from it, who's at fault? Me for being able to do so, or you for *not* being able to do is ;)

    >Tell me, who are you? What great things have you achieved? Why should I listen to you over hundreds of brilliant
    mathematicians and scientists since the Renaissance who have kept in relative obscurity those who have posthumously
    shown to be great thinkers but contributed little toward scholarship because they were awful communicators? Even
    if you were Fermat - and there's no doubt that you are not - you would still never be Euler.

    Suren' I keep my thoughts to myself and certes it isn't for an inability to communicate ;) I say precisely what I mean,
    neither more, nor less. And I don't waste my time with arguing with fools. If you're interested in scholarship you are
    always welcome at my doorstep, be it creative, professional, technical or scientific... If your only critique is both
    anonymous and misguided, what more is there to say other than I suggest you never come work for me ;) Both your ignorance
    and your slovenly thinking will be exposed.

    Ciao ;)

  328. Re: brilliant and dangerous? by mdwh2 · · Score: 1

    Indeed, I'm not saying that the employee should be sacked - just that this doesn't mean he is blameless or not responsible for his own work. He clearly is. Both him, and management, are to blame here. This also doesn't excuse behaviour that affects other employees (e.g., harrassment), which should taken seriously no matter how good he is.

  329. Re: brilliant and dangerous? by Ruzty · · Score: 1

    But, please, do not expect miracles from people with untreatable medical conditions.

    It's taken over 20 years of conditioning myself to not interject in every conversation around me. And, it's taken nearly as long to learn when the other person in a conversation wishes to end it and move on instead of listening to me go on and on. Those are just 2 of the Aspy traits I've learned to overcome. There are dozens more that are works in progress. And, it is ALWAYS a relief when I can drop these artificial behavior patterns and be my unrestricted self.

    You can mask who you are for the benefit of those you work and live with. But, you just can't change how you think deep down in the way your brain is "wired". No amount of medication or behavior modification techniques can change how your mind works permanently. It's just a mask or filter over the top of the source modifying the results on output.

    --
    The Master (Angelo Rossitto) in Mad Max Beyond Thunderdome, "Not shit, energy!"
  330. Re: brilliant and dangerous? by mvdwege · · Score: 1

    There's a bug in your example. isChangingTimeZones is not being used, so why bother assigning to it? I presume this is a typo?

    Mart

    --
    "I know I will be modded down for this": where's the option '-1, Asking for it'?
  331. Re: brilliant and dangerous? by n7kv · · Score: 1

    Absolutely: but this is an age-old debate, and generally boils down to dollars. Management almost always agrees, in principle, with the adage "do it right, the first time, and you will be rewarded over the cycle with a better, more easily maintainable code base." And, in principle, the code _should_ be considered a source of documentation, _if it's well-written_. Unfortunately, quick dollars frequently trump "over the cycle".

  332. Re: brilliant and dangerous? by mvdwege · · Score: 1

    Even the most brilliant programmer is going to need to get their specs from somewhere. Finding out what a program is supposed to do can only be done by, you know, communicating with the people that asked for it to be written.

    Last I looked, communication is a people skill. Now, whether or not the given percentages make sense is debatable, but even if you don't take them as hard numbers, the real insight is there: without communication, there will be no useful software.

    Mart

    --
    "I know I will be modded down for this": where's the option '-1, Asking for it'?
  333. Technical Writers by bebemochi · · Score: 1

    All of these bosses who make developers write documentation need to learn of the existence of Technical Writers. I am one. It's our job to be the nerds who aren't quite geeks -- we're the ones who've always loved technology, yet also love to write. Oh, I know, developers around the world are reeling at the horror of that phrase: "love to write". But yes! It is true!! If only you realized that such people like us truly exist, and are truly motivated by the challenge of learning new technologies, applications, tools, etc. and so forth from their developers, and honestly enjoy translating that into user-friendly documents, and furthermore have proven methodologies for producing quality documentation that take into account any number of different variables (technical users? slightly technical users? highly technical users with a dash of n00bs? and more). if only it were realized! Developers the world over could sigh in relief and say, "why certainly, $boss! I can have that top-quality, user-friendly documentation written up for you without a problem -- I know a good technical writer."

  334. Answer this simple question, stop avoiding it by Anonymous Coward · · Score: 0

    QUESTION (for the 4th time or more now):Is this the "english grammar critique section" of this website's forums, or is it the DEVELOPERS section?

    ANSWER (the one you keep avoiding, or, that your dyslexic ADHD addled brain refuses to assimilate): It is the latter...

    Clearly making YOU just another wannabe Ph D in English (minus the Ph D in English, of course, lol) & another off-topic little troll I can amuse myself & others here reading with!

    (Especially since you state you could not understand my replies, & yet, you responded to them as if you DID understand them... in addition to your avoiding a SIMPLE question, bolded above).

    APK

    P.S.=> "TOO EASY"... apk

    1. Re:Answer this simple question, stop avoiding it by Anonymous Coward · · Score: 0

      You're sorely mistaken if you believe anybody wants to read anything you've written.

      Learn to write a coherent post that doesn't assault the reader with idiotic abbreviations, CAPITALIZATIONS, (parentheticals that lead nowhere), and actually, you know, makes a point. In summary: you lose.

  335. Here's how by geekoid · · Score: 1

    This reminds me of a saying that my former employer said:
    "I don't mind primadonas, but you better be a primadona with your work, and not just your attitude."

    If someone truly is that good, you don't give them daily work, you give them RnD and proof of concept work. You then let other programmers flush it out.

    If they are truly a twit, then replace them they will not save you the amount of money they will cost you. Eventually someone will sue, and you will loose.

    If you are not with a company doing cutting edge or RnD work, get rid of these people. If someone is doing 'routine' development work, they are probably not geniuses, or they have chosen a different outlet for the mind. In either case, a certain level of professionalism is expected.

    In my experience, the programmers management loves and considers 'genius' are only people who fit a certain perceived stereotype and has nothing to do with their work ability.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  336. Is this real? by seebs · · Score: 1

    A friend of mine pointed out that the example is very hard to accept. There are lots of things you can get away with. Sexual harassment, though, is one of the things where there's enough regulations that I have a really hard time believing this.

    I honestly don't believe that "Josh", as described, ever existed. I think he's a hyperbolic example from someone whose writing suggests that he resents the existence of people who are good at what they do without being interchangeable. Sadly, the world's smallest violinist was fired for wearing an offensive t-shirt, and cannot play.

    --
    My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
  337. Re:Answer this simple question, quit avoiding it by Anonymous Coward · · Score: 0

    QUESTION (Now for the 5th time or more):

    Is this the "english grammar critique section" of this website's forums, or is it the DEVELOPERS section?

    ANSWER (the one you keep avoiding, or, that your dyslexic ADHD addled brain refuses to assimilate):

    It is the latter, the DEVELOPERS section on this forums, w/ out question...

    (Despite your rather lame losing efforts? It is not the former)

    ----

    However - then again, you complain of "difficulty reading" (despite you clearly understanding my posts and replying to many of its points "oddly")... lol?

    If reading is too hard for you??

    Go back to Elementary School, & try again, or get "hooked on phonics" (because evidently you cannot read the heading title for this section - the DEVELOPERS section, not the "wannabe Ph D in English grammar checker section" of slashdot!)

    You are "off topic", troll... so much for your lack of a Ph D in English on your part (showing you are indeed a master of the english language), & your "critiques", eh? Considering they are coming from an off-topic no-mind troller like yourself?? Please... lol, keep amusing us, clown!

    APK

    P.S.=> Putting you in your place, with others reading, who see you avoiding answering questions I asked? Ah - "TOO EASY"... your difficulties with reading are only manifesting themselves with your skimming (or, outright avoiding my questions), and 'hard time reading' (hooked on phonics is for YOU), though you oddly respond to most of my points & questions just fine... well, except the question above, lol! apk

  338. Re:Answer this simple question, quit avoiding it by Anonymous Coward · · Score: 0

    All I'm doing is setting them up, and you're knocking them down. You keep proving that you can't write a coherent post, and for that, I thank you.

    But please, tell me I'm off topic, and not an English PhD, and ask your pointless questions again! I find it baffling how thick that skull of yours must be to miss the point this many times.

  339. Can't you read, & answer this simple question? by Anonymous Coward · · Score: 0

    Dearest Troll (lmao):

    QUESTION (Now for the 5th time or more):

    Is this the "english grammar critique section" of this website's forums, or is it the DEVELOPERS section?

    ANSWER (the one you keep avoiding, or, that your dyslexic ADHD addled brain refuses to assimilate):

    It is the latter, the DEVELOPERS section on this forums, w/ out question...

    ----

    However - then again, you complain of "difficulty reading" (despite you clearly understanding my posts and replying to many of its points "oddly")... lol?

    If reading is too hard for you??

    Go back to Elementary School, & try again, or get "hooked on phonics"...

    (I say this, simply because evidently you cannot read the heading title for this section - the DEVELOPERS section, & it's not the "wannabe Ph D in English grammar checker section" of slashdot!)

    You are "off topic", troll...

    So much for your lack of a Ph D in English on your part (showing you are indeed a master of the english language), & your "critiques", eh? Considering they are coming from an off-topic no-mind troller like yourself?? Nobody's thinking too much of what you have to say, this is certain.

    You can't even read & determine this is the DEVELOPERS' SECTION here on this forums, not the "English Grammar critique forums"...

    APK

    P.S.=> Please... lol, keep amusing us, clown! By the way, notice NOBODY is "obeying your orders"? Just because your mama responds to such manipulations, when you rattle your playpen railings (lol), doesn't mean the rest of us will apk

  340. Re:Can't you read, & answer this simple questi by Anonymous Coward · · Score: 0

    Too long, no point. Can't be bothered to read.

    You lose.

  341. Simple question, answer it by Anonymous Coward · · Score: 0

    What is this section of these forums called?

    You have 2 choices: The DEVELOPERS section (which it is), OR, the "english grammar critique section" (which you apparently THINK it is)??

    (Let's "test those newfound reading skills" of yours)

    APK

    P.S.=> If you answer DEVELOPERS SECTION (which it clearly is here), you are proving yourself either illiterate, or just another little troll who has nothing better to do with his time... apk

    1. Re:Simple question, answer it by Anonymous Coward · · Score: 0

      I'll answer your question with another question. What is the point of a forum such as slashdot? If you answered "discussion", you would be correct.

      If your idea of participating in a discussion involves long-winded soliloquies that nobody can understand or make sense of, then congratulations, you've succeeded.

      If your idea of participating in a discussion involves an exchange of coherent ideas, then sorry to tell you this:

      But you lose.

  342. I read his reply and understood it. Why can't you? by MEK_LoveBug · · Score: 1

    You truly must have ADD or dyslexia. I read his replies here in response to your off topic trolling, and the ac apk was completely understandable. Go away troll.

  343. Go away troll by MEK_LoveBug · · Score: 1

    You are off topic and a general nuisance that apparently is illiterate. You were asked what section of this forums this is and you refused to answer because you know you are nothing but a pest. I am going to say it once more to you, Go Away Troll. I am an actual registered user here and you are nothing but a troll loser who lost this exchange very badly. I found it hilarious watching you trying to avoid a simple answer to a simple question of what is the topic of this forums and what is its name. It's the developers section here and you are way off topic and lost badly for your stupidity.

  344. Go Away Anonymous Troll by MEK_LoveBug · · Score: 1

    And you keep on losing Mr. Off topic Troll. I am a registered user here and I am calling you what you are: An anonymous loser.

  345. You lost Troll by MEK_LoveBug · · Score: 1

    You are nothing but a trolllish loser who is off topic and is caught with his pants clearly down with no answers that are valid when you were asked here if this is the english grammar checking forums. It is not and you are off topic troll that is also clearly illiterate.

  346. Re:we should all wear what we want. by cdpage · · Score: 1

    perhaps i wrote that wrong.
    should have said, you could tell more about a person if they were permitted to wear what they wish. That not to say they shouldn't wear a suit wear one as often as you like...

    ok so i took 'formal' too far. but 'business attire' shouldn't be expected day to day.

    if you don't see people outside your own office... whats the point. I'd rather see the people i work with wear what makes them comfortable... house skibbies aside.

  347. Nice post apk by MEK_LoveBug · · Score: 1

    Nice posting. It is a topic that I whole heartedly agree with and especially in regards to managers often leading people who are supposedly their inferiors, yet who know more about the place of business and the section they work in than these so-called management superiors, which you are clearly alluding to here. It is too bad the famous anonymous troll showed up here but I put that idiot in his place already and I found it funny as it gets when you got him to go silent here in asking him what the topic of discussion here was and what this section of this forums is about, which is developers, not english grammar checkers (especially those minus a PHD). Good job ac apk.

    1. Re:Nice post apk by Anonymous Coward · · Score: 0

      Transparent self-congratulation is transparent.

      Did you notice that you're the only person telling yourself that you're smart & insightful?

      I don't know why you feel the need to go through and respond to every one of my posts while logged in as if being logged in would make your babble any more coherent. You're still an idiot who can't formulate an intelligent sentence on a discussion board.

      MEK == APK, obviously. But posting as both an AC & your own login doesn't change the fact that you lose.

    2. Re:Nice post apk by Anonymous Coward · · Score: 0

      Actually, I have an account registered here as "APK", but I never use it troll, and why are you evading the simple question I asked, as have others here now? I'll restate it for you once more:

      QUESTION: Is this the "english grammar critique section" here as this website, OR, is it the DEVELOPERS SECTION?

      Take your pick. There's only 1 correct answer, & it's not the quoted former (clue for you, I know you must be illiterate, but the answer is the title of this section of this forums, & begins with a "D", ok?)

      ROTFLMAO!

      APK

      P.S.=> Yes, I know Mr. Troll: You have difficulty reading, so answering questions is hard on you. You ask others to write well, but it seems others understand my words just fine, as you often strangely do as well (must be 'sporadic dyslexia' or something on your part) but again, for you & those like you? There is always "Hooked on Phonics", lmao... apk

    3. Re:Nice post apk by Anonymous Coward · · Score: 0

      MEK_LoveBug / APK, you are a 1-trick pony. Rather than write something meaningful to clarify your initial post (which was meaningless, and incoherent), you simply conduct ad hominem attacks on the person who pointed out all the fail in that initial post.

      Have fun congratulating yourself. It's not trolling if the point - that your posts are incomprehensibly meaningless - is valid.

  348. It's also much easier to debug by MarkusQ · · Score: 1
    It's also much easier to debug. For instance, I could see right off that the update is going to get called every time since you wrote:

    boolean isChangingTimeZones = hasChangedTimezones(thingy);
    if (hasChangedTimeZones) {
    updateAllCalendarsWithTimeZoneChange(thingy);
    }

    When you meant to write:

    boolean isChangingTimeZones = hasChangedTimezones(thingy);
    if (isChangingTimeZones) {
    updateAllCalendarsWithTimeZoneChange(thingy);
    }

    Of course, I would have dodged that particular bullet by writing:

    if (hasChangedTimezones(thingy)) {
    updateAllCalendarsWithTimeZoneChange(thingy);
    }

    But that's just me.

  349. No one here needs a psych degree to know that by MEK_LoveBug · · Score: 1

    You need to take your meds psycho. Illiterate troll face facts: You lost badly in failing to answer a simple question, and that's easily enough obtained, if you can read that is. Apparently you cannot, so I will tell you what this section is about. It is about developers, not english grammar checking you mentally damaged fool! Especially ones who don't even have a degree that certifies them as experts in the English language. Ones just like you troll. Go away trollish illiterate loser.

  350. Go away Troll: You are illiterate and you lost by MEK_LoveBug · · Score: 1

    What a complete dumb ass you are. I don't need a phd in anything to realize this much about a troll loser like you. The more I read from you, the more I realize you are a childish idiot and not just some illiterate moron. That one I might actually excuse but not a moron like yourself. Face it: You know you trapped yourself here in failing to answer what this section is titled and about and you have been outwitted as well as outsmarted. This section is about developers and not english grammar moron. Troll you lost badly but you are one amusing clown in doing so at least. I wish all the posters at this website were as stupid as yourself because it would be easy to defeat them. You are, so you know, the most stupid I have ever seen.

  351. Re:These guys are all right. by NoOneInParticular · · Score: 1
    For me the outlook of people living forever is so bleak that I'm happy that I'll be dead by then. There'll be no room for children anymore (how can you have children if you don't free up the resources by dying), just massive amounts of dinosaurs that hoard all the cash. Of course a revolution will follow soon, with the happiest outcome involuntary euthanasia at age 100.

    Yes, completely offtopic.

  352. You lost you illiterate troll by MEK_LoveBug · · Score: 1

    I read what the other ac who uses apk wrote and he asked you 2 simple questions which you failed to answer 1 of them because you know you are off topic when you were asked what the forums section topic is and it is developers not english grammar or your opinion of it because minus a phd in English on your part that is all you have an opinion and that of an illiterate trollish loser I felt. AC apk also found out he was correct on you not possessing a PHD in English and the rest of us found out that you evaded his other question as long as you could and you are off topic because this forums is not about English grammar or the opinion of an illiterate troll such as yourself. The ac poster apk beat you to a pulp loser. Accept it.

  353. ac apk you lost nothing. The other ac is a troll by MEK_LoveBug · · Score: 1

    ac apk, rest assured that I read this exchange end to end and the ac trolling you apk is nothing but an illiterate trolling loser who has nothing better to do with his time than to be a petty nuisance here and to be a (what is it you called him? Oh yes, a clown) clown for our amusement and ridicule. At this point he refuses to answer your questions because he knows that by not having a phd in english he is nobody worth listening to, and by his also admitting this is the developers section, he will have conceded that his off topic english grammar critiques are completely off topic trolling. This forums is full of pitiful schmucks like the ac causing us laughter here unfortunately and you have to learn to ignore them at times as well as pity them because this juvenile behaviour of his is all his type have in this life (and they wonder why their lives are worth shit).

  354. Re: brilliant and dangerous? by Anonymous Coward · · Score: 0

    Well, before I blamed MFC, I did plenty of googling.. I found a lot of people with tons of experience who were having the same problems and had to code their own workarounds. I agree that when the API gets blamed, it's usually because someone is trying to do something in the wrong way (to be fair, sometimes the API documentation is crap, but, still, heh).

    A lot of the problems I ran into eventually were fixed in later releases of MFC, but, since it was just a temporary position, and getting the program developed in order to get a more efficient system going was a very time-critical thing, I didn't have the opportunity to wait around for things to be fixed.

    MFC definitely wasn't brand-new at the time, but it was still maturing. There were some ways I needed to interface with other software that required me to use it, and I wish I could have used more mature APIs instead, but I did happen to learn a great deal about debugging on Windows, so I did get something substantial out of it :)

  355. Troll, for the 10th time? Go away you loser by Anonymous Coward · · Score: 0

    I'm telling you that you are nothing but a troll this time for the 10th time and won't you tell us the answer to a simple question troll? QUESTION: Is this the "english grammar critique" section of slashdot's forums, or is it the developer's section? Time to watch the troll evade what has blown him to bits and it made him defeat himself because of it which I find utterly hilarious. After all troll: You haven't spoken of anything on this topic, making you off topic, and this is not the "english grammar section" loser, making you doubly off topic and that to me means you have lost, loser. Nothing you're not used to now, is it? Go away troll. You're unwanted.

  356. Trolls EVER been studied in their natural habitat? by Anonymous Coward · · Score: 0

    See subject-line:

    I have been fortunately graced w/ my own "private troll" here @ /. , & this is not a curse: It's truly a blessing, because nobody is as dumb as your average troll, so he helps me look good!

    LOL, don't believe me? Well, ok:

    Here is a "for instance"/e.g.:

    Watch my pet troll evade answering this SIMPLE question everyone (lol, I can make him do tricks now too, see below):

    ----

    QUESTION TO MR. TROLL:

    The section of this forums we are in currently is the developer's section, correct?

    ----

    (A Yes or No answer is all that is required)

    Thank you for participating in my newly begun study of trolls, in their "natural habititat" (lol) also...

    APK

    P.S.=> ROTFLMAO! I can't wait to see his next "patented" (but, highly predicatable) evasion of answering that question with a Yes or No.

    You see, I have noticed that dyslexic ADHD addled trolls only have, oh, roughly a 10 below plantlife IQ, so perhaps his saying I cannot write is not his fault. His parents allowing him to live, yes, that is a mistake, but what can you do? LOL, but I do not believe one has truly ever been studied (rotflmao) in its natural habititat, and thus it is also an opportunity for research into the mind of the "primitive troll", lol... apk

  357. Re: brilliant and dangerous? by Anonymous Coward · · Score: 0

    Software development is 40% technical and 60% people.

    I disagree, I have measured programming extensively with digital percentometers and to be charitable, I will say that findings are significantly at odds with yours.

    Perhaps you could post some more information about the method you applied to obtain these results so that I can repeat your procedure with an eye to independently confirming your analysis.

    I look forward to your reply and urge you to do so at your earliest convenience to avoid any appearance of impropriety.

    Farquad U Dichwad III.

  358. Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0

    By the way, others can & do often agree with my points... (& they aren't me)

    See below for evidence to that in moderation points upward granted me on this site (in various postings noted below)

    ----

    http://it.slashdot.org/comments.pl?sid=170545&cid=14210206 (Score 5, Insightful)

    http://it.slashdot.org/comments.pl?sid=1139485&cid=26974507 (Score 5, Interesting)

    http://it.slashdot.org/comments.pl?sid=1139485&cid=26975021 (Score 5, Interesting)

    http://hardware.slashdot.org/comments.pl?sid=175774&cid=14610147 (Score 5, Insightful)

    http://science.slashdot.org/comments.pl?sid=982275&cid=25222775 (Score 4, Insightful)

    http://slashdot.org/comments.pl?sid=161862&cid=13531817 (Score 4, Informative)

    http://developers.slashdot.org/comments.pl?sid=167071&cid=13931198 (Score 4, Interesting)

    http://developers.slashdot.org/comments.pl?sid=155172&threshold=-1&commentsort=0&tid=109&tid=187&tid=1&tid=8&mode=thread&pid=13007684 (Score 4, Interesting)

    http://it.slashdot.org/comments.pl?sid=1021873&cid=25681261 (Score 3, Informative)

    http://slashdot.org/comments.pl?sid=175857&cid=14615222 (Score 3, Interesting)

    http://slashdot.org/comments.pl?sid=273931&threshold=1&commentsort=0&mode=thread&cid=20291847 (Score 3, Informative)

    http://it.slashdot.org/comments.pl?sid=166850&cid=13914137 (Score 3, Informative)

    http://it.slashdot.org/comments.pl?sid=1021733&cid=25675515 (Score 2, Insightful)

    http://news.slashdot.org/comments.pl?sid=1135717&cid=26941781 (Score 2, Interesting)

    http://it.slashdot.org/comments.pl?sid=158231&cid=13257227 (Score 2, Insightful)

    http://tech.slashdot.org/comments.pl?sid=1143349&cid=27012231 (Score 2, Interesting)

    http://tech.slashdot.org/comments.pl?sid=1143349&threshold=-1&commentsort=0&mode=thread&pid=27012231 (Score 2, Interesting)

    http://linux.slashdot.org/comments.pl?sid=1162247&cid=27211247 (Score 2, Insightful)

    http://tech.slashdot.org/comments.pl?sid=1010923&cid=25549351 (Score 2, Informative)

    http://tech.slashdot.org/comments.pl?sid=1001489&cid=25441395 (Score 2, Interesting)

    1. Re:Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0

      *yawn*

      You bore me, APK. All you've proven is that you can cut & paste links where other slash-tards with mod points think your rambles are somehow insightful.

      I regret to inform you that long-winded posts such as yours are generally no more insightful than they are meaningful. What we see instead is a case of people thinking, "He took all that time to write a lot. It MUST be pretty good, I'll mod it up."

      This is slashdot. Nobody even bothers to read the fucking article, do you think anybody can be bothered to read your stupid drivel?

    2. Re:Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0

      "You bore me, APK. All you've proven is that you can cut & paste links where other slash-tards with mod points think your rambles are somehow insightful." - by Anonymous Coward on Wednesday March 18, @04:35PM (#27247147)

      Which is proof of about, oh, 100x the amount of people that think I write well enough -> http://developers.slashdot.org/comments.pl?sid=1162403&cid=27240123

      And, evidence that folks DO differently than YOU do, by modding my posts here up +1 - +5 maximum!

      (You aren't everyone world-wide, you know!)

      ----

      "I regret to inform you that long-winded posts such as yours are generally no more insightful than they are meaningful" - by Anonymous Coward on Wednesday March 18, @04:35PM (#27247147)

      Again, 100++ others or so, here on THIS SITE ALONE (want more? I can produce posts like it by the hundreds if you wish from other sites) -> http://developers.slashdot.org/comments.pl?sid=1162403&cid=27240123

      Well, lol, they tend to disagree!

      (AND, you don't have a Ph D in English this is already certain though you see fit to tell others 'how to write', & without that? I have probably been speaking & writing this language longer than you have been alive mind you, you're no authority here to me on this account!

      (Plus, you aren't even a moderator/admin here, so why should I follow your orders? No, your mama may have come running when you rattle your playpen rails, but not I buddy... that type of 'manipulation' of barking orders @ me? Won't cut it...)

      Also, you apparently cannot read very well (did you ever think YOU may have a reading problem? Not kidding around this time either... because that is a lot of others basically saying I do write intelligibly).

      The worst part though? Your evading simple YES/NO answers to questions earlier... rotflmao!

      You also cannot read well because you have trouble determining whether this is the DEVELOPERS' SECTION here (which you have not contributed a valid response here to date on mind you, as far as this posting), and it is NOT "the english grammar critique" section , making you DOUBLY "off-topic" on both accounts.

      ----

      "This is slashdot. Nobody even bothers to read the fucking article, do you think anybody can be bothered to read your stupid drivel?" - by Anonymous Coward on Wednesday March 18, @04:35PM (#27247147)

      I generally do, & there you are again: Speaking like "you are the voice of slashdot"... newflash - you're not.

      (Gee, I wonder who LOST this one, eh?)

      APK

      P.S.=> Part #2 of my research into "the primitive mind of the troll" here @ /., everyone: LOL, this is the "care & feeding stage" - keep them posting, and keep catching them in their errors, & watch them "rage & foam" + avoid & evade answering simple questions, like what this forums section is about (which AC Mr. Troll here won't answer because he knows it will show he is clearly, OFF-TOPIC)... apk

    3. Re:Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0

      ADHD

      troll

      dyslexia

      You keep using those words. I do not think they mean what you think they mean.

      If I'm a troll, why do you keep shouting at me in your poorly written way? Why not just ignore me? It's because you know I'm right, and that your myopic, nonsensical posts have absolutely no intelligence behind them, and you're simply trying to silence me by shouting me down, hoping nobody else will notice what a fool you are.

      Sorry pal, but you lose. Lose, as in complete & abysmal failure.

    4. Re:Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0

      Everything else he evades in my last post aside, lol...

      ----

      QUESTION TO MR. TROLL: (Which he has evaded, roughly 10x by now, "oddly", lmao?)

      The section of this forums we are in currently is the developer's section, correct?

      ----

      (A Yes or No answer is all that is required)

      Thank you for participating in my newly begun study of trolls, in their "natural habititat" (lol) also...

      (& it seemed I provided 100++ proofs of others moderating up my posts here between +1 - +5 on various grounds, agreeing that my writing actually doesn't need the likes of the opinions of someone like YOU... lol!)

      APK

      P.S.=> Is my "ESP" operating on Turbo today, or am I wrong in assuming he will evade answering the question above, to no end...? apk

    5. Re:Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0

      You have provided lots of links to lots of drivel you've spouted.

      I have neatly countered that by pointing out that here on slashdot, the tards can't even be bothered to read the actual article they're discussing, or the summary of it they respond to, much less your dissertation-length crapfests.

      Therefore, it's plainly evident to anybody who's ever read this site that moderation points are awarded for being long-winded - it doesn't matter if you make an intelligent point. You could post a chapter from Charles Dickens in response to an article on Diebold voting machines and get "+5, Insightful" moderation from the slash-tards with mod points.

      Match point. I win, you lose.

    6. Re:Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0

      "You have provided lots of links to lots of drivel you've spouted." - by Anonymous Coward on Wednesday March 18, @07:31PM (#27249487)

      That over 100++ or so people moderated up here on grounds of my words being INTERESTING, or INFORMATIVE & more??

      See here -> http://developers.slashdot.org/comments.pl?sid=1162403&cid=27240123

      They have no problem with my writing apparently, but you, the "No Ph D expert in English" does... have you considered "Hooked on Phonics"?

      ----

      "I have neatly countered that by pointing out that here on slashdot, the tards can't even be bothered to read the actual article they're discussing, or the summary of it they respond to" - by Anonymous Coward on Wednesday March 18, @07:31PM (#27249487)

      Let's see:

      You've called people here "the slashtards" (sounds like a band name, lol), & now this tirade above!

      Do you realize that people like John Carmack post here in this section? Trust me, you may not like him personally, but he's no slouch in this art & science.

      (Ah yes, his reaction rant above? Just part of what I said would be his "foaming @ the mouth RaGiNg RePly", on the part of the 'average primitive troll'... lmao, in a p.s. in my last 2-3 posts I predicted this (trolls: like I said - easily predictable, generally dumb, & easy to put the "puppet strings on", hey, you can even get them to do tricks repeatedly, like evade answers to simple questions below)).

      You're "winning friends & influencing people" (not)... &, especially @ this website.

      AND

      Above all else, 11x now, lol... you avoid a simple yes/no question (again below) like mad ("for some reason" QUESTION TO MR. TROLL: (Which he has evaded, roughly 10x by now, "oddly", lmao?)

      The section of this forums we are in currently is the developer's section, correct?

      ----

      (A Yes or No answer is all that is required)

      Thank you for participating in my newly begun study of trolls, in their "natural habititat" (lol) also...

      (& it seemed I provided 100++ proofs of others moderating up my posts here between +1 - +5 on various grounds, agreeing that my writing actually doesn't need the likes of the opinions of someone like YOU... lol!)

      APK

      P.S.=> Is my "ESP" operating on Turbo today, or am I wrong in assuming he will evade answering the question above, to no end...?

      ("When in doubt, our study now concludes that trolls put aside all easily verifiable truths once confronted with them..." - in Morgan Freeman voice, the only guy I would let speak for me, with the class in his voice to carry it off, JUST right)... apk

    7. Re:Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0

      No, all you've shown is that people mod your rambling screeds up. I've pointed out that that's more likely a function of their length ("gee, the guy must have a great point in there, he had so much to say,") than a function of the quality of the writing.

      And please, do point out an example of John Carmack modding you up, congratulating you on your wonderful post, or in any other way agreeing with your ridiculous nonsense. I'll look forward with great anticipation to seeing Mr. Carmack singling you out as a special slashtard contributor.

      What's that, you say? You have no example? Because you were name dropping in an attempt to lend yourself credibility? Well in that case, Stephen Hawking, Burt Reynolds, and Heidi Klum all proof-read my posts and give me the okay to post! After I post, Heidi, Burt and I engage in a little devil's three-way, too. But we never cross swords, if you know what I mean.

      Wow, look - I can use the names of famous people, and make fantastical claims about them with no substantiation, too!

    8. Re:Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0

      Just answer this simple question, with a YES or NO:

      ----

      QUESTION FOR "MR. AC TROLL": (Which he has evaded, roughly 12x by now, "oddly", lmao?)

      The section of this forums we are in currently is the developer's section, correct?

      ----

      (REMEMBER: A Yes or No answer to THIS question, is all that is required)

      (AND, do answer the other questions below I have for you, as well, won't you? Quit evading them, it doesn't look good for you @ this point since you constantly avoid answering simple questions, doubtless due to your illiteracy which I have produced actual proof of prior to my p.s. below, in regards to Mr. John Carmack!)

      ----

      Plus, I provided over 80++ or so people in posts of mine who moderated my postings here up here on grounds of my words being INTERESTING, or INFORMATIVE:

      See here -> http://developers.slashdot.org/comments.pl?sid=1162403&cid=27240123 [slashdot.org]

      They have no problem with my writing apparently, but you, the "No Ph D expert in English" does... have you considered "Hooked on Phonics"?

      ----

      NOT ENOUGH? Ok!

      So, how about this guide I authored on how to secure Windows 2000/XP/Server 2003 & even VISTA, which has gone over 200,000++ views in 1 yrs.' time online across 20 forums and where it was made either a:

      1.) 5/5 star rated post (indicative of its being completely legible)
      2.) Most viewed (especially this one considering many of the forums it is on have been around for years to a decade or more)
      3.) A "sticky/pinned thread" or "ESSENTIAL GUIDE"
      4.) I was paid for writing said guide up also, here -> http://forums.pcpitstop.com/index.php?s=cba6343f4815761830a54e8eb26a10ee&act=SF&f=66&st=0&changefilters=1 for winning their monthly contest (unknowingly on my part)

      AND, where it literally has been shown that once folks apply it, they have stayed virus/spyware/trojan/rootkit/worm/malware-in-general free for more than 1++ yrs.' worth of time and operate faster than ever also, after applying its points, like THRONKA has here:

      ----

      USER TESTIMONIAL (PERTINENT QUOTE/EXCERPT + ORIGINATING URL):

      http://www.xtremepccentral.com/forums/showthread.php?s=cbf247cdf919c163abcf225737274e22&t=28430&page=3

      "Its 2009 - still trouble free!

      I was told last week by a co worker who does active directory administration, and he said I was doing overkill. I told him yes, but I just eliminated the half life in windows that you usually get. He said good point.

      So from 2008 till 2009. No speed decreases, its been to a lan party, moved around in a move, and it still NEVER has had the OS reinstalled besides the fact I imaged the drive over in 2008.

      Great stuff!

      My client STILL Hasn't called me back in regards to that one machine to get it locked down for the kid. I am glad it worked and I am sure her wallet is appreciated too now that it works. Speaking of which, I need to call her to see if I can get some leads.

      APK - I will say it again, the guide is FANTASTIC!"

      THRONKA @ xtremepccentral.com

      ----

      I guess all those websites (URL's available upon request, just ask, because unlike YOU, I do provide backing proof, inclusive of actual users' own results testimonials above mind you) & respected publications listed below in this field of endeavor, who chose my guide as good stuff, as all of the enumerated points above AND below both illustrate as decent/good don't count, eh, & they don't know how to write or read either, and that you are the only person that can judge it, right??

    9. Re:Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0
      Wow. The screeds just get longer and longer, don't they?! You forgot your important work in:
      • Goat Bangers' Monthly, August 2007, page 75
      • I Was An Incomprehensible Idiot, special issue, Spring 2009.
      • Morons United, April 2008, page 15
      • Special Needs Today, August / July 2006 double issue, page 49.

      I can't be bothered to read your list of "qualifications". They are completely irrelevant to this topic because magazines have editors to polish the turds you no doubt push out when asked to write a magazine article.

      What I do know is that you introduced John Carmack as a red herring here, in an attempt to "wow!" me into believing that smart people find your posts wonderful. But you know what? For every smart person here (like me and John Carmack), there's a million slashtards (like YOU, and MEK_LoveBug - oh, sorry, you're one and the same), and unfortunately, they get more mod points by sheer weight of numbers.

      So once again, YOU LOSE. I can dance all day, son. Give it up.

    10. Re:Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0

      AND, lol, it figures:

      Like usual, you avoided the questions asked of you, like usual (what is the forums section here called? DEVELOPERS SECTION, not the "english grammar critique" section)!

      Plus, you have NOTHING even remotely like the list I can produce of where others found my works in guides good (via their testimonials quoted, plus high ratings & massive numbers of views as well as being made sticky thread/pinned guides), & also that of respected written publications in this field for a decade & 1/2 now almost, over 10x, saying quite the reverse of what you have:

      That my writing is not only legible & understandable, but also good material.

      So, argue w/ this list:

      ----

      Windows NT Magazine (now Windows IT Pro) April 1997 "BACK OFFICE PERFORMANCE" issue, page 61

      http://journals2.iranscience.net:800/www.win2000mag.com/www.win2000mag.com/Windows/Article/ArticleID/37/37.html

      (&, for work done for EEC Systems/SuperSpeed.com on PAID CONTRACT (writing portions of their SuperCache program increasing its performance by up to 40% via my work) albeit, for their SuperDisk & HOW TO APPLY IT, took them to a finalist position @ MS Tech Ed, two years in a row).

      WINDOWS MAGAZINE, 1997, "Top Freeware & Shareware of the Year" issue page 210, #1/first entry in fact (my work is there)

      PC-WELT FEB 1998 - page 84, again, my work is featured there

      WINDOWS MAGAZINE, WINTER 1998 - page 92, insert section, MUST HAVE WARES, my work is again, there

      PC-WELT FEB 1999 - page 83, again, my work is featured there

      CHIP Magazine 7/99 - page 100, my work is there

      GERMAN PC BOOK, Data Becker publisher "PC Aufrusten und Repairen" 2000, where my work is contained in it

      HOT SHAREWARE Numero 46 issue, pg. 54 (PC ware mag from Spain), 2001 my work is there, first one featured, yet again!

      Also, a British PC Mag in 2002 for many utilities I wrote, but by that point, I had moved onto other areas in this field besides coding only...

      Lastly, being paid for an article that made me money over @ PCPitstop in 2008 for writing up a guide that has people showing NO VIRUSES/SPYWARES & other screwups, via following its point, such as THRONKA sees here -> http://www.xtremepccentral.com/forums/showthread.php?s=ee926d913b81bf6d63c3c7372fd2a24c&t=28430&page=3

      ----

      Have YOU done the same, or even CLOSE to that on all those grounds, especially in this field and topic of this section, programmatic development or networking?

      Somehow, lol? Well - I doubt it, & on all counts noted...

      Also?

      So, how about this guide I authored on how to secure Windows 2000/XP/Server 2003 & even VISTA, which has gone over 200,000++ views in 1 yrs.' time online across 20 forums and where it was made either a:

      1.) 5/5 star rated post (indicative of its being completely legible)
      2.) Most viewed (especially this one considering many of the forums it is on have been around for years to a decade or more)
      3.) A "sticky/pinned thread" or "ESSENTIAL GUIDE"
      4.) I was paid for writing said guide up also, here -> http://forums.pcpitstop.com/index.php?s=cba6343f4815761830a54e8eb26a10ee&act=SF&f=66&st=0&changefilters=1 for winning their monthly contest (unknowingly on my part)

      AND, where it literally has been shown that once folks apply it, they have stayed virus/spyware/trojan/rootkit/worm/malware-in-general free for more than 1++ yrs.' worth of time and operate fas

    11. Re:Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0

      Wow, you're really working yourself up into a lather.

      You lose.

    12. Re:Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0

      http://developers.slashdot.org/comments.pl?sid=1162403&cid=27256439

      Anyone can read there, and judge for themselves, as to "what is what" here, as to 100's of others having NO trouble with my writing... lol!

      E.G.-> Why are you avoiding the simple question I keep asking (maybe because it will show you are a troll, who is clearly "off topic")?

      Here it is, again:

      ----

      QUESTION FOR "MR. AC TROLL": (Which he has evaded, roughly 13x by now, "oddly", lmao?)

      The section of this forums we are in currently is the developer's section, correct?

      ----

      (REMEMBER: A Yes or No answer to THIS question, is all that is required)

      Proof of your illiteracy (or ADHD, skimming, or dyslexia etc. et al) further illustrated itself hereL

      YOU SAID ->

      ----

      "And please, do point out an example of John Carmack modding you up" - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

      ----

      So please - DO show us where I explicitly verbatim had said that John Carmack modded my posts upwards?

      (I only stated he posts here on occasion in response to your calling people here "slashtards" & what-not).

      The PROOF THAT YOU TRULY CANNOT READ IS RIGHT THERE ALONE... so, please - look into "Hooked on Phonics", ok?

      (And, you have the nerve to tell others like myself (who have been multiple published to good ratings & reviews no less many times in both written publication in this field, and online also being paid on both notes no less) how to write? Please... lol!)

      APK

    13. Re:Funny, others agree with me quite a lot by Anonymous Coward · · Score: 0

      Stop cutting and pasting the same post, you're boring me. If you can't stop being repetitive, you'll bore me into not bothering to respond.

      Surely you can come up with something comprehensible in the midst of all that lather?

    14. Re:Funny, others agree with me quite a lot by MEK_LoveBug · · Score: 1

      You evaded his simple question of what the forums name is here and we all know why you did that. You admitting this is the developers section here and not english grammar critiquing section of this forums would only further show you to be the troll you are. You did that evasion of that very simple yes or no question because this is the developers section and you came in here saying the other anonymous coward apk could not write. In response apk put up a lot of proof to the contrary from written publications he had software or articles in, as well as guides that I even tried (84/100 on cis tool so far) that worked well for people who tried them including myself, on top of his also having commercial software to his credit that went on to microsoft tech ed as a finalist 2 years in a row. You don't have anything even close to that level of expertise in this field and are an off topic troll as far as I am concerned after reading your profanity based replies. You lost but largely only because you beat yourself. Especially about lying that the anonymous coward apk supposedly said that John Carmack moderated his posts up here and when anonymous coward apk asked you for a quote of him saying that you blew that off also because you had no such proof and it appeared to me that you have dyslexia as he stated also. You can't read correctly so do not tell others how to write, especially since you are no expert by way of education such as an English PHD and also having appeared in written works in this science of computing even once versus apk having done so 100 times inclusive of his being moderated up here many times. You lost but beat yourself into a pulp in lying and trolling.

  359. Why won't you answer what the section name is here by Anonymous Coward · · Score: 0

    "No, all you've shown is that people mod your rambling screeds up." - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

    Which is a hell of a lot more than you have done, considering you failed to produce anything (like a Ph D in English, you know, the one you don't possess, lol) of proof @ all, just your own delusional rantings of "what good writing is"... whereas I produced around 100+ posts of mine that have been modded up between +1 - +5 maximum here -> http://developers.slashdot.org/comments.pl?sid=1162403&cid=27240123 So, "Argue with the numbers" as the saying goes...

    ----

    "I've pointed out that that's more likely a function of their length ("gee, the guy must have a great point in there, he had so much to say,") than a function of the quality of the writing." - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

    What makes you an authority to speak for WHY anyone modded anything up here? You already were shown to have no Ph D in English, and yet, you saw fit to call others here "slashtards" & worse.

    All you do is say a lot of crap and it has no backing whatsoever, other than the views of your brain damaged mind... how can I say that? Well, you really obviously cannot read, per your next statement below:

    "And please, do point out an example of John Carmack modding you up" - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

    Ok, show us this:

    Show me where I explicitly verbatim had said that John Carmack modded my posts upwards?

    (I only stated he posts here on occasion in response to your calling people here "slashtards" & what-not).

    PROOF THAT YOU TRULY CANNOT READ IS RIGHT THERE ALONE... so, please - look into "Hooked on Phonics", ok?

    APK

    P.S.=> Let's see the troll show me say where I stated John Carmack modded up my posts here, this ought to be good for a laugh, since he falsely accused me of that, AND LIKE USUAL? He avoids this simple question:

    ----

    QUESTION:

    What is the name of this forums section @ slashdot, Mr. Troll?

    ----

    Afraid to answer it, because it will show you have not contributed ONCE on topic here, because this is NOT the "english grammar section" of this website now, is it?? apk

  360. Re:Why won't you answer what the section name is h by Anonymous Coward · · Score: 0

    Introducing John Carmack's name into this discussion of YOUR illegible, incomprehensible posts is thus shown to be a diversionary tactic. Just because you post "in the same place" as someone famous doesn't make you smart, funny, insightful, or intelligent.

    Stop name-dropping in an attempt to make a point. It's grotesquely obvious that you're incapable of doing so, I know.

    Once again, I'm afraid to say: you lose.

  361. You really ARE illiterate, aren't you? by Anonymous Coward · · Score: 0

    "Introducing John Carmack's name into this discussion of YOUR illegible, incomprehensible posts is thus shown to be a diversionary tactic. Just because you post "in the same place" as someone famous doesn't make you smart, funny, insightful, or intelligent. - by Anonymous Coward on Thursday March 19, @10:27AM (#27255439)

    ORIGINALLY, YOU STATED THIS ->

    ----

    "And please, do point out an example of John Carmack modding you up" - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

    ----

    So please - DO show us where I explicitly verbatim had said that John Carmack modded my posts upwards?

    (I only stated he posts here on occasion in response to your calling people here "slashtards" & what-not).

    PROOF THAT YOU TRULY CANNOT READ IS RIGHT THERE ALONE... so, please - look into "Hooked on Phonics", ok?

    Hilarious: You REALLY ARE ILLITERATE!

    Just answer this simple question, with a YES or NO:

    ----

    QUESTION FOR "MR. AC TROLL": (Which he has evaded, roughly 12x by now, "oddly", lmao?)

    The section of this forums we are in currently is the developer's section, correct?

    ----

    (REMEMBER: A Yes or No answer to THIS question, is all that is required)

    (AND, do answer the other questions below I have for you, as well, won't you? Quit evading them, it doesn't look good for you @ this point since you constantly avoid answering simple questions, doubtless due to your illiteracy which I have produced actual proof of prior to my p.s. below, in regards to Mr. John Carmack!)

    ----

    Plus, I provided over 80++ or so people in posts of mine who moderated my postings here up here on grounds of my words being INTERESTING, or INFORMATIVE:

    See here -> http://developers.slashdot.org/comments.pl?sid=1162403&cid=27240123 [slashdot.org]

    They have no problem with my writing apparently, but you, the "No Ph D expert in English" does... have you considered "Hooked on Phonics"?

    ----

    NOT ENOUGH? Ok!

    So, how about this guide I authored on how to secure Windows 2000/XP/Server 2003 & even VISTA, which has gone over 200,000++ views in 1 yrs.' time online across 20 forums and where it was made either a:

    1.) 5/5 star rated post (indicative of its being completely legible)
    2.) Most viewed (especially this one considering many of the forums it is on have been around for years to a decade or more)
    3.) A "sticky/pinned thread" or "ESSENTIAL GUIDE"
    4.) I was paid for writing said guide up also, here -> http://forums.pcpitstop.com/index.php?s=cba6343f4815761830a54e8eb26a10ee&act=SF&f=66&st=0&changefilters=1 for winning their monthly contest (unknowingly on my part)

    AND, where it literally has been shown that once folks apply it, they have stayed virus/spyware/trojan/rootkit/worm/malware-in-general free for more than 1++ yrs.' worth of time and operate faster than ever also, after applying its points, like THRONKA has here:

    ----

    USER TESTIMONIAL (PERTINENT QUOTE/EXCERPT + ORIGINATING URL):

    http://www.xtremepccentral.com/forums/showthread.php?s=cbf247cdf919c163abcf225737274e22&t=28430&page=3

    "Its 2009 - still trouble free!

    I was told last week by a co worker who does active directory administration, and he said I was doing overkill. I told him yes, but I just eliminated the half life in windows that you usually get. He said good point.

    So from 2008 till 2009. No speed decreases, its been to a lan party, moved around in a move, and it still N

  362. Answer the QUESTION FOR "MR. AC TROLL" by Anonymous Coward · · Score: 0

    "Stop cutting and pasting the same post, you're boring me" - by Anonymous Coward on Thursday March 19, @12:41PM (#27257609)

    Why should I? You haven't answered my questions, so I repeat them for you (along w/ my evidences):

    No, I think you're just "confused as usual", per your blatantly illiterate screwup here:

    ORIGINALLY, YOU SAID ->

    ----

    "And please, do point out an example of John Carmack modding you up" - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

    ----

    So please - DO show us where I explicitly verbatim had said that John Carmack modded my posts upwards?

    (I only stated he posts here on occasion in response to your calling people here "slashtards" & what-not).

    PROOF THAT YOU TRULY CANNOT READ IS RIGHT THERE ALONE... so, please - look into "Hooked on Phonics", ok?

    ----

    Hilarious:

    You really CANNOT read, because I asked a simple proof to come from you here earlier, since you falsely accused me of saying John Carmack modded up my posts... can you show us where I said that?

    Also hilarious, is your avoiding answering THIS simple question, so, just answer this simple question, with a YES or NO:

    ----

    QUESTION FOR "MR. AC TROLL": (Which he has evaded, roughly 12x by now, "oddly", lmao?)

    The section of this forums we are in currently is the developer's section, correct?

    ----

    (REMEMBER: A Yes or No answer to THIS question, is all that is required)

    APK

    P.S.=> Above all else, as to my writing being decent & my providing proof thereof (vs. your erroneous b.s., lol)? Anyone can verify these proofs of my writing & appearing in respected publications in this field in good articles, softwares, & more as regards the field of computing & software development (especially since this is the DEVELOPERS SECTION HERE, not "english writing class", lol, which YOU seem to think it is, though you obviously cannot read) here below:

    ----

    Windows NT Magazine (now Windows IT Pro) April 1997 "BACK OFFICE PERFORMANCE" issue, page 61

    (&, for work done for EEC Systems/SuperSpeed.com on PAID CONTRACT (writing portions of their SuperCache program increasing its performance by up to 40% via my work) albeit, for their SuperDisk & HOW TO APPLY IT, took them to a finalist position @ MS Tech Ed, two years in a row).

    WINDOWS MAGAZINE, 1997, "Top Freeware & Shareware of the Year" issue page 210, #1/first entry in fact (my work is there)

    PC-WELT FEB 1998 - page 84, again, my work is featured there

    WINDOWS MAGAZINE, WINTER 1998 - page 92, insert section, MUST HAVE WARES, my work is again, there

    PC-WELT FEB 1999 - page 83, again, my work is featured there

    CHIP Magazine 7/99 - page 100, my work is there

    GERMAN PC BOOK, Data Becker publisher "PC Aufrusten und Repairen" 2000, where my work is contained in it

    HOT SHAREWARE Numero 46 issue, pg. 54 (PC ware mag from Spain), 2001 my work is there, first one featured, yet again!

    Also, a British PC Mag in 2002 for many utilities I wrote, but by that point, I had moved onto other areas in this field besides coding only...

    Lastly, being paid for an article that made me money over @ PCPitstop in 2008 for writing up a guide that has people showing NO VIRUSES/SPYWARES & other screwups, via following its point, such as THRONKA sees here -> http://www.xtremepccentral.com/forums/showthread.php?s=ee926d913b81bf6d63c3c7372fd2a24c&t=28430&page=3

    ----

    Have YOU done the same, or even CLOSE to that on all those grounds, especially in this field and topic of this section, programmatic development or networking?

    Somehow, lol? Well - I doubt it,

    1. Re:Answer the QUESTION FOR "MR. AC TROLL" by Anonymous Coward · · Score: 0

      Wall of text is incomprehensible. It burns and stings and hurts my eyes.

      Last post APK. Just to let you know that, in all your nonsense, you have STILL not made a single cogent or coherent point.

      Thus. You. Lose.

      Now I'm retiring from your nonsense because you're a clueless fuckwit who just cuts & pastes the same response to every challenge.

    2. Re:Answer the QUESTION FOR "MR. AC TROLL" by Anonymous Coward · · Score: 0

      "Now I'm retiring from your nonsense because you're a clueless fuckwit who just cuts & pastes the same response to every challenge" - by Anonymous Coward on Thursday March 19, @01:56PM (#27258833)

      Sure, but you only "retired yourself" with errors and shooting your mouth off making mistakes galore... rotflmao!

      LOL... and, don't you mean "the wall of good accomplishments I have", vs. your b.s., troll? After all, again, anyone is free to read those here (vs. you saying I can't write? Please... lol!):

      ----

      http://developers.slashdot.org/comments.pl?sid=1162403&cid=27258053

      ----

      AND, just reply to the 2-3 questions I have there then, I will quit cutting & pasting... ok??

      Now, I DO know that you are illiterate, based on this much here:

      YOU SAID ->

      ----

      "And please, do point out an example of John Carmack modding you up" - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

      ----

      So please - DO show us where I explicitly verbatim had said that John Carmack modded my posts upwards?

      (I only stated he posts here on occasion in response to your calling people here "slashtards" & what-not).

      PROOF THAT YOU TRULY CANNOT READ IS RIGHT THERE ALONE... so, please - look into "Hooked on Phonics", ok?

      ----

      Also, please answer this simple question:

      ----

      QUESTION FOR "MR. AC TROLL": (Which he has evaded, roughly 12x by now, "oddly", lmao?)

      The section of this forums we are in currently is the developer's section, correct?

      ----

      (REMEMBER: A Yes or No answer to THIS question, is all that is required)

      Which you will avoid like mad, lol, hilariously, in addition to your lack of proof of a Ph D in English (which might even make you somewhat of an expert on the English language, instead of an ADHD or Dyslexia addled brain troll on your part), as well as lacking anything of substance or worth you have done in this art & science... especially since this is the DEVELOPERS SECTION, & not "english grammar critique" section as your damaged brain seems to think it is, & clue - it's not.

      APK

      P.S.=> Trolls: They're always the same - and thus, I conclude my "study into the mind of the primitive troll" here, with his avoiding questions, especially ones where he screws up royally, lol, & where I can show tons of others that said I write just fine... too easy! apk

    3. Re:Answer the QUESTION FOR "MR. AC TROLL" by Anonymous Coward · · Score: 0

      *yawn*

      More fail from apk. What a surprise.

    4. Re:Answer the QUESTION FOR "MR. AC TROLL" by Anonymous Coward · · Score: 0

      http://developers.slashdot.org/comments.pl?sid=1162403&cid=27258975

      Anyone can read that & make their own judgements...

      APK

      P.S.=> Thought you were leaving also? Can't stick to your own word?? apk

    5. Re:Answer the QUESTION FOR "MR. AC TROLL" by Anonymous Coward · · Score: 0

      They will, as numerous others have on this site, declare you a monumental idiot who cannot construct a coherent sentence.

      We have already concluded you have multiple accounts from which you astroturf for your own posts, trying to make it look as if you have popular support, you pathetic, sad little person.

      It is thus entirely likely that the other slashtards who mod you up are, in fact, you modding your own posts up from one of your other accounts.

      On a related note, you realize that the point of a "PS" (or "Post script") is to include something in writing that you neglected to include when you were originally writing your missives from the land of fail, right? Given that this posting system makes it impossible to add something "after writing" (the *literal* translation for "post script"), you might as well just include it as part of your post, rather than calling it a "P.S." You're not writing longhand on parchment, tard, you're typing in a submit-once word processor.

      More evidence of just how thoroughly you lose. You are pathetic. When you finally decide to kill yourself, make sure to get both barrels in front of your face. Wouldn't want to do a half-ass job of that (like you do with posting here), right?

  363. Evidences to the contrary are here inside... apk by Anonymous Coward · · Score: 0

    To this:

    "incomprehensible ramble is incomprehensible." - by Anonymous Coward on Thursday March 19, @01:23PM

    All I can say & have said, is this:

    ----

    http://developers.slashdot.org/comments.pl?sid=1162403&cid=27258053

    ----

    (Anyone can read there, and judge for themselves on this account)

    Good luck arguing that I cannot write, especially vs. the 100:1 ratio of evidences to the contrary!

    ----

    (Yes - Especially vs. evidences I put out that when I have been featured @ least 10x in respected publications in this field in the areas of both software engineering, shareware/freeware, and networking topics I did well, and others could read my words, no problem).

    That is also where I showed that guides I wrote up last year, literally "skyrocketed" to good ratings & reviews, most viewed status, sticky/pinned thread & essential guide status, as well as GOOD results (most important of them all) by others once they read my guides for securing Windows...

    ----

    And, of course, this is this list of my posts here being "modded up" +1 - +5 maximum good rating, 80x or so, here on this website by others reading here, where I provided over 80++ or so people in posts of mine who moderated my postings here up here on grounds of my words being INTERESTING, or INFORMATIVE:

    See here -> http://developers.slashdot.org/comments.pl?sid=1162403&cid=27240123 [slashdot.org]

    They have no problem with my writing apparently, but you, the "No Ph D expert in English" does... have you considered "Hooked on Phonics"?

    ----

    The best part though? You really CANNOT read, because I asked a simple proof to come from you here earlier, since you falsely accused me of saying John Carmack modded up my posts... can you show us where I said that?

    YOU SAID ->

    ----

    "And please, do point out an example of John Carmack modding you up" - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

    ----

    So please - DO show us where I explicitly verbatim had said that John Carmack modded my posts upwards?

    (I only stated he posts here on occasion in response to your calling people here "slashtards" & what-not).

    PROOF THAT YOU TRULY CANNOT READ IS RIGHT THERE ALONE... so, please - look into "Hooked on Phonics", ok?

    ----

    Also, please answer this simple question:

    ----

    QUESTION FOR "MR. AC TROLL": (Which he has evaded, roughly 12x by now, "oddly", lmao?)

    The section of this forums we are in currently is the developer's section, correct?

    ----

    (REMEMBER: A Yes or No answer to THIS question, is all that is required)

    APK

    P.S.=> TOO easy, & the funniest parts in the URL above are where you avoid a simple question, to "Mr. AC TROLL" (you), & also where you blatantly showed you obviously are illiterate in stating I said Mr. John Carmack "modded up my posts", & I never said such a thing... I asked you for proof of that, & again, you avoid your mistakes like MAD, rotflmao... too easy! apk

  364. bingo: equally-valid, different someones. by Anonymous Coward · · Score: 0

    and as for slowing one's learning to make it "the same" as others,
    it doesn't amount to torture,
    it *snuffs out* one's learning.

    Something inside one dies.

    Learning's like a plant, or something:
    if it needs water, it needs it now, not next-year.

    If it needs nourishment, it needs it now, not after next season.

    Once a seedling/learning has died, it doesn't come back.

    Burnout is actually the other extreme of the same thing:
    death of a once-living capacity in one.

    I wish to god that the ones with
    exceptional physical ability were pushed just as much, in their way,
    as the ones with exceptional abstract ability.

    ( not in my lifetime:
    physical stuff matters;
    abstract is an insult, in our culture )

    As for kids respecting others:
    what school/authority respects kids' validity?

    I'm not talking "self-esteem",
    I'm talking letting 'em disagree with some adult,
    and them being told they have the RIGHT to disagree:
    THEY are valid.

    Their opinion may be overridden, on that issue,
    but THEY are valid.

    It's the only way we're *ever* going to end up with a population that
    won't "go along with" authority pressuring people into murder/torture:
    get people to grow up *capable of*,
    and *determined to* opposing evil/wrong/abusive authority, or
    the "Stanford Experiment",
    and "Extraordinary Rendition",
    and Nazism, and Robert Mugabe,
    and the Khmer Rouge,
    and Stalinism,
    are inevitable, eventually...

    1. Re:bingo: equally-valid, different someones. by stevied · · Score: 1

      My great-uncle was A. S. Neill - sadly he died before I was born.

      I think these ideas are finally catching on, but it remains to be seen whether they'll manage to set the world alight or just get blown out. There seems to be a developing kernel of kids in the 1/2 generation or so below me (Gen Y — they're not all narcissistic solipsists, thankfully!) who "get it" and haven't (yet) been broken by the realities of adult life. Maybe they'll make it through, either with the assistance of their elders or through their own strength ..

      Incidentally, learning may not survive starvation, but I think wisdom does. As it's pretty much all I've been left with, I'm hoping it will one day turn out to be useful .. :/

  365. At least I can read, unlike you by Anonymous Coward · · Score: 0

    http://developers.slashdot.org/comments.pl?sid=1162403&cid=27258053

    See subject-line & url above, 1st paragraph...

    APK

    1. Re:At least I can read, unlike you by Anonymous Coward · · Score: 0

      So you admit you lose? Agree.

      I'm dubious on your claim of being able to read, however. I think you read like you write - incapable of making sense of anything.

      You lost, APK. I wish I could say it was worth it, but you're just another slashtard who's wasted my time. Remember me when you're cutting to let the pain out, though, mmkay?

  366. John Carmack accusation, & answer a question by Anonymous Coward · · Score: 0

    ORIGINALLY, YOU SAID ->

    ----

    "And please, do point out an example of John Carmack modding you up" - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

    ----

    So please - DO show us where I explicitly verbatim had said that John Carmack modded my posts upwards?

    (I only stated he posts here on occasion in response to your calling people here "slashtards" & what-not).

    PROOF THAT YOU TRULY CANNOT READ IS RIGHT THERE ALONE... so, please - look into "Hooked on Phonics", ok?

    ----

    Hilarious:

    You really CANNOT read, because I asked a simple proof to come from you here earlier, since you falsely accused me of saying John Carmack modded up my posts... can you show us where I said that?

    APK

    P.S. => Answer this question also:

    ----

    QUESTION FOR "MR. AC TROLL": (Which he has evaded, roughly 12x by now, "oddly", lmao?)

    The section of this forums we are in currently is the developer's section, correct?

    ----

    (REMEMBER: A Yes or No answer to THIS question, is all that is required)... apk

  367. Re:John Carmack accusation, & answer a questio by Anonymous Coward · · Score: 0

    Dear tard.

    You brought up John Carmack to begin with, apparently the fact that he posts here was supposed to impress upon me that it was people like him who were modding your posts up. I challenged you to prove that the people modding your posts up were not, as is statisically near-certain, the retards who regularly mod up posts for simply being long.

    I don't give two shits about Mr. Carmack, personally. You brought his name into it in a pathetic attempt to impress people by name-dropping. The clear implication was that it was people like him who were modding you up and finding your posts insightful. This has been proven false by your own claim that Mr. Carmack has NEVER modded you up or congratulated you on your posts.

    So it seems we're in agreement. I win, you lose. Remember, cut with the veins, not across.

  368. Re:John Carmack accusation, & answer a questio by Anonymous Coward · · Score: 0

    "You brought up John Carmack to begin with" - by Anonymous Coward on Thursday March 19, @09:19PM (#27263937)

    Yes, I did, but I never ONCE said "he modded my posts up", as you stated, after you called the people in attendance @ this forums "slashtards" & other 'not-so-nice' things...

    That was after you said I could not write properly.

    So, to that:

    1.) I put up 80++ posts of mine from this site, where I was "modded up", & mostly from sections here that dealth w/ my area of expertise/field of endeavor, computing.

    (You blew that off, as usual (no big secret why, you messed up, and aren't man enough to face it apparently - I literally had 100's of people showing they like what I have written, vs. YOUR opinion only)).

    2.) I later also put up 10 occasions where I have actually had decent success in respected publications in this field, for various things, since you had said I could not write. I asked if you had done the same, & obviously you have not. Small wonder why: You waste time trolling.

    That's (all together) 100:1 odds in my favor, vs. your statement, & I do suspect you cannot read... based on all of this, I have to deduce that.

    APK

    P.S.=> ORIGINALLY, YOU SAID ->

    ----

    "And please, do point out an example of John Carmack modding you up" - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

    ----

    So please - DO show us where I explicitly verbatim had said that John Carmack modded my posts upwards?

    (I only stated he posts here on occasion in response to your calling people here "slashtards" & what-not).

    PROOF THAT YOU TRULY CANNOT READ IS RIGHT THERE ALONE... so, please - look into "Hooked on Phonics", ok?

    ----

    Hilarious:

    You really CANNOT read, because I asked a simple proof to come from you here earlier, since you falsely accused me of saying John Carmack modded up my posts... can you show us where I said that?

    APK

    Answer this question also:

    ----

    QUESTION FOR "MR. AC TROLL": (Which he has evaded, roughly 12x by now, "oddly", lmao?)

    The section of this forums we are in currently is the developer's section, correct?

    ----

    (REMEMBER: A Yes or No answer to THIS question, is all that is required)... apk

  369. Re:John Carmack accusation, & answer a questio by Anonymous Coward · · Score: 0

    *snore*

    I'm sorry, you were saying? Remember to seal any air vents out of the room when you're running that car. Carbon monoxide will diffuse out of the room if you're not careful to keep it in.

  370. What if everyone had to comment their work? by DryBaboon · · Score: 1

    If normal people had to document / comment their normal non programming work it would have interesting results in revealing how most people are either jerks, incompetent, working mostly on irrelevant shit, or, most likely, doing nothing at all.

  371. Re:John Carmack accusation, & answer a questio by Anonymous Coward · · Score: 0

    "I'm sorry, you were saying?" - by Anonymous Coward on Friday March 20, @12:15AM (#27264923)

    For the 15th time now, I was saying you obviously have shown you cannot read, because of this evidence thereof:

    EARLIER/ORIGINALLY, YOU SAID ->

    ----

    "And please, do point out an example of John Carmack modding you up" - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

    ----

    So please - show us where I explicitly verbatim had said that John Carmack modded my posts upwards?

    I never once did so, & you can't and you KNOW it.

    (However, your ADHD, skimming, or dyslexia (take your pick) addled brain apparently made you THINK I did!)

    (Truth of it is, I only stated he posts here on occasion in response to your calling people here "slashtards" & what-not & that Mr. John Carmack is not a "tard" by any means (and you have repeatedly called myself that, & others here as well - real classy of you (NOT))).

    Anyhow/anyways - THE PROOF THAT YOU TRULY CANNOT READ IS RIGHT THERE ALONE... so, please - look into "Hooked on Phonics", ok?

    There's no problem with my writing!

    1.) 80++ mods up here on my posts I produced clearly show that

    2.) As does my works appearing in respected publications in this field since 1997-2002

    3.) As does my security guide I wrote last year doing well being rated 5/5 stars, being made a "sticky/pinned thread" or "ESSENTIAL GUIDE" as well as being highly complimented by those that used it (to the tune of NO VIRUS/SPYWARE/TROJAN/ROOTKIT/WORM/MALWARE-IN-GENERAL showing up on their system for more than 1++ yrs. now & I provided evidences to ALL of the above).

    So, don't go around saying "you can't write", when I put up 100:1 ratio odds of others' opinions, vs. your own... & your opinion is based on yourself having problems with reading that is not a fault of anyones' but yourself

    ----

    Answer this question also, you keep evading it:

    ----

    QUESTION FOR "MR. AC TROLL": (Which he has evaded, roughly 12x by now, "oddly", lmao?)

    The section of this forums we are in currently is the developer's section, correct?

    ----

    (REMEMBER: A Yes or No answer to THIS question, is all that is required)...

    APK

    P.S.=> Evade answering that question, and go falsely accusing me of things I never did... you're only wasting your own time, & that is no one's fault but your own, and making yourself look bad in doing those things, as well as using profanity on your part also... apk

  372. Re:John Carmack accusation, & answer a questio by Anonymous Coward · · Score: 0

    EARLIER HERE, YOU SAID ->

    ----

    "And please, do point out an example of John Carmack modding you up" - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

    ----

    So please - show us where I explicitly verbatim had said that John Carmack modded my posts upwards?

    I never once did so, & you can't and you KNOW it.

    You misquote & twist others' words (which may not be your fault, I suspect you are dyslexic based on the above), but, it's not very effective now, is it, & especially w/ out a quote of my actually SAYING what you accused me of... not even a "nice try" on your part!

    Especially when I can, in turn, ask you to provide the proof, via quoting myself, of my saying John Carmack mods my posts up and you have to omit quoting me saying that, because I never ONCE did.

    BOTTOM-LINE on this account, is this:

    I only stated Mr. John Carmack posts here on occasion (in response to your calling people here "slashtards" & what-not & that Mr. John Carmack is not a "tard" by any means (and you have repeatedly called myself that, & others here as well - real classy of you (NOT))).

    Anyhow/anyways - THE PROOF THAT YOU TRULY CANNOT READ IS RIGHT THERE ALONE ABOVE and in your inability to quote me saying what you accused me of... so, please - look into "Hooked on Phonics", ok?

    (You need it: You cannot read, and your dim brain has already been shown to mess you up on that account, above!)

    After all, you are completely FREE to put up a quote of MY words, stating I literally said "John Carmack mods up my posts", ok?

    (Good luck on that, lol!)

    ----

    AND, there's no problem with my writing, & the evidences below outweigh your "No Ph D in English" opinion, literally 100++:1!

    (but, there obviously IS, with your inability to read correctly above & your own quoted words show it)

    Here are my evidences to that much:

    1.) 80++ mods up here on my posts I produced clearly show that much -> http://developers.slashdot.org/comments.pl?sid=1162403&cid=27240123

    2.) As do my works appearing in respected publications in this field since 1997-2002 , in the list below:

    ----

    Windows NT Magazine (now Windows IT Pro) April 1997 "BACK OFFICE PERFORMANCE" issue, page 61

    (&, for work done for EEC Systems/SuperSpeed.com on PAID CONTRACT (writing portions of their SuperCache program increasing its performance by up to 40% via my work) albeit, for their SuperDisk & HOW TO APPLY IT, took them to a finalist position @ MS Tech Ed, two years in a row).

    WINDOWS MAGAZINE, 1997, "Top Freeware & Shareware of the Year" issue page 210, #1/first entry in fact (my work is there)

    PC-WELT FEB 1998 - page 84, again, my work is featured there

    WINDOWS MAGAZINE, WINTER 1998 - page 92, insert section, MUST HAVE WARES, my work is again, there

    PC-WELT FEB 1999 - page 83, again, my work is featured there

    CHIP Magazine 7/99 - page 100, my work is there

    GERMAN PC BOOK, Data Becker publisher "PC Aufrusten und Repairen" 2000, where my work is contained in it

    HOT SHAREWARE Numero 46 issue, pg. 54 (PC ware mag from Spain), 2001 my work is there, first one featured, yet again!

    Also, a British PC Mag in 2002 for many utilities I wrote, but by that point, I had moved onto other areas in this field besides coding only...

    Lastly, being paid for an article that made me money over @ PCPitstop in 2008 for writing up a guide that has people showing NO VIRUSES/SPYWARES & other screwups, via following its point, such as THRONKA sees here -> http://www.xtremepccentral.com/forums/showthread.

  373. Re:John Carmack accusation, & answer a questio by Anonymous Coward · · Score: 0

    Oh no, I'm ruining the good public image of Anonymous Cowards everywhere by using profanity and not answering your inane questions. Whatever will you do about that? SOMETHING ought to be done!

    You are guilty, APK. Guilty of GRAVE sins against logic & intelligence. I have pointed them out, and you have been judged & found lacking.

    You cannot write well. It is as simple as that. People mod you up because you write HUGE WALLS OF TEXT that overwhelm lazy intellects who assume that, since you've taken the time to write a *lot* of text, there must be *something* worthwile in it. I've challenged that assumption, and shown that it is lazy, moronic slashtards who mod you up. There is nothing informative, insightful, interesting, or intelligent in what you write. Period, end of story.

    Once again. YOU LOSE.

  374. Evading question & not providing proofs via qu by Anonymous Coward · · Score: 0

    EARLIER HERE, YOU SAID ->

    ----

    "And please, do point out an example of John Carmack modding you up" - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

    ----

    So please - show us where I explicitly verbatim had said that John Carmack modded my posts upwards?

    I never once did so, & you can't and you KNOW it.

    You misquote & twist others' words (which may not be your fault, I suspect you are dyslexic based on the above), but, it's not very effective now, is it, & especially w/ out a quote of my actually SAYING what you accused me of... not even a "nice try" on your part!

    Especially when I can, in turn, ask you to provide the proof, via quoting myself, of my saying John Carmack mods my posts up and you have to omit quoting me saying that, because I never ONCE did.

    BOTTOM-LINE on this account, is this:

    I only stated Mr. John Carmack posts here on occasion (in response to your calling people here "slashtards" & what-not & that Mr. John Carmack is not a "tard" by any means (and you have repeatedly called myself that, & others here as well - real classy of you (NOT))).

    Anyhow/anyways - THE PROOF THAT YOU TRULY CANNOT READ IS RIGHT THERE ALONE ABOVE and in your inability to quote me saying what you accused me of... so, please - look into "Hooked on Phonics", ok?

    (You need it: You cannot read, and your dim brain has already been shown to mess you up on that account, above!)

    After all, you are completely FREE to put up a quote of MY words, stating I literally said "John Carmack mods up my posts", ok?

    (Good luck on that, lol!)

    ----

    "You cannot write well" - by Anonymous Coward on Friday March 20, @11:25AM (#27268837)

    Opinions vary, but, I have a lot of proofs to the contrary (unlike yourself):

    The evidences below outweigh your "No Ph D in English" opinion, literally 100++:1!

    (but, there obviously IS, with your inability to read correctly above & your own quoted words show it)

    Here are my evidences to that much:

    1.) 80++ mods up here on my posts I produced clearly show that much -> http://developers.slashdot.org/comments.pl?sid=1162403&cid=27240123

    2.) As do my works appearing in respected publications in this field since 1997-2002 , in the list below:

    ----

    Windows NT Magazine (now Windows IT Pro) April 1997 "BACK OFFICE PERFORMANCE" issue, page 61

    (&, for work done for EEC Systems/SuperSpeed.com on PAID CONTRACT (writing portions of their SuperCache program increasing its performance by up to 40% via my work) albeit, for their SuperDisk & HOW TO APPLY IT, took them to a finalist position @ MS Tech Ed, two years in a row).

    WINDOWS MAGAZINE, 1997, "Top Freeware & Shareware of the Year" issue page 210, #1/first entry in fact (my work is there)

    PC-WELT FEB 1998 - page 84, again, my work is featured there

    WINDOWS MAGAZINE, WINTER 1998 - page 92, insert section, MUST HAVE WARES, my work is again, there

    PC-WELT FEB 1999 - page 83, again, my work is featured there

    CHIP Magazine 7/99 - page 100, my work is there

    GERMAN PC BOOK, Data Becker publisher "PC Aufrusten und Repairen" 2000, where my work is contained in it

    HOT SHAREWARE Numero 46 issue, pg. 54 (PC ware mag from Spain), 2001 my work is there, first one featured, yet again!

    Also, a British PC Mag in 2002 for many utilities I wrote, but by that point, I had moved onto other areas in this field besides coding only...

    Lastly, being paid for an article that made me money over @ PCPitstop in 2008 for writing up a guide that has people showing NO VIRUSES/SPYWARES & other screwups, via following its point, such as THRONKA sees here ->

  375. Re:Evading question & not providing proofs via by Anonymous Coward · · Score: 0

    ELL-OH-ELL.

    That's a lot of bold, APK. But bold text will not save you from the inescapable conclusion that you are a moron, and incapable of intelligent thought or writing, you ridiculous twat.

    You have been judged, and found lacking.

    I have absolutely no need, desire, or cause to justify myself to you. I am more accomplished than you by far - I simply feel no need to trumpet mediocre accomplishments as if they're something special, as you do. I'm smarter, more articulate, and infinitely more coherent than you are. And rather than justify myself to the likes of you, I prefer actually accomplishing things.

    YOU, on the other hand, are unfit to even serve me a chesseburger. You lose.

  376. Re:Evading question & not providing proofs via by Anonymous Coward · · Score: 0

    "That's a lot of bold, APK. But bold text will not save you from the inescapable conclusion that you are a moron, and incapable of intelligent thought or writing, you ridiculous twat" - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Gosh, look @ that "raging foaming @ the mouth reply", complete with the profanities spewing no less, the sign of defeat in debate, everytime... lol!

    ----

    "You have been judged, and found lacking." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Yes, judged by a troll, that has no accomplishments he can put up to show he is indeed, a peer to myself in this area... & by one who has no Ph D in English either!

    (So much for your "judgement" because you can't read, this much is apparent, & you evade questions that will show you are indeed way, Way, WAY off-topic here as well!)

    ----

    "I have absolutely no need, desire, or cause to justify myself to you. I am more accomplished than you by far - I simply feel no need to trumpet mediocre accomplishments as if they're something special, as you do." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Well, where are they then?

    (You don't have any, just your "self-proclaimed greatness", lol, & delusions of your own grandeur)

    ----

    "I'm smarter, more articulate, and infinitely more coherent than you are." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    You certainly aren't showing anything of that nature, & certainly NOT when others (other than yourself, lol) thought so... but, I surely did: See below, again, for your reference...

    ----

    "And rather than justify myself to the likes of you, I prefer actually accomplishing things." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Like what? Trolling, as you have here, off-topic the whole time?

    (LMAO - the ONLY thing you've 'accomplished' here, is making yourself look like the off-topic, foaming @ the mouth profanity spewing troll you are, who is a "legend in his own mind"... lol!)

    ----

    EARLIER HERE, YOU SAID ->

    ----

    "And please, do point out an example of John Carmack modding you up" - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

    ----

    So please - show us where I explicitly verbatim had said that John Carmack modded my posts upwards?

    I never once did so, & you can't and you KNOW it.

    You misquote & twist others' words (which may not be your fault, I suspect you are dyslexic based on the above), but, it's not very effective now, is it, & especially w/ out a quote of my actually SAYING what you accused me of... not even a "nice try" on your part!

    Especially when I can, in turn, ask you to provide the proof, via quoting myself, of my saying John Carmack mods my posts up and you have to omit quoting me saying that, because I never ONCE did.

    BOTTOM-LINE on this account, is this:

    I only stated Mr. John Carmack posts here on occasion (in response to your calling people here "slashtards" & what-not & that Mr. John Carmack is not a "tard" by any means (and you have repeatedly called myself that, & others here as well - real classy of you (NOT))).

    Anyhow/anyways - THE PROOF THAT YOU TRULY CANNOT READ IS RIGHT THERE ALONE ABOVE and in your inability to quote me saying what you accused me of... so, please - look into "Hooked on Phonics", ok?

    (You need it: You cannot read, and your dim brain has already been shown to mess you up on that account, above!)

    After all, you are completely FREE to put up a quote of MY words, stating I literally said "John Carmack mods up my posts", ok?

    (Good luck on that, lol!)

    ----

    "You cannot write well" - by Anonymous

  377. Re:Evading question & not providing proofs via by Anonymous Coward · · Score: 0
    I notice you do a lot of laughing in your posts. You know what the Tao Te Ching says about that? Here's what:

    When a foolish man hears of the Tao, he laughs out loud.

    I suspect this is the same phenomenon. When confronted with the truth of what an incomprehensible moron you are, you (the foolish man) laugh, and then seek to drown out any opinion other than your own, through yelling, bold text, (parentheticals!), and LOTS OF CAPITAL LETTERS.

    You're a moron. Kill yourself and remove bad genes from the gene pool, please.

  378. Why won't you answer a simple question? by Anonymous Coward · · Score: 0

    EARLIER HERE, YOU SAID ->

    ----

    "And please, do point out an example of John Carmack modding you up" - by Anonymous Coward on Thursday March 19, @12:19AM (#27251625)

    ----

    So please - show us where I explicitly verbatim had said that John Carmack modded my posts upwards?

    I never once did so, & you can't and you KNOW it.

    Especially when I can, in turn, ask you to provide the proof, via quoting myself, of my saying John Carmack mods my posts up and you have to omit quoting me saying that, because I never ONCE did.

    BOTTOM-LINE on this account, is this:

    I only stated Mr. John Carmack posts here on occasion (in response to your calling people here "slashtards" & what-not & that Mr. John Carmack is not a "tard" by any means (and you have repeatedly called myself that, & others here as well - real classy of you (NOT))).

    Anyhow/anyways - THE PROOF THAT YOU TRULY CANNOT READ IS RIGHT THERE ALONE ABOVE and in your inability to quote me saying what you accused me of... so, please - look into "Hooked on Phonics", ok?

    (You need it: You cannot read, and your dim brain has already been shown to mess you up on that account, above!)

    After all, you are completely FREE to put up a quote of MY words, stating I literally said "John Carmack mods up my posts", ok?

    (Good luck on that, lol!)

    ----

    "You cannot write well" - by Anonymous Coward on Friday March 20, @11:25AM (#27268837)

    Opinions vary, but, I have a lot of proofs to the contrary (unlike yourself):

    The evidences below outweigh your "No Ph D in English" opinion, literally 100++:1!

    (but, there obviously IS, with your inability to read correctly above & your own quoted words show it)

    Here are my evidences to that much:

    1.) 80++ mods up here on my posts I produced clearly show that much -> http://developers.slashdot.org/comments.pl?sid=1162403&cid=27240123

    2.) As do my works appearing in respected publications in this field since 1997-2002 , in the list below:

    ----

    Windows NT Magazine (now Windows IT Pro) April 1997 "BACK OFFICE PERFORMANCE" issue, page 61

    (&, for work done for EEC Systems/SuperSpeed.com on PAID CONTRACT (writing portions of their SuperCache program increasing its performance by up to 40% via my work) albeit, for their SuperDisk & HOW TO APPLY IT, took them to a finalist position @ MS Tech Ed, two years in a row).

    WINDOWS MAGAZINE, 1997, "Top Freeware & Shareware of the Year" issue page 210, #1/first entry in fact (my work is there)

    PC-WELT FEB 1998 - page 84, again, my work is featured there

    WINDOWS MAGAZINE, WINTER 1998 - page 92, insert section, MUST HAVE WARES, my work is again, there

    PC-WELT FEB 1999 - page 83, again, my work is featured there

    CHIP Magazine 7/99 - page 100, my work is there

    GERMAN PC BOOK, Data Becker publisher "PC Aufrusten und Repairen" 2000, where my work is contained in it

    HOT SHAREWARE Numero 46 issue, pg. 54 (PC ware mag from Spain), 2001 my work is there, first one featured, yet again!

    Also, a British PC Mag in 2002 for many utilities I wrote, but by that point, I had moved onto other areas in this field besides coding only...

    Lastly, being paid for an article that made me money over @ PCPitstop in 2008 for writing up a guide that has people showing NO VIRUSES/SPYWARES & other screwups, via following its point, such as THRONKA sees here -> http://www.xtremepccentral.com/forums/showthread.php?s=ee926d913b81bf6d63c3c7372fd2a24c&t=28430&page=3 [xtremepccentral.com]

    ----

    3.) As doe

    1. Re:Why won't you answer a simple question? by Anonymous Coward · · Score: 0

      When a foolish man hears of the Tao, he laughs out loud.

      If you have nothing new to say, just shut up, you monumental, moronic, indescribably stupid waste of flesh.

  379. Re: brilliant and dangerous? by DarkVader · · Score: 1

    Well, that certainly sends an interesting message to the highly knowledgeable tech worker:

    "Document nothing. If you do, they're just going to fire you and be able to get along just fine without you. Instead, if you document nothing and obfuscate everything, they'll be fucked and likely won't do that sort of thing to anybody else."

  380. Evading questions again: Consider decaf, also, lol by Anonymous Coward · · Score: 0

    "If you have nothing new to say, just shut up, you monumental, moronic, indescribably stupid waste of flesh." - by Anonymous Coward on Friday March 20, @05:59PM (#27274567)

    First of all, why should I "obey you"? You evade my questions, thus, since you have proven the dyslexic who is unable to read correctly (lol, who no less tells others how to write, minus a Ph D in English no less, lol, as well)?? No, don't think so...

    After all - You aren't my superior here, especially here in this forums section (based on your lack of any type of accomplishments in it since you failed to produce them when asked), & you aren't a mod: No, I think I'll do as I please - how's that suit you?

    Nothing you could do about it, anyhow, except be the "frothing @ the mouth troll" I predicted you'd turn up as... lmao!

    (Trolls: Always the same predictable fools... yet more evidence of the same is next readers, lol, for YOUR added entertainment (told you all I could make him "do tricks", easily, lol...)

    ----

    "That's a lot of bold, APK. But bold text will not save you from the inescapable conclusion that you are a moron, and incapable of intelligent thought or writing, you ridiculous twat" - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Gosh, again readers:

    Look @ that "raging foaming @ the mouth reply"... lol, "we spare no expense for your entertainment, in our obtaining the services of ONLY the MOST 'primitive of trolls'", rotflmao...!

    (Complete with the profanities spewing no less, the sign of defeat in debate, everytime... lol!)

    ----

    "You have been judged, and found lacking." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Yes, judged by a troll, sure - I can agree with THAT much, lol!

    (AND, you're a troll that has no accomplishments he can put up to show he is indeed, a peer to myself in this area... & by one who has no Ph D in English either, yet tells us all "you can't write well"!)

    Man, lmao:

    So much for your "judgement" because you can't read, this much is apparent, & you evade questions that will show you are indeed way, Way, WAY off-topic here as well!

    ----

    "I have absolutely no need, desire, or cause to justify myself to you. I am more accomplished than you by far - I simply feel no need to trumpet mediocre accomplishments as if they're something special, as you do." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Ok then:

    Well, where are they then?

    (You don't have any, admit it! All you have is just your "self-proclaimed greatness", lol, & delusions of your own grandeur)

    ----

    "I'm smarter, more articulate, and infinitely more coherent than you are." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Oh, yea, sure - based on your "fantasy list of accomplishments" you've showed us (not, lol)? Yea, "we believe you"... ( sarcasm on that quoted last part )

    You certainly aren't showing anything of that nature, & certainly NOT when others (other than yourself, lol) thought so... but, I surely did: See below, again, for your reference...

    ----

    "And rather than justify myself to the likes of you, I prefer actually accomplishing things." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Like what? Trolling, as you have here, off-topic the whole time??

    (LMAO - the ONLY thing you've 'accomplished' here, is making yourself look like the off-topic, foaming @ the mouth profanity spewing troll you are, who is a "legend in his own mind", @ this point, after that 'tirade' above... lol!)

    ----

    ALSO? Well, EARLIER HERE, YOU SAID ->

    ----

    "And please, do point out an example of John Carmack

  381. Consider decaf, & quit "frothing @ the mouth" by Anonymous Coward · · Score: 0

    "If you have nothing new to say, just shut up, you monumental, moronic, indescribably stupid waste of flesh." - by Anonymous Coward on Friday March 20, @05:59PM (#27274567)

    First of all?

    Why should I "obey you"??

    You evade my questions, AND you have proven the dyslexic dullard who is unable to read correctly

    (lol, AND? A dyslexic dullard who no less tells others how to write, minus a Ph D in English on YOUR PART, no less, & you haven't even been in publication as I have been, MANY times now (so much for you saying I cannot write))??

    No, don't think so...

    After all - You aren't my superior here, especially here in this forums section (based on your lack of any type of accomplishments in it since you failed to produce them when asked), & you aren't a mod: No, I think I'll do as I please - how's that suit you?

    Nothing you could do about it, anyhow, except be the "frothing @ the mouth troll" I predicted you'd turn up as... lmao!

    (Trolls: Always the same predictable fools... yet more evidence of the same is next readers, lol, for YOUR added entertainment (told you all I could make him "do tricks", easily, lol...)

    ----

    "That's a lot of bold, APK. But bold text will not save you from the inescapable conclusion that you are a moron, and incapable of intelligent thought or writing, you ridiculous twat" - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Gosh, again readers:

    Look @ that "raging foaming @ the mouth reply"... lol, "we spare no expense for your entertainment, in our obtaining the services of ONLY the MOST 'primitive of trolls'", rotflmao...!

    (Complete with the profanities spewing no less, the sign of defeat in debate, everytime... lol!)

    ----

    "You have been judged, and found lacking." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Yes, judged by a troll, sure - I can agree with THAT much, lol!

    (AND, you're a troll that has no accomplishments he can put up to show he is indeed, a peer to myself in this area... & by one who has no Ph D in English either, yet tells us all "you can't write well"!)

    Man, lmao:

    So much for your "judgement" because you can't read, this much is apparent, & you evade questions that will show you are indeed way, Way, WAY off-topic here as well!

    ----

    "I have absolutely no need, desire, or cause to justify myself to you. I am more accomplished than you by far - I simply feel no need to trumpet mediocre accomplishments as if they're something special, as you do." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Ok then:

    Well, where are they then?

    (You don't have any, admit it! All you have is just your "self-proclaimed greatness", lol, & delusions of your own grandeur)

    ----

    "I'm smarter, more articulate, and infinitely more coherent than you are." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Oh, yea, sure - based on your "fantasy list of accomplishments" you've showed us (not, lol)? Yea, "we believe you"... ( sarcasm on that quoted last part )

    You certainly aren't showing anything of that nature, & certainly NOT when others (other than yourself, lol) thought so... but, I surely did: See below, again, for your reference...

    ----

    "And rather than justify myself to the likes of you, I prefer actually accomplishing things." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Like what? Trolling, as you have here, off-topic the whole time??

    (LMAO - the ONLY thing you've 'accomplished' here, is making yourself look like the off-topic, foaming @ the mouth profanity spewing troll you are, who is a "legend in his own mind", @ this point, after that 'tirade'

  382. Re:Consider decaf, & quit "frothing @ the mout by Anonymous Coward · · Score: 0
    • You should obey me because I'm your superior. I've already demonstrated this fully and repeatedly in my messages.
    • for somebody who's calling me a frothing-at-the-mouth troll, you seem to be doing all the ranting and raving, twat.
    • I don't "evade" your questions, I disregard them as irrelevant to any coherent point. Why? Because they are!
    • You are still a loser.

    I should impersonate you on the internet somewhere. Maybe go sign up on the CNET site and start ranting and raving like you do, and refer them to all your inane and idiotic posts here. That might be fun. Yes, I think I'll do that!

    It's not enough just for me to know about you. EVERYBODY should see what a failure you are.

  383. Re:Consider decaf, & quit "frothing @ the mout by Anonymous Coward · · Score: 0

    "You should obey me because I'm your superior. I've already demonstrated this fully and repeatedly in my messages." - by Anonymous Coward on Saturday March 21, @01:27AM (#27277163)

    You know, for YOU being my superior (LMAO, not)?

    Well - Why don't you produce a list of superior accomplishments, in this field (since its the developers section of this forums after all) on your part then, vs. my own SMALL & only PARTIAL one I put up above (complete with verifiable backing information, inclusive of quotes of results of my works helping others have NO VIRUS/WORM/TROJAN/SPYARE infestations whatsoever after using them even)...??

    AND, especially MORE of them than I have???

    You can't obviously - Heck, you can't produce 1 even... lmao!

    ----

    "for somebody who's calling me a frothing-at-the-mouth troll," - by Anonymous Coward on Saturday March 21, @01:27AM (#27277163)

    Simple question that: Is this the developers section, or the "english grammar critique section"?

    (You keep avoiding that one, why? Perhaps because it WILL show that you are, indeed, an OFF-TOPIC TROLL??)

    ----

    "you seem to be doing all the ranting and raving, twat." - by Anonymous Coward on Saturday March 21, @01:27AM (#27277163)

    See? More proof of "advanced troll-ism", readers... lol: Note the profanity use? The 1st sign of defeat in debate, is when intelligence 'breaks down' & the raving foaming @ the mouth profanities begin... rotflmao!

    ----

    "I should impersonate you on the internet somewhere. Maybe go sign up on the CNET site and start ranting and raving like you do, and refer them to all your inane and idiotic posts here. That might be fun. Yes, I think I'll do that!

    It's not enough just for me to know about you. EVERYBODY should see what a failure you are." - by Anonymous Coward on Saturday March 21, @01:27AM (#27277163)

    I wouldn't recommend that, but, you're only showing you've probably done this before (the sign of the ULTIMATE loser, &, YOU CALLED ME ONE? Beg to differ, you're only showing you can 'throw a tantrum' & make threats to criminally impersonate me??)

    You have problems... this has been done by some goof over @ 4chan this week already, & you're probably the one who did so as a speculation on my part... I say that, because he trolled me before this week, as you have, and lost then too as you have now thru your own stupidities!

    APK

    P.S.=> The rest is here, utterly hilarious -> http://developers.slashdot.org/comments.pl?sid=1162403&cid=27277101 ... thanks for making me look good, I told everyone you would (because you are the typical unintelligent troll it is easy to get the better of, to find his psychological weaknesses & mistakes + use of them to 'push your buttons' until you crack & fold under the pressure... & the "patented troll foaming @ the mouth, profanities, & threats came along, as I said they would - predictably doltish, but expected (not even original, & certainly NO challenge))... thanks for the easy win, by lol, actually HELPING me prove my point about you, @ every turn! apk

  384. Re:Consider decaf, & quit "frothing @ the mout by Anonymous Coward · · Score: 0

    I have no interest in providing you with a list of my publications, because it would overwhelm you, and probably send you into a suicidal downturn when you realized exactly how hollow your accomplishments are in the face of my magnificence.

    I've changed my mind - I'm not going to impersonate you. I would make an unconvincing moron, and people would see through my ruse. They would never believe that anything I wrote could have REALLY come from you. Instead, I think I'm just going to link these articles everywhere I can find to link them. Let's let the internet see exactly what an idiot and a moron you are! That'll be much more fun, and then you won't have to get your panties in a bunch about someone "impersonating" you. ("Quick, someone call the FBI, Anonymous Coward APK has been IMPERSONATED on an Internet Message Board! Better call in the National Guard too!")

    No, I'm not the person who trolled you on some other site. No, I have no impersonated you on 4chan. Are you adding paranoid & delusional to your list of greatest hits? I think you might be!

    As far as winning is concerned, that's what I do, APK. You, on the other hand, lose. Repeatedly. Dismally.

  385. You are a troll and a liar by MEK_LoveBug · · Score: 1

    I am not anonymous coward apk so why are you saying that I am? Haven't you had enough of being caught in stating falsehoods here already in saying that the anonymous coward apk said John Carmack of Idsoftware modded up his posts and yet there was nothing like that to be found here coming from the anonymous coward apk? You are a troll and a liar too.

  386. As far as winning you are the biggest loser troll by MEK_LoveBug · · Score: 1

    You don't have anything like the anonymous coward apk had in being featured in written respected publications in the science of computing which was an impressive list, inclusive of taking a company to a finalist position at Microsoft Tech Ed, and 2 years in a row. Your self-proclaimed magnificence sounds more like a line of bullshit, and that you are deluding yourself at this point, since you cannot produce a single shred of proof. Your also saying you would impersonate the other anonymous coward apk completely made you look like the troll you are and you know it and now you suddenly recanted? It's more like you knew you blew your cool and looked stupid, and even stupider than you looked when you stated the other anonymous coward apk said John Carmack modded his posts up, and when he asked you to show a quote where this happened, you could not. As far as winning here, the only thing you have won is the troll of the week award at best in being caught lying and having no proof of your "delusional magnificence" on your part. You couldn't even produce 1 thing that others in either websites articles, guides, or articles in written publication you have been in where the anonymous coward apk had 100 evidences or more, of where his writing or software was well received in all of those areas and more. You really cannot read and are dyslexic as well as dumb.

  387. You are a liar, and a delusional troll by MEK_LoveBug · · Score: 1

    You've evaded a very pertinent question of what the forums section is here when you were asked troll. It is the developers section and not the english grammar section of this website and you know when you answer that it will only show you are an off topic troll. As to your being superior in anything here, you are better in only 1 respect, and that is being a profanity spewing troll who is a legend in his own mind only and a trolling loser. Threatening to impersonate others only has me thinking that you are some 10 year old who is caught in his own words' stupidity and now is having a tantrum because he can't get out of his lies and idiocy due to his own stupidity. You blew it and you definitely lost this debate because of your wanna be geek angst.

  388. If anyone lost here, it was you troll by MEK_LoveBug · · Score: 1

    You lost this troll, and not the other anonymous coward apk. You came in here saying the anonymous coward apk could not write and he put up a lot of proofs to the contrary from written and well known publications about computing, and some were fairly impressive imho such as the windows it pro article and his taking a company to a finalist position at microsoft's tech ed for them 2 years in a row. You haven't done the same and you try to play it off as you have done better but it doesn't work when you won't put out even 1 such evidence of you doing the same even. Being caught lying about anonymous coward apk, in you saying he said John Carmack moderated his postings here up, was a lie. The anonymous coward apk asked you to put up a quote of his saying that and you could not because he had not said that at all. You shouldn't tell others how to write, and most especially when you yourself can't even read.

  389. You lost troll, go away now by MEK_LoveBug · · Score: 1

    No you lost, and you are losing your mind as well imho. Especially where you threaten to impersonate the other anonymous coward apk as you have here in this debate which you lost and in doing so threw your little fit and threatened to impersonate someone who clearly got the better of you in actual visible accomplishments in both written publications and website articles as well as software he had done commercially and as freeware or shareware over time. You had nothing like any of that and yet you said he could not write? You also showed you can't read by saying he said John Carmack moderated his posts up and when he asked for a quote from you proving he said that, you again failed to produce such proof. You accuse others of not being able to write and you can't even read properly. Go away troll, you lose, and you know it.

  390. Holy crap you are full of it and a liar by MEK_LoveBug · · Score: 1

    The anonymous coward apk never stated that John Carmack moderated his posts up, and apk only brought up John Carmack only after you called the rest of us here slash tards and other less than cool names. He only mentioned John Carmack as an example of somebody who posts here who is also known to be a great game engine creator and programmer is all. Not once did the anonymous coward apk say John Carmack moderated his posts upward though apk had you saying that in a quote of your own words, and when apk asked you to show where he had said what you accused him of, you were unable to produce proof of apk saying John Carmack had moderated apk's posts up. It only makes sense you could not produce such proof because apk never said that or even remotely insinuated it. You are either a dyslexic brain damaged troll or a lying troll but either way you are a loser.

  391. What gives you the right to give orders here? by MEK_LoveBug · · Score: 1

    You're not a moderator here, and you do not own this forums board either. Quit giving orders to others when you have no authority to give them at all here and especially when you have to toss a profanity loaded mess all over our screens when you do so. You are defintely a troll who talks a lot of his own greatness and yet you have not a single shred of proof where others in the field of computing have ever said they thought highly of your words whereas apk had a bunch of that to his credit. You accused apk of things he had not said and he captured a quote of that regarding you stating that apk said John Carmack moderated his posts up here and when apk asked you to provide a proof of his saying that by quoting him doing so, you evaded providing that quote. It didn't exist and you were caught lying or provided proof that you are really dyslexic and cannot read correctly. Given that, I would not go giving orders and more importantly telling others they cannot write when you have only shown you cannot even read written words properly.

  392. Troll he has done a lot more than you ever will by MEK_LoveBug · · Score: 1

    That's not what I saw and not all of apk's posts that he showed of 80 that were moderated up here are long. One was very cool in that it showed him showing a way to secure programs that the other developers here moderated up because it could help stop binary infecting viruses and also one where he showed the questions microsoft had asked him in an interview with them where they approached he and not he approaching microsoft. Another quite short one he did showed how to secure excel versus a known security vulnerability that is still present in it and many others I found quite interesting but those definitely stood above the others and they were quite short despite your rant here. I don't rate others well or compliment them on length. I only do so on content so don't go and call us slash tards here and speak for the rest of us you troll. Somehow I doubt you have 80 people here who have ever moderated your posts up as insightful, or interesting as apk showed us he had done as well as his appearance in respected publications in this science of computing both in wares he made as well as guides that have done well (I tried that one and it works and I have not been infected since to date). You are a troll and I suspect an adolescent geek is what you are who has been caught in his lies and trolling stupidity and it made you even threaten to impersonate apk. That did it for me. You are a troll.

  393. Reaching for straws troll? Pitiful display by you by MEK_LoveBug · · Score: 1

    He sure caught you off guard and you grabbed the wrong tiger by the tail. You have nothing like the list of what the anonymous coward apk has shown us he has done in response to your saying he can't write. I will believe 80 upward moderations here, topped off by his appearance 10 times in written publication from 1997 through 2002 as well as having commercial software code to his credit plus the results he has shown in the securing windows guide he put out which I tried and it works if you can follow some simple safety rules. Instead of giving him a difficult time here just because you cannot read and cannot admit you made mistakes in accusing him falsely saying that apk had said that John Carmack moderated his posts up and to which apk quoted you accusing him of. When he then asked you to provide the proof of his actually stating that and you could not that also made me think you have problems reading, like dyslexia. The problem is clearly yours and you lost troll. Don't tell others how to write when you cannot read and have not even been featured in publications where others felt your work was good as his was and he had proofs of it and you had none troll. You are just grabbing at straws trying to "save yourself" somehow and it is only burying you deeper in the hole each time you are shown lying or that you cannot read correctly. Either way, it also shows you have no grounds, ability, or rights to tell others how to write when you can't even read correctly on your part.

  394. Troll the only failure here is you by MEK_LoveBug · · Score: 1

    The only failure here is you. I and others have read this end to end and have seen you lie, fail to provide proofs on your part you have been asked to in response to you saying how great and smart you supposely are (in your own mind only because you can't put up proof where others note your work in any form as good regarding this science, since this is the developer section here and not the english grammar critique section which you came in here attacking apk with). You have also shown you lie or cannot read properly when you stated apk supposedly said John Carmack modded apk's posts up and he has you quoted saying it. apk asked you fairly for a quote of his actually stating what you accused him of and you had no proof of it, only proof you cannot read correctly apparently. If you cannot read, how the hell can you go around telling others how to write? You have no PHD in English, you have never been featured in the science of computing in multiple respected publications as apk proved he has over more than a decade now many times (despite you literally saying you are smarter and better than apk also) as well as his guides being popular and most of all effective in securing users machines like my own, and you had the nerve to tell him how to write? Learn to read on your end and go away troll.

  395. You're a superior troll, liar, and screw up by MEK_LoveBug · · Score: 1

    Threatening to impersonate someone because you made mistakes here publicly in saying they said things they had not and when you were asked for proof of you accusation that apk supposedly said John Carmack moderated his posts up here, you did not provide it and were quoted by the person you accused in apk. He asked you for a quote of his stating that and you could not provide that which doesn't exist and it made you look to be either a liar or dyslexic. Liars are trash, but dyslexia is not anyone's fault as far as I know. Since you may be dyslexic I hope you realize it disqualifies you from telling others how to write since you cannot read correctly yourself and you came in here ad hominem attacking apk that way and have proven yourself to not possess anything that qualifies you as expert in the english language like a PHD might do for you if you had one. You also state how great you are (in your own mind because nobody else says you are and most importantly in the science this forums section is about in computing), but you omit proofs of your so called magnificence where others said you wrote well also on top of your being off topic here the entire time too. You are a troll and not even good at doing that.

  396. You are guilty of being a goof and trolling liar by MEK_LoveBug · · Score: 1

    You said he cannot write well, but he had a large amount of proofs of that from 80 or more moderated up posts here (a few were very cool like showing how to protect binaries from viral infestations and also where apk was interviewed by microsoft and he showed some cool algorithms that sparked a good deal of interesting computer science conversation afterwards) and on grounds like informative or interesting, on top of a guide for securing a pc that has done well and he produced testimonial from a user who has done well because of his guide where the person has not been infected by a virus since and I have experienced the same but not as long so far is all. apk also provided his verifiable appearance in 10 publications since 1997 to 2002 that are respected in computer sciences for software he wrote or articles he had done. Windows it pro is a good one he had that stood above the rest and that same work ended up as commercial software and to good review as well as taking the company he wrote parts of those wares for to a finalist position at microsoft's tech end 2 years in a row. You said he cannot write well after you proved that you are either a liar or a dyslexia victim. I say that because I saw the whole exchange here where you accused apk of supposedly stating he said his posts were modded up by John Carmack and he quoted you in that much. He in turn asked for your proof via quoting him also where he in fact said that and you had nothing. Just like you had nothing like the list of what he has done that was shown as good by 100 others in summation versus your mere dyslexic no PHD in English lying and trolling here. Go away troll. You have beaten only yourself. Threatening to impersonate apk on other forums was the last straw though. You have no shame and are a trolling loser. Don't tell others how to write, which is how you came in here ad hominem attacking apk while doing so, after you have been shown to be unable to read correctly.

  397. Re:You are guilty of being a goof and trolling lia by Anonymous Coward · · Score: 0

    LOL You really felt the need to type all that out, didn't you, APK?

    What were you saying about "The End of Days"? That he has a bunch of accounts he uses to moderate up his own points? What do you call this?

    s/anonymous coward apk/mek_lovebug/g.

    You really do need help.

  398. Re:Evading question & not providing proofs via by Anonymous Coward · · Score: 0

    "If you have nothing new to say, just shut up, you monumental, moronic, indescribably stupid waste of flesh." - by Anonymous Coward on Friday March 20, @05:59PM (#27274567)

    First of all?

    Why should I "obey you"??

    You evade my questions, AND you have proven the dyslexic dullard who is unable to read correctly

    (lol, AND? A dyslexic dullard who no less tells others how to write, minus a Ph D in English on YOUR PART, no less, & you haven't even been in publication as I have been, MANY times now (so much for you saying I cannot write))??

    No, don't think so...

    After all - You aren't my superior here, especially here in this forums section (based on your lack of any type of accomplishments in it since you failed to produce them when asked), & you aren't a mod: No, I think I'll do as I please - how's that suit you?

    Nothing you could do about it, anyhow, except be the "frothing @ the mouth troll" I predicted you'd turn up as... lmao!

    (Trolls: Always the same predictable fools... yet more evidence of the same is next readers, lol, for YOUR added entertainment (told you all I could make him "do tricks", easily, lol...)

    ----

    "That's a lot of bold, APK. But bold text will not save you from the inescapable conclusion that you are a moron, and incapable of intelligent thought or writing, you ridiculous twat" - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Gosh, again readers:

    Look @ that "raging foaming @ the mouth reply"... lol, "we spare no expense for your entertainment, in our obtaining the services of ONLY the MOST 'primitive of trolls'", rotflmao...!

    (Complete with the profanities spewing no less, the sign of defeat in debate, everytime... lol!)

    ----

    "You have been judged, and found lacking." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Yes, judged by a troll, sure - I can agree with THAT much, lol!

    (AND, you're a troll that has no accomplishments he can put up to show he is indeed, a peer to myself in this area... & by one who has no Ph D in English either, yet tells us all "you can't write well"!)

    Man, lmao:

    So much for your "judgement" because you can't read, this much is apparent, & you evade questions that will show you are indeed way, Way, WAY off-topic here as well!

    ----

    "I have absolutely no need, desire, or cause to justify myself to you. I am more accomplished than you by far - I simply feel no need to trumpet mediocre accomplishments as if they're something special, as you do." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Ok then:

    Well, where are they then?

    (You don't have any, admit it! All you have is just your "self-proclaimed greatness", lol, & delusions of your own grandeur)

    "Where's your crown, KING NOTHING? (Where's you crown...??)" - Metallica

    That's your song @ this point, lol... because like the song says, @ it's termination (and your lack of proofs here of you doing the same as I have or better)? You have:

    "... ABSOLUTELY NOTHING..."

    But me laughing @ you, & loving it!

    (You sure have lots of "HOT BLOWHARD WIND", but no backing or substantiation of your claims of being smarter/better etc. than I, & that I could not write well, despite my work taking companies to Ms-Tech Ed 2001 & 2002 as 1 single example only as a finalist no less in the hardest category, SQLServer performance enhancement, & more (I have tons of proof to the contrary here in this reply from others here no less, 100:1 vs. your opinion, from forums to written publicaitons in this field, you have not a shred of that in your favor, man... lol, you are hilarious, and good @ looking quite stupid to be honest...)

    ----

    "I'm smarter, more articulate,

  399. Re:John Carmack accusation, & answer a questio by Anonymous Coward · · Score: 0

    "If you have nothing new to say, just shut up, you monumental, moronic, indescribably stupid waste of flesh." - by Anonymous Coward on Friday March 20, @05:59PM (#27274567)

    First of all?

    Why should I "obey you"??

    You evade my questions, AND you have proven the dyslexic dullard who is unable to read correctly

    (lol, AND? A dyslexic dullard who no less tells others how to write, minus a Ph D in English on YOUR PART, no less, & you haven't even been in publication as I have been, MANY times now (so much for you saying I cannot write))??

    No, don't think so...

    After all - You aren't my superior here, especially here in this forums section (based on your lack of any type of accomplishments in it since you failed to produce them when asked), & you aren't a mod: No, I think I'll do as I please - how's that suit you?

    Nothing you could do about it, anyhow, except be the "frothing @ the mouth troll" I predicted you'd turn up as... lmao!

    (Trolls: Always the same predictable fools... yet more evidence of the same is next readers, lol, for YOUR added entertainment (told you all I could make him "do tricks", easily, lol...)

    ----

    "That's a lot of bold, APK. But bold text will not save you from the inescapable conclusion that you are a moron, and incapable of intelligent thought or writing, you ridiculous twat" - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Gosh, again readers:

    Look @ that "raging foaming @ the mouth reply"... lol, "we spare no expense for your entertainment, in our obtaining the services of ONLY the MOST 'primitive of trolls'", rotflmao...!

    (Complete with the profanities spewing no less, the sign of defeat in debate, everytime... lol!)

    ----

    "You have been judged, and found lacking." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Yes, judged by a troll, sure - I can agree with THAT much, lol!

    (AND, you're a troll that has no accomplishments he can put up to show he is indeed, a peer to myself in this area... & by one who has no Ph D in English either, yet tells us all "you can't write well"!)

    Man, lmao:

    So much for your "judgement" because you can't read, this much is apparent, & you evade questions that will show you are indeed way, Way, WAY off-topic here as well!

    ----

    "I have absolutely no need, desire, or cause to justify myself to you. I am more accomplished than you by far - I simply feel no need to trumpet mediocre accomplishments as if they're something special, as you do." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Ok then:

    Well, where are they then?

    (You don't have any, admit it! All you have is just your "self-proclaimed greatness", lol, & delusions of your own grandeur)

    "Where's your crown, KING NOTHING? (Where's you crown...??)" - Metallica

    That's your song @ this point, lol... because like the song says, @ it's termination (and your lack of proofs here of you doing the same as I have or better)? You have:

    "... ABSOLUTELY NOTHING..."

    But me laughing @ you, & loving it!

    (You sure have lots of "HOT BLOWHARD WIND", but no backing or substantiation of your claims of being smarter/better etc. than I, & that I could not write well, despite my work taking companies to Ms-Tech Ed 2001 & 2002 as 1 single example only as a finalist no less in the hardest category, SQLServer performance enhancement, & more (I have tons of proof to the contrary here in this reply from others here no less, 100:1 vs. your opinion, from forums to written publicaitons in this field, you have not a shred of that in your favor, man... lol, you are hilarious, and good @ looking quite stupid to be honest...)

    ----

    "I'm smarter, more articulate,

  400. IF you "won", why avoid 3 simple questions then? by Anonymous Coward · · Score: 0

    "Sorry pal, but you lose. Lose, as in complete & abysmal failure." - by Anonymous Coward on Wednesday March 18, @06:28PM (#27248807)

    Funny: I am not the one who said "he was smarter & better" (as you have throughout this exchange in fact on YOUR part and I quote you again in it in THIS reply below later in it, in fact) & I wouldn't do so, not without proofs thereof.

    ---

    "I'm smarter, more articulate, and infinitely more coherent than you are." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Oh, yea, sure - based on your "fantasy list of accomplishments" you've showed us (not, lol)? Yea, "we believe you"... ( sarcasm on that quoted last part )

    You certainly aren't showing anything of that nature, & certainly NOT when others (other than yourself, lol) thought so... but, I surely did: See below, again, for your reference...

    ---

    Fact is, unlike yourself?

    I never said words of that nature - I only provided proofs of where others noted my works as good in written publications, online, & more...

    A.) When I asked for your list of where you had done decent things in this field, you have zero...

    AND

    B.) When I asked a couple simple questions (1. Where I said verbatim that John Carmack modded my posts up & 2.) What is the name of this forums section) You avoided BOTH questions (gee, I wonder WHY, not) repeatedly through this exchange.

    Some "Win" on your part (not)... The same questions are listed below in THIS post, again, for your reference (and answer them won't you, for once?)...

    ROTFLMAO - "Too Easy"...

    ---

    "I have absolutely no need, desire, or cause to justify myself to you. I am more accomplished than you by far - I simply feel no need to trumpet mediocre accomplishments as if they're something special, as you do." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Ok then:

    Well, where are they then?

    (You don't have any, admit it! All you have is just your "self-proclaimed greatness", lol, & delusions of your own grandeur)

    "Where's your crown, KING NOTHING? (Where's you crown...??)" - Metallica

    That's your song @ this point, lol... because like the song says, @ it's termination (and your lack of proofs here of you doing the same as I have or better)? You have:

    "... ABSOLUTELY NOTHING..."

    But me laughing @ you, & loving it!

    (You sure have lots of "HOT BLOWHARD WIND", but no backing or substantiation of your claims of being smarter/better etc. than I, & that I could not write well, despite my work taking companies to Ms-Tech Ed 2001 & 2002 as 1 single example only as a finalist no less in the hardest category, SQLServer performance enhancement, & more (I have tons of proof to the contrary here in this reply from others here no less, 100:1 vs. your opinion, from forums to written publicaitons in this field, you have not a shred of that in your favor, man... lol, you are hilarious, and good @ looking quite stupid to be honest...)

    ---

    "And rather than justify myself to the likes of you, I prefer actually accomplishing things." - by Anonymous Coward on Friday March 20, @01:36PM (#27270809)

    Like what? Trolling, as you have here, off-topic the whole time??

    (LMAO - the ONLY thing you've 'accomplished' here, is making yourself look like the off-topic, foaming @ the mouth profanity spewing troll you are, who is a "legend in his own mind", @ this point, after that 'tirade' above... lol!)

    ---

    "You cannot write well" - by Anonymous Coward on Friday March 20, @11:25AM (#27268837)

    Opinions vary, but, I have a lot of proofs to the contrary

    (Unlike yourself)

    The evidences below outweigh your "No Ph D in English" opinion, literally, 100++:1!

  401. Re:IF you "won", why avoid 3 simple questions then by Anonymous Coward · · Score: 0

    APK, you're a loser. I'm through with you here, but I'll be sure to spread the good news of your existence far and wide across the web.

    These rambling, incoherent posts are just amazing in their stupidity and incomprehensibility.

    You're a moron. I'm not. You lose. I win. It's just the way it is.