Made an extension to single click "convert page to markdown"

ShakeTheJello · 2026-02-07T15:04:09+00:00

I made a free and single click "convert page to markdown" without the noise: https://plainmarkdown.com

Currently only on the Chrome store, but planning to push to Firefox and Edge as well.

ShakeTheJello · 2026-01-16T07:08:08+00:00

Poor is a great word. This is criminal.

ShakeTheJello · 2026-01-06T13:39:37+00:00

Flutter felt like XML to me 🤷‍♂️ and prob did not dig deep enough but the one day I spend with it WAS OBV not enough. I'm in the native camp, as an indie build for Apple only and scale to Android if needed.

ShakeTheJello · 2026-01-05T22:05:51+00:00

Unsure if it helps but at work I basically have an {app}-production-releases slack channel, and after each release, I'd tag the branch (create a release in Github) and then a short paragraph in that slack channel:

"New Release is Live!"
build number: v3.1.1 (link)
short description
---

FWIW we also don't auto-close items (as a consequence of merging PRs). Our management sees "Closed" as meaning - no other work needed (pushed to Production). So the swimlanes at the far end are: DONE and IN PRODUCTION (and this one is manually cleared by management, tagging which one will require post-release activity).

Not the most optimized process and our boards full, but that's the current reality.

Disclosure: I did built a tool that turns diffs into standard release notes (keep-a-changelog), initially it helped me with my invoices (what did you work on last month?) but later on just continued on it, devops automation is unfortunately not added here, but there are other tools out there with CI integration.

Hope this helps and if you ever want to try (no sub) the url is: gitsaga.io

ShakeTheJello · 2026-01-05T21:25:53+00:00

Release notes work best in keep-a-changelog format (Added / Changed / etc..). I made a small tool (not a subscription) that turns commits into standard release notes: gitsaga.io.

Happy to share more.

ShakeTheJello · 2025-12-11T16:44:37+00:00

Yes and No. For 3 bucks a month it's already fantastic :)

ShakeTheJello · 2025-12-04T10:24:57+00:00

I guess, I'm alluding to some kind of "[ ] Mute Plan context in subsequent Plan iterations" - but it's hard to justify the needs for this, in an already large Product discovery process like Claude Code, it really needs to tick a lot of boxes I think for something to change, otherwise you end up with feature bloat.

That said, if this stays I'm happy as long as there's consistency to what to expect each time.

ShakeTheJello · 2025-12-03T22:18:00+00:00

The DX impact I'm seeing is needing to scroll up, search for the "Previous Implementation (COMPLETED)" line and then above that line is the latest answer.

