I've tried these in the past but always found the software/firmware side of it too fiddly for the reward (against the grain for a lot of people, I know), which is a pity as the hardware side is really rewarding (for me).
Recently, doing it with Claude Code was a breeze. If you are more interested in the outcome than the process, then I'd say it's a great time to buy a few old Kindles and see what you can create with them.
This is really interesting, as a data analyst and product person I like this embedded data modelling approach.
I would be interested in knowing if you’ve thought about what to do with external data (eg Stripe) and data processing engines (eg Snowflake/Databricks/clickhouse or duckdb)
At this point it would rely on the person embedding it in their app to get that data, put it somewhere, and then add a Cube definition on top of it - so this is purely solving the visualisation / report building part of that puzzle (but in a fully embedded / non iframe way).
I used Cube as inspiration, and actually the rest API for drizzle-cube is compatible with the cube-js schema definition. The main difference is that I chose to model the cubes in typescript, so they can be validated in the IDE easily (autocomplete, catch issues early) and not have an option for YAML, but the semantics are exactly the same.
These are great. Something you might find interesting is that you can expose a google sheet to have an interactive database. I have a map similar to yours, but with surf spots. Maybe defeats the point, but I find it handy
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
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
The way you get structured output with Claude prior to this is via tool use.
IMO this was the more elegant design if you think about it: tool calling is really just structured output and structured output is tool calling. The "do not provide multiple ways of doing the same thing" philosophy.
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
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
Recently, doing it with Claude Code was a breeze. If you are more interested in the outcome than the process, then I'd say it's a great time to buy a few old Kindles and see what you can create with them.