Not exactly my project, but I have been helping a friend of mine work on his pet project for the last couple of months: https://limeline.app/.
He currently makes no money from it and has no intent on making any anytime soon, hosting cost are pretty low and it was pretty much just created out of a need we both had: being able to aggregate all our sources for our morning technology watch.
In the end, with feedback from a couple of friends, he built a simple "no inbox" RSS aggregator with some nice extra features (account-less page management, sharing & forking of feeds, ...).
It is still in a pretty early stage, but I really like where this is going and feels like it deserve more visibility.
Agreed, though I don't feel like a Full-Stack Engineer should do the DevOps Engineer job as seems to be required by this hiring manager. I am not saying you should not know the underlying component you are using in your stack though, just what you need to work on it, not how to administrate a large scale database deployment.
It seems that the world clearly lacks a definition of what Full-Stack Engineering really means ...
He currently makes no money from it and has no intent on making any anytime soon, hosting cost are pretty low and it was pretty much just created out of a need we both had: being able to aggregate all our sources for our morning technology watch.
In the end, with feedback from a couple of friends, he built a simple "no inbox" RSS aggregator with some nice extra features (account-less page management, sharing & forking of feeds, ...).
It is still in a pretty early stage, but I really like where this is going and feels like it deserve more visibility.