I Used Google’s New Gemini-Powered ‘Help Me Create’ Tool in Docs. It’s Great at Corporate-Speak - WIRED
I Used Google’s New Gemini-Powered ‘Help Me Create’ Tool in Docs. It’s Great at Corporate-Speak WIRED
Could not retrieve the full article text.
Read on Google News: Gemini →Sign in to highlight and annotate this article
Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
gemini
STEEP: Your repo's fortune, steeped in truth.
This is a submission for the DEV April Fools Challenge What I Built Think teapot. Think tea. Think Ig Nobel. Think esoteric. Think absolutely useless. Think...Harry Potter?...Professor Trelawney?...divination! Tea leaf reading. For GitHub repos. That's Steep . Paste a public GitHub repo URL. Steep fetches your commit history, file tree, languages, README, and contributors. It finds patterns in the data and maps them to real tasseography symbols, the same symbols tea leaf readers have used for centuries. Mountain. Skull. Heart. Snake. Teacup. Then Madame Steep reads them. Madame Steep is an AI fortune teller powered by the Gemini API. She trained at a prestigious academy (she won't say which) and pivoted to software divination when she realized codebases contain more suffering than any teac
How I Track My AI Spending as a Solo Dev (Without Going Broke)
I ship solo. No team, no finance department, no one reviewing expenses but me. When I started using LLMs heavily in my workflow — Claude for code review, GPT for drafts, a bit of Gemini here and there — I told myself I'd keep a close eye on costs. I had a vague sense of what I was spending. Turns out "a vague sense" doesn't cut it when you're getting invoiced. So I built a system. Or rather, I cobbled one together after getting burned. The Moment That Changed How I Think About This I was three weeks into a heavy coding sprint. I had Claude open basically all day — asking it to review diffs, explain errors, help me write tests. Normal stuff. Then my monthly statement hit. Not catastrophic, but more than I'd mentally budgeted. The frustrating part wasn't the money. It was that I had zero vis
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Models
Stop Explaining Your Codebase to Your AI Every Time
Every conversation with your AI starts the same way. "I'm building a Rails app, deployed on Hetzner, using SQLite..." You've typed this a hundred times. Your AI is smart. But it has no memory. Every chat starts from zero. Your project context, your conventions, your past decisions — gone. What if your AI already knew all of that? Here are five notes that make that happen. 1. Your stack, saved once Write one note with your tech stack, deployment setup, and conventions. Now every conversation starts with context. Now ask: "Write a background job that syncs user data to Stripe." Your AI reads the note. It knows it's Rails, knows you use Solid Queue, knows your conventions. No preamble needed. 2. Error fixes you'll hit again You spend 45 minutes debugging a Kamal deploy. You find the fix. A we
Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!