@ireaderinokun@wizaj while you are learning you can really get a lot done without upgrading - tbh a lot of the time i hit a limit i can pause on generating code, write better specs or a work plan for next steps, take a walk, and then start again once the limit is lifted
@clairevo Totally - the technology has drastically changed but "normies" problems have mostly remained the same ... until the technology creates new problems for them
Introducing CallMe, a minimal plugin that lets Claude Code call you on the phone.
Start a task, walk away. Your phone/watch rings when Claude is done, stuck, or needs a decision.
Free & open source (MIT). Underlying API costs are cents per minute of call.
Vibe coded a game character selection screen
Everything here was made with AI tools
Nano Banana: character design + UI
Tencent Hunyuan3D: image to 3D
Gemini Pro: UI
More details ↓
been dreaming about this for a while…
imagine a personal agent that controls your mac from anywhere, chat to it from your phone, it takes action on your machine
built with cloudflare agents + raycast
would love someone to write long form on corporate dark arts:
1. snooping calendars effectively
2. managing up by secretly skip leveling
3. memos, and tactically scooping others memos
4. “boys” vs guys
the best companies run via obscene levels of corporate dark arts
PSA for a CTO, Head of AI, VP/Dir of Engineering, CXO:
This is going to be one of the most important "back to work" weeks of your career. You must get your team aligned on agentic dev ASAP. If you're feeling behind or overwhelmed, here are some good reads to get you inspired 🧵
@ryancarson@obsdmd@AmpCode how far do you think you can go without using task / issue software (Linear, etc)? Is that one use of Obsidian in this stack?
If you started using Claude Code over the holidays, you might be curious about how AI actually works, the benefits and risks, and where it's headed.
Here are some of my favorite papers on alignment, interpretability, and societal impacts 🧵
Today I handed Claude a document that I've been growing for...years on building an orchestrator/distributed runtime that I had only purely theorized possible. One we've been working towards.
It would have taken me probably months to code by hand. Building on 5 years of work and 10 years of experience.
Claude wrote all the code in Golang in 4 hours. I'd always actually wanted it in Rust cause I thought it would be easier to express, so I threw it in a loop with a "Rewrite it in Rust and make it as succinct as possible"
I went and ate a burrito. I came back and it was done.
That's the world we live in now.
@JustJake@bcherny@martin_casado@williamevanl Nice - so in those 4 hours with Claude on the first pass on Go code you built out the Core Architecture section and kept asking Claude to go back to complete what had been added?
@JustJake@bcherny@martin_casado@williamevanl I'd love to see that document and understand at what level it was spec'd. This is the context-providing magic we are all calibrating on