Interested in your workflow @sails
Posted a video in the thread, it’s pretty rudimentary (Claude code does everything) at the moment but I think this has a lot of possibilities.
Readit Newssails commented on Launch HN: Mosaic (YC W25) – Agentic Video Editing mosaic.so... · Posted by u/adishj
sails commented on Launch HN: Mosaic (YC W25) – Agentic Video Editing mosaic.so... · Posted by u/adishj
that's super interesting — what kind of things have you done with remotion and Claude Code?
they're very powerful, when you put them together, it almost feels like Cursor for Video Editing
Mostly using it for technical marketing/explainer videos eg https://x.com/mattarderne/status/1987441582413345016
sails commented on Launch HN: Mosaic (YC W25) – Agentic Video Editing mosaic.so... · Posted by u/adishj
I’ve had a lot of fun with Remotion and Claude Code for CLI video editing. I’ve been impressed with how much traditional video editing I can manage.
I will be checking this out!
sails commented on WeatherNext 2: Our most advanced weather forecasting model blog.google/technology/go... · Posted by u/meetpateltech
I find it interesting that they quantify the improvement on speed and number of forecast-ed scenarios but lack details on how it results in improved accuracy of the forecast per:
``` WeatherNext 2 can generate forecasts 8x faster and with resolution up to 1-hour. This breakthrough is enabled by a new model that can provide hundreds of possible scenarios. ```
As an end user, all I care is that there's one accurate forecasted scenario.
As others have explained, ensembles are useful.
As a layperson, what _is_ useful is to look at the difference between models. My long range favourite is to compare ECMWF and GFS27 and if the deviation is high (windy app has this) then you can bet that at least one of them is likely wrong
sails commented on Structured outputs on the Claude Developer Platform claude.com/blog/structure... · Posted by u/adocomplete
I feel like this is so core to any LLM automation it was crazy that anthropic is only adding it now.
I built a customized deep research internally earlier this year that is made up of multiple "agentic" steps, each focusing on specific information to find. And the outputs of those steps are always in json and then the input for the next step. Sure you can work you way around failures by doing retries but its just one less thing to think about if you can guarantee that the random LLM output adheres at least to some sort of structure.
Agree, it feels so fundamental. Any idea why? Gemini has also had it for a long time
sails commented on Angel Investors, a Field Guide jeanyang.com/posts/angel-... · Posted by u/azhenley
Good guide.
In the spirit of finding the right person through serendipity:
I’m actively looking for intros to angels who are interested in B2B lending. The tariffs have completely disrupted the US SMB lending ecosystem and automation is going to have to ramp up rapidly to close the gap.
Myself and my team have a AI automation tool, we are revenue generating, technical founding team with 2x maths PhDs
Please email me (email in profile) if relevant to someone you know
This problem statement was actually where the idea for Proof of Work (aka mining) in bitcoin came from. It evolved out of the idea of requiring a computational proof of work for sending an email via cypherpunk remailers as a way of fighting spam. The idea being only a legitimate or determined sender would put in the "proof of work" to use the remailer.
I wonder how it would look if open source projects required $5 to submit a PR or ticket and then paid out a bounty to the successful or at least reasonable PRs. Essentially a "paid proof of legitimacy".
$5 could go towards a strict AI reject/review funnel as a prefilter
I feel like these background agents still aren't doing what I want from a developer experience perspective. Running in an inaccessible environment that pushes random things to branches that I then have to checkout locally doesn't feel great.
AI coding should be tightly in the inner dev loop! PRs are a bad way to review and iterate on code. They are a last line of defense, not the primary way to develop.
Give me an isolated environment that is one click hooked up to Cursor/VSCode Remote SSH. It should be the default. I can't think of a single time that Claude or any other AI tool nailed the request on the first try (other than trivial things). I always need to touch it up or at least navigate around and validate it in my IDE.
Agree, each agent creating a PR and then coordinating merges is a pain.
I’d like
- agent to consolidate simple non-conflicting PRs
- faster previews and CI tests (Render currently)
- detect and suggest solutions for merge conflicts
Codex web doesn’t update the PR which is also something to change, maybe a setting, but for web Code agents (?) I’d like the PR once opened to stay open
Also PRs need an overhaul in general. I create lots of speculative agents, if I like the solution I merge, leading to lots of PRs
Not sure "Cargo Cult" is an apt description. Feynman's description of Cargo Cult Science was predicated on the behavior of islanders building structures in expectation it would summon the planes, cargo, personnel, etc. that used the island during WWII.
Without a previous experience they would not have built anything.
There is no previous AI experience behind today's pursuit of the AI grail. In other words, no planes with cargo driving an expectation of success. Instead, the AI pursuit is based upon the probability of success, which is aptly defined as risk.
A correct analog would be the islanders building a boat and taking the risk of sailing off to far away shores in an attempt to procure the cargo they need.
I’m amazed they published it with such a poorly applied analogy.
My tool collection [0] is inspired by yours, with a handful of differences. I'm only at 53 tools at the moment.
What I did differently:
Hosted on Cloudflare Pages. This gives you preview URLs for pull requests out the box. This might be possible with Github Pages but I haven't checked. I've used Vercel for similar projects in the past. Cloudflare seems to have the odd failed build that needs a kick from their dashboard.
Some tools can make use of Workers/Functions for backend processing and secrets. I try to keep these to a minimum but they're occasionally useful.
I have an AGENTS.md that's updated with a Github action to automatically pull in Claude-style Skills from the .skills directory. I blogged about this pattern and am still waiting for a standard to evolve [2].
I have a base stylesheet that I instruct agents to pull in. This gives a bit of consistency and also let's them use Tailwind, which they'd seem to love.
[0] https://tools.dave.engineer/
[1] https://github.com/dave1010/tools/tree/main/functions
[2] https://dave.engineer/blog/2025/11/skills-to-agents/
Edit: come to think of it, I should revisit it now that everyone can vibe code. The sheet was to allow people to add to it, now maybe easier for me to take a message and ask an agent to update the html directly