Cross-posted from Goodreads
The book presents a collection of simple and neat ideas around how to think about managing your money. Notice my emphasis on “how to think about managing” rather than “how to manage.” I guess the title itself makes it abundantly clear that rather than discussing “proven” formulae for increasing your wealth it will talk about the psychological or emotional part of wealth management.
It’s much like how the book Never Split the Difference: Negotiating As If Your Life Depended On It discusses the various tactics of negotiating in the light of human behavior and emotions. So, rather than giving you step-by-step techniques to increase money, it tries to convince you to change your mindset and lifestyle in order to be wealthy. The author nicely backs his arguments up with some good real-world stories and examples. I found it thought-provoking enough to take away a lot of ideas for my own good, and note them down in my personal diary.
If I were to reduce the book to one or two lines, it would be this — the only way to get rich is to save more, be consistent and patient with your investments, believe in the power of compounding, and the ideal financial goal is to be able to do whatever the fish you want to do in life.
The postscript chapter on how the American economy became the biggest in the world through self-sustenance and internal growth is an interesting read. Not to be skipped!
I cannot be happier to write my comeback post to say that I’ve joined Automattic, the parent company of WordPress.com. A8C is an open-source-focused, remote-first, distributed company that has many other cool products in its arsenal, like WooCommerce, Gravatar, Day One, and Tumblr. I’ve joined the WooCommerce division.
Joining this wonderful bunch of like-minded people passionate about making the web a better place is a dream come true for me. This is my chance to work at a product company after more than 10 years of working at consulting/services firms. Product engineering is quite different from the mind-boggling pressures of life in deliveries. It was one thing sorely missing in my resume.
From product development experience, what I want to take away is:
- thinking in terms of creating high quality software directly for the end users rather than a creating custom software for handful of business folks
- meaningful impact made through software to a wider community
- getting paid while working on a popular open-source project 😜
- a feeling of pride when I could walk to a bunch of random people discussing a software and say, “hey, I am part of the team that created this software”
Automattic is a flat hierarchy organization where everyone is a software engineer, including me. So, there’s no manager, director, architect, etc. Each team does have a lead, but it’s not a higher-up or a special role. Having worked in hierarchies for over a decade, it’s a substantial change for me (which will need a bit of adapting) but one I am looking forward to.
I see my new role as an adventure with plenty of opportunities to learn, work without interruptions, live life freely, travel, and do what the flock I want to do. To know about life at Automattic and the various benefits/perks that come along, head over to our Work With Us page.
This is the second part of a two-part series.
This episode is hosted by AnuRock. In the last episode we were joined by Rakesh and Gautam to talk about micro frontends. We discussed the origins of micro frontends and dissected its various integration approaches. Today we will continue our discussion with Rakesh and Gautam.
- Micro frontends as default for all modern web projects?
- Micro frontends decision framework by Luca Mezzalira
- Horizontal vs vertical splitting
- Communication between micro frontends
- Pitfalls of using micro frontends
- Sparse checkout
- Tools to manage micro frontends: Nx, Lerna, Yarn Workspaces, Gitlab
- Libraries for micro frontends: Webpack 5, Piral, AWS Serverless Micro Frontends@Edge
- Special advice
Microservices with Nest.js (by Prashi Kapoor)
- Masala Labs (a book on culinary skills)
- Model-based testing
- The Code Breaker (a book by Walter Isaacson)
- Blockchain Revolution (a book by Tapscott brothers)
- Luca (a movie by Pixar)
Transition music courtesy https://mixkit.co
This is the first part of a two-part series. To be continued in Ep. 5.
This episode is hosted by AnuRock. Today we are joined by Rakesh and Gautam to talk about micro frontends.
Gautam Chadha is a hands-on Senior Experience Technology Architect, specialized in building high-performance web applications. He has architected enterprise applications for Financial, Retail and Hospitality clients. He has also worked in multiple implementations of micro-frontends and microservices in Node.js and demand driven design using GraphQL.
- What is a micro frontend?
- Micro frontends vs. library of components
- Independent deployability and testability
- Different approaches to stitch together micro frontends to create a unified application: client-side composition, server-side composition, edge-side includes
- Communication patterns
- State management
- How to compose a page with a couple of components from Frontend A, one from Frontend B, another couple from Frontend C, and so on
- Microservices as an inspiration model
- Core/Platform vs. Domain teams
- Backend for frontend (BFF) strategy
Real-world case study of micro frontends including challenges (by Sudhir Madaan)
Transition music courtesy https://mixkit.co
This episode is hosted by AnuRock. Today we are joined by Manish to talk about performance. Manish is a Senior Architect Experience Technology. He is currently part of a digital transformation project in retail domain for an Australian client through an omni-channel solution to improve time of market of features across brands and channels in both B2B and B2C market space.
He joins us to talk about performance, an often ignored topic in web development but one that has the potential to make or break your business.
- Why is it important to make a website fast?
- Business/revenue impact
- User engagement/retention
- Customer acquisition
- Perceived vs. actual user experience
- Google WebVitals
- How does one make their website fast?
- Culture, mindset, shift-left
- Platform/framework level optimizations
- JS/CSS/Markup optimization
- Third parties
- Framework specific Issues and optimization – React, routing etc.
- Server side improvement during SSR
- Caching Strategies – redis, node in-memory
- Tools to measure performance: Lighthouse, WebPageTest, JMeter/Load Runner, Gatling
- Important metrics: LCP, TBT, CLS
- Lab vs. field data testing
- Reference web applications
- What the Buddha Taught (a book by Walpola Rahula Thero)
- The Psychology of Money (a book by Morgan Housel)
- Family Man (web series)
- Sport season (Euro Cup, French Open, Wimbledon)