• 0 Posts
  • 44 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle





  • letsgo@lemm.eetoAsklemmy@lemmy.mldeleted
    link
    fedilink
    arrow-up
    1
    arrow-down
    2
    ·
    23 days ago

    I disagree. That’s a consultant-style answer. OP is an idiot newb three months into his first job with zero responsibility, and not in any position to “serve notice” or have any meaningful “professional opinion”.


  • letsgo@lemm.eetoAsklemmy@lemmy.mldeleted
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    8
    ·
    23 days ago

    “This is my first IT job, I’ve only been working here 3 months”

    Then you need to learn this lesson quickly: YOU ARE NOT THE BOSS. The Boss is the Boss. Not you. You make your concerns known to him then you leave it at that.

    “I’m considering talking directly to the owners about this issue” Yeah, going over his head is really going to go down well /s. As you have proven you are hard of learning, let me state clearly: it won’t, that was sarcasm. The owners will see you’ve gone over your boss’s head and when he says “I’ve had enough of this jerk, let’s get someone else in” they’ll be hard pressed to disagree with him.

    “my boss’s refusal puts our operations at risk” Your boss already knows this. Especially as you keep banging on about it. What you’re doing here is heading for an unceremonious out-kicking. Your boss also knows a lot more about the business than you do. If he’s keeping that machine on Win7 then he probably has some good reasons to do so.

    “I want to ensure I handle this professionally” No you don’t. You want to force your boss to do what you think he should do. If you were being professional you’d state your concerns, in email if necessary, then move on.

    “I definitely feel like I’m going to be used as a scapegoat” That’s why you put your concerns in an email (ONLY to your boss, nobody else. Or maybe a sympathetic team member). This creates a paper trail so that if and when they come knocking on your door saying “Why did you let this happen! You’re fired!” you can point to that email which proves you did everything you could. (Which they won’t by the way. You’re an idiot newb three months into your first job. You don’t have any responsibility yet. So this isn’t on you.)

    “I’m also planning on seeking employment elsewhere” It doesn’t matter where you work while you have this attitude. Newsflash kiddo: you’re the asshole here. You’re a newb three months into your first job. No matter what you think you know, you don’t know anything. Instead of trying to dictate to others what you think they should do, try to learn why they’re doing it differently from what you expect. Maybe you have to find somewhere else now; that boat may have already sailed. Maybe if you approach your boss saying something like “er, sorry I was an asshole, I thought I knew more than I do, can we start over and I want to learn from you” (but obvs phrase it better than that) then MAYBE you stand a chance of getting through your first year.

    [Sympathetic mode on.]

    We all have to learn this stuff and it takes time. Your boss also knows this, and remembers when he was an overenthusiastic hothead. So while all the above might seem harsh, especially the YTA bit, hopefully it’ll cause a course correction (which is my intent here) and you’ll be back on track to a successful career in IT. This position may still be salvageable but you need to go in on Monday understanding clearly that it might not be, and that it is your fault. And maybe you need to be fired a few times before this sinks in. Good luck.





  • letsgo@lemm.eetoProgrammer Humor@lemmy.mlgot him
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    2 months ago

    That’s not a real operator. You’ve put a space in “i–” and removed the space in “-- >”. The statement is “while i-- is greater than zero”. Inventing an unnecessary “goes to” operator just confuses beginners and adds something else to think about while debugging.

    And yes I have seen beginners try to use <-- and --<. Just stop it.



  • I’m UK too. As I see it your options are one or more of:

    1. ignore the incident without comment and don’t give him the satisfaction of upsetting you;

    2. block him so he can’t do it again. If he needs your number for other reasons then he gave up that right when he sent you that disgusting stuff; now he needs other routes, which you can block as needed;

    3. raise the issue with your team leader or manager advising that you just want it to stop, you don’t want disciplinary action taken against him, but if he’s a repeat offender then the company might take it further anyway (which would be appropriate and correct);

    4. DO NOT go to HR. They are not your friend or ally. They are there to protect the company and it’s just as likely you’ll be terminated as him. HR is a last resort, if you can’t get any satisfaction from management, and you keep suffering this kind of abuse (because that’s what it is; I’m not exaggerating), only then go to HR and even then only after notifying everyone concerned - the bully/bullies and your manager - that’s what you’re going to do.

    If this cockwomble gets fired because of sending that video to you, you have nothing to be ashamed of. It’s his own stupidity that got him there, not you “grassing him up” or whatever other cockney nonsense you might have knocking around inside your noggin. You don’t owe that wanknugget anything, especially after he sent you stuff you explicitly said you didn’t want to see.




  • letsgo@lemm.eetoProgrammer Humor@programming.devRebase Supremacy
    link
    fedilink
    arrow-up
    21
    arrow-down
    3
    ·
    3 months ago

    Merge gives an accurate view of the history but tends to be “cluttered” with multiple lines and merge commits. Rebase cleans that up and gives you a simple A->B->C view.

    Personally I prefer merge because when I’m tracking down a bug and narrow it down to a specific commit, I get to see what change was made in what context. With rebase commits that change is in there, but it’s out of context and cluttered up with zillions of other changes from the inherent merges and squashes that are included in that commit, making it harder to see what was changed and why. The same cluttered history is still in there but it’s included in the commits instead of existing separately outside the commits.

    I honestly can’t see the point of a rebased A->B->C history because (a) it’s inaccurate and (b) it makes debugging harder. Maybe I’m missing some major benefit? I’m willing to learn.




  • Lexus GS300. Great car to drive. But every fucking thing that went wrong was at least £400. Door check strap? £400. Windscreen wiper? £400. Parking sensor? £400, and all eight of them need doing, and that’s £400 PER FUCKING SENSOR. Everything’s main dealer only. Merc was no better. £600 for a fucking HOSEPIPE. Also tried BMW (bike). Same problem. Had a CANBUS system. I started calling it a CAN’T BUS cos every tiny thing that went wrong shut the entire bike down. Duff indicator? Sorry, won’t start the engine until it’s fixed. Yes that means it’s got to be trailered to the dealer.

    No more fancy marques for me, they can all fuck off until I’m a billionaire. I drive Volvos now.

    I’m still not quite over it. Whenever the garage tells me there’s going to be a big bill on my Volvo I think OMG how many digits, but then they say something like £150. That’s a big bill? Hahahahahahahahaha.