My current job is doing the exact same thing. My manager even showed me a tool with graphs showing token use and related metrics.

I'll have to try some more. I've been playing with gpt-oss 20b on my M4 24GB but it hasn't been the best experience.

Not only for those but being able to nitpick jira tickets or github PRs.

I have multiple Chase cards but they do look different from each other physically and in the Wallet app. Isn't that just a bank issue of not making cards differentiate from each other?

I saw someone else mention this idea, which is that GameStops could be used somewhat like Whole Foods is for Amazon. Basically a drop-off location if you're selling items, especially collectibles, and want to make the process of sending them in for authentication and whatnot simpler.

Not sure if that's the intent behind this move but an interesting thought experiment.

Precisely! Ryan Cohen discussed this very bit on the TBPN interview yesterday, starts at 1:33:20 or so

https://www.youtube.com/live/CxJEIOD9Xow?is=n_o01_LlR4xae4H6

On a visit to Hiroshima, Japan, I went to the Mazda HQ for a factory tour. They took the group on a shuttle bus through their massive city-like complex and then we got to walk through one of the assembly-line buildings. Real fascinating experience.

I'm not sure in this case it's AI per se so much as a change over time.

At the first role I ever had 10+ years ago, we had a TV in our team's office space constantly showing our dashboard for our critical services and health. We still had alerting monitors but it felt like those alarms were for important issues (like sev-2 or worse).

the last couple roles I've had we don't constantly look at our dashboards unless our monitors keep ringing us with alerts. We have also had more monitors in general than the first role I mentioned. Occasionally if another team asks us if we're affected by something we'll look at the dashboards we have to make sure we don't have a monitoring gap.

I was recently job hunting and did something similar. Had it check my bullets and see if they "read well" and it suggested many many tweaks. I tried a few. I'm not sure how much more it helped the applications though.

I very vaguely recall using it right before I started using google. very early 2000s. it was ok.

Where I work that many comments could be taken as a bad thing: "i've seen too many comments finding issues or nitpicks with your PR, why aren't you doing a better job before submitting it for review??"

Where I work, the latest trend is to open the PR with the pure vibe code, then the developer who opened the PR will review it as if its someone else's PR, so before anyone else even looks at the PR it can have upwards of 50 comments on it.

Makes sense but it's a sad issue considering at least in my org we're being told to cut jira tickets such that they can be implemented purely by AI.