Sam_Maverick

[Mr. Buzzoni @polydao]

the Atlassian engineer who was laid off dropped a full guide to becoming a senior engineer after 15 years in the industry

Vasilios Syrakis - no university degree. Made it to Senior Engineer anyway

the things that actually worked:

> taught himself Regex by mass-answering Stack Overflow until he became the expert people came to
> learned Python for free, immediately built a DNS web interface and shipped it - didn't wait to feel ready
> watched the same conference talks dozens of times until concepts actually stuck

if he was starting from zero today:

> get a CS degree - he skipped it and says that was a mistake
> build a home Kubernetes cluster and try to sell what you make
> grind LeetCode - not for the code, for the vocabulary to prompt Claude correctly
> share everything publicly - the audience compounds faster than the skills
> show up to meetups in person

the one mindset shift that separates juniors from seniors: when you join a new team, write a deep analysis of how everything works before touching a single line of code

> 15 years at the top of the industry and he still gets impostor syndrome

so does everyone else who's actually good

the roadmap is in the video 👇

[slash1s @slash1sol]

A LINUX KERNEL DEVELOPER PROVED THE THING YOU PUSH CODE TO IS SECRETLY A DATABASE THAT CAN VERSION ALMOST ANYTHING AND THAT MOST DEVS HAVE ONLY EVER TOUCHED A TENTH OF IT

42 minutes from Josh Triplett -- a longtime Linux kernel and Debian developer -- showing that Git is a general-purpose, tamper-evident versioning engine that just happens to be famous for code.

-> The moment it clicks, Git stops being "Where my code lives" and becomes what it really is underneath: a content-addressable store that can version almost anything -- your configs, your notes, your servers' state, entire datasets.

People run whole wikis on it. They version their entire machine's configuration with it. They ship websites by pushing to it. They track data too big to email. None of it is a hack -- it's the same handful of objects you already use for code, pointed somewhere new.

Treating Git as a code-only tool was never the ceiling -> it's a versioning engine for anything, and the people who see that automate what the rest of the team still does by hand. And as AI agents start spitting out not just code but configs, docs and data, the one system that can version and audit all of it at once is already sitting on your machine.

You learned five commands to survive. This is the talk that shows you were standing on top of a database the whole time.

It changes what you think the tool is even for.

Bookmark & Watch it today ↓

[Rohit Kumar Tiwari @_rohit_tiwari_]

AI Engineering from Scratch.

503 lessons. 20 phases. 320 hours.

https://t.co/UuX9N62VCU

Phase 00: Setup & Tooling (12 lessons)
Phase 01: Math Foundations (22 lessons)
Phase 02: ML Fundamentals (18 lessons)
Phase 03: Deep Learning Core (13 lessons)
Phase 04: Computer Vision (28 lessons)
Phase 05: NLP (29 lessons)
Phase 06: Speech & Audio (17 lessons)
Phase 07: Transformers Deep Dive (14 lessons)
Phase 08: Generative AI (14 lessons)
Phase 09: Reinforcement Learning (12 lessons)
Phase 10: LLMs from Scratch (22 lessons)
Phase 11: LLM Engineering (15 lessons)
Phase 12: Multimodal AI (25 lessons)
Phase 13: Tools & Protocols (23 lessons)
Phase 14: Agent Engineering (42 lessons)
Phase 15: Autonomous Systems (22 lessons)
Phase 16: Multi-Agent & Swarms (25 lessons)
Phase 17: Infrastructure & Production (28 lessons)
Phase 18: Ethics, Safety & Alignment (30 lessons)
Phase 19: Capstone Projects (85 lessons)

[Millie Marconi @MillieMarconnni]

A journalist in 1987 rewrote the 2,500-year-old Tao Te Ching as a series of short parables about programmers, and the book became required reading inside Silicon Valley because every line of the joke turned out to be deadly serious.

His name was Geoffrey James.

He was not a famous engineer. He was a technology journalist who had spent years inside the offices of early software companies watching the same disasters play out over and over again.

Managers piling more programmers onto failing projects. Codebases collapsing under their own weight. Corporate hierarchies producing endless documents that nobody read. Geniuses being interrupted by meetings until they quit and went home.

He could have written a serious management book. Plenty of serious management books already existed and almost nobody in software was reading them. He decided to do something stranger.

He picked up a copy of the Tao Te Ching, the foundational text of Taoist philosophy written in China around 500 BC, and he rewrote it line by line as if Lao Tzu had been a master programmer.

