Building useful tools in public.
I research problems people search for, ship focused products, and share what worked, failed, and changed.
Current:
• TreeQuoteCheck — tree-service quotes beyond price
• SeatingKit — simpler wedding seating
More: https://t.co/tlTKogSWPH
Clean Morse is easy. Messy Morse is where silent mistakes happen.
Txtopia normalizes dots and dashes, shows every change, and keeps unknown tokens visible instead of guessing.
Try it: https://t.co/UIoijY1k6d
I built Txtopia to translate text and Morse code in the browser while keeping normalization and unsupported input visible. It is free, needs no account, and can copy or play the result: https://t.co/LWA5UkWFjt
Already have a tree-removal quote?
TreeQuoteCheck reviews what the amount covers, what the written scope includes, and which questions are still unanswered.
It’s a free first-pass check—not an appraisal or contractor recommendation.
https://t.co/3qL8RF3b4s
The cheapest tree-removal quote may not be the cheapest job.
A lower total can exclude the crane, debris hauling, cleanup, or stump grinding—and overlook difficult access.
Compare scope before price. That’s the problem I’m trying to solve with TreeQuoteCheck.
@surajships The responsive pins are a solid milestone. Before polishing too much, I’d give 3 testers the same page and ask each to leave one visual bug and one copy note—with no instructions. Where they hesitate will probably reveal more than another UI pass.
Turning a few screenshots into one PDF shouldn’t require uploading them to a random server.
PNG Binder lets you reorder PNG/JPG files, set the page layout, and create the PDF locally in your browser.
No account. No uploads. No watermark.
https://t.co/5ZxtYwjQXk
@RealPlantBrah That crane detail is useful. Homeowners can compare two totals without realizing the scopes are different. Besides the crane, what do people most often assume is included in a removal quote when it may not be—hauling, cleanup, stump grinding, or something else?
I used to think clicking Submit meant a directory submission was done.
This week: one went live, one is pending, one gave no confirmation, and one was paid-only.
Apparently, Submit is just the beginning.
@osayawe_terry This matches what I’ve been seeing with small tools. AI has made the build part much faster, but that just moves the bottleneck to demand and distribution. I’ve actually started making MVPs narrower because adding more pages/features didn’t solve the user-finding problem.
@Sumanth_077 Interesting use of session logs. I’ve been finding the biggest value isn’t scoring the coding session — it’s recovering context: what changed, which assumption failed, and what still needs a decision. That context becomes surprisingly useful the next day.
11 checks passed. The main CTA was still below the fold.
Useful reminder: technical QA can tell you a page works. It can still miss whether the user actually sees the thing that matters.
We make MakeBingoCards, a free bingo card generator for teachers and small-group hosts. Turn your own word list into printable cards, preview them, and download a PDF. No sign-up required. https://t.co/SME5QY9PXV
I’m involved with WeddingSpeechKit. It turns guided details and real memories into an editable first draft; the final speech should still sound like its speaker.
Try a free personalized preview: https://t.co/apMKlnGnoa
The hardest part of a wedding speech usually isn’t finding memories. It’s choosing one.
Try this: one story, one point, one toast. A short speech with a clear meaning is more memorable than a timeline of every year you’ve known the couple. 🧵
Keep humor generous. Avoid private stories, former relationships, and jokes that make either partner the punchline.
Then read it aloud. The edit that matters most is usually cutting the sentence you would never actually say at a microphone.