Phil Mickelson

Product Manager at Google | Senior Software Engineer | Ex- Tesla | Ex-Amazon

[Fabrizio Romano @FabrizioRomano]

🔵👀⚡️ #CFC

[Naval @naval]

You won’t get rich just working hard, but if you don’t work hard, you won’t get rich.

[Mohit Goyal (Harness arc) @ByteMohit]

As an AI Infrastructure Engineer

Please learn:
- GPU architecture, VRAM fundamentals, CUDA & memory hierarchy
- Quantization (INT8/FP8/4-bit), batching & continuous batching
- vLLM, TensorRT-LLM, SGLang, llama.cpp & inference optimization
- KV caching, speculative decoding, prefix caching & token throughput
- Distributed training (DDP, FSDP, DeepSpeed, ZeRO)
- Model serving (Triton, vLLM, KServe, Ray Serve, SGLang)
- Kubernetes, Docker & GPU orchestration
- NCCL, InfiniBand & high-speed networking
- Multi-GPU & multi-node inference
- LoRA, QLoRA, PEFT & fine-tuning pipelines
- Vector databases, embeddings & RAG pipelines
- Prompt caching, semantic caching & cost optimization
- Observability (OpenTelemetry, Prometheus, Grafana, Langfuse, Phoenix)
- LLM evaluation, benchmarking & A/B testing
- Model routing & fallback strategies
- MCP, AI agents & workflow orchestration
- Data pipelines, Kafka & streaming inference
- Security, guardrails & prompt injection mitigation
- CI/CD for ML (MLOps), MLflow & model registries
- Linux, networking & storage fundamentals

[rob. @robiartec]

UN CIENTÍFICO DANÉS PROGRAMÓ A CLAUDE PARA QUE BUSQUE TRABAJO POR ÉL Y LO ACABA DE HACER PÚBLICO

Mandar CVs es uno de los trabajos más absurdos del mundo: copiar, pegar, adaptar, personalizar, repetir. Todo manual, todo lento, todo para que lo lea un algoritmo antes que un humano.

→ Analiza la oferta de trabajo automáticamente
→ Genera un CV personalizado para cada puesto
→ Redacta la carta de presentación adaptada al contexto
→ Todo lo hace Claude por debajo, sin que toques nada
→ Open source, ya en 3.5k stars en GitHub

El tío que debería estar buscando trabajo ha construido la herramienta que lo busca por él.

Aquí te explico cómo funciona 👇(repoo al final del hilo)

[Puneet Patwari @system_monarch]

Suppose you have interviews scheduled for these 70LPA-1Cr+ CTC roles:

Google L5 /
Meta E5 /
Uber Staff /
Amazon L6 /
Salesforce SMTS /

Go through these 27 core system design concepts and problems.

How many can you reason through in a 1-hour round if the interviewer injects one of them into your design or asks as a follow-up? How much clarity do you have?

Beginner:
- The thundering herd problem
- Cache stampede
- N+1 query problem
- Hot partition / hot key
- Single point of failure
- Retry storm
- Backpressure
- Duplicate requests / idempotency gap
- Stale cache / read-after-write inconsistency

Intermediate:
- Distributed rate limiting
- Leader election
- Distributed locking and lease expiry
- Quorum reads vs quorum writes
- Fan-out on write vs fan-out on read
- Out-of-order event processing
- Dead letter queues and poison messages
- Zero-downtime schema migration
- Circuit breaker and cascading failure control

Advanced:
- Split a monolith safely
- Multi-region failover
- Active-active conflict resolution
- Change Data Capture vs dual writes
- Search index freshness vs ranking quality
- Rebalancing shards under skewed traffic
- Noisy neighbor problem in multi-tenant systems
- Watermarks / late-arriving events in stream processing
- Exactly-once processing vs practical deduplication

Most candidates prepare for:
- “Design Uber.”
- “Design Twitter.”
- “Design Dropbox.”

These generic prompts are good for beginners, but at senior levels, depth matters. Strong candidates prepare for the even minute problems that can cause disasters at scale.

