• 2 Posts
  • 72 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle


  • Thanks for explaining. I still think “planning” is a weird way to think about what’s supposed to happen during standup-- It seems to me that the whole purpose of working in sprints (and the rituals that that typically entails) is to plan ahead so that during the week you can execute on well-groomed, properly-scoped work. Of course when you notice something is wrong, or needs to be reconsidered, you might need to pull the brakes and realign mid-sprint, but my sense is that if you’re doing planning every day, that might mean that your work isn’t groomed well enough beforehand, or you’re not locking in important decisions during sprint planning.

    But it might depend on the work, and it might depend on what you mean by “planning.” If your planning just looks like “Hey are you free to pair on issue 123 this afternoon? Okay sweet, I’ll throw a meeting in your calendar,” then yeah sure-- I wouldn’t use the word “planning” for that, but it’s not crazy to. Or maybe the work is different than my work, and actually does warrant some amount of day-level of planning that wouldn’t make sense for teams I’ve been on. I’m open to that, too.

    (Btw I tried to look up this “planning planning feedback feedback cycle” thing and the only search results I got were THIS LEMMY THREAD, lol… Cool to see Lemmy show up in search results)



  • In a narrow sense, it’s useful for like… e.g. location-based search…So of you search “cosmetic dentistry,” it’s useful to privilege results closer to you (or at least you could make that argument). But broadly, in practice, “personalization” is primarily optimized for the ad buyer or first-party company’s goals (e.g. engagement, click-through) as per phases 2 and 3 of the enshittification cycle… And we know what happens to secondary goals as systems become increasingly optimized.

    So I’m not claiming that it can’t be los dos, and indeed in phase 1 it definitely is… I’m claiming that it isn’t los dos, in practice, at this moment in history.







  • What in the ChatGPT is this article? It’s like someone from LinkedinLunatics paid an aspiring content writer to write a vapid hype piece but insisted that it be about 6x too long.

    Here are some highlights (although it was hard to figure out which sections were the cringiest):

    This new studio represented more than just a business venture; it was the manifestation of Feng’s dream to create games that prioritized player experience over profit.

    The team’s dedication to authenticity was unparalleled. They immersed themselves in Chinese mythology, reading the classical novel “Journey to the West” over 100 times. They visited countless cultural sites, drawing inspiration from ancient architecture, art, and landscapes.

    The impact of Black Myth: Wukong extended far beyond sales figures. It became a cultural phenomenon, bridging the gap between Chinese mythology and global audiences. The game’s success inspired a new wave of developers to create games based on their own cultural mythologies and histories

    Feng Ji: The Humble Visionary Despite the overwhelming success and adulation, Feng Ji remained characteristically humble. When asked about the game’s achievements, he responded with a touch of philosophy: "When you are at the peak of confidence, you are also staring at the valley of foolishness. This statement encapsulated Feng’s approach to game development and success. Rather than resting on his laurels, he immediately turned his attention to the future, focusing on expansion packs and maintaining the game’s quality

    Jesus christ tone it down.



  • Same experience with my relatives. I had some family whose Macbooks were no longer able to update (for Apple forced obsolescence reasons). They run Mint now, and have never had a single problem since I first set them up.

    Well, one of them called me because they couldn’t figure out how to attach a file to an email… But that problem would have been identical on Mac OS.



  • Yeah but you get a nice ramp-up period where you’re allowed to be bewildered and unproductive. In that time, you can probably pick out two or three grandiose changes (ideally with hot new technologies) to throw on the pile before that period ends, and use them as resume padding and interview stories for the next job.

    Unlike the old developers, you aren’t complicit in the mess until a few years go by.


  • There’s a second-order thing going on though with tech debt that makes it different than just maintenance: Tech debt is when you address a problem in a way that makes future problems more difficult to address. So if the wire-and-tape fix is actually robust, easy to work around, and/or easy to reverse, then it wouldn’t be tech debt. But if it made it harder to unclog/clean the tap, or to fix the next leak, or install/remove things around it, then it would be like tech debt.



  • E x a c t l y! On Windows/Mac, you’re less inclined to be charitable, because most of the time you’re facing down artificially-imposed limitations on how you can interact with your own machine. They seem to say “You’re too dumb to be allowed to mess with that,” which is a tolerable slight if it Just Works every time… But when it doesn’t, ohhh boy…