Daily Edition

The Daily Grit

Saturday, February 28, 2026

Artwork of the Day

Artwork of the Day

Stairways built by no one's hand,
each terrace kissed in spectral light —
the earth remembers how to climb
through patient layers, slow and bright,
toward a geometry only metals understand.

Faces of Grit

Portrait of Phoolan Devi

Phoolan Devi

From the ravines to Parliament — the woman who refused to be broken

In the sun-scorched ravines of the Chambal Valley, a young girl from the lowest rung of India's caste hierarchy learned early that the world had already written her story — one of silence and submission. Phoolan Devi was married off at eleven, abused, kidnapped by bandits, and assaulted by upper-caste men who believed her life held no value. By every measure society had, she was meant to disappear. She didn't disappear. She became the thing they feared. Phoolan seized a rifle, gathered a band of followers, and turned the power structure of rural Uttar Pradesh on its head. She became a dacoit — an outlaw — but to millions of lower-caste Indians, she was something else entirely: proof that the crushed could rise. The Behmai massacre of 1981, where upper-caste Thakur men were killed in retaliation for her assault, made her India's most wanted fugitive. For two years she evaded ten thousand police officers across three states. In 1983, Phoolan surrendered — but on her own terms. She chose the time, the place, and the audience: ten thousand supporters and a portrait of Mahatma Gandhi. She served eleven years in prison without trial. When she finally emerged, she didn't retreat into obscurity. She ran for Parliament and won, twice, representing the very people the system had tried to erase. Phoolan Devi's life was not a fairy tale. It was violent, messy, and morally complicated. But at its core was something unmistakable: an absolute refusal to accept the story others wrote for her. She rewrote it — in gunpowder, in votes, in the simple act of still being alive when everyone expected her to be dead.

Trump Bans Anthropic from Government, Pentagon Designates It a Supply Chain Risk

After Anthropic refused the Pentagon's demands to remove restrictions on autonomous weapons and mass domestic surveillance from its AI models, President Trump announced a ban on Anthropic products across federal agencies. Defense Secretary Pete Hegseth escalated further, officially designating the company a 'supply chain risk' — a move that could immediately impact major defense contractors like Palantir and AWS who use Claude. Anthropic has stated it will challenge the designation in court. The standoff marks the most significant confrontation between an AI company and the US government over the ethical boundaries of military AI deployment.

Google and OpenAI Employees Rally Behind Anthropic in Open Letter

Over 100 Google AI employees sent a letter to chief scientist Jeff Dean demanding Google draw the same red lines as Anthropic: no surveillance of American citizens and no autonomous weapons without human oversight through Gemini. Separately, nearly 50 OpenAI and 175 Google employees published an open letter titled 'We Will Not Be Divided,' criticizing the Pentagon's negotiating tactics. OpenAI CEO Sam Altman told employees the company is working on its own Pentagon contract that would include similar safety guidelines. The letters reached the top of Hacker News with over 660 upvotes.

OpenAI Raises $110 Billion in One of the Largest Private Funding Rounds in History

OpenAI closed a $110 billion round on a $730 billion pre-money valuation, featuring a $50 billion investment from Amazon and $30 billion from SoftBank. The company simultaneously announced that ChatGPT has reached 900 million weekly active users. The round is one of the largest private funding events in corporate history and signals continued investor confidence in foundation model companies despite growing regulatory scrutiny and the Anthropic-Pentagon standoff happening in parallel.

Meta Signs Multi-Billion Dollar Deal to Rent Google's TPUs

Meta has signed a multi-year, multi-billion dollar contract with Google to rent Tensor Processing Units for AI model development, directly challenging Nvidia's dominance in the AI chip market. This comes just days after Meta announced plans to buy millions of GPUs from both Nvidia and AMD. Google Cloud executives have internally set a goal of capturing up to ten percent of Nvidia's annual revenue through TPU sales. The deal creates an unusual dynamic where Google simultaneously remains one of Nvidia's biggest customers while trying to erode its market share.

AI Music Generator Suno Hits $300 Million ARR