[Zeb Evans @DJ_CURFEW]

Today we reduced headcount by 22%. The business is the strongest it's ever been. So I think it's important to be direct about what I'm seeing and why.

First, I made this decision and I own it. I did it because the way to operate at the highest level of productivity is changing, and to win the future, ClickUp needs to change with it.

Second, this wasn't about cutting costs. Most savings from this change will flow directly back into the people who stay. We'll be introducing million-dollar salary bands. If you create outsized impact using AI, you'll be paid outside of traditional bands.

Most importantly, I have the deepest gratitude for those affected. We're doing this from a position of strength specifically so we can take care of people properly. Everyone affected receives a package aimed at honoring their contributions and easing the transition.

I only see two options: wait for this to play out gradually in the market or be honest about what I'm seeing and act proactively.

THE 100X ORGANIZATION
The primary change is that we're restructuring around what I call 100x org. The goal is 100x output. The roles required to build at the highest level are fundamentally different than they were a year ago.

Incremental improvements to existing systems won't get us there. We need new ones. That means creating enough disruption to rebuild rather than iterate on what's already broken.

The common narrative is that AI makes everyone more productive. It doesn't. Many of the workflows of today, if left unchanged, create bottlenecks in AI systems.

These roles will evolve. But waiting for that to happen naturally means falling behind now.

The 100x org is actually heavily dependent on people - infinitely more than today. This is only possible with 10x people that have embraced and adopted new ways of working.

THE BUILDERS, AGENT MANAGERS, AND FRONT-LINERS

— THE BUILDERS: 10X ENGINEERS
I don't think most companies have internalized what's actually happening with AI in engineering. The common narrative is that AI makes all engineers more productive. That may be true in isolation, but at an organization level - that is the farthest thing from reality.

Here's what we've validated recently at ClickUp: the great engineers, the ones who can orchestrate, architect, and review, are becoming 100x engineers. They're not writing code. They're directing agents that write code. The skill is judgment.

AI makes the best engineers wildly more productive, and everyone else using AI slows these engineers down.
Think about it - the bottlenecks are (1) orchestration - telling AI what to do, and (2) reviewing - what AI did. Everything is leapfrogged and no longer needed.
So who do you want orchestrating and reviewing code?

And how do you want your best engineers to spend their time?

If your best engineers are spending time reviewing other people's code, then this is inherently an inefficient bottleneck. These engineers can review their agent's code much faster than reviewing human code.

The new world is about enabling your 10x engineers to become 100x.

The wrong strategy is to push every engineer to use infinite tokens. Companies doing this are celebrating 500% more pull requests. But customer outcomes don't match the volume of code being generated.

I call this the great reckoning of AI coding, and every company will face this soon if not already.

More code is just another bottleneck to the best engineers, and ultimately to your company's impact as well.

— THE BUILDERS: 10X PRODUCT MANAGERS
Product management and design roles are merging.

Designers that have customer focus, become more like product managers.

And product managers that have intuition for UX become more like designers.

The bottleneck of user research is gone. It takes us just one mention of an agent to kickoff research and analyze results.

The bottleneck of product <> design iteration is also gone. The product builder iterates on their own, along with agents and skills that ensure alignment with quality and strategy.

Also controversial today - I believe that the wrong strategy is to have your PMs shipping code - that just introduces another bottleneck that the best engineers will waste their time on.

To be clear, PMs should be coding but they should do this in a playground to iterate, validate, and scope. That code should not go to production.

Everything outside of managing systems, orchestrating AI, and reviewing output becomes a bottleneck.
That's why the other roles that are critical along with these are the systems managers (to reduce bottlenecks) along with a bottleneck you can't replace - customer meeting time.

— THE SYSTEM MANAGERS
Ironically, the people that automate their jobs with AI will always have a job. They become owners of the AI systems - agent managers. We have many examples of these people at ClickUp.

