aed
Joined 16 years ago
Joined 16 years ago
Giving yourself time to be idle and let a problem marinate is often where the breakthroughs and good ideas come from. If taste and human judgment are what separate useful AI output from slop, we need to give our brains time to cook instead of constantly bouncing between agents.
My heart sank when I saw this post. I thought we’d created enemies!
No conflict here, though.
Personal example... A few weeks ago, I realized that with all these agents running and all the things I could be working on, I was spending my days managing shallow pings instead of going deep.
I have AI agents managing SEO and ad spend. I used to spend a little time every day reading what each had to say. Now each gives me one detailed report per week, with links to the underlying reports and specific things I need to look at. I block 90 minutes for each one, on different days, and use that time to go deep. It’s helped a lot.
He and I will give this a spin this weekend.
Does this work for zips? Some zips have a leading 0.
I understand the risks with it but I don't care. I cannot fucking wait for the SaaSpocalypse to hit these companies.
They apparently also made a documentary about it, but I’ve never watched it.
I built a version of this in my org as a slack bot. It has access to BigQuery and I worked with it to document and define the key tables, so when a user asks a question it has a "library" to figure out how to answer it. Then it will respond directly in Slack (plus respond to f/up questions in the thread) and if it's a bigger/more detailed question it can create the report in Metabase and send a link.
One thing I don't have is the governance aspect, so I may give this a spin to see if this is a good middle layer.
I've done lots and lots of financial modeling/budgeting/forecasting in my career. The biggest drag is having to pull in actuals for the prior month, mapping them into the model, etc.
Just about a month ago I used Claude to build a set of scripts that pulls financial data from QuickBooks, operational data from BigQuery and pushes that all into our model in Google Sheets. The biggest pain was definitely connecting to QB because I had to create a developer account to get a key, etc.
I'm going to play with Svelte for some side projects. I've seen it mentioned a few times and I've been meaning to give it a test drive.
But as mentioned throughout the thread it's really just too much. My goodness they really could have a nice, profitable, business with simple software. I'd happily pay $10/month for the version of 1password from 15 years ago! It's just all too much.
A couple of months ago I worked with my 9 year old to have Claude build a little game with threejs. We’ve now got three levels with characters shooting silly string and banana guns. It was really fun to see him imagine something, have it show up on the screen, and iterate it.
Anyway, I tried building an LLM-backed workflow that could guide kids through the game creation process and kids can see their idea come to like (think: “sparkly purple unicorn shoots stars at a dragon”). I couldn’t _quite_ get it to work like I wanted so I shelved it pending future ideas/improved models.
No one has found it yet, but I built an undocumented endpoint around a cheat that I assume you placed in the game for One Laptop Per Child...
Also, will scrub the repo and make sure I'm careful about SC references.
Find me online at www.dunn.us