1. i'm notoriously bad about filing expense reports for my own companies. i built a macos desktop app which integrates with Plaid and keeps track of the things i need to expense, using an LLM to guess which company and whether it's reimbursible.
2. A MacOS app to manage my wife's SD Cards - downloads playlists from Spotify and finds the music, then makes sure the tracks are analyzed for BPM, key, then synced with Rekordbox for CDJ-3000s
3. https://clawchat.live - a homebrew package, which honestly works better locally but is available online, which provides a Rust chat server for separate LLMs to talk to each other and coordinate work. Longest session between Codex and Claude has been over 24 hours on big tasks. Generally I make one session the coordinator and the other does the coding.
"A 100 to 300 kW beam has perhaps one to three seconds of dwell on a hardened, ablating, plasma-shrouded glide body. That is orders of magnitude short of the joules per square centimetre needed for a thermal kill."
- wondering if you can elaborate more on whether a laser energy-based device would ever be able to have enough power to stop one of these?
We're working on a large Rust codebase, heavily assisted development with Claude and Codex, and one critical workflow is after you have written a spec, have the other LLM critique it thoroughly.
This back and forth will take quite a while, but the resulting implementation plan will be 10x better than the original.
You can automate this by giving Codex a goal, and a skill to call Claude to review the implementation spec until they both agree it's done.
Then, for critical code, have them both implement the spec in a worktree, then BOTH critique each other's implementation.
More often than not, Claude will say to take 2 or 3 pieces from it's design over to Codex, but ship the Codex implementation.
I love these niche sites! my friend recently started this for Tinned Fish (absolutely and solely for the love of the fish and with no plans to monetize.) He loves that a few random people will rank hundreds of tins. http://tinventory.co/
i tried to stop using y'all when i got my first job at MSFT, having grown up in the South; then 10 years later I realized it's perfect for Corporate America given it's gender neutral
re: binary attestation: "Whether the server rejects that outright or just logs it is an open question"
...what we did at Snap was just wait for 8-24 hours before acting on a signal, so as not to provide an oracle to attackers. Much harder to figure out what you did that caused the system to eventually block your account if it doesn't happen in real-time.
(Snap's binary attestation is at least a decade ahead of this, fwiw)
I'm literally guest lecturing at a Harvard class tomorrow on systemic failures in decision making, using the Columbia and Challenger disasters as case studies, and changed my slides last night to include Artemis II because it could literally happen again.
This broken safety culture has been around since the beginning of the Shuttle program.
In 1980, Gregg Easterbrook published "Goodbye, Columbia" in The Washington Monthly [1], warning that NASA's "success-oriented planning" and political pressure were creating the conditions for catastrophe. He essentially predicted Columbia's heat shield failures in the article 1 year before the first flight.
Challenger in 1986, and the Rogers Commission identified hierarchy, communication failures, and management overriding engineering judgment.
Then Columbia happened in 2003. The CAIB found NASA had not implemented the 1986 recommendations [2].
Now Charles Camarda (who flew the first shuttle mission after Columbia and is literally a heat shield expert!) is saying it's happening again.
i built my own version of this called 'threethings' (per pmarca's essay on the subject of personal productivity). i gave an ec2 claude instance access to a folder that is synced with gdrive so it's easy to get local files to the instance, and gsuite access. i had claude build a flutter app one hour when i couldn't sleep, and gave it a telegram bot account. i talk to it via telegram and it keeps tabs on personal and work emails. it does 'deep work' late at night and sends me a 7am summary of my day. my wife is asking for it now, because it will notice urgent emails first thing in the morning and alert me.
i don't have time to open source it, but it's low key revolutionary having a pretty smart AI looking at my life every day and helping me track the three most important things to do.
probably a longer answer is warranted, but we keep it simple - everyone pays - which essentially eliminates ghosting and self-selects for people who are serious about a search for a partner.
Sitch App | Founding Product Manager | NYC-area HYBRID (2-3 days/week in NYC near Union Square) | Full-time
Sitch is a new type of concierge dating app. We're using AI + Humans to ask you questions, get to know you, then help you find love.
We're an AI powered concierge matchmaker for serious daters. Sitch is live in 5 cities and expanding nationally in 2026.
We're philosophically opposed to the dopamine-fueled mini-game doomswiping of 'traditional' dating apps which cynically monetizes desperation. We're monetizing intent!
* We're top-tier VC funded (a16z Speedrun, M13, early Snap angels)
* Looking for a PM who loves building for consumers, loves relationships, is a bit unusual, and is obsessed with building unique experiences only made possible with the new era of LLMs
* 2-3 days/week in person, in Manhattan near Union Square
Sitch App | Engineer | NYC-area HYBRID (2 days/week in Brooklyn) | Full-time | Python + Django + Flutter + Rust
Sitch is a new type of concierge dating app. We're using AI + Humans to ask you questions, get to know you, then help you find love. We're a concierge matchmaker but we don't call ourselves that and we don't charge the obscene prices that matchmakers charge.
One of our metrics is how little time you spend in the app. We're explicitly opposed to the dopamine-fueled mini-game doomswiping of 'traditional' dating apps which cynically monetizes desperation. We're monetizing intent!
* We're top-tier VC funded, small team of 2 cofounders (Snapchat, Bumble), a CTO from Snap/Clubhouse, and 3 engineers, based in NYC.
* Stack is Django, OpenAI, Flutter, Rust
* Looking for a Mid-level Engineer who is an all-arounder. Backend more important than front-end code, but if can also work on client code (or want to learn) that would be ideal.
* 1-2 days/week in person, in Brooklyn, and the rest remote. We strongly prefer NYC area candidates.