MrMatt

Flynn [1] is worth a look (having come from dokku). Heroku-like and runs as a cluster.

[1]: https://flynn.io

Yeah, that'd be expected (release of IP etc) however, if you're doing this out of a sense of duty to your ex-colleagues, and the business / management have shown a lack of respect for you up to this point, then I wouldn't be surprised if you see scapegoating.

My point was more that I've seen lots of problems attributed to the last engineer out of the door in the places I've worked. If liability isn't taken care of (sometimes there is a separate contract for liability & scope of work apart from the attribution of IP), and you're doing work to "do the right thing" then it may well be a case of "no good deed goes unpunished".

Be careful if you decide to do this. If you help out & don't have a consulting agreement / contract in place + the correct insurance, etc... then you may find yourself on the hook for any problems that can be pinned on the work you do after you leave.

Been in this exact situation myself a couple of times - one instance that has stuck with me was when >300 sites crashed within around 5 minutes of each other due to a time-sensitive bug.

This was my first job out of University, so I had the unpleasant pleasure of seeing both sides of the coin; my manager panicked, but the senior developer didn't. I got roped into a pointless panic-driven hunt for viruses / corrupted installs / whatever by my manager (at one point we were analysing the assembly code in DOS debug, for some reason), while the senior dev calmly reverse-engineered the crash conditions, reproduced the problem and found the root (a negative index into an empty array, written by the MD of the company).

It was on that weekend I decided to renege on my old panicky habits, and become the calm center of reason in the face of a crisis.

Indeed - will be interesting to see how this pans out, especially as Google already supplies the iOS mapping application backend.

I know they have to find candidates somewhere, but using a mailshot template to feign actual interest in a person is incredibly insulting.

Again, could you trim the number from the title of this post and have a glance at the guidelines, please?

Could you trim the number from the beginning of the title - the HN guidelines specifically guard against this sort of title:

> If the original title begins with a number or number + gratuitous adjective, we'd appreciate it if you'd crop it. E.g. translate "10 Ways To Do X" to "How To Do X," and "14 Amazing Ys" to "Ys." Exception: when the number is meaningful, e.g. "The 5 Platonic Solids."

Interesting stuff, but can you clip the number from the title, please?

How about a link to dismiss the about box? Once I've seen it, it just takes up space.

Excellent to see you iterating so quickly - are you split testing any of your design elements?

Thanks for the kind words - I think you may have saved the site.

I find climbing requires absolute concentration - it fills your consciousness to the point that you can only really think about the problem or route you're currently working, which is pleasant when it displaces all of the other things you've got in the back of your mind as a programmer.

I suppose this is a similar to developing a drinking problem, but far healthier.

Cool beans, cystan!

I'll get those posts up now :D Thanks for the feedback - I have a new design in the works, so I'll see if I can work in your suggestions.

I wasn't looking to threadjack here, but thanks for the feedback :) I'll have a think about that - the app did originally just get climbs in your locality from the web service, but I changed to the cache-only due to coverage problems. I'll see if I can come up with a hybrid.

I second your experience in getting traction for outdoor sports apps/sites.

My own site, Bouldr, has had a bit of traction, but nothing significant, and monetizing seems to be a really tough problem in this field. Our FB page has > 17K fans, and there are a few thousand registered users on the site, but it's got to the stage that I'm not really sure if I should continue the app (I'm going to for the time being, but the thought of closing up has crossed my mind more often recently). Dr. Topo closed for similar reasons.

Anyhow, if you like, I'll Tweet and post on our FB page about your app - hopefully you'll have more success than me :)

I have one of these (they're actually pretty good) it reorients so it always faces the wind and the shape gives you more coverage over your back when it's not too windy. Also, it looks awesome.

The handle is small though, so it's a bit uncomfortable when used for a long time.

Relative to what? Would it be OK if it were 15 things or 10? What about 5?

These sort of headlines have specific rules in the guidelines - I'm surprised it hasn't been changed already.

OK, so I get that a patent allows an inventor to protect their invention from exploitation, but I don't understand why a patent is transferrable - surely the idea is to allow an inventor to license the patent so that even if they couldn't realise a commercial product with their idea, they could allow others to do so, and still get something in return.

I could sympathise if Mirror Worlds were the originators of the patent, but as they bought it, then I get the impression that the whole thing stinks.

You going to be split-testing?

Looks like you need something like Delayed Job:

http://github.com/tobi/delayed_job

Not sure of an equivalent in PHP.

Clicky: http://purifyapp.com

I use Postrank (formally AideRSS) for this reason - BoingBoing have far too many posts for me to read, so I run their feed through Postrank, and get only the most interesting posts.

http://www.postrank.com/main - their index page is baffling.

Nope - I've read before that to move teams at Google, all you need do is say so, and you can move to whichever other project you want to - no questions asked. Not sure how any of the less interesting projects get done, but that's just what I've heard.

What was your company called?

clickable link: http://masterbranch.com

True, but the burdon of proof is on the prosecution. If they have proof, the they could sue, but this looks more like a flimsy attempt to gain information.

Mothball your startup (i.e. don't just kill it completely), and find another job.

I'd be very wary of a company that is that shortsighted.

This seems to be less about Mercurial vs Git, and more Jon Chu vs Git.

Although I haven't used Mercurial, all of the issues he brings up I found really easy to solve when I started using Git (~2 years ago). The number and quality of online resources has only improved since then.

Branching was a pain for me when using SVN - far too much hassle to keep on top of it all; All branches are visible to everyone and merging between them was slow.

With Git, branching is simple and really fast. It can also be done in such a way as to prevent your own personal development and feature branches from making it back into the central repo.

I've also found that cherry picking commits between branches and squishing small commits help me maintain the cleanliness of our repos (At no point in the history of our central repo is there half of a new feature or fix).

Only one of those screenshots is from the iPhone.