Software Engineer, football ⚽, soup 🍲, chess ♞
Florida, USA
Joined October 2009
- Tweets282
- Following181
- Followers71
- Likes521
Juan Elosegui 🍲 retweeted
Confession: I’ve scrolled past dozens of comments on a PR just to find out why I couldn’t merge it. More times than I’d like to admit.
Agents have made this a lot worse. They push commits and leave review comments of their own, and all of it lands in the timeline. PR timelines have gotten dramatically noisier, and the few things you actually need to know get buried.
My team is rethinking the foundations of the PR experience around that problem, and today the first piece went into public preview. The new Overview page puts merge readiness and your next step right at the top. A summary catches you up on review activity, and you can filter the conversation down to unresolved threads. It’s opt-in and rolling out through the weekend.
This is a much-needed start, and there’s a lot more coming as we modernize PRs for the way software gets built now. If you try it, we’d love to hear what still sends you back to the classic view.
github.blog/changelog/2026-1…
Using #FigCraft to design the configuration UI for #mosaico tiling windows manager
github.com/jmelosegui/mosaic…
Juan Elosegui 🍲 retweeted
with current token prices i wouldn't really say "cost of software is going to zero"
our token cost is double our payroll which means even though we're 25 it's like we're 75
and i feel like our output is similar to a team of 75 pre-ai. we're just able to do it without all the downsides of a larger team
this is still a good thing. we couldn't hire 50 more people. so much overhead and impossible to retain a high bar
Tiling window managers don't have to be keyboard-only.
Mosaico 0.11.0 adds mouse support: bar clicks and scroll, drag-to-swap, drag-to-resize. #rustlang
github.com/jmelosegui/mosaic…
Juan Elosegui 🍲 retweeted
We're down to just 47 issues in the StyleCopAnalyzers repo, and almost all of them are new rule proposals. Vote up and down for them. Let's see which ones we should add support for.
github.com/DotNetAnalyzers/S…
A system should only become as complex as the problem demands. There is no reason to start with complexity. Doing so is a design flaw.
Mosaico 0.10.0 is out, a tiling window manager for Windows written in the #rustlang.
- Windows now animate into place when you swap, resize, or change layouts.
- Undock your laptop, come back, and every window goes back to monitor and workspace.
github.com/jmelosegui/mosaic…
This is now an open source alternative to #seq
Aspire 13.6 features, day 1
Dashboard persistence! 💾 The Aspire Dashboard now saves incoming telemetry to SQLite
🔄 Compare current and historical telemetry
🕒 Keep telemetry across dashboard restarts
🧠 Lower memory usage
📈 Higher default telemetry limits - 100,000+ items
ALT Screenshot of the dashboard run selector.
Stacked PRs + squash merge 😒
Even with a simple stack of 2 PRs, with multiple commits in each, my success rate getting everything merged is surprisingly low.
@github @shanselman
I built something like this using GitHub projects. The only thing I haven't figured out is the number of PRs to show (it shows all non-draft PRs that are ready for review).
We built this beautiful, vibe-coded app to manage the day-to-day operations of @aspiredotdev. The main thing it solved for the team over the default @github PR view is a *shared* view across multiple repositories. Individuals do not get to control the order, it is team managed (PS: Everyone seems to be bad at managing Github notificaiton noise).
We only show 10 PRs (max) at a time. This reduces the mental load of scanning through at 180 open PRs (or only looking at the most recent set). Knowing which 10 to show is always tricky and we keep tweaking it, but it's working well.
We also filter out draft PRs by default. With the advent of coding agents, we want the team to spend 20% of their time dreaming up big things but 80% working on the next milestone. Draft PRs are pure noise, prototypes and un-ready experiments. They should not distract.
The next policy we put in place is to make it so that PRs never show up for review until:
- Checks are green
- All review feedback is resolved
Unfinished work pushes the PR back into the individual user's focus queue and out of the shared one.
Cherry on top, we made it a PWA and added support for desktop notification so we can nag people (responsibly) for reviews.
cc @depoll 😅
Juan Elosegui 🍲 retweeted
Finally having to learn rust because more people are slopping out rust with AI 🤓
Juan Elosegui 🍲 retweeted
Go slow to go fast. Invest into infrastructure and developer experience. It’ll make your team more productive and happy in the long run.
Mosaico, the tiling window manager for Windows, v0.9.1 is out with a handful of bug fixes and performance improvements.
github.com/jmelosegui/mosaic…
#tiling #Windows11 #rustlang
Juan Elosegui 🍲 retweeted
We can do orders of magnitude more with agents, but it turns out that building bug free reliable software still takes a huge amount of effort. Now that we can do more, we have to much even more effort into making the software reliable.
You can see these companies crank out more features, but rarely are they high quality. You can feel the jank after the honeymoon phase of the first 5 minutes of use.
Mosaico is in town.
tinytooltown.com/tools/mosai…
Juan Elosegui 🍲 retweeted
Git worktrees are the new hotness now that agents can work on parallel instances of your codebase. What they don’t solve is the port conflict problem, that’s where aspire run/start —isolated comes!
#aspiredev @aspiredotdev
Aspire 13.2 introduces isolated mode, letting you run multiple instances of the same AppHost in parallel without port conflicts. @JamesNK shows us how the --isolated flag solves development and testing workflows. devblogs.microsoft.com/aspir…
#AspireDev
