Although clearly her production value obviously increased since her shitty robots days, she remains a creator that feels very down to earth, doing projects that, while very polished, seem accessible to a normal person with a CNC machine, a couple 3d printers and a laser cutter.
Do you hate everything you don’t understand?
Wait, there are planes where the toilets are not fully enclosed?? In a tightly sealed cabin??? This is beyond disgusting.
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.
I mean, you’re not hired to “code”, you’re hired to do software engineering. That usually means working with other people. Reviewing code is a win win situation because both get a second pair of eyes on their code and prevent each other from committing dumb shit that you might have to fix later.
I feel like these memes of hating everything other than lone coding is because you keep working for toxic companies. Ffs you’re programmers, it’s probably super easy to get another job. It doesn’t have to be like this.
People call you directly without asking? Ignore them ffs.
Absolutely, but the solutions that work for one, might not work for another.
How much do you think the US paid China to lie that the moon is not a flat disk?
Most of the times, I carry a bag or two with me when doing groceries, but sometimes I don’t. Sometimes I wish I had a compact bag in my hat. But I don’t wear a hat.