I think a big part of this discussion lost for a lot is a lot of people are trying to copy/paste how we’ve been developing software over the past twenty years into this new world which simply doesn’t work effectively.
The differences are subtle but those of
us who are fully bought in (like myself) are working and thinking in a new way to develop effectively with LLMs. Is it perfect? Of course not - but is it dramatically more efficient than the previous era? 1000%. Some of the things I’ve done in the past month I really didn’t think were possible. I was skeptical but I think a new era is upon us and everyone should be hustling to adapt.
My favorite analogy at the moment is that for awhile now we’ve been bowling and been responsible for knocking down
the pins ourselves. In this new world we are no longer the bowlers, rather we are the builders of bumper rails
that keep the new bowlers from landing in the gutter.
To be a little less vague - I think the biggest difference I’ve seen is where time is spent. In the past since I know what I’m doing I’d go straight into dev mode pretty quickly
.
Going straight into dev mode with an LLM pretty much always goes wrong - a lot more time is spent in planning and in setting up constraints for how an agent can operate before letting it loose so that once you set it free it can run.
I’ll take a stab after just reading documentation. I’ve been waiting for a good open source “wrapper” for Claude Code that allows me to run it somewhere and expose it as an API to be driven by a thin client elsewhere, and this appears to be that.
Furthermore, it exposes both the main session manager API, allowing it to spawn new sessions, as well as the API to chat with any given session directly. (Many wrappers allow you to wrap a single Claude code session in an API, driven by tmux under the covers, but don’t expose the meta-API to manage the sessions themselves)
I would use it to write a mobile or web client for my “agents” running remotely, either on sprites.dev, or on my MacBook over tailscale. (I currently use a mobile terminal for this, and have a list of Claude Code wrappers to try, but this “feels” like a cleaner abstraction primitive to build around.)
The above might be wishful thinking on my part, but hopefully the OP will correct me.
One usecase we have (we built it ourselves) is to periodically offload data from Postgres to lake house partitioned data on GCS. The way I see it this can now be done with a single query. Another one is the other way around to use posters as a query engine or to merge offloaded data with your live data.
Yeah, I totally abandoned Notion last year because it got too slow. The whole thing is pointless if it takes a minute or two just to navigate to the page I want. It takes a few seconds to do that on an archaic corporate SMB share.
Yes, I just tried using Notion again the other day after being annoyed with Obsidian Projects and even with only a couple entries on a notion database page, it took MINUTES to load, on web and on the desktop version. Uninstalled it immediately and went back to Obsidian.
I’m completely done with Notion now. It was great when it was new, worked well and did what it advertised. But now it has too many features and I feel its core functionality has really suffered.
Surely this could be addressed by putting more AI on top.
On a serious note, my team is very happy we migrated from Notion to Linear for task tracking last year, but we're still looking how to cover the wiki part.
I made a silly twilio app for my daughter’s 1st birthday party where guests had a set of photos in front of them and they had to guess the correct age ordering and could validate their guess to win a prize using the temporary number I had setup.
