We are a Mumbai based home to office bus service marketplace. We recently ported our driver app to react native and the experience has been great. The app has been pretty well received.
We are trying to build a smart bus network to provide another interesting option in the mass transit space. Sort of like a uber but for buses. Efficient mass-transit is a huge engineering problem and one ripe for disruption. We believe the end game will certainly involve an api driven bus fleet. The challenge is absolutely massive and we're very excited to be working in it! Our current stack is Node.js / Rails / Angular.js / React.js / Postgres / AWS / Cordova. Furthermore, we're also looking for mobile developers with previous experience in shipping Android and iOS apps. We are keen to experiment with React native and rubymotion.
We offer a competitive salary, a good team to work with and a good office in Andheri West with lots of amenities. We just closed our first round of funding.
If any of this interests you, email me at anshul AT rbus.in
My instinct would have been to cool it in some liquid nitrogen at the university and just safely let the dry ice out... Glad they had a canal nearby...
I am not a linkedin employee but I wonder what an employee should do or in this case have done when business was insisting on developing such a feature?
Stir the debate, escalate it to management, make your co-workers aware of the wrongdoing. If it's shoved under the carpet, leave, maybe write a blog post.
However, most people care more about their job than their values and for that reason, remain quiet. As long as the paycheck's comin' in, u kno.
You've probably heard of a story like this before recently, just on a bigger scale.
I'd argue that software engineers are some of the most resistant people in the workforce to these kinds of moral high-wire acts. That's simply because they have way more job security than others. They can pick and choose companies with which they are in moral agreement and jump ship when something they disagree with is forced upon them.
That's because it's super easy to rationalize things like this. From the outside, hearing about Intro for the first time, our initial reaction may be "WTF?". But from inside the company it was a slow boil. You know that you mean no harm, and the people you work with are good people, and they mean no harm either. And hey, you're taking all these precautions like using separate servers, and getting security audit checks. And hey, isn't this a clever way to add a cool feature?
Before you know it, it's too late to say "no". Something that may have started as a good idea has transformed into a monster. Human cognitive biases will then kick into action and save you from admitting to yourself that you're part of the problem.
So most of the preconceived uses for their technology were already hashed out and approved prior to purchase...
Even if that wasn't the case, the technology needs to be integrated somehow in the form of a product.
So as a low level employee, what are you expected to do? Be known as a bad and difficult employee? Quit? Even if you quit, others will happily take your place.
As non employees of LinkedIn we can expose this behavior as unacceptable and deceitful.
Yes. And it is somewhat surprising. Matz must have rejected this idea a dozen times. It was certainly one of the oldest feature requests around. Hard to imagine what must have changed his mind. I've rarely seem Matz change his mind.
I seem to recall the issue was more with returning UnboundMethod objects than with symbols, but possibly what's changed is the fact that now symbols can be GCed?
Actually I took it to mean more like wordpress.com and WPEngine - ie. things that people can self host if they want to deal with the hassles of it all.
