I know this is a joke, but it you did that I would reject the pr with the reason of too many things at once. Reopen separate PR to refactor variable names. I actually constaly get people doing this and it’s dangerous exactly for the reason you’re joking about. Makes it easier for errors to slip in.

Was probably made by a child as a school project. At least I hope.

I win screen real estate. I have an abundance of horizontal space.

I think this is the behaviour most people expect. Coming back hours later and finding your old private tabs still in the browser seems to defeat the purpose of using private tabs.

Yes

We’re so many levels of abstraction and emulation deep, that the natural conclusion is that there’s no reason to believe we’re at the top of the abstraction, but somewhere in the middle.

We definitely living in a simulation.

Do you hate everything you don’t understand?

Is it really that surprising? Specially the type of person that would be on Lemmy and use Linux.

This meme only works if you don’t include any example that is better than others in every regard.

You’re not alone… This makes no sense.

Do retros every week or two and use them to improve the process. Best way to learn from others.

That’s what retros are supposed to be for. To discuss how to improve the process.

In the end it comes down to the size of the team/company.

I might… Have mixed multiple thread. I’m sorry

Exactly. Shit happens, and we might need to adapt and even scrap a whole sprint plan. But that’s super rare, or it should be. But changing the Roadmap after each sprint is just something that happens.

Either way, none of that warrants random calls at all times from colleagues.

It’s not a label im making up. Toxic here is a synonym for unhealthy. If someone keeps calling you, interrupting you, micromanaging you, disrespecting your working hours or your focus times, that’s an unhealthy relationship.

Stacy is entitled to regular details, sure. That’s why we have tickets, and daylies and retros. She’s not entitled to asking multiple times day if you’re done yet.

I work above senior, have done management and tech lead. I’ve seen toxic workplaces, and I’ve seen good ones. I recognize the need for all the agile rituals. But that still doesn’t entitle people to call all the time and interrupt you.

It’s not about corps vs startups. It’s about having processes, good communication, dialogue, empathy. And it’s also your manager’s job to protect the team from externals that keep interrupting and making adhoc requests. If you don’t feel safe in ignoring calls and replying with “I’m busy now, schedule smth today please”, I consider that a highly toxic workplace.

I’ve worked in places where QA we people with no coding knowledge who just clicked around looking for bugs, as well as places where QA never did that, only automated tests. And then there are places that believe hiring QA is useless, because “everyone should do QA”.

Gotcha. I mean, all software engineers should do some QA engineering, but we have QA engineers who are the experts and “QA coaches”.