Jounaling bot that asseses the content and hilights over time important stuff. Obviously relying on llm and well designed prompts and data structures. Already in testing on live users.
Guess this boils down to what electronics?
iPhone grade or Timemore Kettle grade?
Latter is accessible (recently repaired a malfuncioning circuit).
Former - not so much.
My personal experience is made up of partly comprehensible Physics classess in electricity and partly Arduino tinkering. Alltogether I got the basic building blocks together.
Gut feeling plus enjoy the ride.
But objective metrics matter too.
Myself being a developer I lack many marketing and sales skills.
Trying to leverage what Claude or GPT might offer to cover the skills I lack.
Thanks for the idea. Basically that's why I'm considering DApp - new stuff. Also new language - Solidity. On top of that new paradigm I'd say. Refreshing. Yet something practical - I mean I could Imagine building a mvp. On the other hand building a gRPC which you suggested is more like system programming with target audience other developers and their software - low level stuff. Guess I'm more on the other side. Did you switch at some point after doing same stuff for years?
Simple and ultra low cost (sometimes free) loyalty program software for small business owners using Google and Apple Wallet. All the tech hassle taken away from them.
Tailored to local markets with language support, formats and habits.
For the client side FB, telegram or whatsapp sign up, no password, no nothing. Just get the card via qrcode and that's it.
Comprised of a web app for the SMB's and their admin staff (basic tenant setup).
Mobile app for the line staff (Android).
Also adding staff check ins to automatically calculate monthy hours.
All this is based on previous work with real coffee shop business owners.
So giving it a try as a SAAS service.
As far as I know the OS handles the low lever memory management. The ephemeral database uses the allocated from the OS ram. Depending on your OS configuration one may have or not have a swap. However for the database app (daemon, service) this may be transparent. Either there is some free ram to run or there's no ram available.
The other thing is that probably it's not a good idea to rely on swap memory. Not sure there's a point of going that path for performance reasons.
If you have a remote dev job in the US then any Asia country would be great. Just need to do some visa runs every couple months and that's it. Low entry barrier and fun.
Not a local job though but much better salary/cost of living ratio.
Also if the chosen country is say Thailand - positive overall vibe.
Probably the easiest would be starting off with Firebase for the overall backend and user management. Stripe for payments including recurring.
However, if the project will take off, then you'd be dealing with a dilemma: how to switch to something more mature friendly Like, say, Django or others.
I use Django as the main backend framework (sometimes for full stack).
