Bridging the gap between data and strategy ✦ Lead Data Strategy Consultant @ Redkite ✦ R Programmer ✦ Policy Nerd

Okay I probably have your attention here for about 10 seconds, so I’m going to be quick:

My niche is navigating the complex data world for organisations to help them deliver on their strategy

Basically, I bridge the gap between data and strategy

Want to know more? Here is how I do it:

💡 Learned as a strategy consultant what matters and what doesn’t
🎤 Storytell to help clients implement effectively (how do you properly engage the audience and infuse that story with the key takeaways/ implications)
💻 Use my R coding and strategy consulting experience to bridge the data scientist's "get lost in the data" approach with the "tell me what I need to know on one page" approach of the business executive
★ Live off my passion to see through positive outcomes, be that at work, on my blog or even when helping a friend

So why should you care?

1) I post my best tips 3-5x per week on LinkedIn
2) I make it relevant to you, as a student, business professional, executive, or whomever. My goal is to share relevant stuff with my audience
3) I try to be unique in what I share and deliver, as few people have the combination of experience I boast
4) I value feedback and input from all others out there. I pride myself on learning from others' perspectives so please add it to my content!

Also some of my other Outputs:
Medium - https://dylansjanderson.medium.com/
Blog Website - https://www.policyinnumbers.com/
Election App - https://danderson.shinyapps.io/Canada-Electoral-Model/
Academic Journal Article - https://www.cambridge.org/core/journals/canadian-journal-of-political-science-revue-canadienne-de-science-politique/article/tipping-point-of-a-strategic-vote-when-does-an-individual-vote-strategically/7FEDD21C59DF03AC15311CD13080881B

Dylan Anderson

Data teams are losing their audiences due to its increasing complexity

Unlimited tools, rising costs, increasing complexity, poor ROI. People want data/ AI, but how can you keep up?

As advanced as our tools have become, there is a growing gap in understanding what data really means for business

Data warehouses, lakes, and AI algorithms are complex, and the people expected to use them often lack the necessary guidance or expertise. After the hype wears off, senior leaders go from the excitement of possibility to the overwhelming reality of implementation.

For data leaders, this lost understanding is a huge problem:
🚫 Hinders potential investment
📉 Reduces organisational data literacy
🛑 Makes it harder to deliver new projects
💸 Complicates the ROI calculation of data initiatives
🧱 Gets in the way of creating a more data-centric culture

There is no silver bullet to solve this, but companies need to recognize why they are in this position, and steer the ship back in the right direction. Instead of thinking with a short-term mindset, they need to plan for the long-term:
🎯 Approach data strategically (including new trends, tools, and fads)
🧭 Understand the actions to operationalise the data strategy
🏗️ Hire and build internal capabilities for the long-term
⚙️ Shore up the foundations (e.g., data modelling, governance, platform, etc.)
🧹 Declutter the tooling repertoire and be smart about new technology choices
🔍 Constantly reassess existing issues and uncover root causes

Data is going to continue to get more complicated.

Are you ready for it?

Bridging the gap between data and strategy ✦ The Data Ecosystem Author ✦ Data & AI Leader ✦ Speaker ✦ R Programmer ✦ Policy Nerd

Your organisational structure underpins everything you do

But companies actively ignore it, and data people don't seem to mind

Here are three organisational structures to understand as a data person

🎯 𝐂𝐞𝐧𝐭𝐫𝐚𝐥𝐢𝐬𝐞𝐝 𝐒𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 – The centralized structure is the most basic view of data where all data functions are consolidated within a single, central team or department. They are responsible for all data activities, from storage to processing & transformations to distributing insights. Usually companies start with this type of structure given its simplicity and the need to have all the data operations in one place.

⚙️ 𝐃𝐞𝐜𝐞𝐧𝐭𝐫𝐚𝐥𝐢𝐬𝐞𝐝/ 𝐌𝐞𝐬𝐡 𝐒𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 – A decentralised data structure distributes data ownership, management, and activities across various domain-specific teams within the organisation. Each team is responsible for building its own data products and solutions, and managing all other data capabilities within that. Companies take a decentralised approach to develop functional domain experience (e.g., marketing, finance) within data teams and to build business-relevant products in a more agile way without the bureaucracy that centralised teams can bring.

🛠️ 𝐇𝐲𝐛𝐫𝐢𝐝/𝐇𝐮𝐛 & 𝐒𝐩𝐨𝐤𝐞 𝐒𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 – The hybrid approach (or hub & spoke model) is the most common organisational structure. It combines elements of both centralized and decentralized structures, usually having a central hub for infrastructure and governance with spokes (individual business units) managing domain-specific data activities like analytics.

