Anyone can start a job board these days. Software-wise anyway. The difficult part is having a targeted audience that employers are willing to advertise their job listings to.
So try to avoid making that same mistake. Building a job board without an audience.
To build a successful job board you either need perfect timing (e.g. start a remote job board a few years ago), great marketing that differentiates you, or an existing audience (started as part of BetaList) to promote it to.
Wait, where does you code go if you don't commit it?
On my local machine. With git setup. No commits yet.
I think I’ll commit once the MVP gets done. 🙂
Whoops. Probably because you received an email about it?
Providing a (paid) self-hosted service might be a way to guarantee the service stays around. Especially if it's self-contained, and easy to deploy and maintain.
Thanks, Marc! This is super helpful. Very good point regarding the tendency to keep projects without attention instead of shutting them down.
Regarding the periodic screenshot-ting idea — what is the main purpose of having those screenshots? Is that mostly for sentimental reasons or to use them for some other reason?
I think with a subscription fee it would be possible to make that project profitable and sustainable. Such service can also provide a way to download the archive of all assets at any time. At least that will guarantee that no snapshots/screenshots are lost. Periodic screenshots can also be automatically emailed to the site owner.
I would like an archive of screenshots for all my websites.
But for me there's never a defining moment where I shutdown a site. It's more likely that I stop developing a site and eventually something breaks the page. By that time it's too late to take a screenshot.
So I guess what I'd rather have is something that periodically takes a screenshot of my sites. Then it's even useful when the site is still active. For example I'd love an archive of screenshots of all the iterations the WIP homepage went through. Even when WIP is still alive (and I hope that will be for a long time!), a service like you describe would still be valuable.
Would I pay for it? I think so, but only if I feel certain your service will outlive mine. I think that's the tricky part. You can promise the service will stay around, but that's different from a guarantee.
If you somehow can guarantee it, then yes I'd use a service like this. Especially if it continuously takes screenshots and is clever enough to throw away the near duplicates.
Providing a (paid) self-hosted service might be a way to guarantee the service stays around. Especially if it's self-contained, and easy to deploy and maintain.
Thanks, Marc! This is super helpful. Very good point regarding the tendency to keep projects without attention instead of shutting them down.
Regarding the periodic screenshot-ting idea — what is the main purpose of having those screenshots? Is that mostly for sentimental reasons or to use them for some other reason?
I think with a subscription fee it would be possible to make that project profitable and sustainable. Such service can also provide a way to download the archive of all assets at any time. At least that will guarantee that no snapshots/screenshots are lost. Periodic screenshots can also be automatically emailed to the site owner.
We have something like this already: wip.chat/@emerson/stats
I'm actually in the process of improving it as the current implementation is a bit rough around the edges.
Which version are you using? The one downloaded from GitHub or the Mac App Store version?
It's the Mac App Store version, Marc. Does that help?
Ah yes, I run into the same problem on my phone. Will fix!