@elshayib_ I just keep rambling, even though what I’m asking for is changing as I’m talking. The models are usually pretty good at figuring out where I ended up.
Lots of talk about "Ox Alpha" on here, so I figure I should contribute some results I found.
On a (fairly tough) private benchmark (i.e. with zero chance of contamination in any model), with minimal/low reasoning, it underperforms quite a lot, even with a reasoning advantage:
@aarondotdev I should say that one practice I do that seems to help is heavy AI adversarial review. I usually have ~a dozen subagents pick the work apart until it's there aren't any issues left to find.
I read the code. I’d be curious to see the critical mistakes you’re finding. My experience has been that frontier models don’t make coding mistakes. The worst I see is they make assumptions based on ambiguous requirements, and that’s usually resolved with something like /grill-me up front.
I open-sourced ThreeUI, my library of three.js components and landing pages.
160+ are free, and the tool is free too. It includes procedural 3D hero sections, icons, and motion designs. Copy the prompt or source, give it to your agent, then change the theme, lighting, motion or layout.
Live site: https://t.co/rtCfqeZnOP
Repo: https://t.co/B66ahgxHVl
I'm adding a lot more soon. Pro comes with 50+ extra components, MCP, and skills. Early adopters get 50% off right now.
Ox Alpha (stealth model) is now free in Cline.
Early benchmarks shows marginal improvement over Fable and GPT.
Try it with:
npm i -g cline
and use /models to see it under Free options
every team needs a gardener. someone quietly watching the stream of PRs flowing into your codebase, noticing the smells: the third isRecord this week, the lint suppressions creeping like ivy across your carefully planned garden. a steady hand tending the weeds that would engulf it in slop if left unchecked.
with careful grooming it stays a garden. every weed you pull becomes a rule, so it can't grow back. without that, it's just whatever grew.
a skill people at Anthropic have been using a lot recently: ELI5
/eli5 <what you want explained>
"explain like I'm someone who knows nothing about this topic, using a HTML artifact with big pictures and few words"
I added a a stick shift to my computer. It's like Raycast but for truckers.
Window management, LLM Model selection, Shift up/down for reasoning levels.
It feels right
This has already been the case at startups for many years.
People who have experience working in startup environments where you have to wear many hats are going to have a big advantage going forward.
Roles are collapsing.
If you're a "Software Engineer" today, you may be a "Product Engineer" soon - with many more responsibilities.
So:
- Learn design/UX/QA/PM skills.
- Focus more on the user, and less on the syntax.
Image via Gartner.