• 0 Posts
  • 8 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle


  • What? Tech companies the world over have people on 24/7 on-call rotas, and it’s usually voluntary.

    Depending on the company, you might typically do 1 week in 4 on-call, get a nice little retainer bonus for having to have not much of a social life for 1 week in 4, and then get an additional payment for each call you take, plus time worked at x1.5 or x2 the usual rate, plus time off in lieu during the normal workday if the call out takes a long time. If you do on-call for tech and the conditions are worse than this, then your company’s on-call policies suck.

    I used to do it regularly. Over the years, it paid for the deposit on my first house, plus some nice trips abroad. I enjoyed it - I get a buzz out of being in the middle of a crisis and fixing it. But eventually my family got bored of it, and I got more senior jobs where it wasn’t considered a good use of my energies.

    Your internet connection, the websites and apps you use, your utilities - they don’t fix themselves when they break at 0300.

    If TSMC’s approach to on-call is bad, then yeah, screw that. I don’t see anything in the article that says that one way or the other. But doing an on-call rota at all is a perfectly normal thing to do in tech.



  • At least for me, there is a big difference between naming things at home and naming things for work.

    Work “pet” machines get systematic names based on function, location, ownership and/or serial/asset numbers. There aren’t very many of them these days. If they are “cattle” then they get random names, and their build is ephemeral. If they go wrong or need an upgrade, they get rebuilt and their replacement build gets a new random name. Whether they are pets or cattle, the hostnames are secondary to tags and other metadata, and in most cases the tags are used to identify the machines in the first instance, because tags are far more flexible and descriptive than a hostname.

    At home, where the number of machines is limited, I know all of them like the back of my hand, and it’s mostly just me touching them, whimsical names are where it’s at.


  • marmarama@lemmy.worldtoSelfhosted@lemmy.worldWhat is your machine naming scheme?
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    2
    ·
    edit-2
    1 year ago

    Ungulates. Because who doesn’t like a hoofed animal?

    My client machines are even-toed ungulates (order Artiodactyla) and my servers/IoT machines are odd-toed (order Perissodactyla). I’m typing this on Gazelle. My router is called Quagga, both after the extinct zebra subspecies and the routing protocol software (I don’t use it any more but hey, it’s a router).

    Biological taxonomy is a great source of a huge number of systematic (and colloquial) names.


  • I wouldn’t say the Pixel line’s hardware is rubbish, more that Google is focused on having a polished “it just works” experience rather than trying to differentiate themselves by having the fastest, biggest, newest hardware in the Android market.

    The mobile market hit the “diminishing returns” point quite a while ago and for a lot of people - probably the majority - the only reasons to upgrade are security updates ending, or because a non-replaceable battery is getting to the end of its life.

    I used to upgrade every 12-18 months religiously, but now my Pixel 5 is coming up on 3 years old and I’d happily keep it another few years with a battery replacement, if the updates weren’t going to end shortly.


  • Bit of a nitpick, but the comparison with the reversing of the MS Office formats is a bit tenuous, and somewhat revisionist.

    Competitors and open-source applications were reverse-engineering the Office file formats long before Apple iWork was a thing, and arguably no-one really gets it right because in order to get it perfect you’d have to reproduce the Office application layouting engine exactly, bug-for-bug. Even Microsoft doesn’t get it 100% from release to release.