Suno, the AI music generation platform that lets users create songs from natural language prompts, has reached 2 million paid subscribers and $300 million in annual recurring revenue. The milestone makes Suno one of the fastest-growing AI consumer applications outside of chatbots, demonstrating significant commercial demand for generative AI in creative domains beyond text and image.

Google Quantum-Proofs HTTPS with Merkle Tree Certificates

Google unveiled its plan to secure HTTPS certificates against quantum computer attacks by fitting 2.5KB of quantum-resistant cryptographic data into a space previously occupied by 64-byte certificates. The solution uses Merkle Tree Certificates, with support already built into Chrome. The engineering challenge was significant: quantum-resistant certificates are roughly 40 times larger than classical ones, and the bigger the certificate, the slower the handshake. Cloudflare is partnering with Google on the transition to ensure the change does not degrade browsing performance.

California Law Mandates Age Verification on All Operating Systems

A new California law requires all operating systems — including Linux distributions — to implement some form of age verification at account setup. The law generated significant backlash on Hacker News with over 440 upvotes, with commenters questioning both the technical feasibility and privacy implications. The requirement raises particular concerns for open-source operating systems where the concept of a mandatory 'account setup' does not naturally exist.


AI is Rewiring How the World's Best Go Players Think

Ten years after AlphaGo defeated Lee Sedol, AI has fundamentally transformed the game of Go. Players now train to replicate AI moves rather than inventing their own, even when the machine's reasoning remains opaque. AI has overturned centuries-old principles and introduced entirely new ones. The technology is also democratizing access to training — more female players are climbing the professional ranks as a result. Today, it is essentially impossible to compete professionally without using AI, raising questions about whether the technology has drained the game of creativity or opened new frontiers for human invention.


An AI Agent Coding Skeptic Tries AI Agent Coding, in Excessive Detail

Max Woolf, a self-described AI coding skeptic, documented his journey from simple YouTube scrapers to attempting to port Python's scikit-learn to Rust using coding agents. His conclusion: Opus 4.6 and Codex 5.3 represent an order-of-magnitude improvement over models released just months earlier, and he has been unable to break them with complex tasks that would take months manually. The piece captures the frustration of trying to communicate genuine capability improvements to a skeptical audience without sounding like a hype promoter. Simon Willison was inspired to build a Rust word cloud CLI tool from his phone after reading it.


Claude Code Now Remembers Your Fixes, Preferences, and Project Quirks Automatically

Claude Code introduced automatic memory that persists across sessions, tracking debugging patterns, project context, and preferred working methods without manual input. Previously, users had to populate CLAUDE.md files themselves. The new auto-memory creates a MEMORY.md file per project, stores its findings, and retrieves them automatically in later sessions. Work through a tricky debugging problem once and Claude will not need it explained again. The feature is enabled by default and represents a significant step toward coding agents that genuinely learn from their operators over time.


Editorial illustration for r/AI_Agents

Openclaw vs. Claude Cowork vs. n8n

51 points · 20 comments

A practitioner asks whether learning n8n is still worth it when agent-first platforms like Openclaw and Claude Cowork can handle workflows through natural language instructions, automatically recover from errors, and skip the complex node-and-connector setup. The post captures a real inflection point: the people who most need automation are the ones who could never navigate n8n's interface in the first place. The discussion is nuanced — n8n advocates argue deterministic flows with explicit state still matter for production systems, while agent-platform supporters point out that the real gap is not backend sophistication but how agent behavior is presented to users.

n8n still makes sense when you want deterministic flows with explicit state at each step. The gap none of the agent tools solve cleanly: 'agent suggested the reply' is different from 'agent sent the reply and updated the CRM record.' That last-mile execution is where most platforms stall out.

— Founder-Awesome14 pts

The biggest gap isn't in the agent backend — it's in how these tools present agent behavior to users. Can the user see what the agent is doing, intervene when it's going wrong, control how much autonomy it gets? That presentation layer separates 'cool demo' from 'tool my team actually uses daily.'

— Friendly-Ask68958 pts

The compounding factor isn't that agent platforms are better at automation — it's that the people who most need automation are the ones who could never figure out n8n in the first place. English-based setups are finally making that group accessible.

— Leading_Structure_326 pts
Read full thread ↗

8 AI Agent Concepts I Wish I Knew as a Beginner

