4 ms·
I keep revisiting this idea myself. I figured a suitable prototype would just let you : * Create a profile. * Record where you've worked. * Post small "upda
by stevekemp 11y ago
I keep revisiting this idea myself. I figured a suitable prototype would just let you :
* Create a profile.
* Record where you've worked.
* Post small "updates". Which would be visible to "connections".
That would be the core of the service and the job-hunting stuff would be kinda-seperate.
The problem is twofold: scaling and getting users. If you have no users then the system is futile (I setup a dating site once, which struggled due to lack of users. You join? No users in your city? Never return). On the other hand if you suddenly have 50,000 users you system will struggle if you're doing it on the cheap with a simple virtual machine. You need to plan for rapid scalability but assume you'll get none.
- vs2370 11y agoYes jotting down notes from this thread to build a MVP. Essentially I wish to target one particular vertical(engineers) or segment(students) of users. Also in case of engineers, let them import their github data or simply allow them to upload their work in files. Regarding the lack of users, I agree that deserted website is not ideal. But I think it should initially go from a individual centric website and organically evolve into a community