I created a make-your-own-circuit simulator in python to help learn electronics. The best part about this is that it is entirely hosted online and people can just go through the lessons, learn electronics by skipping the maths, and in the process have made their own circuit simulator (which is arguably a pretty cool project on its own) at the end of it. https://spicycircuits.dev/
Ask HN: What are you working on? (August 2026)
211–220 of 1001 posts
Re: Ask HN: What are you working on? (August 2026)
#212It's an externally orchestrated (meaning it's not the agent running the loop) spec driven agentic build system.
A bunch of buzz words but essentially it's a tool you use as the last step after planning your work and writing a spec, to actually have agents write the code.
But it happens within an orchestrator that is durable and which coordinates layers of agents to build -> verify -> review -> triage -> fix -> verify fixes , until the code you get as a result is as close as possible to exactly what you specified.
So you can plan however you want, use whatever harness or agent etc and then just delegate the build to the engine (MCP server or CLI)
You can mix and match models from any provider for any part of it.
I'm building this because I think micromanaging agents is what causes AI burnout and because I want to be able to plan work, walk away and come back knowing it's been correctly implemented.
https://engine.build if you want to be notified for the launch, it's going to be free to use and fully OSS (Apache 2.0)
Re: Ask HN: What are you working on? (August 2026)
#213Re: Ask HN: What are you working on? (August 2026)
#214Re: Ask HN: What are you working on? (August 2026)
#215Re: Ask HN: What are you working on? (August 2026)
#216Re: Ask HN: What are you working on? (August 2026)
#217[0] https://parallelthoughts.xyz/2026/08/learning-linux-io-part-...
Re: Ask HN: What are you working on? (August 2026)
#218Aside from this:
- I asked codex to use my mobile app and web page for the flashcard UX, and make me one using qt + qml so I could run it on the remarkable 2, super happy with the initial results. This will be released as a reference for others, as the eco-system is too clunky today to offer it the non-technical users of remarkable devices.
- I learnt about my set-up box, and got assistance in making my first app, so I can post and image from my iphone to it via shortcuts. Currently, it only accepts one photo, but it is cool throwing it up on the tv. This also let me learn a little more about "ios Shortcuts" and cherri, a golang cli, that makes it a little easier to make shortcuts.
- Using nurb, to 3d print things, currently working thru printing a stand, so I can mount an iphone and record doing things on the remarkable. Its been really fun testing with little physical prototypes of small parts to then roll into the stand.
#Reference
Re: Ask HN: What are you working on? (August 2026)
#219The idea is you have a set of sources (e.g. Github, Google Docs, local file system), a bunch of transformations (templates, apps, llms/gen-ai, simulations) and sinks (communicated through changesets). The platform is like a cache layer that connects these together and allows for a graph of operations (source->executor->sink->source->executor->etc.) which allows for tracing the lineage of assets through a system.
It's an impossibly large vision made barely possible with agental coding assistance.
Re: Ask HN: What are you working on? (August 2026)
#220In particular, I’m exploring what the infrastructure should look like when agents are the primary users: deployment, databases, domains, secrets, observability, and lifecycle management.
The goal is that everybody and their pet can deploy an app.
These units are called saasies, and the project is Saasie.