Adhithya Ramakumar

New year, new website ✨ adhi.design

I love @stitchbygoogle! I'm using it a lot more than Figma now, and I get better output in most cases for my purposes.

@intelligibabble thank you!!! let me talk to the team and organize something!

@adhidesign i'm open to it! i'm not sure I will have any revolutionary insights to provide though :)

Good advice for coming months

@intelligibabble Makes sense! On a completely different topic: I'm very curious how your workflow has changed at Anthropic! If you find some time, you'd be open to giving a talk sometime to your old team on it?! 😁

any and all software. The goal is to harden as much as possible before a model of similar capabilities is openly available to bad actors. Which is just a matter of time. Mythos-level LLMs are extremely capable at finding and creating the exploits, whether the software has anything to do with AI or not. For example, an OpenBSD exploit was found, taking advantage of a 27 year old bug in arguably the most security hardened OS in the world for a few $1k of tokens.

@intelligibabble is this for any and all software? or just the ones exposed to LLMs?

wasn't meant to be a vaguepost! this is in reference to mythos/glasswing... Mythos is just the *first* model with this level of cyber capabilities. If glasswing works, there will be thousands of vulnerabilities and hundreds of exploits found in the most important software that exists over the next couple of months. patches will follow but take time. While we undergo this transition, reducing exposure will require that people upgrade software if it can't be done remotely by the vendor.

The Claude app is now in my health folder on my phone.

@csinco And so will generative UI be!

Like I said. Agent Manager is a UX pattern.

What happens when AI stops sitting beside apps as a chat bot, and starts to actually change how we interact with our devices? I made a video exploring my thoughts on the future of apps:

The reward loop to get things working is so short that I'm doing more things in parallel now. Staying up and working way longer. This fries the brain more. Also, its too active during sleep. Does this phenomenon have a name now?

@sciencegirl Prince of Persia!

For those who used a computer between 1995 and 2001, what's the computer game from that time that sticks with you the most, and why

ideas were always cheap. code is cheap now. best execution wins?

@csinco @saketme We're working on this to make lists a lot more usable.

@saketme I don’t think so. I think Swipe Actions were on the backlog forever but didn’t have a definitive spec from Material. In general, OOTB UX for lists in Compose is lacking compared to Swift UI List

Did Google ever release this swipe component as part of Material Design?

I predict that engineers move from IDEs to CLI mostly. Design and product move from docs to IDEs.

Hang on, I had /remote-control working until this morning. Now, I don't see the command pop-up anymore when I try it on Claude Code. I'm on the Max plan, so that shouldn't be the issue. @AnthropicAI @claudeai do we know why?!

