PC Gamer: The top 100 PC games
  • "Initials" by "Florian Körner", licensed under "CC0 1.0". / Remix of the original. - Created with dicebear.comInitialsFlorian Körnerhttps://github.com/dicebear/dicebearDW
    dwemthy
    3d ago 100%

    The pace drove me a bit mad. So much stuff front loaded with all kinds of things in play, then you reach a point where they want you to wait X in game days for a crucial item so it grinds to a halt

    3
  • The downside of larger groups
  • "Initials" by "Florian Körner", licensed under "CC0 1.0". / Remix of the original. - Created with dicebear.comInitialsFlorian Körnerhttps://github.com/dicebear/dicebearDW
    dwemthy
    1w ago 100%

    Your group of five was falling for 30 minutes because they couldn't get through initiative

    My group of five was falling for 30 minutes because they kept trying to rush up a greased ladder

    39
  • technology
    Technology 2w ago
    NSFW
    Jump
    Hacked ‘AI Girlfriend’ Data Shows Prompts Describing Child Sexual Abuse
  • "Initials" by "Florian Körner", licensed under "CC0 1.0". / Remix of the original. - Created with dicebear.comInitialsFlorian Körnerhttps://github.com/dicebear/dicebearDW
    dwemthy
    2w ago 75%

    You can make a free account, some of the articles just require a free account and others require a paid subscription. I can read this one with my free account

    2
  • Why do phone apps update all the time but nothing seems to change?
  • "Initials" by "Florian Körner", licensed under "CC0 1.0". / Remix of the original. - Created with dicebear.comInitialsFlorian Körnerhttps://github.com/dicebear/dicebearDW
    dwemthy
    2w ago 100%

    Having a regular schedule of updates helps get individual big fixes or features out faster. You may not notice a difference because you may not experience the bugs that are being fixed. There may be slight changes to features that you don't use enough to notice. There could even be features that are disabled until they're remotely enabled. Mobile apps often run A/B tests for changes to see how those changes affect user behavior, so you might be in the "no change" test cohort when you don't see changes, those changes may never activate on your installation if the test doesn't pan out.

    I recently convinced my team to adopt this practice so I've been brushing up on it. When done right it can mean a more stable app and quicker response to issues since it relies heavily on monitoring app performance, bug reports, and user reviews. Communication to users is hard since you don't want to have every update be "fixed bugs" but it's also unnecessary to say "fixed an issue where a batch upload job didn't handle individual errors by retrying" for each change that may not actually impact you as a user but which impacts the business that builds the app.

    3
  • Alt text: a bun in a grassy yard

    55
    2