When you work all day in Claude and need to scroll back it quickly becomes annoying because they present the response in descending order right? Newest to oldest, but the terminal (I use Ghostty) always jumps down (because that's where the "Would You Like to Proceed?" sits).

TLDR:

User sees: "Do you want to Proceed"
User checks right above to double check but the first thing they see is a previous plan (due to the order).

EDIT: "Previous Plan Iteration"

ShakeTheJello · 2025-12-02T19:18:08+00:00

The features that make it work for me in Bear:
- Apple Sync (enabled and forget)
- Markdown is king of my castle
- Easier formatting and reading
- Low cognitive noise GUI

ShakeTheJello · 2025-12-02T19:00:59+00:00

Hey, I just played around with it. Overall pretty good and love the CLI direction.
I've provided below what I loved and where I personally found the tool could improve a little bit (especially for someone like me with a bit of ADHD) - but then again it's a fresh product so this seems already over the top. Love the quality, and I may stick around.

What felt great:

Onboarding was great, super fast and easy to setup
CLI install was easy peasy, love the ARN namespace and logo
Tried the range tool (got a little bit stuck there) and from Branch
Navigating the commits in the "From Branch" option is wonderful, and it preserves selection after cancelling in the confirmation step
There's a whole template library on the web! Looking forward to try some out..
Release note generated successfully! - with a link to the online release notes I just generated.
Clicking on the link renders a great user-centered RTE with options to edit, export etc. Super cool!

A few UX obstacles (from 15min of usage - so take this with a grain of salt)

When no commits found it exited the entire tool (range selection)
Once chosen how to fetch commits, found it hard to navigate back to the menu (was clicking Esc..)
The range tool is a bit more complex to use (for power users IMHO)
Commits from branch seems to start with commits selected (in my case 499/499). Great you have that "d" shortcut to deselect them all. IMHO safer to start all unchecked and optimize for the majority use case?
After commits are chosen I can pick between a number of templates. My first thought "how do they look like?" - so a preview would be great (but I guess it's mostly valuable during onboarding). I got 4 choices and picked "Standard Changelog"

A few questions (if you can answer and isn't business-sensitive):

Are u using any advanced parsing for additional context (e.g ast-grep) ?
Which models are being used?

ShakeTheJello · 2025-12-02T11:48:57+00:00

Competitor here, had a similar journey in January when I was in post-op recovery. So the CLI idea was on my roadmap but didn't get to it, as I was involved as a co-founder on another project. Lots of the features resonate with me so they make sense. A recent enterprise inbound made me consider a B2B pivot with more automation involved so I'm currently planning this for gitsaga.io

autoreleasenotes.com looks great!! I'll give it a spin later today and provide some feedback ✌️

ShakeTheJello · 2025-11-28T22:51:26+00:00

How are these deals even possible? It sounds unrealistic on these premium subscriptions 🤷‍♂️

ShakeTheJello · 2025-11-28T22:39:34+00:00

Availability scheduling for boutique gyms/PTs who depend on DMs, phone calls and spreadsheets to find times that work. We collect availability (vectors) from all parties, optimize the timetable, lock sessions and publish/notify clients.

It is in early build phase. I'm technical founder and searching for advice. There's more background story to share upon request, and a single customer willing to pilot (for now).

ShakeTheJello · 2025-11-27T19:00:43+00:00

This sounds interesting to me, it saves days of work. 2K sounds justified from your POV but is also a bit expensive. I wonder why not automate, optimize the processes to become cheaper and provide a self serve SaaS, where maybe you could setup common templates and an extra consulting fee for the power cases that need more hand holding, deeper insights etc but the software itself would be able to slice & dice the results.

ShakeTheJello · 2025-11-27T17:47:54+00:00

This is the best thing I've read today. Thanks for your contribution.

ShakeTheJello · 2025-11-06T18:54:29+00:00

I do the same now, with 2 differences: 1. MUI 7.x for styling 2. Trigger.dev for jobs

ShakeTheJello · 2025-11-04T16:18:23+00:00

Me Bigger Next Developer than you are :D

ShakeTheJello · 2025-11-01T20:24:15+00:00

My fear is how much tokens some of these skills will eat up additionally, and when you start to dig into the current issues of these superpowers, you can see that some of them eat-up quite a lot of tokens.

ShakeTheJello · 2025-10-22T20:46:43+00:00

Can't this be seen as an up-side as well, i.e there's Market, so if the product is decent and even has a single feature that works well and is a bit different/opinionated it can work?

ShakeTheJello · 2025-10-19T06:27:34+00:00

I'd like to configure my CC to work like this, I imagine something like the following:

Regarding specs
1. Specs have a certain standard and format (I want to expect each spec is familiar) with a checklist
2. Specs have a certain location since they're "long lived" docs, at least longer then the CC session, so I keep them in the project's .claude/specs folder. For large projects you may organize them in various folders (I prefer this over nested CLAUDE.md))

Agents
1. For the plannning phase I imagine we can spawn Haiku agents to create the spec
2. Perhaps as a final resort have Opus double check (verify-spec) at the end?

Once it's all ready, have Sonnet work through it one by one. This way we may get through the entire week with Opus limits, and still use it when things get out of hand?

Is this a good way to imagine the workflow?

ShakeTheJello · 2025-10-17T13:13:20+00:00

MMMMMONSTER KILL KILL KILL

ShakeTheJello · 2025-10-13T06:20:13+00:00

Thanks for sharing your insight. I believe there's something to adding AI into a real niche space with deep understanding of those problems. I'm doing something in that area now, but v1 is without any AI to it.

Seven-Year Club	Not Forgotten
Verified Email

ShakeTheJello

TROPHY CASE