fescode ⁖ @fescode

Once you watch ALL THESE VIDEOS, System Design becomes ABSOLUTELY EASY:

Some thoughts on ownership I shared with the team this morning

My favorite @elonmusk quote that I often send friends: Do not fear losing. “You will lose,” Musk says. “It will hurt the first fifty times. When you get used to losing, you will play each game with less emotion.” You will be more fearless, take more risks.

x.com/i/article/2065…

@iam_smx *trillioniare

Your CEO should be strong. Your CTO should be wise. Your COO should be wicked, cunning, of mysterious origins, fluent in the dark arts, blurry in pictures,

Personal update: I've joined Anthropic. I think the next few years at the frontier of LLMs will be especially formative. I am very excited to join the team here and get back to R&D. I remain deeply passionate about education and plan to resume my work on it in time.

x.com/i/article/2055…

x.com/i/article/2038…

A “computer” used to be a job title. Then a computer became a thing humans used. Now a computer is becoming a thing computers use.

we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

the best job interview i’ve had was with @huggingface 🤗 more than a year ago. i got rejected but it was the best rejection of my life. here’s why: > i applied for a couple internships > the application isn’t checked by HR, but by real technical people > a round of interview, a take-home assignment to do whenever and however you want (only with a few hours time limit) > you actually get fast responses and next meeting update > i got rejected in the end but the guys who interviewed me @andimarafioti and @QGallouedec were the absolute best > Quentin told me i should apply later for a full-time role, and when i asked if i can have a meeting to get some feedback he said YES > getting a feedback meeting after rejection is the most rare thing in tech > he explained patiently why they selected another candidate (i was technically good but didn’t have much open source experience) > he suggested what i needed to work on > he answered any of my questions and wishes me luck > no hr, no bullshitting, no wasting each other’s time, absolutely professional even though i got rejected the internship i knew exactly what to work on: open source. ever since then, open source has been the only thing i did work on. ever since then, my respect for HF has been 10x-ed.

Chad Slime ® @ChadSlimeBased

6 months ago

Job interviews are just two people lying to each other

359 12K 145K 1.9M 3K

Computer Networking Fundamentals (mini-course) Everyone who wants to understand container and Kubernetes networking should start from the basics. This heavily illustrated free course walks you through the first two layers of Computer Networking: Ethernet and IP. A must for any developer or DevOps engineer who wants to build a solid understanding of computer networking before they move to the higher-level protocols like TCP, UDP, and even HTTP. labs.iximiuz.com/courses/comput…

This is the fastest way I’ve found to learn any new language or framework 1. Learn the fundamentals: basic syntax, semantics, and core concepts. 2. Code along with a real project (YouTube, course, whatever). 3. Build your own project without a tutorial. Just you, Google, Stack Overflow, and the official docs. Rinse and Repeat for every new stack you pick up.

Piyush @piyush784066

6 months ago

I’m learning Node.js backend and I’m a complete beginner. So can you guys suggest the right approach? Should I learn by building projects, or first clear my fundamentals through tutorials? Please share your advice.

89 15 392 86K 225

x.com/i/article/2016…

x.com/i/article/2015…

x.com/i/article/2013…

i’ve never been more inspired to become a better SWE i spend about ~45 mins a day coding with zero AI tools, learning documentation, browsing libraries benefits: > time to execution dropped by half, i have a sharper sense of what needs to get done, how it will look, and therefore get it done faster > less time debugging, AI’s make more mistakes than you realize if you don’t know what it’s actually writing. i stopped treating it like a black box > culturally inspired to contribute back to OSS. the amount of public libraries that hold up our world is fucking insane. contributions actually make the world a better place. still finding the repo that i feel alignment with i “learned” to code in college about ~3 years ago, and until NOW do i feel like i’m actually getting started

Dmitrii Kovanikov @ChShersh

7 months ago

So, is anyone still interested in becoming a better SWE? Or is everyone obsessed with AI agent orchestrators to build and sell your next SaaS and escape poverty as soon as possible?

402 72 2K 274K 361

x.com/i/article/2008…

A Final Message From Scott Adams

keyboard_arrow_left Previous keyboard_arrow_right Next