603
S&Box went open-source and the comments are very calm (programming.dev)
submitted 11 months ago by to c/programmer_humor@programming.dev
51 comments fedilink hide all child comments
 

More fun ones: https://github.com/search?q=repo%3AFacepunch%2Fsbox-public+fuck&type=code

you are viewing a single comment's thread
view the rest of the comments
[–] 24 points 11 months ago (3 children)

I don't see anything unprofessional there. Just naughty words. But, the naughty words are somewhere where they warn you that the code below doesn't behave as expected, or complain because there isn't a better way to do something. That seems like the best time to use strong language.

Cleaning it up is a great idea in theory, but in practice almost everybody has higher priority things to be doing. Leaving a comment in the code for why something is ugly is the best thing you can do when you don't clean something up, so that someone coming along after you doesn't struggle with it. We have no idea how many "naughty" comments are no longer there because the issues they addressed were cleaned up.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 0 points 11 months ago (2 children)

    If you were to talk like this in any job I've ever worked at, you'd be fired in about a week, maybe faster.

    Same with writing emails with this language.

    And you're missing my point that if you made your own functions... and they don't work right, ... you should fix those functions, rework them.

    Not doing that is how you get technical debt, spaghetti code, which is bad for you, bad for what you're trying to do, bad for anyone else trying to help you do it.

    Commenting on a bunch of slapdash fixes is like covering holes you punched in your wall with framed graffitti about how frustrated you are.

    If you saw that in a date's home, you'd hopefully recognizr that as a red flag and nope the hell out.

    If everybody else is too busy to actually fix the code, you have inept project management.

    You as well have clearly never worked in an actual professional software dev environment, if you think this is reasonable or defensible.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 11 months ago (1 child)

    Absolutely correct.

    I always tell our new developers: If your new feature works, you aren't done, you have to check if your code has to be refined first, before checking it in. (e.g. duplicated passages made into a common function, ugly hacks removed and "done properly", stuff like this) Documentation and testing are also mandatory, but that's because of the industry we work in.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 11 months ago

    Yep.

    You can avoid having to do something like a total refactor that takes half the year, if you do the rough equivalent of a sanity check / clean up pass, when any new system or feature set is added, and make that habitual.

    Its... kinda like how if you just do a bit of regular shopping, regular meal prep, regularly do the dishes, whatever, everything just flows easier in general.

    The longer you run lean, move fast and break things.... yeah it can improve output in the short term, but medium to long term, you'll run yourself ragged, and things will break and fall apart.

  • permalink
  • fedilink
  • source
  • parent