• (disco)

    Frist

  • (disco) in reply to Placeholder

    Bonus frist

  • (disco)

    How could somebody who knows what he's doing not know they have backups?

    The answer, obvious to anyone who has spent more than two minutes reading TDWTF, is that [spoiler]he didn't know what he was doing[/spoiler].

  • (disco) in reply to HardwareGeek
    HardwareGeek:
    not know they have backups?
    maybe it's not that they had backups, it's that they didn't have backups that he knew about?
  • (disco)

    Ah, finally a happy ending to a story with a mistaken over delete!

  • (disco) in reply to boomzilla
    boomzilla:
    a happy ending to a story with a mistaken over-delete
    IKR? It's like someone was patting my back in a consoling manner.

    Now, if only I can recreate the ending in my department. We have almost all of the elements, with a few name changes of course, and nobody but ?#!!8& would attempt to DELETE in prod :flushed:, the only issue is that I'm not exactly planning on leaving for a while...

  • (disco)

    Elaine was lucky that Lloyd was not in superior position when the incident happened.

    I had been assigned task to cleanup the mess that someone in senior position deployed incompatible code (he mistakenly treat a table with one-to-many relationship as one-to-one relationship, and modified about a thousand records the code should not be touching on day-end task.

    Worse, the change is not allowed to be rolled back as it'll break other code that has be deployed, and I have to finish the data patching AND the code fixing before the business hour of next morning.

    And how about the senior who causes all the mess? He claims he was busy working on the other project so do not have time to fix that and leave that afternoon at 6pm as usual.

    So to Llyod's credit, at least he tried to clean up his mess himself.

  • (disco) in reply to cheong
    cheong:
    I had been assigned task to cleanup the mess that someone in senior position deployed incompatible code

    Meh. That's one of the things juniors do sometimes.

    cheong:
    before the business hour of next morning

    Explain your working hours to your boss. Ask for time in lieu. If you have family commitments, honour them. What I'm really saying is don't put up with shit. Do an all-nighter if you like, if it's worth it to you and you have nothing else to do, otherwise tell them to get stuffed.

  • (disco) in reply to another_sam

    The complicated part is that, this is not in-house application but a retail product. The deadline for "fix" is not decided by the boss, but the customer.

    It's fortunate (?) that the part of logic that has problem exist on some part only be used by that customer (that's presumably part of reason why the senior have bug on that part).

    Someone has to work on it, and when you're junior, you don't have choice on what you can do. Complain with the boss won't work as the "senior" is a friend of the boss and there aren't any level higher. That's why he have that kind of privilege.

  • (disco) in reply to cheong
    cheong:
    when you're junior, you don't have choice on what you can do

    You always have choices.

    After explaining, just go home at the end of the day and see what happens tomorrow - that's a choice. I'd probably go with that because your management might begin to understand that just because they say something doesn't make that reality. By doing that you're making it clear you won't put up with shit and demanding some respect, whereas if you do put up with shit they will expect you to continue to do so and will never give you any respect.

    You can straight-up quit, that's a choice you can make. Depending on how easily you'll find your next job and how your bank account looks and how unemployment benefits work where you are, it might not be the best choice, but it's appropriate a lot of the time.

    You could go postal. Bring an automatic weapon to work tomorrow. Not recommended, always ends poorly for everyone involved.

    You can stay back and do sub-standard work. Leave bugs in what you're working on. It may reflect poorly on you, and the "You made me stay all night and I'm tired FUCK YOU!" excuse might not help. If you do an all-nighter this is probably what you're implicitly doing anyway whether you and your boss realise it or not.

    You can stay back and just sleep under your desk, also probably not a great choice.

    Many options are available to you and many choices can be made.

  • (disco) in reply to cheong
    cheong:
    Elaine was lucky that Lloyd was not in superior position when the incident happened.

    :giggity:

  • (disco) in reply to another_sam

    If that happens again to me now, I may just go away as you said. But that's around 2003, when I was just going out from school and having less than a year working experience (strangely for most HR policy, parttime job done on school, even if it's actual delivered product, not ordinary intern-done one, don't count towards working experience). Finding job was difficult.

    And I don't have university degree, with almost 2/3 of other jobs requiring degree, my choice was pretty limited.

  • (disco) in reply to dkf
    dkf:
    cheong:
    Elaine was lucky that Lloyd was not in superior positionhigher rank when the incident happened.

    :giggity:

    Okay. I see what I did here.
  • (disco)

    It feels like something is missing here, why is Lloyd a Senior Developer, able to work under the radar from Mr. Thomassulo, who is the head of IT and therefore, presumably, his boss? I mean, I get the whole Know-it-all senior developer circumvents his teammates story, and I've had to deal with someone like that, but circumventing his supervisor and having the supervisor not do anything about it? The story even says that Lloyd would ignore management, how the heck does that fly?

    Why did Mr. Thomassulo allow Lloyd to get away with that behavior, if he was a good boss as the story makes him out to be?

  • (disco) in reply to HardwareGeek
    HardwareGeek:
    How could somebody who knows what he's doing not know they have backups?

    He knows what he's doing, so he never made any.

  • (disco) in reply to another_sam
    another_sam:
    You could go postal. Bring an automatic weapon to work tomorrow. Not recommended, always ends poorly for everyone involved.

    https://www.youtube.com/watch?v=39xp6SdJLMw&index=17&list=PL565C42B8343143BD

  • (disco) in reply to another_sam
    another_sam:
    You could go postal.

    I knew a guy who did that IRL.

    another_sam:
    ends poorly for everyone involved.
    Yeah.
  • (disco) in reply to cheong
    cheong:
    And I don't have university degree, with almost 2/3 of other jobs requiring degree

    I don't know about your country, but in the US, 12 years or so of experience means they don't care if you don't have a degree.

  • (disco) in reply to FrostCat
    FrostCat:
    I don't know about your country, but in the US, 12 years or so of experience means they don't care if you don't have a degree.

    And if they do care, you don't want to work there as that's a sure sign of a :wtf: factory.

  • (disco) in reply to antiquarian
    antiquarian:
    And if they do care, you don't want to work there as that's a sure sign of a :wtf: factory.

    Yeah. Now you could posit some kind of specialized situation where a job has certain unusual requirements, but generally speaking, no, if you managed to survive a decade, you've got the experience necessary.

  • (disco) in reply to FrostCat

    I'm not saying I have problem finding a job now. In fact, it's rare these day not to receive a email from job agents regarding they have an opening that they think it suits me, and asking whether I'm interest in.

    But I was talking about when I were a fresh grad. When you have below 2 years of experience AND no university degree, your choice is going to be limited.

  • (disco) in reply to cheong
    cheong:
    When you have below 2 years of experience AND no university degree, your choice is going to be limited.

    Yes, that's true. Sometimes you tend to talk about things that happened in the past tense, though, so I wasn't sure whether you were talking about then or now.

    If you're lucky, you might get a local company looking for a student for some summer work, who calls the university. That's how I got into professional development.

  • (disco) in reply to FrostCat

    And I'll say that if you have any two of the following: more than 5 years of programming experience, have survived over 3 companies with programming related job, or have worked as programmer in any company more than 2 years, I'd expect you have some level of competence in the programming jobs.

    It's kind of difficult for people with this kind of experience not to realize what the :wtf:-ty things they code in their earlier days, and than think about how to improve that.

  • (disco) in reply to DocMonster
    DocMonster:
    It feels like something is missing here, why is Lloyd a Senior Developer, able to work under the radar from Mr. Thomassulo, who is the head of IT and therefore, presumably, his boss?
    I assumed protection from a higher level. Perhaps he's the CEO's golfing buddy, or he's just such a fixture that senior management regard him as indispensable.
    Filed under: Or the president's daughter
  • (disco) in reply to another_sam
    another_sam:
    demanding some respect

    I have learned very recently that if you need to demand respect, it's an indicator you DON'T have it. The situation QED's itself.

    Unfortunately, no number of great co-workers could make up for having to work with Lloyd. Lloyd was another senior developer, and Lloyd was a problem. Lloyd wasn’t just a senior developer, he had once been the IT director of a major hospital system. This was a fact he liked to repeat, ad nauseum: “I know what I’m doing,” he would say. “I used to run IT for six hospitals. I supported thousands of users, and it was life or death. I know what I’m doing.”

    When my wife was in labor, preparing to deliver our first child, we had a nurse come in to give her a shot - on the left hand. My wife was looking at what she was doing with a skeptical eye, since she seemed to be having trouble finding a vein, and commented on how to do so. Instead of listening to her, the nurse asserted: "I've been doing this for 18 year, I KNOW what I'm doing!" and promptly jabbed her. My wife screamed. The nurse left. I told the person in charge later to never allow that nurse near my wife again or else...as my wife worked for the insurance company that paid the bill.

  • (disco) in reply to cheong
    cheong:
    have survived over 3 companies with programming related job

    This depends on the duration. If you have 3 jobs each less than 3 months, it looks worse than one job where you've been at least half a year.

  • (disco) in reply to obeselymorbid

    There's a reason I say any two of the three... :stuck_out_tongue:

    Three jobs in five years so at least one of them will have more than 2 years, and with more than 3 companies, you're very likely to be exposed to aspects of modern code management like source control, staged deployments, code reviews, etc. Even if you're not fulltime coders (say, a programmer that also need to do MIS stuffs) your competency is likely to get improved.

    The 2 year requirement is for fulltime programming jobs.

    If you have 5 years of experiences with 2+ years of them in fulltime programming role but never think about how to improve... well I know such people DO appear a lot in articles of this site, but in reality they're minority, or at least I hope so. :giggity:

  • (disco) in reply to cheong

    My bad, I missed the "two of the following" qualifier.

    Let me see, 3 discohours ago, must have been before my second cup of coffee - you can't expect me to read properly before I'm fully caffeinated, can you?

  • (disco) in reply to obeselymorbid
    obeselymorbid:
    you

    We apparently can't prevent you from attempting to reply before fully caffeinated either....

  • (disco) in reply to Tsaukpaetra

    I will never get the fucking spoon if I think before posting.

  • (disco) in reply to obeselymorbid
    obeselymorbid:
    get the fucking spoon
    :giggity: not sure if we needed to know about your incontinence...........
  • (disco) in reply to Tsaukpaetra

    I'm sorry to ruin a joke, but I'll have to ask you to explain that one.

  • (disco) in reply to obeselymorbid
    obeselymorbid:
    explain that one.

    Fucking spoon: a eating implement repurposed for sexual usage, the result of using which may result in incontinence. Not sure if I want to ask :giggity: Engine for more after that... :mask:


    Filed under: I'm getting sick of this keyboard and Chrome...

  • (disco) in reply to Tsaukpaetra
    Tsaukpaetra:
    Not sure if I want to ask :giggity: Engine for more after that.

    I'm pretty sure it's malfunctioning.

  • (disco) in reply to HardwareGeek
    HardwareGeek:
    it's malfunctioning.
    :giggity: Engine chains this to twitching at 64% :giggity:.....
  • (disco) in reply to Tsaukpaetra
    Tsaukpaetra:
    the result of using which may result in incontinence.

    Oh, sounds like you have more experience in this stuff than me.

  • (disco) in reply to obeselymorbid
    obeselymorbid:
    sounds like you

    Not exactly sure how you derive it is my experience that is speaking. :giggity: Engine doesn't learn from what I do or say, after all!


    Filed under: If it did, it would be hella quieter...

Leave a comment on “Bonus WTF: Karmic Cascade”

Log In or post as a guest

Replying to comment #:

« Return to Article