Nitin Dhar

I make http://catalytic.io/
Priority is bottom-to-top!

Know your queries (i.e., “what will I be searching for?”)
Know your indexes (i.e., “which fields will need to be looked up?”)
Know your data (i.e., “what are all the fields I need?”)
Build your schema!

Priority is bottom-to-top!

  1. Know your queries (i.e., “what will I be searching for?”)
  2. Know your indexes (i.e., “which fields will need to be looked up?”)
  3. Know your data (i.e., “what are all the fields I need?”)
  4. Build your schema!

Software/Product Engineering Interview Question Idea

Describe how you would build the software for a digital cash register for Starbucks.

- how would the standard features like payment work?
- What if in the middle of the order customer asks to load a gift card?
- What if a customer wants to use multiple gift cards?
- Can orders be edited after being placed in case the customer forget to order their favorite chocolate chip cookie? :p

Shortcuts!

Shortcuts is similar to .dotfiles that many people add to their Github accounts. With shortcuts I wanted to focus on terminal shortcuts to make my life and my teammates lives easier. I find each of us using different shortcuts to do the same thing (which is totally ok), but there are certain commands that we all run without any shortcuts, which is where this project comes in!

A People Dilemma

Two technicians work on a wiring project. Their task is to setup all the wiring for a tall business building! Quite a daunting task. Naturally two roles emerge as one takes up wiring the lighting, gadgets, wall sockets, emergency circuits, etc and other takes up figuring out where to get the wires from, materials, circuit blueprints, etc. Clearly both are important or at least it would be an endless argument as to which is more important. So, the day comes when all the wires have been purchased, the plan laid out and both the fellows get to work. Within a short period of just a week all the work has been completed and the desks start getting filled with the new employees. The employees are so amazed at their new lights, fancy tables with embedded sockets, awesome air conditioning, and the amazing placement of the power strips under their desks! A bunch of them want to express their gratitude and so they group up and seek out the technician that setup the sockets, switches, gadgetry. The technician loves to meet these co-workers and becomes friends with all of them.

Meanwhile, the other technician is trying to figure out how to untangle the mess that has been created, reevaluating the wires, triple-examining the circuit blueprints. As a result he is left out of the excitement and never gets to meet the people who he just built an amazing wiring system for!

A People Dilemma - how to give people recognition for the behind the scenes work / ground work they do. Just because some work is behind the scenes, or too technical, should we not attempt to make others understand the significance or the quality or the impact of this work? Is this not a human problem that no one tries to solve? Should we just accept that it is too technical and not even try to make people understand?

1 of 8
Load More Posts
Sorry, No More Posts
Loading...