Amit Kumar

Opinions expressed here are my own and do not reflect those of my employer

Building & scaling Engineering team

Building an Engineering setup in Financial Services - I

First article of the series of 5 posts describing the journey to build Product & Engineering for Financial Services

Building an Engineering setup for a Financial Service Institution

A series of 5 posts describing the journey to build Product & Engineering for Financial Services

I have been part of building Product & Engineering teams and Digital Transformation setup for almost more than a decade. My first experience was during the build of MDL (McKinsey Digital Labs) by our leaders: Satty Bhens and Biju Bhaskar - a startup-like setup (for both engineering and business building) inside a large organisation. Both strongly believe in a garage-like setup and gave full support to establish guard-rails in protecting the culture of working as a startup.

Re-Engineer v/s Rewrite

A tale of choices you have to make when taking a decision

We are engineers (can be safely generalised to humans), who at heart enjoy building not extending/enhancing/improving Disclaimer: doesn’t mean we don’t enjoy extending/enhancing. I strongly believe in the philosophy of – You touch it, you improve it! This is driven by the fact - programmers think old code is messy as Joel Spolsky writes – It’s harder to read code than to write it Having said that, programmers use tonne of external libraries & modules to avoid re-inventing the wheel.

Guardrail-ed Autonomy

Instill gurad-rails for team autonomy

I haven’t written much in recent years, at least not through blog posts. I thought 2021, would be a good time to start penning some of my thoughts & learnings I have had in the recent past years. Team formation, functioning, reporting are the most common challenges every organisation have. Lately, I have been involved in discussions related to Team Autonomy. Hence, this article. Autonomy has different meaning based on context: political, medical, HR, organisation.

Managing multiple SSH Keys with Github & Gitlab

SSH Keys - multiple GitHub account, Gitlab accounts

I have always stumbled on this problem of managing SSH keys for multiple Git based SCM (Gitlab, GitHub) including multiple GitHub accounts. If you’ve single account - adding the SSH keys on your github or gitlab is simple. I currently have the following accounts: Github 1 personal account 2 behind the firewall (corporate accounts) Gitlab 1 personal account 1 corporate account If ever face a problem like this, it is best to create a ssh-config file which aggregates all your SSH keys.