https://probplanner.com/ - I never had the time to dedicate to building a Monte Carlo simulator for project estimates. It was always something I just couldn't justify given my short commute. I used this project to teach myself how to use Claude Code and Codex over last summer.
I've done a lot of little things in Emacs since. Just minor things to improve my workflows or build up Chief of Staff type information flows.
Funny, I started vibing this (https://github.com/deangiberson/emacs-mux) yesterday on the train after playing with cmux for the day and thinking to myself there was nothing that emacs couldn't accomplish.
The repo doesn't quite work yet. Many sharp corners. But the basic idea is there.
pama, I'd be interested in hearing more about how you are using emacs for multiplexing. I'm trying to build up tooling for myself based around file and input workflows and I /really/ don't want to write a text editor and would prefer to stick with emacs.
I have time to code up little tools for myself and my team. I can now automate simple things quickly to improve workflow, like gathering all the modified tickets in the past 24 hours and writing them out in our daily sprint document (it's the process they want so I go with it). Am I directly contributing to the critical path code, no, but I'm able to understand more quickly. I'm a Sr SDM and have been divorced from daily code for several year, now I'm able to get a broad view of things more quickly. Even just the act of finding dependent packages removes a little friction which means I'm less likely to let it become a road hump.
I have a system that runs on edge services and captures everything to logs through FluentBit. Then there's a cron job that compresses, encrypts, and tries to send the logs to device specific S3 buckets. If the on device logs get too big they start dropping old logs first, with a heuristic for certain logs being more/less important. When devices reconnect to the cloud they start pushing logs as quickly as they can, the cloud infra backfills metrics as they arrive.
Once in S3, triggers start a series of lambdas to decrypt, decompress, analysis. Works well, easy to reason about.
The backend can easily be swapped out for something else. The harder part is the log compress/encrypt/rotate. It's important that you don't treat all logs exactly the same. Some are much more important and should be preserved over others.
I've done a lot of little things in Emacs since. Just minor things to improve my workflows or build up Chief of Staff type information flows.