sekasi

That is incredibly depressing to hear. I'm glad I operate out of another country if this is the case.

Second round interviews, after having passed a code test as well, I do exclusively with the team in question all present.

It's less of an interview and more of a meet and greet, and we spend 30 minutes talking about anything under the sun.

The team makes the decision from this point. I very rarely veto.

Candidates know this is the process, because I tell them about it before hand. Does that make sense?

Seems you've had some bad runs.

I can pretty much debunk 1 and 3 personally. Good companies and people take hiring very seriously.

"Not a fit" is another way of saying "We don't like you" in a strange way.

I stay far away from those sweeping personality statements personally.

I work in Australia, not in the US. I don't know the intrinsic legal differences here, but I do know a few things about my local market.

I feel really strongly about trying to help people improve, and it's really challenging to do that if you can't bring up the reasons for rejection. If you're being dicky about it "You're not good enough in memory management", that instantly makes people defensive.

If you're trying to help them forward and give them useful tips for improving their portfolio and skillset, the conversation is almost exclusively positive and 9/10 times I get a thank you very much in the end.

I've never had any issues in years and years.

I guess as long as you're being positive about it, and try to reinforce the shortcomings versus the positives it ends up being a good conversation. Always do it over the phone, email doesn't cut it.

I've done a LOT of interviewing, recruiting and ultimately a lot of saying "no" to people.

Over the years I've landed on a series of personal rules on how to do just that.

1. Always explain rationale around the No, to help them improve 2. Always let people down gently reinforcing positive notions as well, you never know what state of mind they are in. 3. Always respond to requests for more information

This takes me a lot of time in my professional life, but it's making me a happier person. Ultimately, it's people's lives you're dealing with. You don't owe anyone anything, but life is about treating people well.

Do you require a whole new device for frictionless shopping? I'm not so convinced that's the case.

Bold or irresponsible move? Not sure. Given the incredibly low profit margin of most non-iphone smartphones on the market today (I think the average samsung profit margin on a phone is $11) I can't help but wonder what the real source of revenue was planned to be.

Increased shopping through mobile? Make your android/ios products better?

It just never made any sense, but I guess many successful products don't make initial sense either.

How is it not rate limited? I don't understand why this is not a thing in every login activity everywhere. can someone explain one reason you might choose to NOT rate limit auth attempts? I don't understand :S

Can you elaborate somewhat? I'm genuinely curious.

Great post. I think what you're referring to is Buckminster Fuller's 'Knowledge Doubling Curve'.

I get a sense from your post that we're most likely roughly the same age and grew up in very similar circumstances. If you do get around to reading this comment, can I just ask;

Do you feel a sense of marvel at where things have ended up, or disappointment?

Thanks for a good read, as comments go.

The first Miyazaki film I watched was Spirited away. The moment I saw it I became a life long fan of his work.

I've been to the museum in Mitaka twice, seen all his movies and despite pushing 35, I'm just as amazed and gleeful watching his work today with my three year old.

I can't think of any artist that had a greater influence on me. Much love.

Reading that, I can't really see much difference between a much older approach called Multiple Buffering? (http://en.wikipedia.org/wiki/Multiple_buffering)

Happy for someone to point out the error of my thinking though..

Question: don't process names usually change between versions of individual apps? Seems a large task to keep all that updated.

When investing (time) into something like this I always try to work out how the business is going to be sustained. Like many of us, I've been burnt badly before.

I'd genuinely like more businesses like this to be up front with commercial plans just to give reassurance to its customers.

What I've heard on the grapevine on this is that it's used as a method to defeat internet censorship in countries that are subjected to said censorship.

Not sure if that's true, but just passing that on.

Why do you expect him to be some sort of super hero that continuously risks his own life to expose information to the general public when you do nothing at all but whine on a forum?

Got a bit of entitlement there do we?

Can someone living in the US tell me how this could be legal? Surely it's not?

A mate of mine once said you can rate the quality of a society based of the quality of their toilets.

At the time I shrugged it off a bit, but certainly there's a bit of merit to that statement.

Great way of putting it. I see Ruby in it personally, and loads and loads of C#, but I have heard the Rust thing before from other people.

I always wonder why I find things I don't understand so fascinating. It's the same reason I read in depth articles on cryptography and play the 'wikipedia rabbit hole' game.

Because it describes most primes, the ignorant part of me can't help but wonder if it does have anything to do with the magic that is crypto.. but I digress. Wikipedia might tell me more, brb losing eight hours!

Thanks for the share.

Very common solution to this is following:

Offer a 90 day code warranty period. Over those 90 days you'll fix (For free) defects in your application.

However, wild goose-chases like you're mentioning above will result in an invoice. Only problems originating from YOUR code will be covered.

IE: You spend 2 hours finding the issue they mentioned.

1) Problem exists in your code. a) You fix it, and you don't invoice them.

2) Problem is in another part of the system a) You invoice for the time spent.

This is by far the most far and reasonable way to look at this problem I reckon..

Is this a warrant canary?

No. Word lens doesn't have to use data. The glass version works without any connection whatsoever.

I'm not saying you're wrong.. but I feel this argument is getting a little bit old in an era where we're being filmed everywhere by everything from subway cameras to iPhones.

To me, one of Glass's biggest problem has always been its looks. But this isn't an iPhone on your head. We can't compare this to any polished products anywhere. It's a cellphone in a briefcase.

'Would you want a wearable computer on your head' ? - Answer will be no, generally.

'Would you like sunglasses that can do a little bit more than just being sunglasses?' - Answer is now not as obvious.

I've used Glass for a few months now and I don't think it's a consumer product as it stands.

It WILL be, but it's not a consumer product now. Think certain sectors and use them 'for a purpose'.

"Calling the Kettle Black"

I like how you didn't address his concern, but instead responded with a completely different concern. Good response. Five stars. Very helpful.

Applaud the efforts. Motion/gesture libraries in general are notoriously tricky to get right.

I am a little bit confused at the three gestures you chose in terms of 'launching' with. Recording custom motions and a good path to implement those could be incredibly useful, but I'm a little bit hesitant at the real world use of the 'knock' and 'backtap'.

Either way, signed up. Keen.

The use of backgrounds in that website make it a little bit hard to read stuff, by the way :)

What are the plans long-term for this?

Amazing summary, thank you for taking the time.