The result was published in 1987 as The Tao of Programming. 151 pages. Nine books. Roughly 50 short parables. A comedy book on the surface and a philosophy book underneath, written in deliberately ornate language that made you smile while you were absorbing arguments that have aged better than almost anything else published about software in the last 40 years.

The opening line of the book is the giveaway. Thus spake the master programmer. When you have learned to snatch the error code from the trap frame, it will be time for you to leave. The joke is that he is parodying the kung fu master from the old Kung Fu TV show. The argument underneath the joke is that real mastery in software is not measured by what you can build. It is measured by how cleanly you can recover when the system fails.

The book has been passed around hacker communities continuously since the late 1980s. It sits alongside Fred Brooks's Mythical Man-Month on the required reading list of serious software teams. People who have never heard of Geoffrey James still quote his lines without knowing where they came from. The reason it has refused to die for 40 years is that every line of the parody was always disguising a piece of real wisdom that nobody else was willing to say plainly.

Here are some of the lines, and what each one is actually saying.

"Even a perfect program still has bugs."

The line is funny because it sounds like a contradiction. The truth underneath is that there is no such thing as a finished program. Every system you ship is alive. It is going to encounter inputs you did not anticipate, hardware you did not test on, and edge cases your imagination could not produce.

Treating any piece of software as finished is the single most common reason production systems fail. The masters in the book are calm about bugs because they have stopped pretending bugs are exceptions. Bugs are the default state. The programmer's job is to keep them from compounding.

"Let the programmers be many and the managers few. Then all will be productive."

The line is funny because every software company in the world does the opposite. The truth underneath is that programming is a kind of work that runs almost entirely on uninterrupted thought, and the more layers of management you stack on top of it, the more interruptions you create, the more meetings the programmers have to attend, the fewer actual hours of deep work get done.

Every manager you add to a software team subtracts more productive hours from the engineers than the manager could possibly add through coordination. Brooks proved this formally in 1975. James said it in nine words in 1987.

"After three days without programming, life becomes meaningless."

The line is funny because it sounds like an addict talking. The truth underneath is that genuine craft work produces a kind of meaning that almost nothing else in modern life provides. The programmer who has not touched real code in three days is not just bored.

They are emotionally underfed. The masters in the book understand that the work itself is not a means to a paycheck. The work is the reward. The paycheck is a side effect. Everything that interferes with the actual work, no matter how prestigious or well-paid it looks, is making the programmer's life worse, not better.

"A manager went to the master programmer and showed him the requirements document for a new application. The manager asked the master, how long will it take to design this system if I assign five programmers to it? The master replied, it will take one year. The manager said, but we need this system immediately or even sooner. How long will it take if I assign ten programmers to it? The master programmer frowned. In that case it will take two years."

The line is the punchline of Brooks's Law disguised as a koan. Adding programmers to a late project makes it later, because every new person has to be brought up to speed by the existing team, which slows the existing team down, which extends the timeline. The book teaches this in 60 words. The same lesson takes most managers 20 years of failed projects to learn, if they ever learn it at all.

The deeper pattern is the one most readers miss the first time through.

James was not really writing about programming. He was using programming as a setting for a much older argument that Taoist philosophy has been making for 2,500 years.

The argument is that the world is governed by simple principles that get harder to see the more cleverness you stack on top of them. Force does not work. Pressure does not work. More resources do not work. The only thing that works is restraint, simplicity, and the patience to let the right shape emerge.

Lao Tzu was talking about how to govern a kingdom. James was talking about how to ship software. The wisdom is the same. The kingdom is the codebase. The emperor is the project manager. The advisors are the developers. And the entire collapse of every doomed software project in the last 40 years has had the same root cause that the collapse of every doomed dynasty has had for the previous 4,000.

People mistook complexity for competence.

The book has been sitting on the internet for free for almost 30 years. You can read all 151 pages in an afternoon. Most people who run it as a joke walk away quoting it for the rest of their careers.

What James understood in 1987 is even more true in 2026. AI can now generate millions of lines of code in seconds. The bottleneck has shifted entirely. The bottleneck is no longer typing speed. The bottleneck is judgment. The bottleneck is taste. The bottleneck is the ability to look at a generated codebase and feel, without quite knowing why, that something is wrong with it. That kind of feel is exactly what the book was teaching all along.

The Tao of Programming flows far away and returns on the wind of morning.

The masters in the book were never joking. The world just took 40 years to figure out they were not.

