481 karma · joined September 25, 2019
Or maybe it’s learnt like you say, I think both areas would be worthy of researching.
The only data we need is if you’re at home and the charging metrics /w commands.
But the amount of unnecessary data that is available, is a real privacy concern.
It would make sense to me that evolutionary there would be different mental development paths depending on the requirements of their situation.
This is coming from my understanding that ADHD is more prevalent in stressful upbringings.
With your foraging example, it does make me think ADHD is a small group/individual optimisation. Prioritising high vigilance and individual productivity over social cohesion.
I speak with no authority. I don’t even know how such a theory could be tested.
Also the selling point was latency, but I suspect we’ll see bandwidth being the important metric with AI using deep pipelines to stream in the weights in a latency insensitive manner.
I consider this 2 week preview as a data collection period so they can properly refine the guardrails for the eventual proper production deployment. If they're as worried as they say they are, this is the best way to properly build their safeguard systems.
It's annoying af, but I'd rather be cautious here.
Just like in software, some of the most beautiful solutions come from constraints. Think, the optimisations that game developers implemented because of the frame budget.
I’ll confess the reason it hit us so hard is because the code quality was so low and wasteful on allocations that it didn’t hide the problem as well as previous versions.
So I plan the next work, while the current is still running and if that's a task that can't have parallel work, I have a bunch of time to keep planning the next steps for other systems.
And then there's time for reading through the changes and applying corrective changes to the code or the meta-skills.
I use CMUX and setup workspaces for each topic I'm working on, each workspace has number of tabs. That helps keeping track of everything I'm working on, but also means no topic gets left behind until I close the workspace. So they accumulate
But maybe that was a me error and worth a second shot.
It’s just that the rush is more frequent, addiction intensity scales with dose and frequency.
The addiction part, the ADHD part and the pending test part.
The fear of becoming addicted to AI is real and I don't think I'll be capable to stop it, considering we're asking people who struggle with avoiding quick dopamine to use it professionally in their daily work life.
My Pro went to Max(5) to Max(20) pretty quickly and I was burning through that weekly limit still, without large agentic workflows that burn tokens. Just me and 4-5 terminals. Sometimes I was happy to hit the limit because I was forced back to normal life.
I've gone back to Pro to stop what was happening.
Now I'm self-aware enough to notice the trend and put up safe guards, but that's because I've always had to adapt my environment to control my behaviour because I know direct behaviour control is abnormally challenging. I fear for those who won't see it coming, until they're in deep.
The second it works, bake the workflow into the harness. Yesterday I was doing just that, and the whole agent loop disappeared because the process could've been condensed into a one-shot request (+1 MorphLLM fast apply) from careful context construction. (It was an Autoresearcher)
Seeing the idea explored in such depth is great, I really am concerned about this.