If you are serious about ML Engineering, then you should buy this book.
Go into debt if you have to.
We will be discussing few chapters of this book in next week's space with @kmeanskaran, @Kashh56@shreyas_tweeets.
P.S. On a serious note, if you’re genuinely committed to learning but can’t afford the book, DM me. I’ll order it for 3 folks.
Let’s grow together.
First X Space 🚀 ✅
We talked about ML and shared our experiences. Hope it helped and answered your questions.
From next week, we’ll dive into:
- MLOps
- Technical Writing
- ML career insights & doubts
Thanks to @Kashh56@NotNotTushar@shreyas_tweeets for the great convo!
Flat hunt 🏠
Looking for a well-lit flat around Bellandur / HSR (close to ORR). Good locality and plenty of sunlight are must-haves.
And yes, if I end up renting a place you recommend, a treat at your favorite spot is on me.
Flat hunt 🏠
Looking for a well-lit flat around Bellandur / HSR (close to ORR). Good locality and plenty of sunlight are must-haves.
And yes, if I end up renting a place you recommend, a treat at your favorite spot is on me.
Anthropic 2026 Hiring Announcements:
May 19th: Andrej Karpathy
June 19th: John Jumper
July 19th: Alec Radford
August 19th: Jeff Dean
September 19th: Alan Turing (resurrected by Fable 5)
One way to think about your job security is to ask yourself how “prompt-resistant” is the work that you do.
Some activities are more prompt-resistant than others, and pivoting to the former can save your job.
In fact, trying to automate your own job is the right way to securing your future job.
Automating your own job will just you where the frontier is (so you don’t get rug-pulled), but more importantly it’ll give you extra bandwidth to build non-automatable skills that keep justifying your job.