• nshntarora

    @arkokoley Well, bitching is something that comes with anonymity. But, if not contained, it can be really dangerous. Secret shutdown because they couldn't control bullying on the network. That is something both of our projects are vulnerable to. Having said that, it's the same thing which makes it fun and better than others.

    The problem with Open Letters is, no company would adopt the idea until they see someone else using it. The famous chicken and egg problem.

    Btw! Loved your Github profile! (thanks for starring the repo)
    Even you're from Bangalore. Let's catch up sometime.

    posted in Product read more
  • nshntarora

    @rudimk Yeah! I'll be doing that this week.

    Where do I see it going?
    I don't know. It can go anywhere. It is just a simple app, I want other developers to add features, build clones and work on stuff that could help bring in the culture of open letters. Someone might clone it and build some cool shit over what I've started and start licensing it. It will be fun. The day I made it live, someone contacted me on twitter saying, "Open Letters is a company's own private Wikileaks".

    About using this thing,
    That would be great! Give it a try at your workplace, see how it works out and introduce other people to it. Also, to @santoshpanda and @paraschopra how about using something like this Explara and Wingify?

    posted in Product read more
  • nshntarora

    TL;DR
    https://github.com/nshntarora/OpenLetters

    Give a man a mask and he will tell you the truth.
    ~ Oscar Wilde

    I want to propose something.

    How about we start using open letters to communicate in our workplace?

    No, I am not kidding.

    If you aren’t on a covert operation by the CIA, or living under a huuuuuuge rock, you might have noticed a lot of open letters popping up in the news during the last few months.

    I definitely did.

    And to be honest; I like the idea of it. Sharing your thoughts addressed to another person, in PUBLIC.

    I got to thinking. Initially it was one of those stupid ideas (maybe it still is).

    How about we use open letters in workplace communication. The ecosystem is encouraging transparency (Cheers to the guys at Buffer and Groove), and I am learning ruby on rails, there couldn’t be any better time to do this.

    Every company, no matter the size, is making its processes more transparent to all of its employees. Heck! some have even made their processes and revenues PUBLIC.

    The sole reason behind all of this being,

    Transparency breeds trust.

    Initially I thought of building a global community where we could address a letter to someone’s twitter handle while staying anonymous (or not).

    Then I thought of associating the letters with company emails, people could have a healthy debate (with comments and hundred other features).

    Then it struck me, people could use Slack. They could share their opinion about a person or his/her decision on a team channel. This made a lot of sense.

    But slack has a problem.

    Identity.

    Take that away, and you will start to see the magic of Open Letters.

    I started working on this simple rails app in April this year, then forgot about it. Then, this week I ran out of stuff to do, I got to work again. Added some stuff and gave all of it a makeover.

    Use it at your startup, share it with the community, contribute a few lines of code. Heck! Correct my grammar in the README.

    Here is the link to the Github repository.

    Whatever you do, don’t take away the anonymity, it’ll take the spirit out of this piece of code.

    Note: Using Open Letters effectively requires a sense of responsibility among the people using it. As uncle Ben puts it, “with great power comes great responsibility”. So beware, you are playing with fire, don’t burn your house in the effort to heat it.

    posted in Product read more
  • nshntarora

    Every product has a USP, the unique selling proposition. The one feature that sets you apart from the competition.

    Imagine, you want to start an eCommerce store and your USP is one day delivery. Consider this USP to be the ball and all other things like the actual store, payment integration, design etc. to be the box.

    What do you build first?

    Most people try to build the box first and then put in the ball later.

    They are doing it wrong.

    With your MVP what you want is to validate is your USP. You want to know that are people willing to buy what is unique to your business?, competitors HAVE everything else.

    The appropriate approach here would be to first build the ball and then build the box around it.

    Taking the same example, first work on your logistics to make sure the one day delivery service works as expected. The rest of the stuff can be made later, you can just copy that from your competitors if you want :smiling_imp:

    What are your views on the topic?

    posted in Product read more
  • nshntarora

    https://github.com/nshntarora/Indian-Cities-JSON

    *After hundreds of unsuccessful searches for a rails gem to add the cities and states select option which could work the way I wanted it to, I gave up. Then, I began searching for a .json from which I could directly fetch the information and make it work, there too, I failed, I couldn't find the "perfect" file.

    So, I downloaded the largest Excel sheet of cities I could find, and converted it to a JSON. For me and for any "not a god" developer like me.

    Open citites.json and search for your (or your girlfriend's/boyfriend's) hometown and current location. If you don't find it, create a pull request :smile:

    posted in Tech read more

Internal error.

Oops! Looks like something went wrong!