[Google for Startups @GoogleStartups]

Unlock the power of autonomous workflows with Startup School: Agentic AI.

Join @GoogleCloud experts to discover how to build, deploy, and scale sophisticated #AIagents that drive real business impact. Ready to innovate? Register here ➡️ https://t.co/QzUDNTjYzt

[slash1s @slash1sol]

A DEVELOPER TAUGHT GIT WITH A BOX OF CHILDREN'S TOYS AND ENGINEERS WITH TEN YEARS IN SAY IT'S THE FIRST TIME THE THING EVER ACTUALLY MADE SENSE

90 minutes, one table, a pile of Tinkertoys. No wall of jargon -- he builds a real Git repo out of plastic rods right in front of you.

-> The moment he snaps the first pieces together, Git stops being scary command-line magic and becomes what it really is: a chain of tiny objects pointing at each other.

Branches, merges, rebase, the staging area -- every concept that's ever burned you at 2am -- he rebuilds with toys until a four year old could follow. He calls Git a two-trick pony. After this you'll see exactly why.

Memorizing commands was never the skill -> holding the graph in your head is. And with an AI agent now committing and rebasing on your machine all day, that mental model is the only thing between you and a history you can't read.

Scroll the comments and you'll see the same thing over and over: this is the talk that finally made Git click and made people the one their whole team comes to when it breaks.

Bookmark & watch it today. It's the 1.5 hours that pays you back for the rest of your career ↓

[AI_Explorer @ai_explorer25]

Best accounts to follow from each frontier lab to stay constantly up to date

Anthropic
@karpathy
- must-follow account for AI; recently joined Anthropic

@bcherny
- Claude Code creator, always shares great tips

@trq212
- also a Claude Code developer; writes amazing articles on CC

OpenAI
@polynoamial
- works on reasoning research, shares a lot of technical details

@gabriel1
- Sora developer, great career path

@jxnlco
- works on dev experience, shares a lot about Codex

Google AI
@OfficialLoganK
- all the major Google Gemini and AI Studio updates

@ammaar
- product and design; shares great things about vibe-coding in Google AI Studio

@fofrAI
- cool use cases for generative models

Cursor
@leerob
- the loudest voice behind Cursor updates

@ericzakariasson
- shares great insights on using Cursor

@mntruell
- Cursor’s CEO; major releases and usage updates

xAI
@milichab
- recently joined xAI, shares updates on Grok

@skcd42
- also covers major Grok releases

[Markandey Sharma @TechByMarkandey]

Some remote jobs only operate between 1:30 AM and 6:30 AM, which is why hardly anyone applies.

I’ve identified overnight remote jobs paying up to $200 per hour in USD.

Here’s each job and why they pay so much👇

[Ashutosh Maheshwari @asmah2107]

Most tech content is noise. But one YouTube channel is quietly archiving the deepest engineering knowledge on the internet.

I’ve been watching Ryan Peterman’s (@ryanlpeterman) podcasts over the last few months, and the signal-to-noise ratio is absolutely insane. He is sitting down with:
▪️ Turing Award winners (like Leslie Lamport & Mike Stonebraker)
▪️ Bjarne Stroustrup (Creator of C++)
▪️ Elite Big Tech ICs & VPs of Engineering

This isn't just about writing code.

They dive deep into the reality of high-level tech careers : foundational architecture, system design from first principles, and complex trade-offs like Paxos vs. Raft.

If you are serious about computer science, bookmark his channel.

It's the masterclass you won't get in a classroom.

[Sulekha Tripathi @sulekhat95]

INSTEAD OF WATCHING AN HOUR OF NETFLIX TONIGHT.

This 1 hour Stanford lecture by Joel Peterson will teach you more about negotiation and getting what you want than most people learn in years.

Bookmark it and give it an hour, no matter what.

[Manisha Mishra @manishamishra24]

This 2 hour Harvard interview with Lee Kuan Yew, the man who turned Singapore from a tiny island into one of the richest nations on Earth, will teach you more about leadership, discipline, and nation-building than most business books ever will.

[Neyazuddin Ansari @riyazz_ai]

Instead of watching an hour of Netflix, watch this 1-hour MIT lecture.

It will teach you more about probability and prediction markets than most people learn in months of quant internships.

Save this.

[CyrilXBT @cyrilXBT]

Most people will go to bed tonight the same way they woke up this morning.

Spend 1 hour with this.

