@kobo when are we getting LLM integration into your ereaders. I would love nothing more than to be able to highlight a word, a sentence, or a passage and be able to quickly get LLM generated content, like summaries or explanations.
WARNING: Longer post (but worth reading or bookmarking for later).
Your life has seasons.
Each one is unique. Characterized by its own distinct desires, struggles, opportunities, and identity.
But one reflection I've had recently is just how easy it is to completely disassociate with the present season.
To give all your time and energy toward a longing for some nostalgic memory of a prior season or an anticipation for some beautiful state of a future season.
You look back at the past and all you see is sunshine. Because it all worked out. You forget (or glaze over) the struggle you endured. You're here today. You made it. You're alive. You're doing fine.
You look forward at the future and dream on what could be. You'll have so much more. More freedom. More purpose. More health. More deep connection. More everything.
The past is beautiful and the future feels limitless. So, logically, you slowly start to treat everything about the present as the bridge. A dash connecting your past and your future. A gap to be crossed as quickly as possible.
Everything you do today is in anticipation of some eventual end state.
I'm doing this now, so that I can have that later.
Unfortunately, the danger of that dissociation with the present is significant. You may spend your entire life living for a future that has a decidedly mirage-like property. You inch closer, but when it's right in front of you, it disappears and reappears on the horizon.
You may spend your entire life skipping through the present, deferring your presence, your joy, and your very humanity to a future that never comes.
In a classic French fable, a young boy is gifted with a magic ball of golden thread. He's told that if he simply pulls on the thread, time will leap forward. The catch, of course, is that once it's pulled, it can never be put back.
The young boy takes advantage of the newfound powers. Each time he's faced with a boring day at school, a frustrating set of chores, or a scolding from his parents, he pulls the thread, skipping through to the good parts.
As an adult, he continues, leaping through mundane struggles in his marriage, the friction of having a newborn, and the boredom at work. He finds himself pulling on the thread more and more, avoiding even the most minor inconveniences of his life.
But when he wakes up one day and sees an old man looking back at him in the mirror, he's filled with regret. He realizes in that moment that as he chose to skip through the boredom, struggles, and friction, so too did he miss the real texture of being alive.
How often do we all do the same? How easily do we default into this disassociation? Disconnecting from the present in anticipation of some future.
A mentor recently asked me this:
"Where are you going and why are you in such a rush?"
It hit me hard.
And to be honest, I haven't stopped replaying those words since he said them.
Why are you in such a rush?
The world wants you to rush into everything. Rushed decisions. Rushed conversations. Rushed relationships. Rushed timelines.
In doing so, you slowly relinquish your agency. You give up your claim on your own life. Surrender authorship to a pen that was never even yours.
In a world that wants you to rush, the ultimate act of rebellion is presence.
Be in the season you're in. Don't romanticize the past, don't fantasize the future. Be here. Be now. Be in this. All of its texture, depth, and struggle. All of its joy, tension, and pain. Sit with the uncertainty. Become friends with it. Fall in love with it.
Because every single thing you do today is something your younger self dreamed of and something your older self will wish they could go back and do.
The good old days are happening, right now.
And the next time you find yourself skipping through the present, remember these words:
Where are you going and why are you in such a rush?
I'm having a lot success using Fable xhigh as a planner/architect, using GPT 5.5 xhigh (subscription) as a coder, then Fable xhigh again as a judge. At API pricing, planning+judge costs are in the ~few dollar range compared to typical $50+ full round trips.
I've seen some others using dumber/cheaper coders, but GPT 5.5 even at xhigh compared to Fable 5 is very cheap and very fast. And GPT 5.5 is just... really good.
Still been less than 24hrs since the re-release so the longevity of this approach is unclear, but its been working really well.
# on shortification of "learning"
There are a lot of videos on YouTube/TikTok etc. that give the appearance of education, but if you look closely they are really just entertainment. This is very convenient for everyone involved : the people watching enjoy thinking they are learning (but actually they are just having fun). The people creating this content also enjoy it because fun has a much larger audience, fame and revenue. But as far as learning goes, this is a trap. This content is an epsilon away from watching the Bachelorette. It's like snacking on those "Garden Veggie Straws", which feel like you're eating healthy vegetables until you look at the ingredients.
Learning is not supposed to be fun. It doesn't have to be actively not fun either, but the primary feeling should be that of effort. It should look a lot less like that "10 minute full body" workout from your local digital media creator and a lot more like a serious session at the gym. You want the mental equivalent of sweating. It's not that the quickie doesn't do anything, it's just that it is wildly suboptimal if you actually care to learn.
I find it helpful to explicitly declare your intent up front as a sharp, binary variable in your mind. If you are consuming content: are you trying to be entertained or are you trying to learn? And if you are creating content: are you trying to entertain or are you trying to teach? You'll go down a different path in each case. Attempts to seek the stuff in between actually clamp to zero.
So for those who actually want to learn. Unless you are trying to learn something narrow and specific, close those tabs with quick blog posts. Close those tabs of "Learn XYZ in 10 minutes". Consider the opportunity cost of snacking and seek the meal - the textbooks, docs, papers, manuals, longform. Allocate a 4 hour window. Don't just read, take notes, re-read, re-phrase, process, manipulate, learn.
And for those actually trying to educate, please consider writing/recording longform, designed for someone to get "sweaty", especially in today's era of quantity over quality. Give someone a real workout. This is what I aspire to in my own educational work too. My audience will decrease. The ones that remain might not even like it. But at least we'll learn something.
I stole this idea and now use it with every single employee.
It’s the best illustration I’ve seen of teaching someone to be high agency.
It says there are 5 levels of work:
Level 1: “There is a problem.”
Level 2: “There is a problem, and I’ve found some causes.”
Level 3: “Here’s the problem, here are some possible causes, and here are some possible solutions.”
Level 4: “Here’s the problem, here’s what I think caused it, here are some possible solutions, and here’s the one I think we should pick.”
Level 5: “I identified a problem, figured out what caused it, researched how to fix it, and I fixed it. Just wanted to keep you in the loop.”
Using this framework, here’s what I say to every new employee…
You will live at Level 4 from Day 1 and as we build trust you will rise to Level 5.
Being high agency doesn’t just mean tackling problems in this way. It means your entire way of working should be oriented to being a Level 4+ employee.
Plz feel free to steal it as well.
And ty @stephsmithio for the framework!
Mijns inziens is dit een van de beste use cases voor AI-videocontent op dit moment. Een AI-influencer reist terug in de tijd naar 1536 om te vloggen over haar ervaringen in Tudor-Londen.
The basic idea is easy and v0 is a hackathon project. The product here is a lot closer to *it actually works*, for enterprise grade deployments, and after quite a bit of internal experimentation and iteration. It’s kind of hard to describe other than (per the post) it’s writing majority of code, it’s deeply integrated, multiplayer, and it starts to feel like everyone is a manager. So I understand it looks easy to dismiss on quick reading but it’s not some LLM Q&A with RAG over Slack, it’s not even OpenClaw adjacent, it’s a different way of working entirely, for people and teams. I work from Slack now.
Today on the blog, we discuss a pathway for the second life of phones through the exploration of “phone cluster computing”, which can directly reduce the environmental footprint of computing by avoiding the need for further raw material extraction. More →https://t.co/FFUNjfaEm5
I use Cursor, Codex, and Claude Code. I want to make sure I use all my tokens during each period. What are some recurring tasks I should do on my codebase?
Barbell strategy for killing it in an age of superhuman AI:
Simultaneously get as close to AND stay as far away from AI as humanly possible.
1. Get close — play with AI models, use them to help you think, ask them to teach you about the world, get them to help you create, work with them to write code, understand what makes them tick, embed them into your everyday life, have fun.
2. Stay far away — learn to tell stories, make eye contact, build a team, lead with courage, connect far-flung ideas, build lifelong friendships, debate persuasively, think forbidden thoughts, handwrite ideas, confess your fears, fall in love.
Spend less time trying to master mental transformations that are purely mechanical — building spreadsheets, analyzing trades, balancing accounts, writing code by hand, following playbooks, searching for needles in haystacks. These are the emerging no-man's land, squarely the domain of AI.
Venture to the extremes. That’s where all the fun is anyway.
This is a super exciting release - Claude Fable 5 is the same underlying model as Mythos but with added safeguards. The benchmarks are great and it's SOTA on everything by a margin but I'll add that *qualitatively* also, this is a major-version-bump-deserving step change forward (imo of the same order as Claude 4.5 was in November), peaking especially for long problem-solving sessions on very difficult problems. You can give it a lot more ambitious tasks than what you're used to, the model "gets it" and it will just go, and it's never felt this tempting to stop looking at the code at all (but don't do this in prod!). The model still has quirks that people will run into and the safeguards are configured to be a little too trigger happy for launch, which can hopefully be tuned over time.
I feel a lot of things changing as working software increasingly comes out on a tap. The Jevon's paradox kicks in and I feel my own demand for software growing substantially. You can ask for anything - explainers, visualizers, dashboards, bespoke single-use apps (e.g. a full wandb that is hyper-specific just for your project), you can 10X your test suite, auto-optimize code, run giant research projects with custom HTML for the results, anything! "Free your mind" (Matrix ref). Really looking forward to all the things people build!
"Men with two children had an estimated brain age that was 0.6 years younger than their childless peers had, and for men with three children, it was 0.7 years younger. That’s similar to the brain benefit associated with exercising 2.5 hours a week." https://t.co/28mz6llyyp