• 0 Posts
  • 397 Comments
Joined 1 year ago
cake
Cake day: August 16th, 2023

help-circle







  • No it doesn’t sound bad, words don’t need to be thrown away forever just because they’ve been used to describe unfair treatment. I’m so sick of having to relabel so many things that are so far divorced from the social issues they are used to describe. It’s so pointless and has no impact, the code doesn’t care which is master and which is the slave for they are simply descriptive labels.

    Are we supposed to never use the words master or slave ever again?? What’s next?

    My dev friends, no matter their race, all say the exact same thing. We still use master over main, come at us I guess.








  • Yeah absolutely.

    I would go a step further and point to how a lot of companies these days supplement their workforce with low skill contractors from places like India who are like 13 hours ahead, do not have any actual investment/commitment to the project/company.

    Why pay high prices for competent developers that can work alongside each other when you can have a just few competent ones and outsource the rest for those competent workers to corral, right? 🙄

    Generally this results in more work for the full time devs. When you ask for senior developers and get a team of ”seniors” that write code like juniors…. That’s just more work for the full time devs. Ask me how I know.

    Maybe I just need to stop working for Fortune 500s





  • Yes absolutely, the parameter even if not in a strongly typed language should be a specific number and the unit should be implied. Overload the method to support different units if necessary or provide a unit as an additional parameter instead of forcing the method to parse the string for any unit type hints that may or may not be there