dsmmcken
The report leaves out a lot of detail. Several changes I found useful were: Pair with/without on same screen as left/right for easier viewing, token count for skill consumed, token used per run, time, pass rate, estimated cost, detailed aggregate stats, a parsed version of the conversation log (capturing the jsonl with each run, sometimes reading the log is the only way to find out why it's screwing up), work output logging (in my case screenshots and outputted script code), better formatting (syntax highlighting, log formatting).
Finally, I think the most useful thing was adding a self-reflection pass. After an eval is done, another agent looks at everything from that eval and tries to evaluate what went wrong along the way and what should be added to the skill, and conversely, from the without skill run what was in the skill that didn't need to be. It produces a skill change recommendation file for each eval. A further summary agent aggregates up all those recommendations in a way I can feed back to an agent.
Vite just hangs when running vinext dev, with no output in logs whatsoever beyond printing`vinext dev (Vite 7.3.1)`.
https://codepen.io/dsmmcken/pen/WbwYOEQ?editors=0100
p{counter-increment:n;--n:counter(n)}p:nth-child(3n){--f:"Fizz"}p:nth-child(5n){--b:"Buzz";--n:''}p::after{content:var(--f,var(--n))var(--b,'')}
> n-th child variable
See sibiling-index() and sibling-count() https://developer.mozilla.org/en-US/docs/Web/CSS/sibling-ind...
> Reusable blocks
See @function and @mixin draft spec, https://drafts.csswg.org/css-mixins-1/ and https://css-tricks.com/functions-in-css/
Both are available in chrome already.
People seem more willing to ask an AI about certain things then be judged by asking the same question of a human, so in that regard it does seem to surface slightly different feature requests then we hear when talking to customers directly.
We use inkeep.com (not affiliated, just a customer).
Maybe a CSS `subgrid` would help? Subgrid is newly available. (I know nothing about music notation, and basing this entirely off that statement).
I can't think of any of their design patents this would interfere with. There's a small chance of some internal mechanical or light guide related patents, but that would be pretty unlikely. Even more unlikely would be BlackBerry having anyone around still that would even know what to look for.
It does a subtle blur, then a subtle sharpen, then repeats the middle pixel of a 3x3 grid. Happy holidays!
Doesn't work on mobile, probably needs some pixel scaling math.
The style transfer is really impressive (watch past the underwhelming first example of the airplane).
See video: https://www.adobe.com/max/2023/sessions/project-stardust-gs6...
For however long the user has a browser focus state on the element seems like a reasonable answer, and submit changes as they are made. However, I don't know how you resolve conflicts of two users simultaneously attempting to acquire a lock.
They explicitly studied ecommerce/product pages here. The relevant metrics are which page had a higher perceived product value? Which page had a higher conversion ratio? Which page resulted in a higher NPS? Which page created a more positive brand affinity?
You don't sell portable speakers using specs, you sell it with aspirational images of it being used on a beach. Of course expanding an accordion of product details then asking "On a scale from 1-7, How well do you feel you understood the offering communicated on the page?" results in a higher survey score. If you said the more dense page converted better, then I would be surprised.
It's like designing a study on the negative impact of hard F1 race car seats, adding a bunch of foam, testing which is more comfortable, then proclaiming one is better than the other because it was rated more comfortable, when the only metric they were designed for is lap time.