MrMatt

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?