Check out my article that digs into this in a lot more detail, including the pros, cons, best approaches, and considerations for each of these structures

AI is the first time we are seeing data become truly democratised
 
And that is a competitive advantage, if you are doing it correctly
 
This was the topic I addressed in the latest episode of DQE, Data Quality Everywhere's podcast "Let's Talk Data”: making data quality a competitive advantage with AI
 
Here’s why data quality matters and why you should listen to this episode if you have any of these goals:
 
𝐂𝐫𝐞𝐚𝐭𝐞𝐬 𝐚 𝐧𝐞𝐜𝐞𝐬𝐬𝐚𝐫𝐲 𝐟𝐨𝐮𝐧𝐝𝐚𝐭𝐢𝐨𝐧 𝐟𝐨𝐫 𝐀𝐈 𝐚𝐧𝐝 𝐚𝐧𝐚𝐥𝐲𝐭𝐢𝐜𝐚𝐥 𝐭𝐨𝐨𝐥𝐬 🏗️
- Reduces the cost of model development and maintenance
- Makes it easier to train, fine-tune, and deploy models effectively
 
𝐁𝐮𝐢𝐥𝐝𝐬 𝐭𝐫𝐮𝐬𝐭 𝐚𝐧𝐝 𝐚𝐜𝐜𝐞𝐬𝐬 𝐚𝐜𝐫𝐨𝐬𝐬 𝐭𝐡𝐞 𝐨𝐫𝐠𝐚𝐧𝐢𝐬𝐚𝐭𝐢𝐨𝐧 🔐
- Increases user adoption (think about how/ why ChatGPT took off)
- Reduces manual fixes and furthers automation
 
𝐃𝐫𝐢𝐯𝐞𝐬 𝐜𝐨𝐧𝐬𝐢𝐬𝐭𝐞𝐧𝐜𝐲 𝐚𝐜𝐫𝐨𝐬𝐬 𝐭𝐞𝐚𝐦𝐬 🎯
- Aligns your KPIs and definitions so everyone speaks the same language
 
How does AI do this?
🔍 Deduplicate data to eliminate redundant records
👁️ Provides better observability that captures business logic and context
📖 Clear data documentation and explanation (because people are lazy and don’t do this)
📐 Standardisation across sources for KPIs, metrics and processes
🔧 Ongoing data maintenance and compliance
 
Before AI, being data-driven meant coding. Even BI tools and dashboards require some level of technical skills to extract real insight
 
With a high barrier to entry, data stays siloed with the people who could query it (or stuck in Excel spreadsheets)
 
With AI, that's changing and natural language interfaces are opening up data to everyone.
 
But that only works if you set the right foundation. AI doesn't fix bad data, it amplifies it.
 
🎧 Listen to the full episode for more on how to make data quality your competitive advantage in the age of AI. Great to partner with DQE, Data Quality Everywhere on this one and check out their continuing podcast series on Data Quality, AI and what is next in data!

#ad

If you build it, they will come…user feedback that is, not users 😯

In the end your dashboard isn't for you, it's for the user! 

And their feedback isn't just advice; it's actionable intelligence. So here are some tips:

👂 𝐋𝐢𝐬𝐭𝐞𝐧 𝐛𝐞𝐟𝐨𝐫𝐞 𝐝𝐞𝐟𝐞𝐧𝐝𝐢𝐧𝐠 – Your dashboard may be your baby, but your baby needs to grow up. And when feedback comes in, absorb it before formulating a counter-argument

🔎 𝐒𝐞𝐞𝐤 𝐨𝐮𝐭 𝐭𝐡𝐞 𝐬𝐢𝐥𝐞𝐧𝐭 𝐦𝐚𝐣𝐨𝐫𝐢𝐭𝐲 – Only a fraction of users voice their opinions so find ways to capture input from others through surveys or one-on-one chats.

💡 𝐏𝐫𝐢𝐨𝐫𝐢𝐭𝐢𝐳𝐞, 𝐝𝐨𝐧’𝐭 𝐩𝐚𝐧𝐢𝐜 – Not all feedback needs immediate action. Categorize suggestions into 'Now,' 'Soon,' and 'Later' buckets based on urgency and impact.

🔄 𝐈𝐭𝐞𝐫𝐚𝐭𝐞, 𝐝𝐨𝐧'𝐭 𝐨𝐯𝐞𝐫𝐡𝐚𝐮𝐥 – Small, frequent updates are better than rare, seismic shifts. Your users will thank you for not changing everything at once.

