Why has Germany, #Deutschland taken such a bad decision to phase out clean, reliable nuclear energy? Why are the German people still not pushing for a change? Why don't the Germans follow the example of so many countries turning more to nuclear? It saddens me so much.
#atomkraft
AS PREDICTED: FABLE EXPECTED BACK TONIGHT
That 1 smoking hot ex girlfriend just texted your phone again. She wants you back
I encourage you to prepare ahead of time
Get a list of prompts and projects ready to go that you can feed Fable immediately
Here are a few you can use:
1. Connect it to the X MCP. Have it read your last 100 posts. Come up with 5 SaaS ideas you could build
2. Use the Unreal 5.8 MCP to build incredible, in depth, 3D games
3. /loop it every 24 hours to do a security check on all your API endpoints in your existing apps
4. Make a checklist of every task you do from now until tonight. Then feed that task to Fable and ask what it could automate for you
5. Go to Sonnet 5 and ask based on what it knows about you, what would be some incredible prompts you can give to Fable tonight
Our savior is back
βLoop engineeringβ is a hot buzzphrase after mentions of it by Boris Cherny (Claude Codeβs creator) and Peter Steinberger (OpenClaw's creator) went viral on social media. Loops are now a key part of how we get AI agents to iterate at length to build software. In this letter, Iβd like to share my 3 key loops, shown in the image below, for building 0-to-1 products. These loops guide not just how I build software, but also how I decide what software to build.
Agentic coding loop: Given a product specification and optionally a set of evals (that is, a dataset against which to measure performance), we can have an AI agent write code, test its work, and keep iterating until the code is bug-free and meets its specification. This idea of closing the loop took off around the end of last year, and it has been a game changer in enabling coding agents to work longer productively without human intervention. For example, over the weekend, I was building an app for my daughter to practice typing, and my coding agent could easily work for around an hour, using a web browser to check what it had built multiple times before getting back to me, without needing my intervention.
The engineering loop executes quickly. Every few minutes, the coding agent might build and test a new version of the software. I hear frequently from developers who are finding new ways to engineer more effective engineering loops. This is an active area of invention!
Developer feedback loop: In this loop, a developer examines the current product and steers the coding agent to improve it. Last year, a lot of developers (including me) were acting as the QA (quality assurance) function for our coding agents, manually finding bugs and then asking the agent to fix them. But with coding agents much more able to test their own code, the amount of time we need to spend on this function has decreased significantly. This allows us to make higher-level product decisions, such as what key features to offer, where the UI needs improvement, and so on.
The developer-feedback loop operates over time intervals between tens of minutes and hours β that's how frequently a developer might review a product and give feedback. In the case of the typing app, I changed my mind a few times about the visual design, what cat costumes she can unlock as she learns (she loves cats), and the user flow for a grown-up to log in and steer the child's learning experience.
When a developer has a clear vision for what to build, it is still a lot of work to translate that vision into a specification for a coding agent to implement. Further, after the developer has seen an implementation, they might update (or perhaps clarify) the spec to steer it toward what they want. If you find that the system repeatedly runs into certain problems, building a set of evals for the agent becomes useful.
AI-native teams are increasingly using AI to help shape product direction, for example, automating the gathering and analysis of usage data, summarizing written and verbal customer feedback, or carrying out competitive analysis. However, for pretty much all the products Iβm involved in, I see humans as having a significant context advantage over current AI systems β we know a lot more than the AI system about the users and the context the product has to operate in β and thus humans play a critical role. Many people describe this human contribution as βtaste,β but I prefer to think of it as humans having a context advantage, since that gives us a clearer path to helping AI systems get better. This also speaks to why this step canβt be automated: So long as the human knows something the AI does not, human-in-the-loop is needed to to inject that knowledge into the system.
External feedback loop: This includes a wide range of tactics like asking a few friends for feedback, launching to alpha testers, or putting the code into production with A/B testing. These tactics are usually slow, rarely taking less than hours and sometimes taking days or even weeks. This data informs the developer vision, which in turn continues to drive the detailed product spec, which in turn drives the coding agent.
With coding agents speeding up software development, more engineers are starting to play a partial product management role. For many engineers who are growing into this role, the hardest part is shaping the product vision and striking a balance between building (bridging the gap between vision and spec) and getting user feedback to evolve the vision. It is important to do both!
I will write more about how to do this in future posts, but for now, I find it encouraging that engineers are playing an expanded role (just as product managers and designers now do more engineering).
[Original text: The Batch]
Your 9-to-5 is officially a scam. While youβre stressing over emails, people are literally printing $5,300/month using nothing but fake digital girlfriends.
Forget SaaS, forget dropshipping. The absolute dirtiest cash cow of 2026 is running automated AI Creators on Fanvue.
The masterclass blueprint just leaked, and it takes 40 minutes a day:
> The Trap: Use Claude Fable 5 to engineer an ultra-viral Emo/Alt e-girl persona that dominates growing niches.
> The Illusion: Spin up hyper-realistic Flux images in ComfyUI and turn them into viral 9:16 thirst-traps using Kling 3.0.
> The Ghostwriter: Connect your Fanvue account directly to Claude using the Fanvue MCP (Model Context Protocol). The AI literally reads your fan chats, auto-calculates your pricing strategy, and writes the premium paywall replies for you in your exact voice.
One viral reel hits 600k views, and boom
you hook 50 high-paying subscribers on autopilot. No webcam, no inventory, 99% pure profit margins.
I was 19kg overweight, had a big belly and double chin, and I needed to reach 13% body fat before summer ended.
I got there with these 25 rules:
1. STOP RUNNING (for your knees).
I'm joining OpenAI next week!π₯Ή The job search turned out to be really challenging but also super rewarding, so I wrote a small blog to share what I learned along the way and hopefully make the process a little less mysterious for the next person. https://t.co/6FigSBdenD
There is a graveyard in American tech right now and nobody is walking through it. Companies down 70, 80, 90% from the highs. Still profitable. Still growing. Still the leader in their category. Just unloved. The Trade Desk at 9x earnings. PayPal at 12x with $6 billion in free cash flow. Adobe at 17x and people are talking about it like itβs Kodak. Etsy at 8x EBITDA running a marketplace that two billion people have heard of. Roku trading below its own balance sheet liquidation value if you squint. Match Group, Zoom, Pinterest β each of these would have been a hedge fundβs top pick at this multiple in 2017. Now theyβre orphans. Everyone is buying the Mag 7 because the Mag 7 is the trade. The Mag 7 IS already the trade. The trade is over. The next trade is in the rubble pile. You donβt get rich buying what worked. You get rich buying what stopped working for reasons that turn out to be temporary. Every name on that list was a market darling 36 months ago. The fundamentals didnβt fall 80%. The narrative did. Narratives come back. Earnings compound. Iβm not buying NVDA at 45x. Iβm buying the names CNBC wonβt say out loud anymore
Late eating spikes blood sugar. Insulin clears it overnight. Then glucose crashes at 2-3 AM.
Your body fires cortisol to rescue you.
That's not insomnia β that's a metabolic emergency you scheduled at 9 PM with your last bite.
Many devs are using Retrieval Augmented Generation - or RAG - to improve their LLM's capabilities.
And in this course, you'll learn RAG fundamentals, along with key model context protocol concepts.
The course uses the Python SDK and covers chunking strategies, working with AI agents, and lots more.
https://t.co/tcG07C3e22
Microsoft Senior AI developer just showed how they build AI agents with Claude at Microsoft.
34-minutes. free. By Microsoft team
Opus 4.7 + 1,400+ pre-built MCP tools
plug Claude into agent β give it tools β ship to production
worth more than any $500 vibe-coding course.
A Norwegian neuroscientist spent 20 years proving that the act of writing by hand changes the human brain in ways typing physically cannot, and almost nobody outside her field has read the paper.
Her name is Audrey van der Meer.
She runs a brain research lab in Trondheim, and the paper that closed the argument was published in 2024 in a journal called Frontiers in Psychology. The finding is brutal enough that it should have changed every classroom on Earth.
The experiment was simple. She recruited 36 university students and put each one in a cap with 256 sensors pressed against their scalp to record brain activity. Words flashed on a screen one at a time.
Sometimes the students wrote the word by hand on a touchscreen using a digital pen, and sometimes they typed the same word on a keyboard. Every neural response was recorded for the full five seconds the word stayed on screen.
Then her team looked at the part of the data most researchers had ignored for years, which is how different parts of the brain were communicating with each other during the task.
When the students wrote by hand, the brain lit up everywhere at once.
The regions responsible for memory, sensory integration, and the encoding of new information were all firing together in a coordinated pattern that spread across the entire cortex. The whole network was awake and connected.
When the same students typed the same word, that pattern collapsed almost completely.
Most of the brain went quiet, and the connections between regions that had been alive seconds earlier were nowhere to be found on the EEG.
Same word, same brain, same person, and two completely different neurological events.
The reason turned out to be something nobody had really paid attention to before her work. Writing by hand is not one motion but a sequence of thousands of tiny micro-movements coordinated with your eyes in real time, where each letter is a different shape that requires the brain to solve a slightly different spatial problem.
Your fingers, wrist, vision, and the parts of your brain that track position in space are all working together to produce one letter, then the next, then the next.
Typing throws all of that away. Every key on a keyboard requires the exact same finger motion regardless of which letter you are pressing, which means the brain has almost nothing to integrate and almost no problem to solve.
Van der Meer said it plainly in her interviews.
Pressing the same key with the same finger over and over does not stimulate the brain in any meaningful way, and she pointed out something that should scare every parent who handed their kid an iPad.
Children who learn to read and write on tablets often cannot tell letters like b and d apart, because they have never physically felt with their bodies what it takes to actually produce those letters on a page.
A decade before her, two researchers at Princeton ran the same fight using a completely different method and ended up at the same answer. Pam Mueller and Daniel Oppenheimer tested 327 students across three experiments, where half took notes on laptops with the internet disabled and half took notes by hand, before testing everyone on what they actually understood from the lectures they had watched.
The handwriting group won by a wide margin on every question that required real understanding rather than surface recall.
The reason was hiding in the transcripts of what the two groups had actually written down.
The laptop students typed almost word for word, capturing more total content but processing almost none of it as they went, while the handwriting students physically could not write fast enough to transcribe a lecture in real time, which forced them to listen carefully, decide what actually mattered, and put it in their own words on the page.
That single act of choosing what to keep was the learning itself, and the keyboard had quietly skipped the choosing and skipped the learning along with it.
Two studies. Two countries. Same answer.
Handwriting makes the brain work. Typing lets it coast.
Every note you have ever typed instead of written went into your brain through a thinner pipe. Every meeting, every book highlight, every idea you captured on your phone instead of on paper was processed at half depth.
You did not forget those things because your memory is bad. You forgot them because typing never woke the part of the brain that would have made them stick.
The fix is the thing your grandmother already knew.
Pick up a pen. Write the thing down. The slower road is the faster one.
/goal is f*cking insane.
You can literally turn your AI agents into 24/7 employees that work for HOURS with zero manual intervention.
This has to be the most powerful AI feature release of the month.
If you try one thing in AI this week, make it this.
Godfather of AI: "If you sleep well tonight, you may not have understood this lecture."
This 47-minute lecture is the best thing I saw about AI in the last few months.
It will definitely help you understand how it actually works and where it's going.
Geoffrey Hinton built the neural networks behind every AI alive, then quit Google to warn the world about it.
The part nobody wanted to hear:
> AI is already developing abilities its creators didn't intend
> in most cognitive tasks it's already ahead of us
> the question is no longer if it surpasses us but when
> the only decision left is which side of that line you're on
Right now the average person opens Claude, types something, gets an answer, closes the tab.
They think they're using AI. they're using maybe 10% of it.
I went through his entire lecture, built a practical system from what he was describing.
18 steps to actually use Claude the right way, with copy-paste prompts that work today.
Full guide in the post below.
Hi guys
My account is about to cross 10k followers because the amazing @evfcfaddict shared it.π
To celebrate, I decided
1. I'll never again act like Austria is part of Germany
2. Made Alquiber a free post π»
Thanks Andy!