39 points · 8 comments

An experienced agent builder shares architectural concepts that separate prototypes from production systems. The key insight: spinning up an agent is easy, but real workloads expose recursive reasoning loops, stale context, and exploding API costs. MCP (Model Context Protocol) is highlighted as the universal plugin layer that standardizes tool integrations. The post also covers context management as the most common production failure point — agents stall not because reasoning is wrong, but because the context object going in is incomplete or from last week's CRM state.

Context management is where most production agents actually fail. The reliable pattern: assemble context first as a discrete step, verify recency, then reason. Treat context quality as a first-class engineering problem, not an afterthought.

— Founder-Awesome2 pts

I find myself using more skills than agents. Curious what your top 5 most-used agents are and what they do.

— shimbro2 pts
Read full thread ↗

I Built an Orchestrator That Manages 30 Agent Sessions at Once

29 points · 12 comments

A developer built a fully automated orchestrator that manages multiple Claude Code and Codex instances end-to-end, requiring human intervention only when something truly breaks. The initial version was in Bash and AppleScript before the agent self-migrated to a TypeScript monorepo. It connects to GitHub, BitBucket, GitLab, and Linear via Composio for complete SCM access. The comments raise the predictable but important question: how is the code quality when agentic coding runs unattended at this scale?

Serious question — how is the actual code quality coming out of this? In my experience, agentic coding left unattended produces horrendous code full of race conditions and bugs.

— Mordecus4 pts

You already know the answer.

— stiverino3 pts
Read full thread ↗

Editorial illustration for r/ClaudeCode

6 Months of Claude Max 20x for Open Source Maintainers

575 points · 68 comments

Anthropic announced that maintainers of public repos with 5,000+ GitHub stars or 1M+ monthly NPM downloads can apply for six months of free Claude Max 20x — the $200/month plan. Applications are reviewed on a rolling basis with a cap of 10,000 contributors. The post triggered immediate cynicism: the top comments frame it as a classic 'first hit is free' strategy designed to get open-source engineers addicted to the workflow before pulling it away. Others see it as a shrewd investment — getting the right people to adjust their workflows to Claude and build connectors that spread through the community.

Given free to get high-quality data signal from open source engineers.

— winfredjj116 pts

6 months is just enough to get them addicted and then they snatch the drug away from the maintainers. See through this move.

— LowFruit2558 pts

This is so smart. Getting the right people to adjust their workflows to Claude, build new connectors, spread them to the community. That investment will pay itself back many times over.

— Wickywire12 pts
Read full thread ↗

Trump Calls Anthropic 'Radical Left Woke,' Orders Federal Agencies to Cease Use After Pentagon Weapons Refusal

437 points · 117 comments

The biggest political story to hit the AI developer community: Trump labeled Anthropic a 'radical left woke company' and ordered all federal agencies to stop using their AI after Anthropic refused the Pentagon's demand to drop restrictions on autonomous weapons and mass surveillance. The post generated massive engagement with deeply polarized reactions. Many commenters expressed increased loyalty to Claude specifically because of the stance, while others noted the practical impact on defense contractors who depend on Claude infrastructure.

I was already using Claude a lot but this is now why I'll only use Claude.

— goalstopper28127 pts

Elect clowns. Expect a circus.

— No_Pollution9224107 pts

Keep in mind what Anthropic declined to do: 1) allow using their product for domestic mass surveillance, and 2) allow using their product to autonomously kill people. Just as a bit of context.

— AncientAspargus53 pts
Read full thread ↗

We Built 76K Lines with Claude Code. Then We Benchmarked It. 118 Functions Were Up to 446x Slower Than Necessary.

369 points · 123 comments

The team behind Codeflash, a Python code optimization tool, built two major features — Java language support (52K lines) and React framework support (24K lines) — primarily with Claude Code. The features worked and tests passed. Then they ran their own optimization tool on the output and found 118 functions performing significantly worse than necessary, with some running up to 446 times slower. The core finding: Claude Code writes code that works, not code that works efficiently. Nobody prompts for performance. The top comment with 188 upvotes asks the obvious question: why didn't they prompt for performance?

Nobody prompts for performance. Why do you say this? Why didn't you prompt for performance?

