Hey @theo, @jullerino, @maria_rcks 👋 it's incredible how T3 Code has been good for me, and improves day by day in the past weeks!
Recently, I'm having a blast asking my threads to speak with each other and coordinate to share work more efficiently. Thanks for that capability!
Also, Theo said he missed Muse's shorter writing... I think what Ryan says here is key to overcoming the next frontier in agentic development.
We all feel the chat tax, don't we? We need more persistent means of communicating about our work.
I think we're going to see a new wave of interest in usability.
Chat is hard on the brain. Total opposite of what Don Norman wrote about. 100% holding in your head, remembering things, special modes, etc.
Nobody wants the stuff in their kitchen to be in a different place each time they walk in.
System of record + recognizable display are not going away. What's new is how fluidly we can change state WITHIN those as users.
Since moving to the unified X AI subs, Grok Bot no longer has its separate token allowance. I didn't realize this was the case until it was too late and my Cursor agents had used up all the tokens. Could Grok Bot protect what I need to safely end the week with my bots?
@mathieu_1224@guilippert_v4@theo Les crons, oui.
Le plugin, je pense que oui. Pour confirmer, tu peux installer T3 Code et essayer de te servir du plugin et tu sauras en moins de 5 minutes.
@vladquant@kepano One thought about markdown editors that don't do rich WYSIWYG...
They say they're *distractionless* and this never felt right to me.
Using them, I constantly needed to switch between the editor and the preview (or waste w/ split view), and I felt they are... *distractionful*
@vladquant@kepano The fact I could drag audio and video files and get proper embeds, from day 1, is what surprised me the most.
Dictation included is a nice touch for those who are not set up for it.
And you provide WYSIWYG live preview. I hate seeing markdown markup and switching modes. :)
@vladquant@kepano Impressive feature set for a first version!
Compares favorably to the very first version of Docs, Notion, DropBox Paper, etc. Of course, we're many years later and it follows their examples.
I'm a bit surprised you're launching this and I'll be happy to read the manifesto.
@mipsytipsy@JeromeMirc than to anticipate the many dozens of
OS/packaging/scripting/sdk/infra/process/auth/networking challenges
that will need to be solved, and
that will not necessarily be visible in the final set of parts of the solution that an external observer will look at when opining about it
Perceptions about the complexity of Dev vs DevOps
Some retrospective thoughts after many years in Development positions, and then in DevOps positions...
@mipsytipsy@JeromeMirc It's probably easier to imagine oneself
developing the domain of the software,
visualizing:
- what will need to be done,
- what kinds of issues will have to be solved,
and how long it can be, ...
@borkdude You seem to be validated by my morning's reading of the new edition of the thoughtworks Radar:
> we’ve continued to receive positive feedback ... from teams.
> ... much faster feedback loop with minimal compatibility issues, ... our default choice
https://t.co/5Er1UwOQIt