• 5 Posts
  • 244 Comments
Joined 1 year ago
cake
Cake day: July 10th, 2023

help-circle








  • The issue is your mindset.

    You write bugs because you have something to learn. You’re so focussed on what you’re making, that when a learning opportunity arises, you are not open to it. You’re just looking to speedrun/hack it.

    You need to drop the delivery pressure and enjoy the journey. When a bug comes up, celebrate it “ah, you got me here. Interesting. What am I missing?”. Then you slow down, focus not on solving it, but understanding it. If you understand it, the solving is easy.

    If you consider learning “not progressing”, then you need to reflect on what benefit the pressure and delivery focus is.




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