No BS AI/ML Content | ML Engineer with a Plot Twist 🥷30M+ Views 📝

Done-for you Audience Building & Content Writing for AI/ML Founders that frees up 100% of your time, so you can focus entirely on building your company  
  
Is your work too important to ignore? 💌 https://tally.so/r/wk69VJ  (or shoot me a DM) 👉
  
It's 2025 and we're at the peak of the attention economy  
  
Where Authenticity is king, visibility is currency and people wanna buy from people

Not faceless dehumanized brands  
  
So, they told you LinkedIn was "free marketing" you slapped some posts and called it strategy  
  
You've poured hours crafting the 'perfect' post, only to watch it sink without a trace..  
  
Then it dawned on you, your technical brilliance isn't enough to draw a crowd  
  
Hell, maybe you've even tried mimicking influencers, scrambling for any traction..  
  
Your post got 500 f*cking views... from your friends...  
  
Being ignored is soul-crushing  
  
It's not your fault tough  
  
When you started your company, you didn't sign-up for a degree in an Audience Building, Copywriting and LinkedIn strategy 

And here you are, sacrificing yet another late night for your vision  

"Am I just sabotaging my efforts?"  
  
"Is my life-work meaningless?"  
  
Getting traction feels impossible  
  
You hoped hiring some marketer would save your weekends but..  
  
Tech is a code they can't crack  
  
They can only churn out the lame, soul-sucking crap we all ignore on sight  
  
With armies of founders flooding feeds, your voice dissolves into meaningless white noise  
  
But in the process, you've wasted more of your precious time explaining 101 tech concept and rewriting low-quality drafts 

Done being ignored?  
  
Let's make the world listen 
  
I can help you with:  

✒️ No BS AI/ML Content  
⭐ LinkedIn Profile Revamp
🎯 Website Copy Optimization  

I've done it before:

↳ For founders backed by YC, a16z, Sequoia, and Techstars
↳ For bootstrappers in LLMs, ML, Vector DBs, Data Analytics, and Engineering
↳ For AI and Machine Learning leaders at Google, Microsoft, Airbnb, and YouTube

If they could rise above the noise, so can you

Yeah, even if you're an introvert with a "boring" niche

Still with me?  
  
Amazing—You're amazing!  
  
Cheers,  
Paolo

My booking link: 💌 https://tally.so/r/wLW0oz (or shoot me a DM) 👉

Paolo Perrone

LangChain just open-sourced their answer to Claude Code.

9.9K GitHub stars. 5 hours old.

Deep Agents: the batteries-included agent harness. MIT licensed. FREE.

Here's why this is a big deal:

Claude Code is amazing but closed-source and locked to Anthropic.

Deep Agents gives you the same architecture. Any model. Any provider.

What's included out of the box:

1️⃣ Planning
write_todos for task breakdown and progress tracking. The agent plans before it codes.

2️⃣ Filesystem access
read_file, write_file, edit_file, ls, glob, grep. Full codebase navigation.

3️⃣ Shell execution
Run commands with sandboxing. Build, test, deploy from the agent.

4️⃣ Sub-agents
Spawn isolated workers with their own context windows. Parallel work without context pollution.

5️⃣ Context management
Auto-summarization when conversations get long. Large outputs saved to files. The problem Claude Code solved, now OPEN SOURCE.

Two lines to start:

pip install deepagents

agent = create_deep_agent()

Works with Claude, OpenAI, Google, or any LangChain-compatible model. Swap providers without rebuilding.

Built on LangGraph. Streaming, persistence, checkpointing: all production-ready.

The CLI adds web search, remote sandboxes, persistent memory, custom skills, and human-in-the-loop approval.

From their README: "This project was primarily inspired by Claude Code."

They're not hiding it. They're DEMOCRATIZING it.

Are you still locked into a single AI coding provider? 👇

♻️ Repost for someone who wants Claude Code capabilities without the lock-in

No BS AI/ML Content | ML Engineer with a Plot Twist 🥷100M+ Views 📝

