• 0 Posts
  • 17 Comments
Joined 11 months ago
cake
Cake day: January 31st, 2025

help-circle




  • And it killed all interest I had in Vite as well. This kind of thing practically guarantees that they’ll spend their effort on the for-profit stuff and gut the open source project of things it would otherwise have had built in.

    Sure, maybe not today, but eventually some bean counter is going to look at it and demand it.



  • That sounds like pretty much exactly what we did at my last job, and it worked pretty well IMO. The individual commits in a PR didn’t ever matter. I don’t even think we used them for code review, except if it came up for review a second time after rework. In that case, we were able to just look at the new commit to see if the right changes were made.

    And we definitely avoided basing off each other’s branches. We had to do it a few times. The only times it went well was when the intent was to merge the child branch into the feature branch. If they were actually separate tickets (and the second relied on the first) it was generally chaotic. But sometimes, it was just necessary.









  • I’m not sure who needs this advice. The game was designed to be played without it, so that’s good.

    People that need the feature will use it, of course. For whatever reason.

    Everyone else has a choice: Mindless running through the wilds to get where you’re going, sometimes seeing something interesting on the way… Or just letting this thing get you there, without the “follow the white line” minigame.

    The people who are going to use this were already using in-game features to do it as much as possible, but with a manual component that irked them. Asking them not to use it isn’t going to improve their game experience.

    Anyone who roams without the white line isn’t even in this discussion. They would never use this feature, so the advice doesn’t change their mind at all.