📏 𝐌𝐞𝐚𝐬𝐮𝐫𝐞 𝐭𝐡𝐞 𝐢𝐦𝐩𝐚𝐜𝐭 – Before and after making changes, look at metrics like user engagement and task completion times. Did your tweaks lead to improvements?

⚙️ 𝐒𝐢𝐦𝐩𝐥𝐢𝐟𝐲 𝐭𝐡𝐞 𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐨𝐧𝐬 – Explaining the connections between databases and dashboard tools goes a long way in creating trust. Using tools like Orchestra (which are drag and drop, low-code) to do this make it that more relatable for stakeholders

🗂️ 𝐃𝐨𝐜𝐮𝐦𝐞𝐧𝐭, 𝐝𝐨𝐜𝐮𝐦𝐞𝐧𝐭, 𝐝𝐨𝐜𝐮𝐦𝐞𝐧𝐭 – Keep a log of all feedback and changes to track your progress and provide insights for future projects.

🙏 𝐀𝐜𝐤𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞 𝐚𝐧𝐝 𝐭𝐡𝐚𝐧𝐤 – Remember to thank the feedback-givers. Even a simple "Thank you for your input!" goes a long way in building a positive feedback culture.

So, how do you handle feedback for your dashboards? Any other tips?

The best thing about data is the conversations everybody wants to have to make things better

One of my favourite topics to discuss is data quality and its recent relevance in this new AI world

Teams need to take the time to think about this intersection in more detail because they are missing out

…And trust me, 80-90% of the organisations I work with aren’t doing this. There are so many data quality quick wins they can invest in to get them to the next level, if only they dug into it further and spent some time really thinking about what works!

 DQE, Data Quality Everywhere released their latest “Let’s Talk Data” podcast, where I had these great conversations with Philippe BOULANGER, PhD. It was a ton of fun and I recommend a listen for anybody wanting to learn more about the intersection of data quality and AI!

Open article: Ep2 | Data quality: How AI can turn data quality from a challenge into a competitive advantage by smartlink.ausha.co

Ep2 | Data quality: How AI can turn data quality from a challenge into a competitive advantage

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 📝

Google's new agent framework makes LangChain look like a toy.

It's called ADK. It treats agent development like software development
Not prompt engineering.

What it is:
→ Code-first agent development — Python, Java, TypeScript, Go
→ Event-driven runtime, not request-response
→ Version control, testing, CI/CD all work naturally

The agent primitives:
→ LlmAgent for reasoning
→ SequentialAgent, ParallelAgent, LoopAgent for deterministic pipelines
→ AgentTool: use agents as tools inside other agents
→ LLM-driven routing for dynamic task delegation

The tool ecosystem is where it gets ridiculous:
→ Google Search, Code Execution built-in
→ Full MCP support (BigQuery, Google Maps MCP servers)
→ Point it at any OpenAPI spec → auto-generates tools
→ Direct LangChain, LlamaIndex, CrewAI, LangGraph integration
→ Human-in-the-loop confirmation before tool execution
→ Long-running async tools

Model support:
→ Optimized for Gemini but model-agnostic
→ LiteLLM integration: swap in Anthropic, Meta, Mistral, anything
→ Any model in Vertex AI Model Garden

And it streams bidirectional audio and video out of the box.

pip install google-adk

💾 Save this before your next "which agent framework" debate.
♻️ Repost if your team is still duct-taping agents with prompt chains.

Stop paying for AI engineering bootcamps.

The fundamentals can be learned in 2-3 weeks. For free.

Here's everything you need:
→ https://lnkd.in/gCFQ69G9 — Andrew Ng's bite-sized courses
→ huggingface.co/learn — NLP, transformers, diffusion models
→ openai/openai-cookbook — Real production patterns
→ karpathy.ai/zero-to-hero — Build GPT from scratch
→ fast.ai — Practical deep learning, no PhD required

All excellent. If I had to pick one: Karpathy.
He teaches how it works, not just how to call the API.

♻️ Repost to save someone $2,000.

Open article: Hugging Face - Learn by huggingface.co

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.

taplio

The Battle

Dylan Anderson

Paolo Perrone

Followers

Posts

Engagements

Likes

Performance ScoreDylan Anderson's LinkedIn Performance

Performance ScorePaolo Perrone's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Dylan Anderson

Paolo Perrone

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);}Dylan Anderson's LinkedIn Performance

Performance ScorePaolo Perrone's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreDylan Anderson's LinkedIn Performance