My Meta Staff Engineer friends shared their Claude Code setup with me.

Changed how I build software FOREVER.

10 tips. Here's why they matter:

1️⃣ Always start in Plan Mode
Never execute first. Argue with Claude. Challenge its assumptions. Spend 80% of your time here. The code generation is the easy part.

2️⃣ Run /init on every project
Claude scans your codebase and creates a CLAUDE.md rules file. This controls everything. Skip this and Claude is guessing blind.

3️⃣ CLAUDE.md under 300 lines
Every line bloats your context window. More bloat = worse output. Only add what's unique to your project. Think lint rules, not docs.

4️⃣ Build a validation loop
Build, test, compile commands inside CLAUDE.md. Claude self-corrects when it can validate its own output. Without this, it hallucinates fixes.

5️⃣ Interrupt early, interrupt often
Claude going off track? Escape. Don't wait. Don't hope. Fresh context beats bloated context every single time.

6️⃣ /clear between features
Old context contaminates new tasks. One feature per session. Start clean or pay the token tax.

7️⃣ Multiple instances simultaneously
This is the REAL unlock. Multiple terminals. Multiple Claude sessions. One builds, one plans, one debugs. Jump between them like Starcraft.

8️⃣ Never manually edit rules
"Update the rules so we never do this again." One sentence. Claude maintains its own CLAUDE.md. Stop hand-editing config files.

9️⃣ Audit with /context regularly
MCPs destroy your token budget. /context shows the biggest offenders. Disable what you don't need. Most engineers never check this.

🔟 Sub-agents for atomic tasks ONLY
Don't create CEO agents and product agents. Keep shared context in ONE session. Sub-agents lose the reasoning chain. Bring work to the context, not context to the work.

The meta-lesson:

AI coding is 80% context engineering, 20% code generation.

Most engineers optimize the 20%.

These 10 tips optimize the 80%.

That's why they ship faster than entire teams.

Are you still treating Claude Code like a chatbot? 👇

♻️ Repost for someone using Claude Code who hasn't optimized their workflow

2 founders built Claude Code but for marketing, and it's already compressing 10-month execution cycles into 10 days

After multi-billion dollar exits to Salesforce and Oracle, Tom Chavez and Vivek Vaidya noticed something:

AI eliminated manual work for engineers, but marketers were still dealing with analysis and dashboards.

I was watching their conversation with Navin Chaddha from Mayfield and it struck me what has driven their success as serial entrepreneurs:

•⁠ ⁠“A bad decision made quickly is better than a good decision made slowly.”
•⁠ ⁠“Everything we used to do in 10 months, we now try to do in 10 days.”

Hear them break it all down:

You don't need 14 courses to build AI agents.

You need 6 weeks and this path:

Week 1️⃣: Understand the pattern
→ Anthropic's Building Effective Agents: https://lnkd.in/ew-rnBgD
→ Chip Huyen's agent explainer: https://lnkd.in/gKNqjeGZ
→ 3 hours total. No courses yet.

Week 2️⃣: Build something ugly
→ Langflow (no-code, 1 hour to ship): langflow.org
→ A research agent. A Slack bot. Anything.
→ Now you have context for everything else.

Week 3️⃣–4️⃣: Understand what you built
→ AI Agents in LangGraph: https://lnkd.in/g7raxjpC
→ Agent Memory: https://lnkd.in/ehtwbCVz
→ Rebuild your ugly thing. Properly.

Week 5️⃣–6️⃣: Deploy it
→ LangSmith for tracing: smith.langchain.com
→ Railway or Render for hosting
→ Now it's a portfolio piece.

The trap:
"I need to understand transformers first."
"I should take the Andrew Ng course first."
"I'll start when I have more time."

Build ugly. Learn why it's ugly. Fix it.

💾 Save for your next "where do I even start" spiral
♻️ Repost if you've bookmarked 47 courses and finished zero

Everyone's building AI agent demos.

Palantir shipped an end-to-end agentic architecture.

