Akshay
18.9K posts

Akshay
@ProgrammerMonk
Programming || Richard Feynman || Marcus Aurelius || Books || Minimalist || Tweets on Tech/Books/Work/Philosophy


Most Neovim setups look great in a screenshot but fall apart under real-world load: large codebases, flaky LSPs, and terminals full of competing tools. In this session, @ProgrammerMonk will explain his Neovim plugins choices to ensure the editor remains fast and predictable.










1. Error rate: Check 4xx/5xx spikes to see if the system is breaking under load. 2. Latency (p95/p99): Identify if response times are degrading.

You must create a sense of urgency and desperation.

how to study and learn really difficult subjects: 1. don’t panic. hard just means dense. it’s not impossible, it’s just packed. unwrap it slowly. 2. get a map before diving in. watch an overview video, read the table of contents, or skim the wikipedia page. you need context first. 3. use multiple sources. one book will confuse you, two will clarify, three will enlighten. 4. build intuition, not memory. visualize it. simulate it. code it. teach it to a friend or a wall. 5. tolerate confusion. you’ll feel dumb 90% of the time; that’s the price of learning something that rewires your brain. 6. connect it to reality. every abstract thing has a real-world analog. find it. relate it. ground it. 7. revisit the same topic after a week. mastery is not about reading once; it’s about returning after your brain has “chewed” on it. 8. don’t romanticize genius. smart people aren’t born knowing it. they just survived longer in the confusion phase. the truth is; learning hard stuff isn’t about intelligence. it’s about endurance, humility, and curiosity. you stay long enough in the fog until it clears.