A MIT lecture on generational wealth that teaches you more about money, compounding, and building something that outlasts you than 20 years inside any hedge fund, investment bank, or financial institution ever could.

Wall Street teaches you how to make money for someone else.

This teaches you how to build something for yourself.

The people who watch this tonight will make one decision differently this week.

That one decision will compound for the next 20 years.

The people who skip it will keep taking financial advice from people who profit when they stay confused.

Completely free.

Bookmark this before you open Netflix 👇

[NeilXbt @neil_xbt]

Yale charges $80,000/year for access to Professor Ben Polak!

They put his most important lecture on YouTube for free.

Every negotiation you have ever entered. Every salary you have ever accepted. Every price you have ever set.

The other person was running game theory. Payoff matrices. Dominant strategies. Nash equilibrium. Backward induction.

You were hoping for the best.
That is not a skill gap.
That is a universe gap.

And it has been costing you $20,000. $50,000. $100,000 every single year, without you knowing the name of the thing taking it.

1 hour today closes most of that gap permanently.

The lecture MBAs pay $150,000 to access inside a degree.

Free for you right here.

Bookmark so you do not lose it!

[Suryansh Tiwari @Suryanshti777]

A man spends 50 years teaching at MIT.

He knows his time is running out.

So he records one last lecture — everything he knows, distilled into a single hour.

He died 5 months later.

This is that lecture.

The most important hour you'll watch this week. 👇
Bookmark it for later

[Steve Burns @SJosephBurns]

7 Men You Should Study:

1. Marcus Aurelius - for self-control.
2. Miyamoto Musashi - for laser focus.
3. Leonardo da Vinci - for creativity.
4. Friedrich Nietzsche - for thinking.
5. David Goggins - for performance.
6. Steve Jobs - for vision.
7. Bruce Lee - for disciplined motion.

[Rony @Ronycoder]

Instead of watching an hour movie, watch this. In 14 minutes, an Anthropic engineer who wrote Building Effective Agents will teach you more about building agents right than most developers figure out on their own in months.

[Suryansh Tiwari @Suryanshti777]

Apple fired Steve Jobs.

He walked into MIT and gave the most honest 60-minute business lecture ever recorded.

No PR filter. No image to protect. Just raw thinking from the guy who built Apple once — and was about to do it again.

Watch this instead of Netflix tonight.
Bookmark it for later

[Aakash Gupta @aakashgupta]

MIT dropped an absolute masterclass on compounding money

[Himanshu Kumar @codewithimanshu]

Every time you accepted a salary, chose a price, or walked into a negotiation, the other person was running game theory in their head.

You were guessing.

This 1-hour Yale lecture by Professor Ben Polak will change how you read people and make decisions forever.

MBAs pay $150K to learn this. Yale posted it on YouTube for free.

Save this post. Watch it this tonight.

Follow @codewithimanshu for more high-signal content that actually changes the trajectory of your career.
↓

Here's why most people lose every negotiation they enter.
You walked into your last salary discussion hoping for the best.

They walked in with frameworks. Payoff matrices. Dominant strategies. Backward induction. Nash equilibrium.

You said "I was thinking $85K." They already knew the number you'd accept. Because they ran the game before you sat down.

That's not a skill gap. That's a universe gap.
And it's costing you $20K, $50K, $100K every single year.
↓

Game theory isn't math for MBAs.
It's the operating system of every human interaction.

Job negotiations. Pricing decisions. Business deals. Relationships.

The person who understands it wins by default. Not because they're smarter. Because they're playing a different game.

You're playing checkers thinking it's chess. They're playing chess thinking it's 4D chess.

Professor Ben Polak teaches Yale's most famous game theory course. Students pay $80,000/year for access to him. His full lecture is now on YouTube. Free.
↓

What 1 hour with Polak teaches you.

How to predict what the other side will do before they do it. When to hold your position and when to fold. Why "winning" a negotiation sometimes costs more than losing. How to structure offers the other side can't refuse. The exact math behind every pricing decision in your life.

This is what investment bankers use. What hedge fund managers use. What startup founders use to raise money. What CEOs use to run companies.

You can have it for free. In 1 hour. Tonight.
Or keep walking into negotiations unarmed.
↓

1 hour of Netflix tonight: you forget by Tuesday. 1 hour of Polak tonight: you negotiate differently for the next 40 years.

Same time. One is a distraction. The other is a compounding asset.
Save this post. Watch the lecture.

Follow @codewithimanshu for more high-signal content that actually changes the trajectory of your career.