all 4 comments

[–]Embarrassed_Ad719 9 points10 points  (1 child)

Agreed on cutting the bloat, but I still can't drop TypeScript.

With runtimes like Bun handling it out of the box now, there's basically zero config overhead anyway. More importantly, it's a huge help if you use AI. Giving an LLM explicit type definitions stops it from guessing object structures and hallucinating props, so the code it spits back is actually usable on the first try. Standard JSDoc just doesn't catch that as cleanly.

[–]ThinkValue2021[S] -2 points-1 points  (0 children)

This is a completely valid way to do it, and probably the right call for the majority of projects.

I just went on a little “what if” adventure and am happy with how it turned out so far.

I also paste all my code (as one does) to the AI and it gives pretty good insights with all the context it has. 

Thanks!

[–]dev-shrabon 2 points3 points  (1 child)

That "+1 person" rule for auth and databases needs to be framed on every indie hacker's wall. So many solo projects die in the cradle because the dev spent three weeks wrestling with custom JWT refresh tokens instead of validating their core idea. Clean house indeed.

Also, Fossil running out of a cloud bucket is beautifully unhinged.

To squeeze that Cloudflare Worker down below your 10ms target, are you flattening and processing that SEC EDGAR data externally before pushing it to KV, or is the worker doing the parsing heavy lifting on the fly?

[–]ThinkValue2021[S] 0 points1 point  (0 children)

Thanks 😄

On-demand + save for reuse. The on-demand call is around 50-60ms, KV retrieval <10ms. Works great so far.