Alexandre Zajac — SDE & AI @Amazon | Building Hungry Minds to 1M+ | Daily Posts on Software Engineering, System Design, and AI ⚡
SDE & AI @Amazon | Building Hungry Minds to 1M+ | Daily Posts on Software Engineering, System Design, and AI ⚡
Alexandre Zajac ranks #96 of 14,983 LinkedIn creators in Computer Software, and is a standout voice in United States. They have 156.8K followers and published 48 posts in the last 30 days at a 0.2% average engagement rate.
- 156.8K followers
- 48 posts / 30d
- 0.2% avg engagement
- — follower growth / 30d
The roast
Alexandre Zajac claims he is building a community of hungry minds, yet he has posted 48 times in a month to maintain a 0.21 percent engagement rate. It is not a software company; he is just the world’s most expensive bot for people who find ChatGPT too intellectually demanding.
About Alexandre
Tell me about the last time you felt growing as a software engineer. Really. 𝙽𝚞𝚕𝚕𝙿𝚘𝚒𝚗𝚝𝚎𝚛𝙴𝚡𝚌𝚎𝚙𝚝𝚒𝚘𝚗? Here's why: We all face information overload as software engineers. There's too much content and too little time. You have to stay relevant, but it's hard. Right now, you're either working or taking a break. You are hoping to get a dopamine shot from scrolling your feed. You can find: 💡 A practical tip to implement 📚 An inspirational quote 😆 Something funny And then what? → Scroll past it? → Forward it blindly to a friend? → Forget about it in the bookmarks? The harsh truth: nothing. What you consume passively doesn't make you learn. How do I know? It was the same for me for years. How do you stay updated with AI, stay relevant in the job market, and continuously grow? That's the problem I set out to solve with Hungry Minds - a free weekly newsletter to help software engineers learn and stay updated, without the noise. I'm doing that by: 1. Writing to you daily on LinkedIn to 40K+ followers and over 5M impressions last year 2. Compressing 1 week of software deep dives and trends in 1 free newsletter issue 3. Sharing my thoughts and learnings being promoted to SDE II in 1.5y at Amazon If that sounds interesting, check out Hungry Minds or DM me! I'm always down for a chat. Save 50+ hours of your week here: 𝗵𝘁𝘁𝗽𝘀://𝗵𝘂𝗻𝗴𝗿𝘆𝗺𝗶𝗻𝗱𝘀.𝗱𝗲𝘃 (6K+ engineers from startups to big tech are reading already) DISCLAIMER: Opinions expressed are solely my own and do not express the views or opinions of my employer. My career background: I'm currently an L5 software engineer at Amazon in Madrid, working on core Search CX and Personalization. In 2022/2023, I delivered 2 successful billion-scale projects with multiple teams across different time zones. I have worked with multiple code languages (although this doesn't make a difference), and with tech stack in the lines of AWS CDK, React applications, scheduling systems, backends with GraphQL, and simple AI applications. My education background: - I finished a Master's in Machine Learning and AI with l'Ecole Polytechnique and IPP - I completed a Master's in Computer Science and Data Science with ESILV Paris - I got a Master's in business development and marketing with EMLV Paris
Highlights
- Top 1% in Computer Software — Ranked #8 of 4267 creators
- Big Audience — 156,756 followers · top 1%
- Top 1% in United States — Ranked #36 of 5205 creators
- Consistent Creator — 48 posts in 30d · top 5%
Recent posts
I'm excited to announce that you can officially retire localhost:3000 Simply by using Portless from Vercel. It's pure magic; your app gets a name instead of a port. portless your-app next dev → http://your-app.localhost What comes for free with it: → No more memorizing ports → Makes worktree painless for agents → Cookies + localStorage isolated per app → Browser history in names and not numbers How does it work? It grabs a random port, runs a reverse proxy with certs, and points your .localhost name at it. It's literally a one-time setup. Would you use this?
31 reactions · 8 comments · 0 reposts
An agent can write 500 lines in 10 seconds. It still can't tell you which one breaks prod. Every week there's a new agent, a new framework, another "this changes everything." And every week, the same quiet voice: I'm falling behind. No you aren't. You're measuring the wrong thing. I work on systems at a scale where one wrong change can ripple across a dependency graph that no single person fully holds in their head. The tool can NEVER be the bottleneck. Understanding the system well enough to know what should change is the hardest part. And AI simply exposes this bottleneck. It makes
60 reactions · 15 comments · 0 reposts
You are what you read. 10 brain foods to grow as an engineer: 0. AI Engineering For Software Devs: ► https://lnkd.in/gi5vnbU3 1. How Notion Cut Spark Compute Costs: ► https://lnkd.in/gjwrS7Pb 2. The Hidden Differences Between Latency, Throughput, And Bandwidth: ► https://lnkd.in/grwCCkTE 3. Isolate Your Dev Environments Using Git Worktrees: ► https://lnkd.in/gH_TS5z9 4. Things You Didn't Know About Database Indexes: ► https://lnkd.in/g9UX4GDH 5. Why "Null" Has Caused Billions Of Dollars In Software Failures: ► In today's Hungry Minds issue 6. How Stripe Cut CI Time In A 50M-Line Rub
58 reactions · 11 comments · 0 reposts