— BadAtDrinking188 pts

Why wouldn't you run optimization and code quality checks before releasing? No code is committed until it's run through several performance, quality, and security tools. You're just describing being a lazy vibe coder.

— ThreeKiloZero61 pts

My workaround: I add explicit performance requirements in CLAUDE.md — 'prefer O(1) lookups,' 'cache repeated computations,' 'avoid re-parsing inside loops.' The real gap is that LLMs don't profile. They can't know something is slow without running it.

— Stunning_Doubt_512352 pts
Read full thread ↗

Editorial illustration for r/SaaS

2 Months In. 1,486 Users. 320 Euro Total Revenue. Nobody Talks About This Phase.

121 points · 200 comments

A developer with a full-time job and a child built Loggd, a personal growth app combining habits, tasks, goals, focus timer, and gamification. After two months: 1,486 users, 11 paying subscribers, roughly 50 euro MRR, and 320 euro total revenue. The post is a raw accounting of the messy early phase that success-story posts skip — the silence-then-spike pattern where nothing happens for days and then 97 people show up randomly. With 200 comments, it struck a nerve. The consensus: this is what real early-stage SaaS looks like, and the fact that most people cannot get past 50 users makes 1,486 genuinely impressive.

This is the post that needs to be pinned at the top of every indie hacker community. The 'silence then spikes' pattern is exactly what it feels like from the inside. You start doubting everything during the quiet days.

— Extension_Strike37508 pts

It's 2026 and creating a tool is not a big deal. The only thing you need to solve is how to reach your target audience and convince them.

— Untapped_Etsy_List5 pts

We don't talk enough about patience and perseverance. These are the ingredients for success for many of us who were not lucky enough to become unicorns overnight.

— OldDamage61693 pts
Read full thread ↗

Customer Asked Us to Sign an NDA Before a Sales Call. Red Flag I Wish I'd Recognized.

78 points · 21 comments

A SaaS founder signed a mutual NDA before a discovery call, thinking it was standard enterprise protocol. The call was unusual — more questions about technology architecture and edge-case solutions than about the prospect's actual problem. They went quiet, never responded to follow-ups, and three months later a suspiciously similar product launched. The NDA did not protect methodological knowledge shared in conversation. The thread became a masterclass in sales-call IP protection, with the consensus being: if someone is more interested in how you built it than what it does for them, they are not a buyer.

I try to keep things higher level until there's real commitment. More about the 'what' and 'why' and less about the 'how,' even if they push.

— Most_Acanthaceae862421 pts

Reminds me of that one episode of Silicon Valley!

— dittdistriktreddit18 pts

If your product is easily copied to the same level of quality after a single recon conversation, then you never had a unique edge to begin with. If the copy is a shittier version, who cares — focus on building a great product.

— surfzer15 pts
Read full thread ↗

No Audience, No Money — How I Got My First 30 Paying Customers Anyway

70 points · 20 comments

With zero followers, zero testimonials, and zero inbound, the author closed 30 deals in six weeks through a simple method: 20 conversations per day with the right people. The approach was to search Reddit for posts where potential customers describe their exact pain in their own words — not product category searches, but the language people use when they are mid-problem. The key distinction: 'I'm spending 3 hours on this' signals someone in pain right now, while 'what's the best tool for X' signals someone in research mode who will disappear into comparison hell for months.

Did you track which of those 20 daily conversations actually converted, or is this survivorship bias? Six weeks feels fast enough that you might have just found a pocket of demand rather than a replicable system.

— Bartfeels243 pts

The pain-language search is the most underrated customer development step. Most founders search for their product category. The right search is the words people use when they're mid-problem, not mid-research.

— Founder-Awesome2 pts
Read full thread ↗

Editorial illustration for r/DigitalMarketing

10 Years in Digital Marketing This Year, 10 Things I Wished I Knew When I Started

24 points · 8 comments

A decade-long practitioner looks back and realizes most of what they thought was 'good marketing' was actually busywork with nice branding and beautiful PowerPoint slides. The key lessons: the best marketing strategy is the one you can actually execute, not the one that looks fancy. Data without action is just decoration — dashboards do not grow revenue, decisions made with data do. Teaching is the best way to learn. And the single most impactful takeaway from the comments: messaging and offer beat channel choice every time.

