carlisle_

This is a strange post to me. You can immediately see that you value soulslike as a superior genre, yet to me I see those games are just as grindy. Die to a boss a million times to learn the timings -> finally you beat it. Not that much different than ARPGs where you kill lots of stuff and die infrequently. It's just two sides of the same coin.

Really these posts that call one kind of game time wasting or drug-like but not another just miss the brutal irony.

It’s amusing you picked this as an example because the EFT subreddit is notoriously moderated. This one works because it has overwhelming evidence. The author of this post only has a few screenshots and assurances. I imagine these players would have the same experience as the author otherwise.

>I don’t think they’re aware of the disservice they’re doing to their community by actively suppressing these reports (or conspiratorially, they’re influenced by Activision itself).

I think you underestimate the deluge of posts that are made by cheaters pleading their case in a public forum. It's so common that it's basically a meme. I don't blame the moderation policies that prohibit these posts. These posts are typically provocative and often try to riles users up against the developer. Nobody wants to read these posts, you can never be sure they're real and there's nothing a regular user can do except upvote it and subsequently ignore it. There's no good conversation or comments to be found, it's all bad stuff.

This is not to say the issue at hand isn't a very real problem. Anecdotally it feels like these kinds of situations are increasing with frequency as developers tire of the inevitable losing fight against cheating and are desperate to show their customers they're taking the problem seriously.

Unless you work in finance.

The use of the term was supposed to be illustrative and mostly facetious, hence the quotes.

I’m really grateful we don’t work together.

There are plenty of comments that do a much better job explaining why a context switch isn’t just 30 seconds in this example.

Besides if all I’m doing is taking 30 second to copy and paste something what value is that really adding? If nobody says anything the docs stay incorrect. But when I want to fix an error I need to context switch and open a ticket and copy and paste what I already wrote once? I’d rather just do nothing.

Really though, I’d rather just have up to date docs, so let me update them instead of insisting people do things your way. Fix the problem with people not being able to see the PR, don’t make me do the same thing twice.

And the PR doesn’t do that?

At this point you’re just strawmaning.

> and the autonomy of "rockstars" is of dubious value.

I agree, but with your example, I wouldn’t call somebody committing massive amounts of tech debt a “rock star”. I used the term fairly facetiously anyway, because I think we all know the 10x engineer is a myth.

Can you explain why it’s necessary I need to write a ticket to update documentation?

You really want to add friction to completing those tasks? How long does it really take to complete any one of those things, and how is a ticket going to change the fact it probably needs to get done anyway? Why am I going to write a ticket for docs I can write in an hour and be done with? Why would you want the docs to stay out of date until a ticket is created, rather than just fixing them?

Frankly I think you missed the point of the article. If you don’t trust your engineers to prioritize their own time when it comes to writing documents, you don’t trust them to do anything. You’re exactly a part of the problem that Will is talking about.

I think you made that leap, but I was responding to the specific example. I don’t think anybody is contesting the use of tickets in engineering, but I’ll certainly oppose the idea that Jira is important.