The current "clear context and execute plan" would be great to be joined by a, "clear context, switch to regular speed mode, and execute plan".

I even think I would not require fast mode for the explore agents etc - they have so much to do that I accept that takes a while. being able to rapidly iterate on the plan before setting it going would make it easier.

Please and thank you, Boris.

Diffing and only updating the parts of the TUI which have changed does make sense if you consider the alternative is to rewrite the entire screen every "frame". There are other ways to abstract this, e.g. a library like tqmd for python may well have a significantly more simple abstraction than a tree for storing what it's going to update next for the progress bar widget than claude, but it also provides a much more simple interface.

To me it seems more fair game to attack it for being written in JS than for using a particular "rendering" technique to minimise updates sent to the terminal.

I got a lot done, but my brain was fried after that. Like wired but totally exhausted.

Has anyone else experienced this and did you find strategies to help (or find that it gets easier)?

We're building a regulatory intelligence platform for AI in healthcare. In effect a specialist dataset + search engine for that information. Currently working to get from a Beta to production ready. This is a Full-stack role, working alongside CTO.

Stack: Python, Node, React, GraphQL, PostgreSQL, Data scrapers

Fully remote with quarterly meetups. Flexible hours.

Must have UK work authorization (no visa sponsorship).

Find out more and apply: https://www.hardianhealth.com/careers-list/product-engineer

Seeing this did make me wonder how I might be able to get better at memorising important parts of iso/iec standards at work, but I can't see how that maps to flashcards

Edit: As a sibling comment says quite rightly, you do feel hungry in the late morning, but reacting to that feeling is optional

I work (freelance) with a consultancy [1] that helps specifically with software-as-a-medical-device (SaMD). My email is in my profile if you want to chat about what might be the best way forward.

[1]: https://www.hardianhealth.com/

It's a tight-rope walk of ensuring that all testing (software and non-software testing) and evidence is produced correctly and being able to release at a rapid pace to derisk each release. It's not uncommon for software to only be updated yearly, leading to very conservative changes and little iteration. Monthly releases are okay, but still not great.

I want to make it possible to release at least weekly and to do so safely.

If you work in this area, I'd love to chat and hear your experiences (email available via my website in bio).

Neuronostics is revolutionising diagnosis and prognosis of neurological conditions. We create algorithms and software which can be used to aid medical professionals gain more value from EEG data than ever before.

Seeking: Mid/Senior Fullstack Engineer

Stack: Python, Django, Postgres, HTMX, Terraform, AWS

Role involves: Working within the tech team to take scientific code from our science team and get it into the hands of our customers, help to build out the rest of the tech team.

Full job ad: https://www.linkedin.com/jobs/view/4028079138

Apply: recruitment@neuronostics.com

https://neuronostics.com is revolutionising neurological disease diagnosis and prognosis through innovative algorithms and software.

We're seeking a lead engineer to join our early-stage team and help bring our products to market.

Key skills: Python, Django, HTMX, postgres, terraform, AWS, full stack development.

Email in profile for general questions about the role/company, or application link: https://www.linkedin.com/jobs/view/3927996419