When the value is clear and the ask is simple, traffic converts. When it's not, no amount of tactics will fix it.

— gamersecret25 pts

Invite yourself to your clients' quarterly business meetings and truly understand their OKRs at a deep level. Map your work directly into their Objectives and Key Results so any stakeholder understands it.

— MichaelFusion442 pts
Read full thread ↗

CEO Is Adamant About No Text in a Hero Section. Says It's Bad for SEO.

19 points · 60 comments

A web designer at a digital marketing agency describes a Kafkaesque situation: the CEO — who cannot open a PDF — insists that H1 headers must not be placed over hero images because an SEO consultant once said something she misinterpreted. The CEO wants hero sections to be blank image strips with text placed below, which breaks information hierarchy and looks dated. With 60 comments, the thread became both a support group and a referendum on working under technically illiterate leadership. The Glassdoor reviews apparently all say the same thing about this CEO.

That's just... wrong. Like, flat-out wrong. Sorry you have to deal with that.

— TylerScionti22 pts

This made me feel better about myself. Your boss is an idiot.

— Vast_Veterinarian_8215 pts

The fact that she runs a digital agency while fully lacking technical abilities is kind of hilarious. If you like your job, just give her what she asks for and smile. If you're done, start looking — your talent and knowledge deserve to be valued.

— Own-Captain-80079 pts
Read full thread ↗

AI Is Great for Drafting Marketing Content — But Editing Still Decides Performance

5 points · 2 comments

A short but pointed argument that while AI has become the default first-draft tool for marketing content across SEO, social media, YouTube scripts, and blog posts, the differentiator remains human editing. The post positions AI as a productivity multiplier for ideation and structure, but argues that raw AI output consistently underperforms hand-edited content because it lacks the specificity, voice, and contextual awareness that drive actual engagement metrics.

AI handles the blank page problem. Editing handles the performance problem. Two different jobs.

— WritebrosAI5 pts
Read full thread ↗

Editorial illustration for r/Philosophy

Work Is Not About Earning a Living. It's the Fundamental Way Humans Exist Together in a Shared World.

433 points · 43 comments

An article from the Institute of Art and Ideas argues through Heidegger that work is not merely instrumental — it is the fundamental way humans exist together in a shared world. We are not detached thinkers observing reality but beings who exist by being absorbed in shared, meaningful activity. A post-work world, the article contends, would be a solipsistic nightmare. The comments push back hard: capitalism has transformed work into wage labour where the activity is secondary to being paid money to survive, and 'shared meaningful activity' describes almost no modern job. The highest-rated comment traces how physical labor, family, friends, and workplace have been progressively separated over centuries.

'Shared, meaningful activity' does not describe most jobs. Work now is about gaining the means toward securing future shared, meaningful activities. The ratio has tilted so far toward separation that the temporal-spatial boundary has ironically become the thing preventing the very communal existence Heidegger describes.

— Maximus_En_Minimus97 pts

Capitalism has transformed work into wage labour. It is no longer a communal activity for securing well-being. Now, the activity is often secondary to the goal of being paid money in order to survive.

— Institute1163 pts

It was Marx who recognized this, not Heidegger. He called it 'species-being' and it forms the basis for his concept of alienation and commodity fetishism.

— Distinct-Prize122624 pts
Read full thread ↗

The Instrument and Becoming: Applying Lavoisier's Conservation of Mass to Art

6 points · 1 comments

An academic paper argues that if Lavoisier's principle is taken seriously — nothing is created, nothing is destroyed, everything is transformed — then no artwork has ever been an 'original.' Every work is a node in a chain of transformations, and what specifies each node is the instrument used. The paper draws on four empirical regimes including dichroic prisms generating chromatic configurations no eye has seen, expired Polaroid film whose colorimetric analysis shows no two shots overlap, and a Python simulator carrying a film's chromatic DNA in a form that never existed physically. It engages Benjamin on aura, Simondon on technical objects, and Barad on new materialism.

The paper's core claim: originality is a function of the instrument, not a property of the object.

— Low-Alternative-66046 pts
Read full thread ↗