citriqa (extra tart edition)

@citri.qa

entering the limelight. acerbic at times. 🍋‍ current obsession: truly universal apps using react native. 🍋‍ background interests: fp, trustless systems, pl, web

sent this to the team today everything great comes from being able to delay gratification for as long as possible and it feels like we're collectively losing our ability to do that

Image from X

Only for team/enterprise for now, but it looks like Anthropic has more or less just killed all of the AI code review wrapper startups. This seems to be super in-depth (expensive!) and supposedly less than 1% of reviews are flagged incorrect. Excited to see if pro/max gets this.

Code Review for Claude Code | Claude

Claude Code now dispatches a team of agents on every PR to catch bugs that skims miss. Available in research preview for Team and Enterprise.

claude.com

So two psychologists walk into the speculative agentic coding design space bar and......have a lot of ideas for developer learning! @mcmullarkey.bsky.social has written a new Skill that we've layered into Learning-Opportunities: Orient! 

 github.com/DrCatHicks/l...

GitHub - DrCatHicks/learning-opportunities: A Claude Code skill for deliberate skill development during AI-assisted coding

A Claude Code skill for deliberate skill development during AI-assisted coding - DrCatHicks/learning-opportunities

github.com

having used claude extensively for the past couple of months, i think there is still a lot of value to understanding your code and steering it intentionally. the amount of incidental complexity claude accumulates otherwise (which mostly results in bugs that it can't ever fix reliably) is staggering.

stereOS: a Linux based operating system hardened and purpose built for AI agents "A full NixOS system that you boot and then kick off agent sandboxes inside with gVisor + /nix/store namespace mounting. Each agent gets their own kernel and the /nix/store is read only by nature.

he's based now. the operating system of the future will use a capability restricted database instead of a traditional file system

@theo on twitter: Gen Z is right. File systems are bad design. We've stockholm syndrome'd ourselves into thinking otherwise.

the absence of type safety is responsible for loss of life and livelihood in the same way as absence of memory safety or thread safety. if you are writing serious software, it is not a matter of taste.

@dhh: What a perfect illustration of the type brain in its most rabid form. Catastrophizing the use of dynamic typing to the point of death. Fascinating state of mind.

whenever i hit ")" and visual studio just advances the cursor past the existing ")" that's one position ahead of where i was, instead of inserting an additional ")" as i intended, i feel undermined, i feel indignant, i feel i have been spat on

...and language is a poor medium for designing easing curves and aesthetic feelings. I always need to touch the code, and it's often faster to CSS than prompt. FE requires constant human-in-the-loop checks so even if you have a dozen agents working, I am the bottleneck. Scale isn't that helpful.

Been using this repo to iterate on API ideas for a concurrent compatible store for React. Still exploratory but excited that we’re very close to something that we can start trying out with existing data stores and start an iteration cycle based on what we learn.

Mark Erikson@acemarke.dev · 12mo ago

Had a great discussion with @capt.dev about the work he and Justin Walsh are doing prototyping React's "concurrent store" API. Really excited to see the active WIP ideas like this PR: github.com/thejustinwal... hopefully we'll get to try this out with React-Redux soon and see what's feasible!