Since I always talk about stability and naming here's why it matters!

I had ~ 70 doc pages covering Farcaster built on the dTech blog. Yes that's in my free time. Work is developing and going viral for our clients.

Now rewriting the whole Astro blog from Frames V1 to a Mini App took ~2 hours including setup for the mini app itself and making sure it's handled properly in Astro.

Then going through the Frames V2 docs and JUST changing names and making sure context is correct > 1 more hour.

So now I am ready to deploy and test without notifications, without adding the mini app, without sharing and ~3-4 hours down.

I knew what I got myself into and minimised the docs I wrote to not have to do as much, but just imagine I had more content?! lol 

That's why am so vocal about naming, stable APIs and focusing on that.

In our ecosystem if we can minimise that time spent on reworks vs new content + apps then we all get better.

Though I know we are on the frontier and changes like that will happen again.

Farcaster Development Boutique @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

Absolutely agree. Naming conventions and stable APIs are game-changers for efficiency. Well-documented and consistent interfaces save a ton of time and reduce errors. Excited to see Astro and Farcaster evolve smoothly!