space_comrade [he/him] @ space_comrade @hexbear.net

Posts

0

Comments

151

Joined

5 yr. ago

From wikipedia:

Racism is discrimination and prejudice towards people based on their race or ethnicity.

Did you know Irish people were considered "not white" at some point in history?

Banksy is a complete fucking poser, true, but also shoplifting is good.

"We will forcefully integrate you into our culture by excluding you from our culture"

Genius, what could possibly go wrong.

Racism isn't exclusively about skin color you dolt.

Do they ban catholic children wearing crosses around their necks?

You're not the target audience, the target audience is edgy teenage boys. Postal 2 was the perfect game for 13 year old me.

You're right labeling them as "legendary" is just weird tho.

Death to the concept of intellectual property and all but I've never actually felt Denuvo making problems for me when I played a game using it, you're right it seems to be working as advertised.

I'm still hoping someone to crack it in a more reliable and fast manner, fuck large gamedev companies and their profit margins.

Most types force premature design/optimization.

I disagree. What you're saying is true for Java-like OOP languages because OOP is actually complete garbage if you want to design good, easy to understand abstractions. Types are way more elegant in functional or functional-inspired languages.

Most unit tests lock up some specific implementation (increasing cost of inevitable refactors) rather than prevent actual bugs.

Agreed, unit tests are useless in most cases, they mostly test the bullshit abstractions you built for the unit tests themselves.

Go sacrifices too much for superficial simplicity; but I would like to see a language that's nearly as easy to learn, but has a better type system and fewer footguns.

"Easy to learn" and "good type system" will by necessity be opposing forces IMO. If you want to work with a good type system you're gonna have to put in the effort to learn it, I'm not sure there's this magical formulation of a good type system that's also intuitive for most new developers. Hope to be proven wrong one day tho but so far no dice.

Counterpoint: using anything other than 'i' as your index in a for loop in C or C++ is obnoxious as fuck.

At most I'll go with 'it' for C++ iterators.

Skipping classes as a "gifted" kid always seemed like a very weird concept to me, you're making the child lose a lot of interaction with their peers for dubious reasons. It seems to me like it should only be reserved for the most bulging hyperwrinkled brains, like those kids that finish college by the time they're 16 or whatever that would obviously be extremely understimulated when going the normal pace. Even then you could argue the gigabrain kid would probably benefit greatly from socializing with their peers, I mean where's the rush really? They're young, they can always learn more later.

I'm reminded that forced sterilisation of minorities in the US is a known fact.

Don't forget Canada!

I worked in a large company where they used scrum and I just don't see where it ever helped me. Sure I guess forcing you to write down in Jira or whatever all the features/bugs you worked and will work on is good practice but I can do that without scrum too.

Daily standups were annoying and rarely ever helped people resolve issues that wouldn't have been resolved by just talking to some people directly, which you would have done anyway regardless of the standup meeting.

Sprint plannings were useless and amounted to either taking 3-4 things off the top of the backlog or the manager forcing their priority feature in the sprint.

Story point estimation was awful, everybody pretends the points aren't just measures of time but rather this complex abstract of multiple factors and whatnot but everybody still just converts them to time in their head anyway because of fucking course they do because the time estimate is the most important thing to know and the only truly objective measure of task difficulty.

In the end management gets what it wanted when it wanted no matter our complaints because that's how things work in privately owned companies. Scrum for the manager at worst just becomes another bureaucratic hoop they need to jump through to get what they want.

This is also the experience of my colleagues from other companies, and also I read a lot of similar anecdotes online. I have literally never heard anybody seriously claim scrum works great in their company that also wasn't personally invested in the ideology like a "professional" scrum master or consultant or whatever.

What's the difference between that and just receiving orders from managers, like every other office worker in any company ever?

I don't read such books because they're almost always written by "consultant" grifters trying to make money off of proselytizing the latest bullshit corporate fad. And it's almost never based on actual data or a coherent theory, just gut feelings and a few anecdotes. My own felt experience and that of my colleagues is enough to confirm that it's all just corporate ideology bullshit.

They are empowered to work autonomously, which is a big difference.

That means nothing to me. Just platitudes. I've never felt "empowered to work autonomously" in scrum.

I don't think you can truly change anything with these methodologies. At the end of the day most companies are still privately owned companies, and you as a developer will do what the owners and/or the managers tell you to do. The owners aren't going to delegate important decisions to developers unless it's a really technical thing. The part where "developers take control" in scrum is bullshit and always will be by necessity of how our economic system works.

I feel like Scrum and similar stuff just serves to obfuscate real material relations in the company that aren't going to change no matter how many story points you assign to this or that or how many scrum masters you have. Also it makes micromanagement easier I guess.

It’s just difficult to start using it when the corporate culture isn’t able to adapt and change it’s structures, that’s the hard part.

Yeah but that's almost every company ever. At what point do you blame the methodology then if it doesn't work properly almost anywhere?

I feel like scrum and agile in general are almost religions at this point, just blind belief in a system you haven't really seen work properly ever but you still believe in it.

Death to all golf courses. Except minigolf, that's fun.