12 layers. The ENTIRE production stack. Here's what's inside:

1️⃣ Secure LLM integration
GPT, Gemini, Claude, Llama, Meta: commercial and open-source. Zero data retention by providers. Swap models without rebuilding.

2️⃣ Context Engineering
Real-time, pro-code and no-code. Contextual data, contextual logic, and systems of action feeding the Ontology.

3️⃣ The Ontology
Not a data lake. A digital twin with semantic, kinetic, and dynamic layers. Human+AI decision model built in. This is their moat.

4️⃣ Agent Lifecycle
Agent building, orchestration, and evaluation suites. All integrated. No stitching 5 tools together.

5️⃣ Security & Governance
Role-based, marking-based, purpose-based controls. System-wide branching. Approvals. Checkpoints. What regulated industries ACTUALLY need.

6️⃣ End-to-end Observability
Every tool call. Every data access. Every decision traced. Full model catalog.

Plus 6 more layers: tool services, multimodal compute, development environments, human+AI applications, package/release/deploy, and enterprise automation.

12 layers. One architecture. Production-ready.

The framework wars were the warmup.

The real game is agentic architecture.

Are you still debating agent frameworks? 👇

♻️ Repost for someone building agents who hasn't seen this architecture

Google just gave every AI coding assistant NATIVE knowledge of how to build agents.

15,600 GitHub stars. One command. FREE.

Your coding assistant doesn't know ADK. It hallucinates APIs and invents methods that don't exist.

Here's why this changes everything:

npx skills add google/adk-docs/skills -y

One command. Your coding agent now knows:

1️⃣ ADK Cheatsheet
Full Python API reference. Every method, every parameter. No more hallucinated imports.

2️⃣ ADK Dev Guide
Development lifecycle and coding guidelines. The patterns Google's own team uses.

3️⃣ ADK Deploy Guide
Agent Engine and Cloud Run deployment. Prototype to production in the same workflow.

4️⃣ ADK Eval Guide
Evaluation methodology and scoring. Test your agents before they hit production.

5️⃣ ADK Observability Guide
Tracing, logging, and integrations. See what your agents are ACTUALLY doing.

6️⃣ ADK Scaffold
New agent project in seconds. Right structure from the start.

Works with everything:

⚡ Claude Code: one command install
⚡ Cursor: MCP server config
⚡ Gemini CLI: extension install
⚡ Any MCP-compatible tool

Plus a docs MCP server that connects your editor directly to ADK documentation. Always up to date. Machine-readable.

What this replaces:

Hours of Googling API docs → $0
Debugging hallucinated methods → $0
Manually reading changelogs → $0

ADK has 15,600 stars, 2,800+ dependent projects, and now ships in Python, TypeScript, Go, and Java.

Google isn't just building an agent framework.

They're teaching YOUR coding assistant how to use it.

🔗 Install skills: npx skills add google/adk-docs/skills -y
🔗 Full docs: google.github.io/adk-docs

Are you still letting your coding assistant hallucinate ADK APIs? 👇

♻️ Repost for someone building with Google ADK who doesn't know about this

Google just dropped a FREE agent starter pack.

One command. 60 seconds. Full production stack.

3,100+ GitHub stars. Here's why:

5 agent templates, ready to deploy:

1️⃣ ReAct agent (ADK)
2️⃣ RAG agent: document retrieval + Q&A
3️⃣ Multi-agent with A2A Protocol
4️⃣ Live API: real-time multimodal
5️⃣ LangGraph base

That's the starting point. The infrastructure is what makes it DIFFERENT:

⚡ Cloud Run + Agent Engine deployment
⚡ Terraform configs included
⚡ CI/CD with Cloud Build + GitHub Actions
⚡ Vertex AI evaluation built in
⚡ Interactive playground for testing

One command:

uvx agent-starter-pack create my-awesome-agent

No boilerplate. No config hell. No "works on my machine."

Google gave away what most teams spend weeks building.

For $0.

Which template are you starting with? 👇

♻️ Repost for someone building agents from scratch

