• 0 Posts
  • 16 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.




  • I feel like you’re missing out on a ton of awesome features by not using a debugger? Step backs are super useful, inline/live commands save you from re-running the code to see a different value, you can change values on the fly.

    And it’s nice to say “think about your code more” but when you’re working with large teams, on legacy codebases, you don’t often have the opportunity to “think about your code” because you’re trying to decipher what someone wrote 3 years ago and they don’t even work with the company anymore.



  • 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.