Why subscribe?
If you are interested in topics of personal development, productivity, software engineering, people management, and anything in between, you would find this blog valuable.
I write short, atomic, and actionable micro-blog posts on macro-ideas. I promise to publish three times a week on Tuesday, Thursday, and Saturday.
Here is the table of content for this blog. I hope you find it useful. Looking forward to sharing more content with you.
Who am I?
My name is Mayank Verma. I have over a decade of experience working in the tech industry. In my career, I have played various roles starting from an intern to a tech lead. I am currently in a people manager role at big tech.
I am writing this blog to share everything I have learned (and still learning) in my various roles. My goal is to share actionable takeaways that can be immediately applied to any workspace. I am choosing engineering and tech as the means to drive these takeaways. However, they can be applied to any organization where there are people and processes.
I have iterated over these lists and improved them over my career. Until now these lists existed in my private notes which I shared with few close friends. Seeing how successful these takeaways have been, I have decided to share this with a wider audience.
I hope these takeaways are as helpful to you as they have been to me. If you find them useful, I encourage you to share this with your close circle of friends and family.
Note: The views and opinions shared here are my own and not reflective of the companies I have and work for.
Why is the blog called ‘Thinking Through’?
As an engineer, I was taught to think through every engineering problem. This meant
Reasoning with the problem.
Rationally and objectively evaluating the problem, and
Form an understanding of the idea before attempting to solve it.
Over the years, thinking-through has served as a reliable and successful mental model for solving problems. A model that I regularly fall back on. Every post in this blog is a problem I have tried to solve using thinking through mental model. Hence, it made sense to name it so.