The complete AI Agents learning stack for 2026.

31 resources. Every single one free.

Most engineers bookmark 50 resources and finish ZERO.

This isn't a bookmark dump. It's a 5-phase path:

📹 UNDERSTAND

1️⃣ Intro to Large Language Models (Karpathy) → https://lnkd.in/egCPxzEx
2️⃣ Deep Dive into LLMs (Karpathy) → https://lnkd.in/euMCHnyv
3️⃣ Agentic AI Overview (Stanford) → https://lnkd.in/etjh6sYZ
4️⃣ Building and Evaluating Agents → https://lnkd.in/e45S6ZcZ
5️⃣ Building Effective Agents → https://lnkd.in/eKEaupVF
6️⃣ Building Agents with MCP → https://lnkd.in/eVhWN9kK
7️⃣ Building an Agent from Scratch → https://lnkd.in/eY3c5npC

📜 READ THE SCIENCE

1️⃣ ReAct → arxiv.org/abs/2210.03629
2️⃣ Chain-of-Thought Prompting → arxiv.org/abs/2201.11903
3️⃣ Tree of Thoughts → arxiv.org/abs/2305.10601
4️⃣ Reflexion → arxiv.org/abs/2303.11366
5️⃣ Toolformer → arxiv.org/abs/2302.04761
6️⃣ Generative Agents → arxiv.org/abs/2304.03442
7️⃣ RAG Survey → arxiv.org/abs/2312.10997

🗺️ STUDY THE ARCHITECTURES

1️⃣ Google's Agent Whitepaper → https://lnkd.in/ejiEnCdK
2️⃣ Building Effective Agents (Anthropic) → https://lnkd.in/ew-rnBgD
3️⃣ OpenAI's Practical Guide → https://lnkd.in/ef2vzH2C
4️⃣ Claude Code Best Practices → https://lnkd.in/eRBfw9k5
5️⃣ Google's Agent Companion → https://lnkd.in/eezmZrVs

🧑‍🏫 BUILD

1️⃣ HuggingFace Agent Course → https://lnkd.in/gxSFVqhY
2️⃣ MCP with Anthropic → https://lnkd.in/efqmGWaR
3️⃣ Agent Design Patterns → https://lnkd.in/gHhvHAKq
4️⃣ Multi-Agent Systems → https://lnkd.in/gkg3qzMG
5️⃣ Building Browser Agents → https://lnkd.in/etMGU_bi
6️⃣ Computer Use with Anthropic → https://lnkd.in/edR3Qg94
7️⃣ Evaluating AI Agents → https://lnkd.in/eFFiUue5
8️⃣ Building & Evaluating RAG Apps → https://lnkd.in/gWAbB363
9️⃣ Agent Memory → https://lnkd.in/eCf57tqh

🗂️ SHIP

1️⃣ GenAI Agents → https://lnkd.in/gykAzWMt
2️⃣ Microsoft AI Agents for Beginners → https://lnkd.in/efzMR5aU

5 phases. 31 resources. $0.

Bootcamps charge $5,000+ for LESS.

Which phase are you starting with? 👇

♻️ Repost for someone who wants to build agents but doesn't know where to start.

RAG, CoT, ReAct, RLHF, LoRA, MoE

What do these acronyms actually mean?

If you're breaking into AI engineering, these come up constantly. 

Here's the breakdown:

🔹 RAG (Retrieval Augmented Generation)
Instead of relying only on what the model "knows," you retrieve relevant documents and feed them into the prompt. Reduces hallucination. Powers most production AI apps.

🔹 CoT (Chain of Thought)
Prompting the model to "think step by step" before answering. Dramatically improves reasoning on complex tasks. Free performance boost.

🔹 ReAct (Reasoning + Acting)
Agent pattern where the model alternates between thinking and taking actions. Think → Act → Observe → Repeat. Foundation of most agent frameworks.

🔹 RLHF (Reinforcement Learning from Human Feedback)
How ChatGPT became ChatGPT. Train the model to prefer outputs humans rate highly. Why models are helpful instead of just predictive.

