been thinking how to add PostgREST to my stack.
since i already use Django Rest Framework.
but Today i realized it can replace the most tedious thing of DRF, writing serializers.
use Django for services, e.g., auth, email sending, job queue, etc. and use PostgREST to serve the API tied to the models.
there's still the issue of caching, tho 🤔
writing a new feature with tests takes a lot of time, but consistency and data integrity are things that pay off in the long term.
it just feels weird that at the end of the day what you complete is that a button does what i needs to do with a click, it feels like it's too little of an accomplishment.
Just realized that I ignore reels from brands and always try to consume content from people. And this is as default, from previous experience outside instagram.
It nails down to stories (literal storytelling) or what feels like a story (because most of them are faked now).
So it’s difficult for brands to market directly, but there are exceptions like Nuphy (mechanical keyboards).
But the entry barrier for a new brand is high. At least for a niche target in my demographics.
A small story every day. Steady progress VS big tiring sessions.
But first, I need to reply to the support emails 😅
I finally finished the migration from fastAPI to Django and with it a migration to a new database schema.
Budgetwise now uses double-entry in the backend. The frontend remains the same.
So Mint announced they are shutting down and that sent a bunch of users over to @budgetwiseapp but we aren’t ready so we moved it to close beta.
@josh please don't spread your htmx propaganda here thank you 😂
TypeScript junkie, Python hipster, and Golang wannabe | Product-focused Software Engineer building SaaS apps.