An ever growing list of things to revise everyday, because I want them to stay in my brain.

Heavily written by LLMs and my own brain-dumps.

Highly unpolished infodump. Not intended for public use.

I'm easily one of the top engineers in every company I've worked for or consulted. And have been regularly told this by heads of various departments.

Just that I never put any effort or focus into finding a good job at a good company. Just kept treating the job as a hobby. And that has led me here, and I am incredibly bored.

Having to study for interviews is a failure, and a pathetic state to be in.

Everprep exists to prevent this.

Daily revision of everprep keeps you warmed up.

I can be laid off in the morning and crack an interview in the same afternoon. There is no need for "I need 2 weeks to study".

That's the magic of being ready.

These notes are to be revised everyday. They will keep my knowledge sharp and interview ready. 24/7/365.
Once used to the info, revision barely takes 20mins/day, because maintenance is a very low effort thing.

If I think - "but interview questions don't correspond to real world skill" - then that's the failure of the industry itself.

If the industry is gonna gatekeep jobs with its interview games, then that's actually easy mode for me, and I'm gaming the industry back.

By narrowing the game, it has made it easier for me to get in even into positions I may not be competent enough for. It cuts both ways.

In choosing a more restricted game, the companies have ended up giving me (and people like me) a very distinct advantage.

Everprep. Everready.

Dump to process

• Executor tuning - Afaque

• DE system design - Afaque

• Delta lake

  • 6h
  • 3h
• Spark joins

• Dynamic partition pruning

• Spark 30 concepts - Afaque

Knowledge holes

Product sense

Metrics to start out with
- Engagement metrics
- Retention metrics
- Monetization metrics
- Activation metrics

Segmentation - segment problem across various dimentions
- Geographic, time etc
- Platforms (android, ios, web etc)

• spark

  • executor tuning concepts
  • data skew

• How lambda and kappa architectures work - in depth

Sys design stuff

Build data model for swiggy/zomato/ig/social media apps

Make star schema

Made some bridge tables for handling many to many relationships

Implementation of scd - practice writing queries for their implementation

Consider sources like cdc. Design system around capturing cdc ingestion, storage, transformation, building the data mart.

External resources dump

System design

• overall lectures
  • 2h lecture - Afaque
  • Sys design - manish kumar
  • playlists
    • System Design Interview channel
    • Jordan has no life - playlist - Systems Design Questions 3.0
• individual components
  • kafka - Piyush Garg - Apache Kafka Crash Course | What is Kafka?

Personal Notes for system design:

• Alex Xu's sys design book wasn't good
• HelloInterview is not always correct

• DEDIA is a great book

• data modelling

  • Airbnb Data Warehouse Schema - Data Engineering Mock Interview

Leetcode

Solve at leetcode or neetcode

• Leetcode inspiration (leetcode is fun yo!)
  • I SOLVED 750 LEETCODE PROBLEMS and here's what I've learnt
  • My Brain after 569 Leetcode Problems
• Peng Cao's profile

Misc

Must know:

• big o intuition
• arrays/binary search/ strings
  • 2 pointers etc
• hashmaps/sets
  • count freq, grouping by key, deduplication, checking membership
• sorting and searching
• stacks and queues

overkill:

• graph algos