🔹 LoRA (Low-Rank Adaptation)
Fine-tune a model by training only a small number of new parameters. Makes fine-tuning accessible without massive GPU costs.

🔹 MoE (Mixture of Experts)
Model architecture where only a subset of parameters activate per token. How Mixtral and Nemotron run 30B+ params on consumer hardware.

Frameworks change every quarter.
These acronyms won't.

💾 Save for your next "wait, what does that stand for?" moment
♻️ Repost so they don't have to ask you.

Fabian Werkmeister

I help you to become fluent in Data and enable you to translate between business & tech ★ Data Scientist @FUNKE ★ 🐍Python 🤖Data Science 🛠️Data Engineering

We are swimming in data.
Yet decisions are still based on gut feeling.
I build systems that close this gap ⬇️

I didn't start in tech, but switched over from economics.
That made me become a data engineer, who understands both business and data very well.
I don't just build pipelines, I build actionable data systems on the Google Cloud Platform that help you decide what to do next.

Here's what you can expect working with me:
1. Business First
Coming from a business background, I speak your language. I use simple and GCP-native setups, keeping your costs low and maintenance easy. My success metric isn't lines of code written, it's how fast I can help you make good decisions based on your data.

2. No Black Boxes
I don't build for you, I build with you. My process is "White-Box," meaning nothing is hidden and you will be involved from day one. All done within in a transparent and communicative partnership. 

3. Engineering with Heart
I believe technical projects fail due to human friction, not because of technological issues. I bring reliability, empathy and a huge passion for my craft to actually solve your business problems.

If you are looking for a Senior GCP Data Engineer who combines technical depth with business clarity and a genuine, transparent partnership  - let’s talk!

👉 Book a free call with me (you can find the link below) to see if we are a match.

Data Scientist

Your 2 most used data layers have 0 lines of code.
𝗧𝗵𝗮𝘁'𝘀 𝗮𝗯𝗼𝘂𝘁 𝘁𝗼 𝗯𝗲𝗰𝗼𝗺𝗲 𝗮 𝗽𝗿𝗼𝗯𝗹𝗲𝗺.

I'm talking about ingestion and dashboards.
The entry and exit points of every data stack.

Fivetran or Airbyte. Power BI or Looker Studio.
These tools run on GUIs. Click, drag, configure.
Most often no code touches your repo.

For years, that felt like an acceptable trade-off: 
Faster setup. 
Lower entry barriers.
Ship something today.

The transformation layer settled this years ago with e.g. dbt:
Most teams write SQL, version it, review it.
Code won the middle of the stack.

But the edge layers?
Still most often click-ops. 
And these two layers sit closest to the business.


👉 𝗡𝗼𝘄 𝗵𝗲𝗿𝗲'𝘀 𝘁𝗵𝗲 𝗽𝗮𝗿𝘁 𝗽𝗲𝗼𝗽𝗹𝗲 𝗴𝗲𝘁 𝘄𝗿𝗼𝗻𝗴:
"Click-based tools can't use AI."
That's not true.
These vendors know exactly what's happening.
Each tool gets smarter every quarter, but inside its own walls.

The problem isn't that individual tools lack AI.
The problem is that each tool's AI only sees its own layer.
Isolated pockets of intelligence and no cross-stack visibility.

In a code-first stack, AI traces changes through every layer.
From ingestion through transformation to the final report.
One change, one traceable thread.

In a click-based stack, you remain isolated within the tools.
Your AI can't look in.
Your AI can't help you here.

This isn't anti-no-code dogma.
These tools rightfully earned their spot.
But building your entire stack on clicks means building black boxes at the most volatile points of your architecture.

The transformation layer already solved this.
Integration and dashboards deserve the same discipline.

PS: Was inspired to write this piece while having a conversation with Tom Wolting about AI-accessability and his perspective completely changed mine - you should give him a follow! ✌️ 

---