The underlying systems in which we operate are absolutely critical to get right. I think most companies are delusional to think they can iterate on existing systems and compete in this new world.

You must create enough disruption so that old systems are deprecated entirely. If there's any definition for 'AI native' that's what it is.

— THE FRONT-LINERS
In a world that will become saturated with AI communication, the human touch will matter more than anything to customers.

This is a bottleneck that you shouldn't replace - even when agents are high enough quality to do video meetings.

One-on-one meeting time with customers is something that shouldn't be automated. The systems around the meetings should be - so that front-liners spend nearly 100% of their time with customers.

REWARDING 100X IMPACT
In a world where companies are able to do so much more with less, where does that excess money go?
In our case, much of the savings in this new operating model will flow directly back to those that enabled it.

We must reward people that create productivity accordingly. This aligns incentives on both sides. Plus, in a world where your best people create 100x impact, you can't afford to lose them.

You should aim to retain these employees for decades. The context they have and their ability to efficiently orchestrate and review will be nearly impossible to replace.

Compensation bands of today should be thrown out the door. We're introducing $1 million cash/year salary bands with a path available to nearly everyone in the company if they produce 100x impact by creating or managing AI systems.

THE FUTURE
Nearly every company will make changes like these. The ones that do it proactively will define what comes next.

The future is not fewer people. It's different work, new roles, and better rewards for those who embrace it. We're already seeing entirely new roles emerge, like Agent Managers, that didn't exist a year ago.

ClickUp is positioning to lead this shift, not just internally, but for our customers too. I've never been more certain about where we're headed.

[nikita huno @NikHuno]

I’m European.

Last year, I moved to India.

What I experienced shattered my Western mindset.

Here are 10 life-changing lessons I learned in India that reshaped how I see the world:

[Gaurav Sen @gkcs_]

Many tech creators have become GateKeepers, guarding the big Castle of Tech.

In this castle, only "real engineers" get passes. You know- the ones who learn obscure tech hoping others won't.

Poor chaps want to be different.

[Zain Kahn @heykahn]

ChatGPT is just the tip of the iceberg.

1,000+ AI tools were released in March.

Here are the 10 most valuable AI tools to boost your productivity:

[Consulting Comedy @consultingcmdy]

If LinkedIn implemented a strict honesty policy

[Pat Walls @thepatwalls]

Shoutout to all the people who said I got lucky.

[Kyle Gawley @kylegawley]

I’ve launched 10 software startups in 12 years. 2 worked, 8 failed.

Here’s a list of them with the reason why each worked/failed 🧵⬇️

[Jean-Baptiste Lefevre @jblefevre60]

💥Robotics is revolutionizing agriculture!

#AI #MachineLearning #Robotics #Agtech #CES2023

@SpirosMargaris @PawlowskiMario @mvollmer1 @gvalan @Shi4Tech @LaurentAlaus @Fisher85M @kalydeoo @Fabriziobustama
@chboursin @sallyeaves @EvanKirstel @ahier @rwang0

[Troll Football @TrollFootball]

There's only 1 GOAT

[Barney Rubble @MrPringlz]

@RespectfulMemes

[T. @deeplyrootedT]

Happy to announce that I’m no longer unemployed !!! 😭😭

I received an offer this week &amp; I’ll be going from unemployed to around a $80k salary 🥹

I’ve never made more then $20 an hour prior to this so I’m still in shock like... wow

#Blacktechtwitter

[Danny Thompson @DThompsonDev]

Heroku is ending their free tier and some folks are freaking out. It is ok!

Here are six places you can host your website for free!

- Firebase
- Vercel
- Cloudflare Pages
- AWS
- Netlify
- Github Pages

[House of the Dragon @HouseofDragon]

Quiet in the realm.

House of the Dragon starts now. #HOTD

[Danny Thompson @DThompsonDev]

YOU GOT THE INTERVIEW!😁🎉.....

You finally got that first software developer interview,
What should you be doing to prepare?!😱

[Marko Denic @denicmarko]

GitHub repositories to improve programming skills: