Of course Jared didn’t document anything and made themselves a bus factor. Real success is when Jared makes themself replaceable because hiding detail and making yourself critical is the best way to take a site down when you’re on holiday and prevent other team members stepping in and taking ownership.

Blender or GIMP? Idk.

Unit tests, yes, but you don’t only do unit tests. Integration and e2e tests still exist.

Was there even tests?

I’m not sure what’s with your first sentence. Everything else you said agreed with the point I was making…

Garbage in, garbage out. Keep feeding it shit data, expect shit answers.

Real mugs.

Henry Ford invented breaks to extract more out of the peasant Labour.

The fact we’re years later and cognitively demanding jobs don’t support this well show how amateur managers are and his spineless devs that enable them are.

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.

It’s unfortunate they couldn’t use a Euro figure which would have made it much clearer.

Are you a recruited? JavaScript is not Java.

Really ain’t writing code in termux. I want an IDE. Why use a substandard device?

Programming? Nah. It’s a consumption device, not a creation device.

“If you would like me to be on call, we need to discuss remuneration.”

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”

That era was peak Pro Evo.

You can ignore that also…

Length of time never means quality of decisions. Always best to validate. So easy to package up malware and farm folks bank accounts.

Nah, it’s quite big and well known in open source circles.

You do you, though.

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.

Well Devops isn’t a role. It’s an approach in which bridges development and operations and integrating it in the team. It isn’t sticking a cloud engineer (cloud biased sysadmin) in the team. It’s about collaboration and delegating and supporting.

Cloud engineer is unfortunately what many orgs think devops is.