Hi, I'm Fabian👋
I write about lean & actionable data systems on GCP
👉 Hit Follow
♻️ Repost, if you found this useful

I build actionable data systems on GCP that drive decisions | Technical excellence delivered with passion & ♥️ | Freelance Data Engineer & Independent Consultant

𝗚𝗲𝘁𝘁𝗶𝗻𝗴 𝗮 𝗽𝗲𝗿𝘀𝗼𝗻𝗮𝗹 𝗰𝗼𝗮𝗰𝗵 𝗰𝗵𝗮𝗻𝗴𝗲𝗱 𝗺𝘆 𝗹𝗶𝗳𝗲.
It costs me $20/month.

Over the past 6 years, I put a lot of time in collecting everything I learned about myself:
My HSP wiring.
Therapy insights.
My Journal entries.
Coping techniques.
My triggers and patterns.
My inner child mechanisms.
Frameworks that help me when I'm stuck.
My vision for the person I want to become.

All valuable.
All in much detail.
All scattered across notebooks, docs, and my head.

This was difficult to access in critical moments.
Impossible to connect all of that into a full picture.
AI with custom context completely changed that for me.

𝗜 𝘂𝘀𝗲𝗱 𝗖𝗹𝗮𝘂𝗱𝗲 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝗺𝘆 𝗼𝘄𝗻 𝗽𝗲𝗿𝘀𝗼𝗻𝗮𝗹 𝗹𝗶𝗳𝗲 𝗰𝗼𝗮𝗰𝗵.
A coach that holds my entire psychological map.
A coach that helps me reflect on myself.


𝗛𝗲𝗿𝗲'𝘀 𝗵𝗼𝘄 𝗶𝘁 𝘄𝗼𝗿𝗸𝘀:
I bring a feeling, a situation or a mental block and the coach will put this situation into context and then
➡️ connects it to patterns I already know about, but can't see in the moment.
➡️ draws a line between my programming and today's reaction and feelings.
➡️ reminds me of a technique I learned but forgot the second stress hit.
➡️ links themes I explored separately over years into one coherent picture.

This is not generic, like "have you tried journaling?"
It is tailored to the exact situation.
To my patterns, tools and context.


𝗧𝘄𝗼 𝗺𝗼𝗻𝘁𝗵𝘀 𝗶𝗻, 𝗜 𝗿𝗲𝗮𝗹𝗶𝘇𝗲𝗱 𝗵𝗼𝘄 𝗺𝘂𝗰𝗵 𝗵𝗮𝘀 𝗰𝗵𝗮𝗻𝗴𝗲𝗱 𝗳𝗼𝗿 𝗺𝗲:
✅ Every conversation teaches me something new about myself and is an invitation to reflect.
✅ I catch my loops faster and understand my reactions in real time instead of three days later.
✅ I navigate difficult emotions with more clarity and don't end up spiraling my thoughts for hours.
✅ I live more freely because I understand the mechanisms that used to run me on autopilot and cause pain

I'm being honest with you here - most often I sit in front of my screen crying
From being understood so completely that something breaks open within me.
A kind of recognition that's very rare, since no single person holds all your context at once.


Of course, Claude (or any other LLM) is not a therapist, and deep-seated issues need professional support.

But for me it works wonders as a daily companion for self-reflection to make tiny steps into the right direction.

And these tiny steps are what healing is all about!

Wishing everyone reading this a wonderful day and lots of strength and love for their very own path ❤️

---

Hi, I'm Fabian👋
I write about actionable data systems on GCP
(and how AI can be your personal coach 😉)
👉 Hit Follow
♻️ Repost, if you found this useful

taplio

The Battle

Paolo Perrone

Fabian Werkmeister

Followers

Posts

Engagements

Likes

Performance ScorePaolo Perrone's LinkedIn Performance

Performance ScoreFabian Werkmeister's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Paolo Perrone

Fabian Werkmeister

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Paolo Perrone's LinkedIn Performance

Performance ScoreFabian Werkmeister's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScorePaolo Perrone's LinkedIn Performance