731 karma · joined October 2, 2013
One difference is that I decided to stick with a raw Docker container rather than going with Replicated (who are really nice people, don't get me wrong). In my case, everything runs on a single horizontally-scaled server so it's pretty easy to get running "manually". Also, all the potential customers I asked said that they were comfortable managing their own Docker environment, and some would actually prefer to get Docker images since they'd be easier for them to manage than "virtual appliance" VMs.
Another difference was that I use Firebase for the app's datastore and Google doesn't (and likely never will) offer an on-premises version. This was a show-stopper for nearly all customers, but it turned out that offering at-rest encryption of sensitive data with a key that never leaves their premises was sufficient to get through many of the security reviews. This obviously won't be acceptable to everyone but it can be useful to know that even if you have a fundamental dependency on an external third-party service there may be a way to keep using it in your "on-premises" product.
That said, greenyoda does bring up some good points: time, risk, and quality are very much issues with the solo approach. But I see these more as opportunities to be addressed via new products or services as the number of solo development businesses grows...
Will they? I'd expect an autonomous car's doors to be under its control unless the passenger declares an emergency (which would be a Big Deal, call the police, etc.). Also, once autonomous cars are plentiful and transportation is dirt cheap, how many people will still be riding bikes in congested areas?
(Disclosure: I'm the founder of Reviewable.)
I wonder whether this is actually statistically true, if false positives cause true positives to be ignored by some non-trivial proportion of the population? I think it's just as likely this is legal CYA from the alarm makers -- they can only get sued for false negatives, after all.
Plus there's the fact that many official forms require a phone number of some sort, and it seems less evil to provide a number you own but don't answer than a random one.
(Disclaimer: I run reviewable.io.)
> By the way: I live in Europe and I haven't worked for one single company which would allow their developers to host proprietary source code with a third party SaaS provider.
Fair enough, companies vary widely in their acceptance of SaaS -- though Reviewable has plenty of European customers too. But to clarify, neither Review Ninja nor Reviewable (not sure about Omniref) actually host code themselves: they just access it through GitHub APIs without storing it. You can also deploy Review Ninja (and soon Reviewable) on-premises, though of course that means you're on the hook for administrating the system again.
It's really odd that you got a nil default diff range. I can't reproduce it with either anonymous or authenticated access. If you can, could you please open an issue with more details so I can debug? Thanks!
A lighter-weight SaaS like https://review.ninja, https://omniref.com, or https://reviewable.io (disclosure: this one's mine) might be a more appropriate solution. Specifically to the article's points, Reviewable has a nice reviews dashboard and will show inter-commit diffs within a PR (whether you're rebasing/amending or not), hiding any files with no changes since you last looked. Its default review completion criterion is that all files have been marked as reviewed by at least one person and there are no unresolved discussions still going on, but you can customize this to your team by writing a snippet of code to run against the review's state, e.g. to implement LGTM approval or even a voting system. Reviewable will also update a status check on the PR so you can enforce review completion before merging if that works best for your situation.
Best of all, because both systems integrate tightly with GitHub, there's no need to learn a new workflow or mess around with new git commands. Gerrit still has its place but I don't think it should be the tool of first resort.
(Edit: added mention of Omniref.)
Disclosure: I'm the founder.
Let me know if you need anything else!
Disclosure: I'm the founder.