• 1 Post
  • 56 Comments
Joined 1 year ago
cake
Cake day: July 10th, 2023

help-circle





  • In agile development. You do a little, release. Otherwise it is too big and may never be done. The fact they committed resources to improve this is a positive. The hope is they build on it and add more options.

    However, if they get trashed for trying, they and many other companies may not try. Why spend money to get a bad reputation when the spending nothing creates less I’ll will to the company. That is ultimately the decision Product Owners and Designers will weigh up.

    I think for progress, the best approach is maybe “positive first step but more options are needed for non-bonary for this to really make players feel comfortable”.

    From a technical perspective, separating pronoun hard coding from the models gives more scope to give more options in the future, however, as someone mentioned, there is a lot of art work needed on assets and animations so the new shapes function the same in all cases.



  • “When I work I like to do my job and then relax.”

    They like to do it the other way around. They do nothing, then something. You do something then nothing. Why do you feel that your way has to b the right way and everyone else is wrong?

    Do your workload, and no more, and be fine with it, or move to another organisation with the same problem.

    The goal is for you to be able to understand that people in this world are different to you and that is fine. As long as you aren’t doing their job for them, it’s all good. If you choose to do that, it is on you.



  • If you cannot ignore slack in the evening, weekends, you gotta be bad at your job. If you are good, employer won’t want to replace you and you can condition them to respect boundaries.

    “I sent you a message, why didn’t you respond?”

    “I didn’t see it.”

    “What were you doing?”

    “Cooking. Food shopping. You know, the essentials to survive”

    Not that I’d elaborate. I much prefer the “I had plans/a prior engagement”.

    If they ask, “I cannot really discuss this, it’s private”








  • Yes, and you do it at the point you need to work on that feature. The business pay for it when they want the change.

    You do not pay for the refactor with your time, if the company won’t pay to fix their code. Just make it clear the risks and how bad it could be if you carry on with duct tape fixes.

    You have to be strong and firm and not agree to hacks. You need to work with your team to ensure you’re on the same page rather than getting undermined by cowboy dev claiming he can do the feature in 2 days when it needs 2 weeks to do the necessary work.