• (cs) in reply to pouzzler
    pouzzler:
    This site has gone from a repository of charming bugs that made coders remember their early code with a slight tinge of nostalgia, or else roll their eyes until they were about to burst out of their heads, to a venting ground for employees resenting their (ex)management, and this article is another one of that sort.
    I disagree. Strongly! This site has gone to a clusterfuck of boring Hanzo stories, embellished beyond belief by that Erik Gern author who is so technically incompetent that he cannot describe the actual technical reason of the WTF but thinks adding Ninja and Samurai themes to the story is a good idea.

    Compared to that the description of the fallout of WTF-Inc-WTF is gold standard and i welcome every day that does not have a Hanzo story!

  • belzebub (unregistered) in reply to gnasher729

    Yes, that's what I assumed was the reason.. I personaly have a tendency to think there is only one Truth. And that is Technical Truth. If someone asks me in hurry, I'll think only in technical terms, and so if that happened to me, I would start talking about what they do in wrong way and why do I think it's wrong. And only after I've told everything, I would realize I've probably told too much.

    One time, I've almost blew one big contract when sitting at the meeting with a customer as my boss's "technical adviser" - and the customer wanted to solve some problem using our product in a very stupid way, which required him to order roughly 100 times more HW and SW then I thought would be needed if the product was used correctly. So my "technical" brain took over and started to explain how this could be done more efficiently using just a few pieces of HW.. and then my boss stomped on my feet really hard under the table.. I was shocked and did't understand for at least next 10 seconds in which my boss managed to save the day and a big pile of money also. I still have the job, but I'm no longer allowed near customers.. which is fine by me..

    So I'd like to have more common sense.. just like snoofle showed in that situation.

  • modo (unregistered) in reply to belzebub
    belzebub:
    but I'm no longer allowed near customers
    Because you might help them too much? Sad, but probably typical.
  • Harrow (unregistered) in reply to belzebub
    belzebub:
    One time, I've almost blew one big contract when sitting at the meeting with a customer as my boss's "technical adviser" - and the customer wanted to solve some problem using our product in a very stupid way, which required him to order roughly 100 times more HW and SW then I thought would be needed if the product was used correctly. So my "technical" brain took over and started to explain how this could be done more efficiently using just a few pieces of HW...
    I did exactly this working for Wang Labs in 1978, and I received a bonus and a promotion. We used to think that an educated customer was a valuable asset. Apparently that customer has now become a liability.

    -Harrow.

  • CigarDoug (unregistered) in reply to EvilSnack
    EvilSnack:
    ObiWayneKenobi:
    It's always funny to watch a shithole company flounder, but even better when you can see it happening and (hopefully) educate others that the company is awful. I've seen far too many crappy companies stay afloat because nobody spreads the word that they're terrible and need to be avoided.
    Although there are quite a few companies that have quite a few people going around decrying their awfulness, and they still manage to stay afloat.

    It pays to have friends in Washington.

    I think many of the people on this site would agree that government picking winners and losers is an untenable situation *cough* Solyndra *cough* . This is one of the main themes Ayn Rand addresses in Atlas Shrugged: Those businesses who were incompetent but connected were kept alive by looting successful businesses. The longer I live, the more I see of Atlas Shrugged coming true.
  • ¯\(°_o)/¯ I DUNNO LOL (unregistered) in reply to Alex
    Alex:
    Dev: Quits, goes to work for client, tells the client what part of the system was broken so badly that they would have been wasting their money because it could never work with the size of their data.
    FTFY
  • (cs)

    Despite the fact that this is supposedly a site where code snafu's and what not are its focus, it is always refreshing to see snoofle's posts.

    After all, let he without a former company to grudge about cast the first rock.

    As for snoofle: kudos my man, kudos. Give them fuckers what for.

    BTW, how long must we wait until names can be named and individuals shamed?

  • RockyMountainCoder (unregistered)

    Well, I would have to give a tip-o'-the-hat to BigCo, Inc. for having the ability to realize that every single employee has unique knowledge and experience, and putting that realization into practice by looking through the HR database to see if they have anyone with specific knowledge of the potential vendor.

    They may be a lumbering bureaucracy, but that's almost unheard of in large organizations, today.

    To me, TTRWTF in today's world: A large company that sees its staff as individuals, and not line-items on spreadsheets.

  • Also Not snoofle (unregistered) in reply to luctus
    luctus:
    gnasher729:
    If you moved from company A to company B, and then spill the beans on company A, then company B has to assume that you will spill the beans on them when you eventually move on to company C.
    That's company B's fault for having beans to spill in the first place.

    I challenge you to find a company that doesn't have beans to spill.

  • Mandalf the Manly (unregistered)

    I for one enjoyed this story.

  • (cs)
    snoofle:
    (my spies back at WTF-Inc know where I'm working; they called, and hysterically informed me that all of my code [*] had been reverted back to the way I wrote it)

    *deleted "that"

    Is that what you meant to write? In other words, they went back to your code because it was right even though no one believed you at the time?

    (And why no [strike] BBCode directive, dammit?)

  • Anomaly (unregistered) in reply to Valued Service
    Valued Service:
    Mr.Bob:
    Let's not be coy... this is about Healthcare.gov, right?

    I don't have to argue the premise. I just have to point out how hard the gov fails all the time.

    It doesn't mean something shouldn't be done, just that the gov will fail to do it.

    When you have a stack of papers telling you what to do that no one has read, no one knows what it is, and no one can understand it, how can you expect a development team to achieve the correct requirements and produce a sound and valid set of logic to develop from.

    Frankly I would reccomend they read it. Who ever needs to read it reads it. And Anyone actually interested in it reads it. Instead of looking for the damn cliff notes version.

  • Scourge of Programmers! (unregistered)

    another work of fiction by mr know-it-all aka snoofles.

  • (cs) in reply to Pawprint
    Pawprint:
    snoofle:
    (my spies back at WTF-Inc know where I'm working; they called, and hysterically informed me that all of my code [*] had been reverted back to the way I wrote it)

    *deleted "that"

    Is that what you meant to write? In other words, they went back to your code because it was right even though no one believed you at the time?

    (And why no strike BBCode directive, dammit?)

    Did you mean like that?

  • nobody (unregistered)

    Snoofle,

    Much better! Your writing has substantially improved. B+

  • Mandalf the Manly (unregistered)

    Do they actually write this? I thought site editors re-write quite a bit before posting it...

  • Essex Kitten (unregistered)

    But they went with WTF-Inc for Obama's National Health Insurance Microsoft Exchange (that's what WTF-Inc's sales drones thought they should deliver, since it had Exchange in its name) anyway, right?

  • (cs)

    I don't get it. Is snoofle really G.R.G.?

Leave a comment on “WTF Inc Epilogue - From the Other Side”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article