3 ms·
I agree that dealing with the front-end can be a drain sometimes, but unfortunately it's necessary for many types of MVPs that require a rich UI. Do you have a
by JohnnySpaghetti 10y ago
I agree that dealing with the front-end can be a drain sometimes, but unfortunately it's necessary for many types of MVPs that require a rich UI.
Do you have any such MVPs or projects you could share?
- adnanh 10y agohttps://github.com/adnanh/rye https://github.com/adnanh/rye - simple url-catcher on our slack channel (live at http://rye.hajdarevic.net/ http://rye.hajdarevic.net/) (Using slack outgoing webhooks + https://github.com/adnanh/webhook https://github.com/adnanh/webhook for catching the webhook and running a simple shell script that parses the slack message and extracts all URLs and then hits rye with curl to store and crawl them) https://github.com/adnanh/mikro https://github.com/adnanh/mikro - my personal micro blog that I mainly use to store interesting links (live at http://blog.hajdarevic.net/ http://blog.hajdarevic.net/) I'm currently working with a friend of mine on an MVP that we plan to offer as a service, and the source code is not open, but the stack is: React (JSX + ES6 + Webpack) + Tachyons for frontend, Ruby (Grape + Sequel) for frontend API, Golang for workers and processing, PostgreSQL as a DB and Redis for caching