• Harry (unregistered) in reply to ayende rahien
    ayende rahien:
    J Mac:
    gwenhwyfaer:
    Harry:
    I fired one guy because he changed the brace style on an entire project and then committed the change.
    ...with an overactive trigger finger and a "zero-tolerance" approach to mistakes.

    I read that as "This guy needed to submit changes to CVS every $INTERVAL to prove that he was working. He, thinking I wouldn't check what he submitted, changed the brace style instead of actually working."

    I'd fire someone for that too.

    There are times that I am doing five - six checkins in an hour, or go without the whole day. Sometimes I might over a day without checking stuff, if this is a big change (if it is bigger than that, I branch). I requires that everyone in the team would checkin once a day or so to avoid accidental conflicts, but that is not because I need to check on them (although I do use the checkin mail for code review).

    Requiring that I would check something at $inverval is stupid. It is very easy to burn hours tracking and fixing a problem, especially with new / complex technologies. Equating checkins to work is just as bad as measuring lines of code per day for productivity.

    I agree that equating checkins to work is dumb. But if you have a new hire and he doesn't check in anything in his first week of work you should be asking some questions. Is he stuck? Does he realize that not checking in means that he's likely to be causing merge problems? Intelligent management is catching problems before they get out of hand. Monitoring VCS activity is one of the best ways to do this.

  • KnowNo (unregistered) in reply to Franz Kafka
    Franz Kafka:
    gwenhwyfaer:
    Harry:
    When I was supervising contractors ...

    I fired one guy because he changed the brace style on an entire project and then committed the change.

    (Harry has) ... an overactive trigger finger and a "zero-tolerance" approach to mistakes.

    So, maybe firing the guy was over the top if it was the first time, but you can't really allow people to touch every damn file for something as petty as brace preference. Did he even talk to the other developers?

    It seems to me that everyone is parsing out Harry's sentences separately... I took the firing as for a contractor. If I'm paying a guy contractor rates and he spends a half day of my budget commiting brace changes, I'd fire his ass too.

  • smile (unregistered) in reply to Phil E Stein
    Phil E Stein:
    there are some very successful comedians who I think are incompetent, and conversely some of the ones I think are competent are not very successful professionally.
    You are just not as skilled at gauging the competency of comedians. :P
  • Matt (unregistered) in reply to Salami
    Salami:
    Fudge Packer:
    I've done a lot of consulting, and I gotta say it just comes down right off the bat as to WHY the consultant needs to come on board in the first place.

    If you're overworked, staff is stretched thin and you just tack on resources without really checking up on them and mentoring the resources, well--you get stuff like this.

    If you have a small staff of programmers and you overwork them, they will demand help. So, if you are smart, you bring in an incompetent contractor, so your staff no longer asks for help and you only have to pay for one 8 week contract (and not even that in this case).

    You think overworking your staff then lying to them when they ask for help is smart? It's quite the opposite. They'll start lying to you in return (because honesty is, by management example, not an office virtue), resent the overwork and move on well before they might have otherwise. You'll lose competent workers and business knowledge. All for the sake of avoiding a difficult explanation and (perhaps but unlikely) saving a few bucks.

  • MoroS (unregistered)

    I sometimes work as a contractor myself, but that dude is just a disgrace, not only to contractors, but to generally coders. He/She should be punished by whiping.

    CAPTCHA: muhahaha (and a sound of a swinging whip)

  • skztr (unregistered) in reply to Harry
    Harry:
    ayende rahien:
    J Mac:
    gwenhwyfaer:
    Harry:
    I fired one guy because he changed the brace style on an entire project and then committed the change.
    ...with an overactive trigger finger and a "zero-tolerance" approach to mistakes.

    I read that as "This guy needed to submit changes to CVS every $INTERVAL to prove that he was working. He, thinking I wouldn't check what he submitted, changed the brace style instead of actually working."

    I'd fire someone for that too.

    There are times that I am doing five - six checkins in an hour, or go without the whole day. Sometimes I might over a day without checking stuff, if this is a big change (if it is bigger than that, I branch). I requires that everyone in the team would checkin once a day or so to avoid accidental conflicts, but that is not because I need to check on them (although I do use the checkin mail for code review).

    Requiring that I would check something at $inverval is stupid. It is very easy to burn hours tracking and fixing a problem, especially with new / complex technologies. Equating checkins to work is just as bad as measuring lines of code per day for productivity.

    I agree that equating checkins to work is dumb. But if you have a new hire and he doesn't check in anything in his first week of work you should be asking some questions. Is he stuck? Does he realize that not checking in means that he's likely to be causing merge problems? Intelligent management is catching problems before they get out of hand. Monitoring VCS activity is one of the best ways to do this.

    Are you letting the new guy commit to trunk??

  • StressBomb (unregistered)

    You know, don't be so quick to judge people based on stories, and especially a story by Alex (who always adds lots of drama to everything posted here :).

    Truth of matter is with today's level of stress some people, even though competent, simply blow a fuse and can't work.

    Been there myself. During hard times, I just can't myself work and may just stare and the screen or find myself checking my mail every minute.

    Then I try to relax, and may spew enormous amount of high quality (well.. at least not poor, not to claim a lot) code from morning to evening.

    My point is, calling someone "Incompetent" isn't telling the whole story.

  • (cs) in reply to J Mac
    J Mac:
    I read that as "This guy needed to submit changes to CVS every $INTERVAL to prove that he was working. He, thinking I wouldn't check what he submitted, changed the brace style instead of actually working."

    I'd fire someone for that too.

    And if I were working somewhere I had to check something in every $INTERVAL to prove I'm working, I'd just leave. It'd feel like the worst kind of micromanagement to me. If you won't trust me, don't hire me.

  • (cs) in reply to ayende rahien
    ayende rahien:
    Obviously you have never been involved in trying to hire good people... Nothing promotes malcontentness like backstabbing employers.
    So naive. It's touching... And yet even though what you say is apparently true, backstabbing employers not only persist, they rapidly become middle managers.
  • Brady (unregistered)

    hmm!!! I love this guy's commenting style. Here comes a conclusion! hmmm!!!!

  • (cs) in reply to Harry
    Harry:
    But if you have a new hire and he doesn't check in anything in his first week of work you should be asking some questions.
    Not half as many as I'd be asking of a manager who expected a new hire to start checking in code before they'd learned their way around the system...
    Intelligent management is catching problems before they get out of hand
    ...not creating the bloody things in the first place.
  • (cs) in reply to StressBomb
    StressBomb:
    Truth of matter is with today's level of stress some people, even though competent, simply blow a fuse and can't work.
    I've been there myself; in fact, the second job I took, I first went off sick with stress, then quit, after my whole life fell to pieces and I found myself not even able to understand the screenful of Perl I was supposed to be fixing. It was over a year before I took another computer-related job. Some people use work as an escape, or a relief, from the stresses in their life; others, like me, grind to a halt in stressful circumstances - potentially up to a fifth of the population will react this way.
  • (cs) in reply to Shaun
    Shaun:
    Funny story, love the actual physical evidence of this guy but I have one bone to pick. There's nothing wront with asking a lot of questions about process and design when you start up. That's not a sign of a poor developer.

    Thats not exactly true. There IS something wrong with asking lots of stupid questions. And yes, despite what some people tell you there ARE stupid questions.

    What is 1+1? Oh, ok so what is 1+2?

    It is one thing to come in and asks questions like "How do I get the source?" is fine, but "How do I build? hmmm I get ';' missing, how do I fix that?" etc isn't fine.

  • (cs) in reply to chrismcb
    chrismcb:
    What is 1+1? Oh, ok so what is 1+2?

    Right, so proof by induction is a stupid question... guess that Kurt fella was just wasting his time then...

    (Seriously, just because something seems obvious doesn't mean it actually is. I'd have thought the existence of this site proof enough of that.)

  • Ugh. (unregistered) in reply to gwenhwyfaer
    I've been there myself; in fact, the second job I took, I first went off sick with stress, then quit, after my whole life fell to pieces and I found myself not even able to understand the screenful of Perl I was supposed to be fixing. It was over a year before I took another computer-related job. Some people use work as an escape, or a relief, from the stresses in their life; others, like me, grind to a halt in stressful circumstances - potentially up to a fifth of the population will react this way.

    Damn. I've been fighting the same problem recently, and it only seems to be getting worse. I've heard of people saying they're "burned out", but I can't help but wonder... is this what it feels like? Do you feel like you've recovered after your hiatus?

    I used to churn out a few hundred lines per day, and now if I do 20% of that, it's a lot. It's scary, really.

    I know this is OT, but it's weird to see someone randomly describe exactly how I've been feeling the last few months.

    Captcha: burned (out?) Captcha is eerily prescient...

  • (cs) in reply to ayende rahien
    ayende rahien:
    There are times that I am doing five - six checkins in an hour, or go without the whole day.
    I often go weeks without checkins (at least on code for large new featuers). What's the point of checking in something that isn't finished? It makes comparing the code versions much more difficult if there is a bunch of fluff checkins cluttering stuff up and making a mess of history. No one needs to see the intermediate changes, and premature checkins will cause problems for everyone else.

    I know people on the other hand who do like to "check in early, and check in often", including my boss. But inevitably this leads to a lot of panicked scrambling to check in patches to fix the previous check ins, while the rest of the team is stuck with a broken system.

  • (cs) in reply to Harry
    Harry:
    I agree that equating checkins to work is dumb. But if you have a new hire and he doesn't check in anything in his first week of work you should be asking some questions. Is he stuck?
    Holy crap! I've rarely worked on a system so simple that a new hire could be checking in code in the first week. It takes almost that long just to get through all the HR paperwork, get the computer set up, arrange for source code control and bug database access, read through the procedures, etc.
  • Hank Miller (unregistered)

    As to the team getting the work done in a weekend, everyone is missing one major point: WTFs.

    The company appears to have wanted high quality code, so they hire someone and give him plenty of time so that they can get high quality results. Instead they got a lot of kludges messing up the code, most likely a lot of copy and paste coding, and constants hardcoded all over so nothing can change. It all seems to work, except for random crashes every few days that nobody can figure out. But it was done by the deadline so they live with it.

    If this contractor was half way competent he would have beautiful code that was well tested.

  • (cs) in reply to chrismcb
    chrismcb:
    It is one thing to come in and asks questions like "How do I get the source?" is fine, but "How do I build? hmmm I get ';' missing, how do I fix that?" etc isn't fine.
    "How do you build" is a perfectly valid question. It's non-obvious. He have a large document on it (intended for the build engineer mostly).

    I didn't know how to build when I first started my latest job. They had this bizarre thing called Visual Studio which I wasn't too familiar with, plus a cross compiler plugin, and all sorts of wierd projects and sub projects. I was more used to just typing "make".

    Now if they don't understand simple compiler errors, that's a problem.

  • Mr. Physics (unregistered) in reply to chrismcb
    chrismcb:
    And yes, despite what some people tell you there ARE stupid questions.

    No. There are no stupid questions. Those questions may be perfectly reasonable for a 3 year old. However, there are a LOT of ... well I'll let you read the following (de-)motivator poster yourself:

    http://despair.com/cluelessness.html

    ;-)

  • TSK (unregistered) in reply to Phil E Stein
    Phil E Stein:
    Jon W:
    This is heart-warming! He might suck at programming, but at least he has some self-knowledge.

    For more fun in that regard, google "unskilled and unaware of it" for a great psychology report.

    If its the report I got, its a WTF in itself. They studied competence in humour, comparing against a panel of "professional comedians". This is about the worst thing you could possibly study scientifically. There is very little agreement about what is funny, there are some very successful comedians who I think are incompetent, and conversely some of the ones I think are competent are not very successful professionally.

    No, it isn't. Humor cannot be studied "scientifically" because it does not depend on reason and cannot therefore defined. Science isn't a silver bullet which can be applied to every person. The most intelligent person in the world can still be total humorless and cannot recognize a good joke if it is dancing on his nose. But that good jokes can be recognized is proved by the fact that the report states a 0.76 correlation which is damn good (if you compare that with other correlations in psychology).

  • Anonymous (unregistered)

    Has anyone ever just written a bunch of test cases, handed these to a contractor and said you'll be paid when the tests pass? automate this and you wont need to check up on 'em if your really too busy.

    Obviously, you'll need fairly comprehensive test cases to avoid the morons that will just check in a series of hardcoded if/then/else statements. Use the contractor(s) as coding robots, you write the test cases/specification, they make it happen. Use FIT and management will just see a bunch of nicely formatted documents with pretty colors they can understand.

  • (cs) in reply to KattMan
    KattMan:
    gwenhwyfaer:
    Harry:
    When I was supervising contractors I was set up to get emails every time they committed something in order to take a look at exactly what was going on.
    So you're a confessed micromanager...
    I fired one guy because he changed the brace style on an entire project and then committed the change.
    ...with an overactive trigger finger and a "zero-tolerance" approach to mistakes.

    Yeah, I bet you're a real joy to work for...

    I'll disagree with you on the micro-manager. Perhaps he only does this on short term contractors. That actually seems appropriate.

    I will agree on the Overactive trigger, especially since this isn't really a mistake to move the braces. It is a style issue and ultimately it matters not how they are placed. Granted the developer that went and changed them all suffered from the same problem.

    Making a sweeping global change to the source code IS NOT a mistake?

    Changing the style of the project to fit your own personal style is bad enough. But potentially destabilizing the entire project on a whim seems like a firable offense to me.

    Can you look at the code and prove that nothing was broken? If it was only a whitespace change, you may be able to run the code through some comparison utilities to prove that there was no real changes made. But still, looking at the normal diff will be almsot impossible. Who is to say he didn't try to slip some backdoor in there?

  • Harry (unregistered) in reply to gwenhwyfaer
    gwenhwyfaer:
    Harry:
    But if you have a new hire and he doesn't check in anything in his first week of work you should be asking some questions.
    Not half as many as I'd be asking of a manager who expected a new hire to start checking in code before they'd learned their way around the system...
    Intelligent management is catching problems before they get out of hand
    ...not creating the bloody things in the first place.

    What's the context of the story? Contractors that float through an assignment because they aren't looked at to start contributing in a reasonable time frame and end up hiding their lack of capability and not contributing at all. This is clearly a failure in management. If you are approaching things intelligently you give the person a small piece of work to start with to get his feet wet. This should not be something that takes more than a week to do. If your IT systems and HR take a week to get the new hire access you have a management problem. That week can be costing you $3000 in just his billing costs. If he does something destructive like change the brace style on the project and then commit it, he is not the person you want. If he isn't handling a small piece of work in a reasonable period of time, find out why. If he does handle it, lengthen the leash. This is obvious, basic stuff. I hope. If you can't do this you are going to have people leaving notes reading "I focked up" and putting your project behind schedule.

    captcha = craaazy

  • PaulaBean (unregistered)

    Brillant!

  • axl (unregistered) in reply to Jno

    Well, didn't you ever notice that you write code substantially faster if the spec is clear to you (i.e. written by yourself) and all the other code you are interfacing is already finished (by you and your colleges) .. at least an all-nighter creates working code most of the time.. maintinance is another issue....

  • toganet (unregistered)

    Holy crap I think I just hired that guy.

  • PHP coder (unregistered) in reply to suetanvil
    suetanvil:
    Do Incompetents ever read TDWTF and realize what a pain in the ass they are?

    No, never. True incompetents never, ever question their own competence. They read TDWTF and say, "Ha ha, what a goober that guy is," never even entertaining the possibility that they may well be the person being mocked. They believe (or at least, firmly stick to the fiction) that they are supremely competent in what they do.

    The fact that this guy actually admitted to making a mistake means he's less incompetent than the average Paula Bean.

    Someone once wrote a research paper called "Unskilled and Unaware of It: How Difficulties in Recognizing One's Own Incompetence Lead to Inflated Self-Assessments", they were trying to prove "that such people are too dumb to be knowledgeable of their own feeble mindedness".

    To sum it up: People tend to hold overly favourable views of their abilities in many social and intellectual domains. The authors suggest that this overestimation occurs, in part, because people who are unskilled in these domains suffer a dual burden: Not only do these people reach erroneous conclusions and make unfortunate choices, but their incompetence robs them of the meta-cognitive ability to realize it.

    apa.org/journals/features/psp7761121.pdf

  • StressBomb (unregistered) in reply to PHP coder
    Someone once wrote a research paper called "Unskilled and Unaware of It: How Difficulties in Recognizing One's Own Incompetence Lead to Inflated Self-Assessments", they were trying to prove "that such people are too dumb to be knowledgeable of their own feeble mindedness".

    This is an overly complex way to just say you can't judge what you don't understand.

    You can't exactly expect someone who never for example wrote a class in his entire life, understand the benefits of OOP. I've had talks just yesterday with two developers that were convincing me OOP is a passing fad and it's too unnatural to code in OOP.

  • (cs) in reply to ayende rahien
    ayende rahien:
    There are times that I am doing five - six checkins in an hour, or go without the whole day. Sometimes I might over a day without checking stuff, if this is a big change (if it is bigger than that, I branch).

    You manage to make the code change, build it, test it, and check it in all in under 10 minutes? If someone on my team was checking into a product 5-6 times an hour I'd probably be double checking all his check ins and getting him on the short track out the door.

  • Anony Moose (unregistered) in reply to Rob
    Rob:
    Now why is it that contractors are paid more then salary employees? (And don't give me that stock option crap)
    Salaried employee: work X weeks per year, get paid each week, 2 weeks a year. (Or monthly. Or whatever.) Get insurance. Company's lawyers go to court if company is sued. And other stuff.

    Contract employee: work 3 months, submit invoice, look for next gig while waiting, get paid. Pay own taxes. Pay own insurance. Pay own lawyer's fees. Go to court when sued personally. A vacation means not getting paid.

    The cash left in the bank account for buying food, clothing and shelter (and maybe toys) is significantly less than the hourly billable rate for a contractor. Onl a retard would take a contracting position without getting paid enough to cover all the extra bits.

  • Creachadair (unregistered)

    What we seem to be missing here is that the wording of his note is quite ambiguous. When he writes, "I won't bill obviously" he could very well mean "I will not bill you in a manner that is obvious," rather than "it is obvious that I will not bill you." This COULD imply that he intends to pull a fast one with the Accounting department. :-)

    Now, I grant you that given the "quality" of his other efforts as illustrated by this WTF, I don't think this is terribly likely, but you never really can be sure.

  • Failure (unregistered) in reply to tharfagreinir

    I would have...

  • J355ga (unregistered)

    Hey - at least he left some documentation!

  • (cs)

    This ... This ... This ...

    . . . . .

    This is outrageous.

  • (cs) in reply to rioshin
    rioshin:
    kimbo305:
    Is there not a contractor black list somewhere in the industry? That man/woman needs to be punished.

    And if there isn't, why not? It'd be an awesome service...

    Interviewer: Let's check up on you at www.whatever.com. Interviewee: Uh, oh...

    Why would you interview if the person is listed on whatever.com ?

    On an-unrelated note: The first entry on whatever.com should be 'Elbonia'.

  • (cs) in reply to rmr
    rmr:
    justsalt:
    // hmmm!!! // Where can I find a more clueless company that I // can bill for doing nothing.

    In lala land.

    Seriously, there is something a little "foched" about this whole story. How could someone possibly give "daily status reports" for weeks without the manager realizing that there was little to no progress?

    He betrayed the trust extended to him by lying.

    Trust does not substitute for control - it implies it.

  • (cs) in reply to Shaun
    Shaun:
    Funny story, love the actual physical evidence of this guy but I have one bone to pick. There's nothing wront with asking a lot of questions about process and design when you start up. That's not a sign of a poor developer.

    Second that: there are no stupid questions - only stupid answers.

  • (cs) in reply to jrrs
    jrrs:
    Based on what little I saw of the "American Idol" trials: many incompetents do not recognize themselves as such.

    American Idol .. is nothing.

    "Ethiopian Idol" tops it - easily.

  • MrJohnson (unregistered) in reply to Dan
    Dan:
    So, your contractor can't spell. He (obviously) has a hard time with basic grammar.

    Maybe he was a British.

  • Brady Kelly (unregistered) in reply to Unomi
    Unomi:
    It is classic. Something to remind never to do. Fucking up and saying you won't bill.....

    That is a WTF in itself.

    Yes, always be sure to bill.

  • Raw (unregistered)

    Well, at least he was honest about it and didn't try to shift the blame. That's much more than the fuckup contractors I've seen has ever done.

    The contractor tradition is usually to claim they are the experts, blame everybody else and bill for overtime because they had to "fix" everybody else's mistakes.

    Too bad there is some kind of rule against throwing furniture at guys like that...

  • passerby (unregistered) in reply to StressBomb
    StressBomb:
    You can't exactly expect someone who never for example wrote a class in his entire life, understand the benefits of OOP. I've had talks just yesterday with two developers that were convincing me OOP is a passing fad and it's too unnatural to code in OOP.

    Depending on the context, they may have been right. Some things are unnatural to write in an OOP form. OOP is a fad in the sense it is understood today by a lot of people who don't have historical perspective and insist that everything should be written in "OOP style" (meaning whatever the person insisting on it wants).

    C++/Java -style classes are a useful mechanism of abstraction, which is very well suited for some tasks, less so for others. It is certainly not the best way to do everything, and certainly not the only means of abstraction that should be taught, encouraged or accepted.

  • Dave (unregistered) in reply to Dustin

    Not so much a WTF as an OMG. This is why I think contractors should have to take out insurance for damages they cause, like doctors etc.

    At least they had his personal details on file.. I can only hope the guy had a few dark alleys to walk through on his way back home.

  • Anonymous Tart (unregistered) in reply to Harry
    Harry:
    gwenhwyfaer:
    Harry:
    When I was supervising contractors I was set up to get emails every time they committed something in order to take a look at exactly what was going on.
    So you're a confessed micromanager...
    I fired one guy because he changed the brace style on an entire project and then committed the change.
    ...with an overactive trigger finger and a "zero-tolerance" approach to mistakes.

    Yeah, I bet you're a real joy to work for...

    Actually I think I am a pretty laid back guy, however there are some things that you have to do to protect your code base. Changing the brace style on an entire project and then committing the result isn't just a normal mistake - it is an utter disregard for company standards, plus all of the other people you are working with who are accustomed to a particular style. Plus it destroys the ability of code analysis tools to produce usable change summaries and can make the project history in your VCS almost worthless. It is why many open source projects do not accept changes that are mere code reformats. If you think that is just a simple mistake, think again.

    Most open source projects come with a vimrc or equivalent specifying the formatting. If you are sacking people over a single checkin, your project could probably use one too.

    You could have just set the hairdryer to roast, and reverted the check-in tbh. If you were my boss, and had fired one of my colleagues for something as trivial as that, I'd be looking to get out ASAP...

    Incidentally, if he had changed it to 1TBS, then you were wrong, and he should be your boss :D

  • (cs) in reply to Harry
    Harry:
    I fired one guy because he changed the brace style on an entire project and then committed the change.

    That would depend on which way he changed it. If he changed it from K&R to Block then good on him and you'd have probably ended up firing me too.

    Maybe he wanted the code he was going to maintain to actually be readable?

  • (cs) in reply to KnowNo
    KnowNo:
    It seems to me that everyone is parsing out Harry's sentences separately... I took the firing as for a contractor. If I'm paying a guy contractor rates and he spends a half day of my budget commiting brace changes, I'd fire his ass too.

    Then you have a complete misconception about software engineering if you think it is all about just writing code. Writing code is only a very minor part of writing software.

    The first stages are gathering the requirements (the specification) plus examining what is already there.

    The software engineer in question was probably doing exactly that - examining the code base. He may well have had macros / scripts to modifying the bracing style. (I used to have them).

    And as I said just before, if he was changing it from K&R to block style, that makes the code far more readable and I am assuming this might be the code he was actually going to maintain, so it was good for him to read through it and see what it did.

    Not every CVS submission is a major change. Just label this as a style change only and then do your code compare between this version and the next, or between the previous version and this one. Presumably you label your releases properly.

  • Paula (unregistered)

    //hmmmm!!!! no quack.

  • (cs) in reply to MrJohnson
    MrJohnson:
    Dan:
    So, your contractor can't spell. He (obviously) has a hard time with basic grammar.

    Maybe he was a British.

    I think you should restrict yourself to saying something relevant, rather than merely making racist comments which give away your ignorance. Why should being "a British"(sic) and having an understanding of grammar be mutually exclusive? What on earth makes you think that your race has somehow cornered the market in intelligence or knowledge? Ffffft!

  • Ex-Narutard (unregistered) in reply to darin
    darin:
    ayende rahien:
    There are times that I am doing five - six checkins in an hour, or go without the whole day.
    I often go weeks without checkins (at least on code for large new featuers). What's the point of checking in something that isn't finished? It makes comparing the code versions much more difficult if there is a bunch of fluff checkins cluttering stuff up and making a mess of history. No one needs to see the intermediate changes, and premature checkins will cause problems for everyone else.

    I know people on the other hand who do like to "check in early, and check in often", including my boss. But inevitably this leads to a lot of panicked scrambling to check in patches to fix the previous check ins, while the rest of the team is stuck with a broken system.

    Huh, have you ever heard about branches?

Leave a comment on “The Contractor's Note”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article