Pinned Tweet
Just released my web app Super Simple Secret Santa! This was just a fun side project I did because I hate making accounts and downloading apps. It's completely FREE and stores NO data. Source code is public on my GitHub.
Shameless tags:
- video recorded on @cap
- built completely on @cursor_ai
- uses @shadcn components everywhere
- emails are sent and managed on @resend (react-email)
- hosted on @CloudflareDev free tier
- code is public on @github
- using @tan_stack by @tannerlinsley
- domain purchased on @Porkbun
- all icons are from @svgrepo with slight customizations to fit my theme
- demoed on @diabrowser
:)
Launching a new product in beta: PCOBooster!
I made it for my own church team, and I’m excited to see other churches start using it
If you lead a worship or production team, you probably know the routine in Planning Center: checking who’s available, who served last week, who’s already scheduled, then clicking back to the position you were trying to fill. I wanted all of that in one place... so I built it
Then I kept finding other things I wanted to make easier:
• Filling open positions with availability, blockouts, and serving history side by side
• Song transition recommendations from key to key
• Importing and transposing chord charts
• Finding songs we haven’t sung in a while
• Catching open spots, missing keys, and missing times before Sunday
Changes save straight back to Planning Center, so the rest of your team can keep working as usual
It’s currently in beta, so I’d love for you to try it out. Tell me what helps, what’s annoying, and what you’d like to see next. I’m the one reading the feedback and building it
Try it out: pcobooster.com
And if you know someone who’s always getting the team and songs ready for Sunday, pls send this their way!
(Independent project, not affiliated with @PlanningCenter )
Jake retweeted
Safari on iOS makes it too easy for your beautiful website to get clipped under app chrome and look terrible.
Here's how to fix it:
joshpuckett.me/seamless-mobi…
something that keeps bothering me is how some people see slop as something that is happening to them, like they're some kind of helpless bystander powerless to do anything about it
excuse me but you are a software engineer, you literally learned how to make sand think and make computers do your bidding?! and now you can't do anything about it? please
the 2 things you should know to cut through all the noise:
1. you need to give your agent a way to verify its own work (i just posted about this so won't rehash)
2. your codebase is memory
the 2nd is not new either, we have always had lint rules, compilers with good diagnostics and strong type systems, LSPs, etc to help us write better code. there is no difference when agents write the code instead, you just need more of them, and stronger ones.
forget rules and skills. you can add those later.
yes, your codebase is a form of memory to agents! agents love extending what already exists. so every nit and every annoyance you've ever seen, every mistake and bad pattern you observe from agents, needs to turn into a constraint, or the agents will just keep repeating those same mistakes like a virus in your code. then you keep observing and repeating this process until your codebase is locked down enough that even agents with little context can one shot a high quality PR.
an even better direction is to refactor/rewrite your code such that agent anti-patterns become categorically impossible. use type systems to your advantage, use libraries/frameworks that reduce the architectural search space, or heck, create your own framework like we did for grok bot and design high quality primitives and well thought out APIs
Was asked yesterday “do you recommend ChatGPT or ‘Cloud’ for AI?” I was confused what that meant at first, then realized they were talking about Claude
We’re still early.
the 🐐
Added two new skills to my skills repo recently.
/mobile-native - makes your web app feel native by doing stuff like disabling hover on touch devices.
/break-ui - tries to break your UI by adding long names, unusual emails, long lists, and fixes it.
github.com/emilkowalski/skil…
So apparently Codex Computer History uses ~ 7-8% of weekly limits while on the $100 plan?? Could help explain some of the unexpected usage?
I feel like Computer History went a bit under the radar feature-wise. Wonder if it's worth keeping on
Jake retweeted
Claude FM 🎵 music for thinking and building xitter.cf/i/broadcasts/1YGNrbqpR…
Jake retweeted
Linkdin is not real anymore 😭
Readers added context they thought people might want to know
Image is AI generated and contains a SynthID watermark. openai.com/research/verif…
















