Rob Floyd - Eikon Digital Solutions

@bitphantom__ yes - it's been going on for at least an hour.

anyone having login issues with claude code this morning?

@dav @AnthropicAI well at least it's not just me - ugh

Spent the last 30 minutes failing to `/login` or `claude setup-token`. Fails in every way possible but what is consistent is every web page load is slow and the best I end up with is `OAuth error: timeout of 15000ms exceeded`. Help @AnthropicAI

@hodgetwins Say it all you want! I've said it too... but lately I've been listening to @sjkokinda and it's as though a veil has been lifted. He's draining the swamp and this is what it really looks like.

Not unless you want to be labeled a Democrat

@bcherny @ThePrimeagen i was hurting yesterday for a bit - but back to normal speeds! Thank you!

@ThePrimeagen 👋 We’ve been seeing insane demand the last few days, with a huge influx of new users straining our services. We’re here for it and are working around the clock to stabilize & improve reliability. More updates soon, should be feeling better for most people.

we are about to hit 1 9 of availability while coding is largely solved

@BoSnerdley Any video that is exactly 10 seconds long is immediately suspected AI. 6 seconds too. If it's in numbers divisible by 5 like 15, 20, 25... same thing. But the longer they get the more obvious the AI errors are.

Sure. How long did it create to make this AI fantasy?

But as a symptom of the ever growing divide in our country it's telling. I don't have a good answer to any of this: I pray that we stop participating in ideologic divides. Instead let's focus on the ties that bind - those that are rooted in our humanity and love.

At the risk of going into dangerous territory, I want to talk about the alternative halftime show at the Super Bowl. This will be short - we all have choices in how we engage with the world around us.

It's one thing to offer alternatives to a commercial event that really has little consequence to our daily lives. But it's another thing entirely to treat the State of the Union in the same fashion. Is this consequential? Not really...

I've sat through many of these addresses and eventually opted to read about the highlights after the fact. The theater of the event often times is worse than the worst of anything the Super Bowl has ever done. But here's my thought... (next post)

Clearly there was a segment of the audience that wanted to watch the official show and a segment that wanted to have an alternative option. We are now engaging in this kind of consumerism for the State of the Union - there's now going to be a 'People's State of the Union'

@david_gossett I cancelled Office account completely and get my mail through my MCP. :)

I just cancelled my MSFT Office 365 subscription and bought Office 2021 online. Beyond happy! Copilot and OneDrive were driving me nuts!

@DineshDSouza I’ve finally unfollowed you after yet again clicking on a conservative brief article. These clickbait titles and unreadable posts are stupid and you’re the only person I follow that posts them. Fixed.

Trump leaves with a 51-45 Senate vote!! Big win! conservativebrief.com/gop-accelerate…

@thenanyu Until you ask it to change a button in a CTA on a landing page and your whole site is redesigned and rewritten.

The real risk to SaaS is not that you can reproduce an app with AI. It's that the usecase is directly eaten. The clearest example is low-code website builders. They're directly eaten by Claude. No one needs to clone squarespace or wix. They just ask Claude to build websites.

@burkov These are the anti-norms that I celebrate. But people want to be grumpy so they cling to old workflows.

You only care about structuring in a human-readable way and understanding the code you put in production because many years of work taught you (via painful and traumatizing experiences): 1. You will be blamed if the code bugs. 2. You will be asked to fix it fast, often on Saturday. 3. Other humans will see your code and cuss you out for not being neat. Now imagine all your traumatizing memories are erased, no one will ever blame you for a bug, and you know no anal and grumpy human being will ever look at the code you delivered. What a relief, right?

@Prathkum you're reviewing your code manually, aren't you?

I’m amazed to see developers’ AI workflows: a lot of mcps, agentic workflows, multi-agents, and tool integration. Meanwhile, I use AI like this: give prompt, get code, review, and merge. 👀

@CatholicRob @tmornini @argosaki Did you know that the core of your ‘AI-slope’ bias shares social roots with religious and racial discrimination? Well now you do.

@tmornini @argosaki It's amazing how many of you like slop

