Story time:

I worked for an insurance company a long time ago. We sold insurance for 1, 2 or 3 years, and each year we would prompt the user to extend.

At some point we changed to a yearly subscription that you could cancel at any time and even get a prorated refund. This made us substantially more money because far more people would forget to cancel their subscription than there were people committing or extending to 3 year insurance. So the number of users reaching the max of 3 years increased.

I prefer that than to sneak defects in huge PRs.

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.

Do you hate everything you don’t understand?

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”.

Sorry, I’m not native English. What would be the difference?

In my company QA is dedicated to manual and automated tests. I haven’t met many QA engineers who could effectively review any of my code.

Yes. But I don’t really count testing as part of code review.

QA and Code reviews do different jobs. Manual and automated testing will not notice your code is shit, so long as all test cases pass.

We’ve been seeing this tech for 10+ years slowly progressing to the point of commercialization, and finally the release of foldable phones and curves displays.