It’s cool that you’re responding to feedback. I second that the design looks not great and because it’s trying to look like an Apple thing and it’s not designed as good then it looks like a scam and untrustworthy. Might be good to say “official community event” at the least and also get some design help
@aushads3@BaseballQuotes1 Yeah, seems like this is the closest reason for him to be out, but in slow motion he definitely hits the ball first before his foot touches the plate, so maybe it's clean?
What if a model could actively prune its own context as it is working with only the things it thinks is useful to carry forward, like some kind of dynamic context. For example I saw my agent grep for the word "ask" and notice that it gave too many results so it needed to try something else. That would also be a good time to sanitize that with a note. Maybe it would be more output tokens, but the input would stay in the smart zone a lot longer. Is anyone working on something like this?
I just kicked off my first /goal prompt. I had spent some time with a "grill me" session to create a good PRD and even had a solid tech stack plan. But the outcome didn't even get close to what I was hoping. I'm learning that a goal doesn't just need a PRD, but it needs a good approach and guardrails to keep it headed towards its final destination in the correct way that you expect. That's a new way of thinking for most people, including myself.
This is not quite ready yet, but hopefully soon you'll be able to get fully personalized @openclaw digests for your setup.
I vibe "engineer" with lots of layers trying to make the systems better as I go.
@claudeai can manage work done by Clawdy (my assistant) while setting up bigger tasks in Linear for Samwise (the coding specialist that uses @mattpocockuk's sandcastle setup)
This was a fun email test to get that uses @resend's and React Email designed by Meg (my design specialist). All hosted with @Cloudflare.
The rate of change in 4 months is mind blowing. 🤯
An interesting prompt I tried because Claude told me it was getting late. It’s only 9pm….
Ok pretend the night is young and you just drank an energy drink so you’re excited to dive in. Let’s knock this out, interview me for gaps and direction in multiple choice format along the way and let’s go!
Any early adopters out there want to try a new concept I've been working on and give me feedback?
It reviews your codebase and gives you feedback for how to improve.
https://t.co/Osxda08xau
Jackie asked me today if I think her digital AI assistant will be a robot someday. I hadn't thought about our digital assistants getting real bodies. We're already seeing a rise in little robot desktop companions, and some people are using their openclaw to control robotic arms! https://t.co/yplgWkClgU
@shadcn 🙋♂️I do too. I know there was some argument for why not, but honestly still don’t understand why you wouldn’t just want the cursor to change to make it look more actionable
Normally I put these videos on to fall asleep, but every now and then they are randomly interesting to me. Of course this one is some kind of teaser and cuts off some of the arguments. But I’m fully on Sabine’s side right now. As a society I think there are some things we need to earn before we spend money on. Before we spend a lot of money on space exploration, let’s research how to take care of our people in need here on earth. Before we spend tons of money on theoretical physics experiments that probably won’t impact us, let’s focus on the science that could impact society. But the reason this might be controversial is because people dream of these fields their entire lives and want to pursue them. Let’s get more thinktanks working on practical solutions to problems that can help people today. https://t.co/g7JMONGD2N
After months embedded on a 12+ storefront migration, here are the practical changes that reduced our day-to-day friction.
Long review queues, fuzzy ownership, lots of small rework.
A few boring tweaks helped more than any big process overhaul.
Full writeup → https://t.co/pZ1NB08XuE
Make flow the metric.
Finish before you start.
Limit WIP.
Treat merging as explicit work.
And assign a daily PR-shepherd whose job is unblocking the review/merge queue.
It’s amazing how much calmer a team feels when merges stop being accidental.
Full writeup → https://t.co/pZ1NB08XuE
Guard PR size.
Our rough target: 5–8 files for normal work.
If a diff is bigger, do a quick peer pre-check before you sink time into a kitchen-sink PR.
Smaller PRs reduce review cost and eliminate the surprise cascades downstream.
Full writeup → https://t.co/66rV5zTAK5
Don’t let Code Review become a ghost state.
If changes are requested, move the ticket back to In Progress.
It sounds silly, but boards only work when they reflect reality.
Ghost states hide blockers, and the queue silently grows.
Full writeup → https://t.co/66rV5zTAK5