Tejas Kumar

honestly, @cursor_ai has the best execution of context engineering ive ever seen credit where credit is due

did skills.md kill mcp (model context protocol)? a lot of people are talking about this so i thought this excerpt from the latest podcast episode might help distinguish these two concepts in ai engineering full ep in reply

if you've ever had trouble understanding mcp (model context protocol), i made a podcast episode that explains this. i hope it helps? (full ep in reply)

❗ llms are not agents and agents are not llms here's a clear explainer of what an agent is and how it compares to regular language models from the podcast for those who are feeling a bit behind full episode in reply

context engineering in ai is a thing because it's really just working memory optimization. both humans and machines have distinct working memory vs. long-term storage mechanisms. more on this in the podcast (links in reply) h/t @hubermanlab for a great episode on memory (also linked in reply)

every time i ask someone if they can be an ai engineer, they say "no because i don't know anything about machine learning" ...these are very different topics. here's an excerpt from the contejas podcast that clearly defines what ai engineering is full episode in reply

I just created a podcast episode I'm quite proud of: what is AI engineering and how to become an AI engineer. Links in reply.

the bar is so low.

how to get a job at your dream company: cold applying doesnt work anymore. just listen to how @mkrl.xyz got an interview at @supabase.com when they previously ignored his emails.

i think @vercel.com does devrel extremely well because it's more "build in public" than shilling. you don't need "devrel" in your title. you just need to build things youre proud of and share them.

Leetcode interviews don't make sense anymore with AI. Is it cheating or is it just modern engineering? Is tech interviewing totally broken? @mkrl.xyz and I discussed this recently on the pod.

Don't Idolize Tech "Superstars". They drink coffee and have bad days just like you. Stop putting senior engineers on pedestals. Great advice from @mkrl.xyz on the latest podcast.

If you're looking to network effectively at an event, always leave the "mouth" open. Here is the Pac-Man rule explained by @mkrl.xyz. 👻

Got the Sunday Scaries? Stop trying to "relax." Anxiety and Excitement are the exact same biological signal (high arousal). The only difference is the story you tell yourself. Don't calm down, get ready.

Steve Jobs wasn't the best coder in the room. Neither is the person who just got promoted over you. The best communicators aren't always the smartest engineers—they are the ones who make you feel something. Here is the difference explained:

Want to know if you're actually listening or just waiting to talk? Try the 4 L's: Listen, Loop, Label, Lead. If you can get the other person to say "Exactly!" before you pitch your idea, you've already won. Full episode in reply.

no one cares about your reasons when the room is hot, tired, or checked out. instead, you communicate well when you do so with clarity and brevity: short and sweet.

Stop rambling. If you can’t summarize your thesis in one sentence, you don’t understand it well enough to teach it. Here is the template: "I believe [X] because [Y], so we should [Z]." Try it for your next meeting.