matneyx

The burningest of burners

No, sir, I don't like it.

That last sentence is so perfect, like my dad answering the question of how he lost weight. "I ate less and exercised more."

Maaan, this seems so great except it's MacOS only.

The FAQ just keeps getting creepier...

In Claude's defense (and I cannot believe I'm defending it), I know no single dev who could create what it did (Concord), from a 19-page design document, in 9.5 working hours.

We're gonna go back to the days where our bosses ask why we're just sitting around, but instead of saying "compiling," we'll just say, "waiting for Claude."

By the headline, I was half expecting "Trump Mobile was found selling customers' personal data"

Not to mention earrings -- I've yet to find headphones that I can wear comfortably for a couple of hours that won't leave my piercings sore.

I -just- started compiling my own list as I head back out to find a new job. This will be so helpful!

I totally forgot about the PM / PO role -- probably because I've literally never had one that did their job. I've had someone in that role, sure, but they were either too busy trying to climb the corporate ladder to care about their teams (and were eventually let go), were puppets for the team lead (the lead who eventually left the company because they didn't have a PO / PM who actually did their job, go figure), or were too busy trying to micro-manage the dev teams (and, again, were eventually let go).

But a cultural issue is ultimately what I was trying to say, and you kinda nailed it with the idea that cultural issues generally stem from someone not doing their job, or trying too hard to do someone else's.

How is your organization structured in regards to dev and QA? Do your devs feel like QA is there to help them succeed, or to catch them in their mistakes?

I worked for a company that briefly had a "bug scoreboard," where QA were rewarded for finding a larger quantity of bugs, regardless of quality. Typos, weird UI things being 1px off (no joke), weird edge-case stuff like "if I load this item into my cart in Chrome, but then change the quantity in IE, and then try to check out in FireFox, it will say I'm not logged in..." The value was next to nil.

As was the company's way, each bug was logged (as is good), but because the bugs were usually found in the test environments, the devs who were actively doing the work felt like they were being directly attacked for focusing on the big picture and NOT the edge cases.

This ultimately lead to the QA director being demoted, once management realized how much money was being wasted on meaningless stuff and not being spent actually improving the site, but the damage was done -- some devs who were working in that environment will never trust QA again.

So, to simplify my question: do your devs feel punished by missing edge cases, or do they feel rewarded by providing functionality?