• 2 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2023

help-circle







  • That’s just how federation works. You’ve federated with an instance/user so now your self hosted instance will be updated.

    Is there a reason you’re concerned about the requests? The payloads should be relatively small, and unless you’re running on some really old hardware, one request a second with a small payload should not have any noticeable impact.



  • I try not to just reverse decisions I end up not liking, but I’ll tell you what I’m a goddamn adult with minimal game time and I’ll be damned if I’m going to restart because I accidentally clicked on the wrong thing or decided to pick a very stupid fight.

    It’s going to take me forever to get through the game as is, I don’t need to add all that extra overhead.






  • Its wild to me that some people hear “your code should be self documenting” and take that to mean “never write comments”.

    All self documenting should mean is I can look at a method and get a general understanding of what it does, and it shouldn’t have any unknown functionality. Specific implementations, design quirks, choices that might only make sense if you know business context should all be comments in your code.

    On the other side of all that I worked with someone who insisted methods were documented college style, the “authors” name, date it was written, what it does, why it’s here, our star sign. I hate that just as much, so much clutter.




  • My problem with trunk based development is I feel like people treat it as the solution to a problem that is fundamentally a developer culture problem.

    You need to commit small changes, frequently, which requires you to only change small sections of the code and make incremental changes, something which can be a difficult habit to get used to.

    This is really the main benefit of trunk based development, and it’s something you can get with feature branches as well, you just have to make sure everyone on your team starts reducing scope of their features and merging in smaller and smaller features sets.

    There’s nothing inherit in the trunk based development model that stops someone from sitting on changes for a month, never pulling, and then trying to pull and ending up with a bunch of conflicts anyways. So it really feels like “yeah use trunk based development” boils down to “integrate continuously” which can be done with a branching model.