Learn Everyday

Tenets are at the core of #Amazon culture. We expect every team to have them. Though I had drafted and used tenets in the past, but had not seen them being used effectively. While we use leadership principles (like ownership, earn trust, invent and simplify) in everyday conversations, I found limited usage of tenets. As a result, I had never dived deep into ‘Why’ they were there or how to raise the bar on writing them. So what are tenets? The standard definition is that it is a guiding principle or belief that helps teams align and bring everyone into an agreement around critical questions. The perspective I understood recently is that Tenets are a tool to reduce the *bandwidth of a team’s leadership that goes in taking decisions*. There are some decisions or tradeoffs where you can codify so that if any team member faces that choice in their daily work, they can take those decisions themselves basis the tenets. They know that if they go to any leader in the org - the de...

If you google, there are thousands of articles available on SOAP vs REST API. But it was a new learning for me.. hence posting First, what is API. Application Programming Interface or APIs are like a Window at the McDonald’s drive thru. As a customer if you order something - anywhere in the country - you will get the exact same thing. You do not need to care about how it is managed inside McDonalds. You just need to know the correct name. APIs are same - as long as you give them the information as per a given pre-decided structure or contract - you will always get a standard response. SOAP APIs Simple Object Access Protocol. It uses XML as the underlying protocol  to communicate across networks. XML is a very structured and as a result more complex way to communicate. Using the above McD example, It is something like writing your order, folding the paper, putting it in an envelop and giving it. REST APIs are simpler. They use JSON or simple URLs or web verbs like POST, GET to commu...

  “If you fail to identify and analyze obstacles, you do not have a strategy. Instead you have a stretch goal, budget, or a list of things you wish would happen”                                                                                                          -from the book Good Strategy/Bad Strategy

When you get feature requests, you should ask the following questions:  Why do you want that? What would that let you do? How are you coping without it? Is it a launch blocker? How would this feature fit in your day or process?

  Though I knew it conceptually , but started reading about cloud computing in a structured manner . Learnt some basic terminologies.  SaaS: Software as a Service These are the applications which any user can use it. Users can be individuals like you and me or can be large businesses. e.g. Notion or google drive or Todoist are software applications with certain set of features that we can use in our daily lives . But organizations can use SAP or Salesforce applications to set up their operational workflows . You can start using it with zero to minimal set up time. You don’t need to think about maintenance or upgrades — everything is take care by the application provider . Users: Individuals and Organizations IaaS: Infrastructure as a Service In pre-cloud times, we had to get all the physical infrastructure — like servers, storage, etc. The processing powers, memory was fixed and scaling up or down was a major effort . Now all this is available virtually . Some one has spent ...