someoneelse @ someoneelse @lemmy.ml

Posts

0

Comments

4

Joined

2 yr. ago

Wikipedia has the much longer list. https://en.wikipedia.org/wiki/Suspicious_Russia-related_deaths_since_2022

Madrid?

Going against the current for a couple of things, I guess, but there are two points there that I actually like, but probably not in the way they are usually implemented.

• 4 hours planning is bad if it's 4 hours sprint plannig. Then somebody should be sacrificed for the greater good, but for the love of god, can somebody take their time to plan features and architecture carefully before dumping stories for development? Smaller group and whole long term system overview. Let them spend 4 hours to make something coherent and elimitate tech-debt creation.
• 1 point = 1 hour is fine if you don't think that it's set in stone, but it allows for very easy sprint planning. If your ballpark estimate for the sprint is more than 20 hours/developer for the week, you are overplanning. Normalize creating tasks for thinking how to solve a fucking problem instead of saying it's complex.

She might not even have known that there is a different way of doing it. The guild had to tell her that she was owed money and benefits. That's different from taking somebody else's place. There is probably no entry process for newcomers to lean about better way, since it is not a company but a nebulous industry with thousands of independent actors in the game. That's why the guild is necessary, it's impossible to expect each new excited, clueless person with an idea to know and bargain for that on their own.

The problem will persist as long as the exploiters can do it. You will never get every person to individually negotiate the right way.

Game developers should also unionize at industry level. That way new developers would be protected right away and could not be exploited before they realize it. No need to dissuade them, although there probably will not be that many openings that often anymore.