BREASTMILK She thought she was studying milk. What she uncovered was a conversation. In 2008, evolutionary anthropologist Katie Hinde was working in a primate research lab in California, analyzing breast milk from rhesus macaque mothers. She had hundreds of samples and thousands of data points. Everything looked ordinary—until one pattern refused to go away. Mothers raising sons produced milk richer in fat and protein. Mothers raising daughters produced a larger volume with different nutrient balances. It was consistent. Repeatable. And deeply uncomfortable for the scientific consensus. Colleagues suggested error. Noise. Statistical coincidence. But Katie trusted the data. And the data pointed to a radical idea. Milk is not just nutrition. It is information. For decades, biology treated breast milk as simple fuel. Calories in. Growth out. But if milk were only calories, why would it change depending on the sex of the baby? Katie kept digging. Across more than 250 mothers and over 700 sampling events, the story grew more complex. Younger, first-time mothers produced milk with fewer calories but significantly higher levels of cortisol—the stress hormone. The babies who drank it grew faster. They were also more alert, more cautious, more anxious. Milk wasn’t just building bodies. It was shaping behavior. Then came the discovery that changed everything. When a baby nurses, microscopic amounts of saliva flow back into the breast. That saliva carries biological signals about the infant’s immune system. If the baby is getting sick, the mother’s body detects it. Within hours, the milk changes. White blood cells surge. Macrophages multiply. Targeted antibodies appear. When the baby recovers, the milk returns to baseline. This was not coincidence. It was call and response. A biological dialogue refined over millions of years. Invisible—until someone thought to listen. As Katie reviewed existing research, she noticed something unsettling. There were twice as many scientific studies on erectile dysfunction as on breast milk composition. The first food every human consumes. The substance that shaped our species. Largely ignored. So she did something bold. She launched a blog with a deliberately provocative name: Mammals Suck Milk. It exploded. Over a million readers in its first year. Parents. Doctors. Scientists. People asking questions research had skipped. The discoveries kept coming. Milk changes by time of day. Foremilk differs from hindmilk. Human milk contains over 200 oligosaccharides babies can’t digest—because they exist to feed beneficial gut bacteria. Every mother’s milk is biologically unique. In 2017, Katie brought this work to a TED stage. In 2020, it reached a global audience through Netflix’s Babies. Today, at Arizona State University’s Comparative Lactation Lab, she continues reshaping how medicine understands infant development, neonatal care, formula design, and public health. The implications are staggering. Milk has been evolving for more than 200 million years—longer than dinosaurs walked the Earth. What we once dismissed as simple nourishment is one of the most sophisticated communication systems biology has ever produced. Katie Hinde didn’t just study milk. She revealed that nourishment is intelligence. A living, responsive system shaping who we become before we ever speak. All because one scientist refused to accept that half the story was “measurement error.” Sometimes the biggest revolutions begin by listening to what everyone else ignores.

Fascinating trend I’m seeing in AI work. Engineers are eating up all of knowledge work. The most AI-native marketers? Engineers. The most AI-native writers? Engineers. The most AI-native ops ppl? Engineers. Because the technology is outpacing the tooling, I’m seeing engineers do non-engineering shit in Cursor and Claude Code that non-technicals aren’t dreaming of yet. It’s both fascinating and a massive opportunity to close the gap.

@bielok_ @pmddomingos You show me an example of how it’s wrong and I’ll show you how to break it down into the core primitives it’s based on. The expression of it may be new or novel - but it’s not original.

@Frapster @pmddomingos The proverb is wrong!

I’ve never seen an LLM come up with a new concept.

For context - my documentation consists of: vision document > research > roadmap (written for the LLM) > The rest of this is created by the LLM from the roadmap > documentation (canon) > runbooks (execution). I work to eliminate ambiguity in my roadmap in an iterative process - it's human facing language for the most part. I then iteratively have my CLI LLM build the documentation plan which is assessed for ambiguity and drift from the roadmap. Once that plan is done I ralph wiggum it to create my LLM-centric documentation which is assessed for drift to the roadmap and from section to section and more. After that I then have it build the runbooks in another ralph wiggum process again testing for drift against the docs/plan/roadmap. It's a LOT of up front effort that ends up causing my builds to be efficient and very 'run-til-done-able'.

Or maybe the way to look at it is who really needs to read documentation? Just prompt against it and define the scope of what you need to see. I started to build human-facing documentation but my NotebookLM of my platform's core code does a great job of answering questions and explaining things.

Your auto-generated API docs are useless. If the documentation doesn't explain why I should use an endpoint or how the auth flow works, you haven't documented anything. You've just listed your code in a browser.