• 3 Posts
  • 222 Comments
Joined 3 years ago
cake
Cake day: June 1st, 2023

help-circle


  • We get encouraged to try out AI tools for various purposes to see where we can find value out of them, if any. There are some use-cases where the tech makes sense when wielded correctly, and in those cases I make use of it. In other cases, I don’t.

    So far, I suspect we may be striking a decent balance. I have however noticed a concern trend of people copy-pasting unfiltered slop as a response to various scenarios, which is obviously not helpful.










  • GissaMittJobb@lemmy.mltoSelfhosted@lemmy.worldAWS is having a bad day
    link
    fedilink
    English
    arrow-up
    59
    arrow-down
    2
    ·
    6 months ago

    It’s mostly a skill issue for services that go down when USE-1 has issues in AWS - if you actually know your shit, then you don’t get these kinds of issues.

    Case in point: Netflix runs on AWS and experienced no issues during this thing.

    And yes, it’s scary that so many high-profile companies are this bad at the thing they spend all day doing


  • You prepare for these by doing specific exercises for them, sad as it may seem.

    Leetcoding problems? You grind them out for a month or two to prepare for doing them during interview loops.

    Mock interviews can help too, to get you better at handling the stress. You can use services/groups for these, or just go interview for random places you’re not necessarily planning to actually say yes to.



  • Well, you might be inclined to not roll the feature out at all, depending on the results you see from the rollout/an A/B-test. Also, having it written out with a date in the changelog binds you to that date, unless you want the embarrassment of not shipping on a promised time. Maintaining a changelog for very large app development organizations is also a pretty damn hard task, trying to coordinate whatever all teams are releasing in a particular build.

    I agree that getting cute with the changelog messages is a bit stale. Might as well not add anything at that point.





  • Your phone is trying to keep your battery alive. The lower the specs of the phone, then the more aggressive the OS is.

    No, apps closing between switches is not a matter of battery, it’s a core feature of Android related to the management of RAM. Whenever the OS needs more available RAM, the OS will close a backgrounded app to make those resources available. This is why it happens more frequently on low-end devices - these generally ship with less RAM.

    Some misguided vendors will limit background execution in incorrect ways in the name of saving battery, but the general thing with apps living in background is a story of RAM.

    Interestingly enough, apps are supposed to be built to cope with being closed down due to lack of RAM and then be restored seamlessly, but this is an art that is uncommonly done correctly in the Android development space. The OS support is there, though.