An introduction to Big O using a non-computer science example.

https://abhyrama.com/2019/08/25/intuitive-introduction-to-big-o/

When faced with a production issue: \1. Do not play the guessing game of what the problem might be. \2. Do not try to work around the problem.

Reproduce the problem with the below: \1. Add observability interventions like log. \2. Zoom in by reducing the surface area of the issue.

If you want someone to do something make it extremely easy for them to do it.

A mantra for everyone to live by.

The best time to submit interview feedback is right after the interview when it is fresh in your mind.

What people claim they want and what they actually want might be two different things.

What people say and what they actually mean might be two different things.

If you build it they will come - said no person ever who built chat into an existing application.

Would you call a person who keeps changing her stand based on ground realities a turncoat or a pragmatic?

Dissatisfaction leads to progress.

Hard critical feedback is a must for growth. Be thankful to the one who gives you unflattering feedback.

If everything HAS to happen tomorrow, it will all be done next year.

Mistaking years of doing something with expertise is a common occurrence.

Deliberate practice leads to expertise, not JUST doing the same thing for ages.

HOW you say matters more than WHAT you say.

Avoidable and hard to avoid phrases - I TOLD YOU SO BEFORE ONLY.

We do not follow best practices, we follow practices which our brain tricks us into believing are the most convenient.

Result over process - said no successful poker player ever.

Wisdom is tough to measure.

One yardstick that can be used is whether one paints everything black and white or sees different shades of grey in things.

Practises outlive the context in which they evolved.