Every time I use Astra I have go back through and remove the extra silly text blocks it injects. It is as if the model constantly feels like it is has sell you everything it builds.
This is a big improvement over VoxType.
Made Hex available as a dictation option on Omarchy Dev. github.com/omacom/omarchy/pu…
Peanut butter Twix is superior to carmel.
I don't know we ended up a world where all you see is carmel.
I am still trying to figure out the next monitor. I have used a 32 inch benq for many years and the plan was 30+ inch 6k. But after a month or two using Omarchy and the semi-forced side by side view by default, I am realizing I rarely want to see two windows a the same time....especially when I am not comparing code to something anymore. But I also don't need a single window that on a 30 to 52 inch display.
Maybe I should just rob a bank and snag a Studio Display XDR.
That's a move.
Day 25/
We are doubling all usage limits for all Pro 100/200/500 tiers and Business Premium, effective today.
We heard your kind feedback and won’t be reducing usage limits for Pro 200, so your Work and Codex usage will stay the same. We’re also going to continue offering extended limits for dots for now, and usage of your dot will still continue to be separate from your default usage.
And we'll of course also keep shipping better models and other efficiency improvements that increase your effective usage over time.
On the topic of crushing it.....@bot has been fantastic as well. I have been offloading more tasks (especially deep research work) to it and the results have been top notch.
Last week, we removed the need for a developer account and X API credits to use the X connector in Grok Bot
Ask @bot to manage your bookmarks, go over your DMs, or draft an article for you free of additional charge
It is hard to keep up the pace of change in @t3dotcodes. @theo and team are crushing it.
It is the best mix of local and remote development I have tried. I agree with the sentiment that the future of development is remote, but that doesn't have to be VM (and it can be both)
Kudos to past me, creating a script and wiring this up to 1Password knowing current me would forget about it.
Like others, I’ve been re-evaluating how and what to run in CI.
I’m going to try this approach:
1. Simplify CI to only the highest-value tests
2. Run syntax checks, linting, etc., only on what changed
Then, in an Orb, I’ll run the important high-level end-to-end tests plus full syntax checks, linting, audits, etc., on a recurring schedule.
Agents can then address the small paper cuts (occasional flakiness, etc.) and flag anything major that needs human intervention.
For major changes, humans/agents can always run everything locally or trigger the Orb before deployment.
Not quite pushing directly to main (yet). It requires a bit more diligence, but I think this will make CI feel less like a chore.














