jangofett27

Tangential but reminds me of the backlash Clair Obscur got after they had AI assets in their early development. https://www.polygon.com/clair-obscur-expedition-33-indie-gam...

Feels like a nobrainer at this point to "build fast with AI, prove its use, then tear parts of it down and make it good"

AI tooling is moving so fast that the only way to stay afloat is to go as generic and pluggable as possible. That's the case for coding agents whether they're writing code or fixing tests.

This would've saved me almost an hour yesterday alone. Looking forward to see how this tool matures

Crazy that a tool like this doesn't already exist. Interested to see how this tool matures and also if it will change the way they write tests and generate test artifacts.

Interesting, but only 2 of the 6 experimental females actually mated, so feels barely statistically significant.

Interested to see how different case studies pan out with this product. A mentor once told me that data is only useful if you can tell a compelling story. Hopefully soon something like this will make it easier to tell stories that help both business and engineering.

We need more jurisdictions monitoring and publishing local PFAS levels, or people are never going to realize just how much of a problem this is in their areas. Most reports so far have just been case studies, and few states have picked up the torch and actually started regularly monitoring.

I'll always be a rebase diehard, but the core message here is great. If you have to do more than a little bit of git surgery, you're probably doing something else wrong.

I think this is one that goes back to engagement experience. A lot of engineers have not read enough technical writing, and they've only read from their own bubble. As a start, have them go out and fully read technical writing from products they already use, and try to emulate that.