One of my perpetual problems with releasing software is that I hate writing for humans. Marketing blurbs, blogs, emails to the right people. It all sounds so easy when native speakers write or talk about it, but I'm so shy about this stuff that I'm never looking forward to finishing a project. Is there a low-cost service that will proof-read everything you do (not for grammar accuracy, but also tone)? The easiest fix…
Ask HN: How long did it take to release your side project in 2016?
31–40 of 47 posts
Re: Ask HN: How long did it take to release your side project in 2016?
#32I had the idea for the feature that would eventually turn into Unwaffle [1] back in July. It was initially just going to be an internal tool to track trial user actions for S3stat so that I could detect trends to predict who would convert on their own and who would need intervention. But it quickly became apparent how useful it would be as a product, so I built it that way from day one, with its own domain and API fo…
Re: Ask HN: How long did it take to release your side project in 2016?
#33I launched DesignerJobs (https://www.designerjobs.co) about three weeks ago: posted on HN a friday afternoon and got like 5 upvotes. I thought that was going to be it but someone picked it up on ProductHunt the next day and it ended up ranking #4 on there all weekend. I got plenty of traffic from there, realized I wasn't collecting emails (oops) or had links to social media (duh) and rushed to deploy the features. Got my first customer on Monday! From there, I contacted a lot of companies with open positions for designers and eventually added more sales, one after another. So far things are going pretty well, I've added features, companies and I'm trying to maintain growth.
The biggest challenge for me was/is marketing. I'm finding it's actually pretty easy to code and design anything, but marketing/reaching out/selling whatever you have is what truly separates having a website from having a business.
Re: Ask HN: How long did it take to release your side project in 2016?
#34Earlier quoted context omitted.
When I view your landing page, the graphics spaz out. Is that intended?
Yes. I wanted to try something a little different for the design. It's meant to give off a 'hacker' vibe (complete with a few Mr. Robot references).
Re: Ask HN: How long did it take to release your side project in 2016?
#35The tool is called Skeema [1] and it allows you to manage relational database schemas as code -- a bridge between git (or hg, svn, etc) and SQL DDL. You can use it to export CREATE TABLE statements from a DB to a repo, and then auto-generate and run DDL based on changes to that repo. Currently it just targets MySQL (due to personal familiarity, and the historic complexity with schema changes there), but if it's successful I could envision porting it to other DBs.
The open source CLI is still in alpha, but getting very close to a first release candidate. I've spent 9 months of working 5 to 25 hours/week on it so far.
Some unexpected challenges:
* Even for entirely text-based command-line tools, building a nice polished interface takes a lot of time! My goal has been to make Skeema's CLI paradigms immediately intuitive to users of Git and MySQL, in terms of option-handling, subcommands, and config file format. Even little things like exit code values, and STDOUT vs STDERR for different types of output, matter a lot for building CLIs that are friendly to pipelines.
* None of the existing Golang CLI/config packages were the right fit. After a couple attempts at hacking/forking popular ones resulted in overly-awkward code, I scrapped all that and wrote my own. I should have done that from the start, but it felt like yak-shaving.
* I eschewed unit testing at first, going with the common side-project wisdom of only prioritizing functionality. But as the codebase grew, I really wished I had spent more time writing tests from the start. I suspect it would have been a net time-saver vs the manual ad hoc testing I was doing initially.
Re: Ask HN: How long did it take to release your side project in 2016?
#369 months: January to September. It took 2 weeks after launch to get the first paying customer. The product is a SaaS progressive web app for budgeting. It's $12/year for the premium version. The main challenges were adding the last few features, making it production ready, and polish. The 80-20 rule really applied here (it took 20% of time to get 80% of the way), and that's only for the MVP! I still work on the app a…
Wow awesome job you have done there! Mind sharing how you manage to get your first client?
It is a side project though, and I'm not under pressure to acquire customers.
Re: Ask HN: How long did it take to release your side project in 2016?
#379 months: January to September. It took 2 weeks after launch to get the first paying customer. The product is a SaaS progressive web app for budgeting. It's $12/year for the premium version. The main challenges were adding the last few features, making it production ready, and polish. The 80-20 rule really applied here (it took 20% of time to get 80% of the way), and that's only for the MVP! I still work on the app a…
Re: Ask HN: How long did it take to release your side project in 2016?
#389 months: January to September. It took 2 weeks after launch to get the first paying customer. The product is a SaaS progressive web app for budgeting. It's $12/year for the premium version. The main challenges were adding the last few features, making it production ready, and polish. The 80-20 rule really applied here (it took 20% of time to get 80% of the way), and that's only for the MVP! I still work on the app a…