@lik_ai_@jaffathecake IMO one of the pitfalls of responsive design is placing too much emphasis on the ‘resize’ case. I’m definitely guilty of it, because it’s so much fun, but real users don’t resize the window very often
I'm kind of iffy on "skills discourse" but I think I came up with one so good that its worth sharing. The basic ask is to "describe the UX of my application completely". In doing so, agents will discover inconsistencies, bugs, and design errors that have never come up before
@trq212 Everyone is projecting human intuition for how they would detect a watermark. Don’t LLMs have an implicit fingerprint by nature of having fixed weights? A model could say ‘prefer “overcast” when causally discussing historical Autumn weather in Edinburgh’
@invict37@Spectromachina@M1Astra Couldn’t you just use another non-Anthropic model to rephrase the text? Pangram might still say ‘looks like AI’, but the Anthropic fingerprint would be gone
@GergelyOrosz@tanishqk Isn’t code review more about shared responsibility and ownership of a potentially user-facing change to the product? The code quality is usually not the problem, rather that they’ve mis-understood a feature request or missed some important context
@trq212 I never understood CLAUDE.md. Aren’t the models trained on tens of millions of README.md docs? Looking forward to the day the advice becomes ‘keep your readme up to date’
@aaron_lou Even with no explicit web search, is there really no kind of higher-level / semantic caching going on? Like a global ‘collective concept cache’ that could be interfering?
I feel the same way about Linear, where a product wonderfully designed around a human activity feels sort of less good or pointless as it pivots towards AI workflows, where the biggest competition comes from more convenient throwaways like md files or one page sites