• 0 Posts
  • 35 Comments
Joined 2 years ago
cake
Cake day: June 26th, 2024

help-circle

  • I’ve got like 10k hours in the game and I play for the combat and, for the past few years, the “joy of movement” (their words) with mounts. And the story has ups and downs but there are definitely some ups. The telling thereof has certainly gotten pretty good. (Early stuff… isn’t.) Story content peaked between the 2nd and 3rd xpac.

    But having tried to get my gf into the game relatively recently, I was frustrated that the sense of progression and story doesn’t really line up with the difficulty curve – first expansion is still the most brutal place in the world, prior to mounts, and we’re on what, the 6th now? So as a new player to play the most fun mechanical parts you’ve got to go to from the vanilla story, skip the first xpac, hit the second (most mounts) and fourth (flying mount)… making for a really disjointed experience. Which is sad because once you have all the bits (or if you played it all along) it’s fantastic. Or alternatively to play the story in order (and the way it was paced along the way) you basically play a ten year old game as it evolves in front of you, where some parts don’t hold up super well.

    Far and away my favorite MMO combat. And some of my favorite movement; definitely for the genre. But I get the frustration.



















  • svtdragon@lemmy.worldtoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    27
    arrow-down
    2
    ·
    1 year ago

    I just spent about a month using Claude 3.7 to write a new feature for a big OSS product. The change ended up being about 6k loc with about 14k of tests added to an existing codebase with an existing test framework for reference.

    For context I’m a principal-level dev with ~15 years experience.

    The key to making it work for me was treating it like a junior dev. That includes priming it (“accuracy is key here; we can’t swallow errors, we need to fail fast where anything could compromise it”) as well as making it explain itself, show architecture diagrams, and reason based on the results.

    After every change there’s always a pass of “okay but you’re violating the layered architecture here; let’s refactor that; now tell me what the difference is between these two functions, and shouldn’t we just make the one call the other instead of duplicating? This class is doing too much, we need to decompose this interface.” I also started a new session, set its context with the code it just wrote, and had it tell me about assumptions the code base was making, and what failure modes existed. That turned out to be pretty helpful too.

    In my own personal experience it was actually kinda fun. I’d say it made me about twice as productive.

    I would not have said this a month ago. Up until this project, I only had stupid experiences with AI (Gemini, GPT).