When the source maps leaked for the harness, it was revealed that they track how often tool use is rejected and how many times you say "fuck". They definitely try to track frustration sentiment.
That said, given the propensity for mature code bases to have "fuck" in commit messages/comments and those are typically of higher quality, I curse up a storm when the clankers make mistakes, if only to try put more quality-code valence into context. https://news.ycombinator.com/item?id=36584464
I found some news articles that seem to back up this stat. It wasn't all attributable to the cameras though. It also included targeted enforcement strategy with bait cars and what not.
> The public perception of crime is persistently incorrect for many if not most people and this incorrect, emotional rather than evidence-based view of the world is unfortunately what drives political pressure.
Some of this is definitely the BBC's fault. I happened to be over at a friend's one morning and he had it on. It smelt just like right-wing media in the US with big stories on mega important topics like... shoplifting. The crime reporting just felt really amplified up.
Tell it that. Seriously. "Shut the fuck up and do what I say. Don't think about it. Don't go spelunking through the code base. I've already given you all the context you need." I've needed to start doing this because otherwise, it wants to `find /` and grep its way across my system for everything. I've got one project where I force certain complete documents into context, specifically to avoid it trying to grep around and only load partial chunks. It will still want to go do that grepping of those documents for some reason.
The key phrases I've found that help is to tell it "No memorializing decisions in output artifacts" and "Only describe what is, never what was in documentation"
I'd argue that Star Trek: Lower Decks flirts with this with its treatment of megalomaniac AIs in the AI prison. Apparently, it is very common to come across AIs worshiped as gods in universe.
A company I used to work at has a CEO/Founder just like that. He's a sad sack of shit. Got up on stage at the company christmas party drunk to sing karaoke and noticed not enough people were paying attention to him, so he "joked" about firing people. Same dude some years later would bribe employees to work over the christmas holidays with him and was bragging about it on LinkedIn. He's rich. Could do any number of things. But its obvious he's got no friends and clings to the company as his identity; likely having been self-sabotaging the IPO that was always right around the corner he was working on.
Even more extreme than that, if you were working on a large code base where compiling it took forever, or you needed to rely on a very slow CI pipeline, it became very important to git gud and write shit that worked first time in order to deliver when promised. I'd argue if you've never had one of those moments where you sunk a bunch of time into some changes and it all compiled/worked flawlessly the first time, you're missing out.
I've been that engineer and with good reason. That obscure edge case which rarely comes up in production is very disruptive when it does come up. The product person waving it off is also not the one that will get paged at 2am to address the issue when it occurs. Accepting that 90th percentile use case is infuriating because it is tacit consent for an unfinished solution with the rest being made up later with additional toil, now constrained by load bearing things you cannot change. Thanks for rushing the thinking and making my life harder later for no reason.
Don’t forget months or years later when shit hits the fan, developers will be blamed for being lazy and not the product person. No one will remember Joe said something on one or two meetings we build for 90th percentile - code in git repository will point to a developer who wrote and GitHub will point to the one that approved merge request.
In online discussions people always blame „lazy developers „ like there would be no product owners, testers, business analysts, scrum masters etc.
This is one of the reason I like a ticket tracker. I make my commit as descriptive as possible and I tag them with the ticket number. Also I add comments when Product says to cut corners. It's nice to spread responsibility around when things take a bad turn.
That said, given the propensity for mature code bases to have "fuck" in commit messages/comments and those are typically of higher quality, I curse up a storm when the clankers make mistakes, if only to try put more quality-code valence into context. https://news.ycombinator.com/item?id=36584464