I wonder though if someone tested mutating training objective though, like keeping original loss/goal and somehow defining loss differently and then comparing against original. This intuitively feels like how mind tries to handle difficult tasks.

1) The getter trap - if you forget to export hooks via getters you don't get reactivity and it's not easy to figure out (Svelte)

2) The async data fetching - for example fetching data async is currently coupled to views which it shouldn't be - was frustrating a lot (SvelteKit)

3) That reactivity system is not runtime only (Svelte)

I am also not a fan of adding these new things like remote functions - most of apps need multiple frontends and this coupling isn't needed. This will be fad same as GraphQL

Getting close to it with my recent test of cursor cloud workflow.

I've spent 300M tokens in a day and it achieved what I wanted. Manually would take me a month instead of day so it's not 2x it's 20x faster but project was quite simple rewrite of 20k lines of C++ and there was reference implementation. It also improved on original implementation perf wise.

The problem is with fuzzy ideas for new development and with catching up with comprehension when working on something new - I guess we need better visualization tools for code. Product manager work seems like bottleneck currently and monitoring because coding can move quite fast.

Do I feel better? Yes. Was it hard first 2 weeks? Yes, I had even to resort to painkillers.

I think the best for people who sit a lot are core, mobility and back exercises. Huge motivation for me when I finally started prioritizing back on machines and progressed on all other things and finally look like I go to gym :)