This week I decided to just permanently switch to running Claude Code on the server mostly on bypass permissions mode: c() { IS_SANDBOX=1 claude --dangerously-skip-permissions "$@"; } And for the first time in my life I think I've actually managed to outrun my todo list What happened is I simply blasted through my to do list of features I had to build and bugs I had to fix I've never shipped so fast and Claude Code almost made no mistakes, and when it did it they were tiny that weren't fatal (important because I'm mostly working on the server in production now) Before I was always known to ship fast (also because I always work alone) but while I shipped new things would always build up on my features/bug board (my users can submit them there) But this is the first week where I've been fast enough to outrun them The board is actually empty! As other people have written on here the real bottleneck is becoming myself and my creativity, not how fast I can ship. Because I think I ship faster now than I can come up with new ideas, or maybe my brain will adjust to this new speed (probably) Also I feel another limit is becoming my own mental context window, as in how many things, features, bugs, projects, I can keep in my mind in parallel while building on all of them. It's a lot and I haven't reached that limit yet but I feel I might be close I also noticed that you start going really fast the more you let it just go loose, before I was slow because I didn't trust it and I was scared it would destroy my code, now I just let it go. As @karpathy wrote, things feel like they've changed a lot around December last year when models became good enough to really code with and I feel the same When I see other friends code with Claude Code I often notice they're slow because they still check everything, which is good of course, but I feel the better way would be to create some tests and just let it run freely and see if it can pass those For me the tests are mostly just me checking out if the new feature on the site works or not, and in 99% cases it just does, and then I ask it to improve it further Because I run Claude Code on the server in production, I don't have to wait for deployment anymore (although that took only 3 seconds anyway before, that still adds up), now it's wait for it to be done coding, I refresh the site and I test it, that feedback loop is how I work and it's made me WAY faster Anyway here's what I did this week and the majority of these things were requested by people on the bug board, I'd say this is about 10x my normal output: 📸 Photo AI - Built new image viewer and mobile image viewer - Added batch remix, multi-photo import, filtering by model in gallery - Security overhaul: phased out insecure ?hash= login, migrated to session tokens - Fixed Google login loop, multi-model selection, talking scripts - Added custom audio upload for talking videos - Created dynamic model selector from server endpoint 🏡 Interior AI - Revived [ Add furniture ] feature (started 6 months ago, image models now good enough) - Added custom style upload for redesigns - Built own Gaussian Splat viewer for 3D - Made /remove_bg endpoint for furniture backgrounds - Migrated 3D walkthrough to new World Labs API - Added .skp file support, paint color masking, empty room button 🎒 Nomads - Launched weekly AI-generated newsletter from chat - Built profile edit modal, moved profile editing from /settings to profile page - Added TikTok/YouTube links, status bar, server-side API tracking - Added hundreds of new profile tags and traits - Fixed timezone filters, broken links, user avatars 🗺️ Hoodmaps - Revived write mode (before was only read for last few years because db was rekt) - Built heatmap mode using sentiment-scored tags (50K+ tags) - Fixed root cause: tags not entering DB due to wrong PRAGMA (should be WAL) - Added good/bad area detection with admin grid controls - Set up Claude Code Telegram bot for live changes - Enabled CF cache, fixed health check, fixed Brussels 📕 MAKE book - Built auto ePub/PDF generator cron worker - Added dynamic generation with personal customer watermarks - Added image compression for file size 💾 Pieter .com - Added Wikipedia text-only reader for Kindle - Exploring Windows 3.11 emulator using v86 (to replace Em-DOSBox) - Added product recommendations on homepage - Installed Wall Street Raider (1986) 👩‍💻 Remote OK - Installed Chatbase AI customer support bot - Added "report not remote" link on job posts 🏨 Hotelist (3 todos) - Fixed hotel URLs and city range bugs - Added iron amenity

Wasn't there a reason we built stuff to mimic the terminal visually? Thinking everyone is moving back to the CLI is misrepresenting working styles.

The past few weeks, it's been efficient to exercise influence through quick, highly functional prototypes. This is the way design will evolve. Docs and slides are less powerful than just handing someone a working prototype.

It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December and basically work since - the models have significantly higher quality, long-term coherence and tenacity and they can power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow. Just to give an example, over the weekend I was building a local video analysis dashboard for the cameras of my home so I wrote: “Here is the local IP and username/password of my DGX Spark. Log in, set up ssh keys, set up vLLM, download and bench Qwen3-VL, set up a server endpoint to inference videos, a basic web ui dashboard, test everything, set it up with systemd, record memory notes for yourself and write up a markdown report for me”. The agent went off for ~30 minutes, ran into multiple issues, researched solutions online, resolved them one by one, wrote the code, tested it, debugged it, set up the services, and came back with the report and it was just done. I didn’t touch anything. All of this could easily have been a weekend project just 3 months ago but today it’s something you kick off and forget about for 30 minutes. As a result, programming is becoming unrecognizable. You’re not typing computer code into an editor like the way things were since computers were invented, that era is over. You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel. The biggest prize is in figuring out how you can keep ascending the layers of abstraction to set up long-running orchestrator Claws with all of the right tools, memory and instructions that productively manage multiple parallel Code instances for you. The leverage achievable via top tier "agentic engineering" feels very high right now. It’s not perfect, it needs high-level direction, judgement, taste, oversight, iteration and hints and ideas. It works a lot better in some scenarios than others (e.g. especially for tasks that are well-specified and where you can verify/test functionality). The key is to build intuition to decompose the task just right to hand off the parts that work and help out around the edges. But imo, this is nowhere near "business as usual" time in software.

Been working hard on this one for the past year or so! It's amazing to see Glimmer get the love! ✨❤️

Figma is too slow for me at this point. The debate of whether designers code is irrelevant at this point. Vibes all way ✨