NewCurious how Socialpruf works?Learn more
instagram analytics
Similar Accounts:
followers
114K
impressions
4.90M
likes
123K
comments
11.8K
posts
120
engagement
2.71%
emv
$144K
Average per post
40.8K

Key Metrics

Distributions

Top Content

👀 NEW Claude can now control your computer: Mouse, keyboard, and screen, giving it the ability to use any app without an MCP or connector. It does first check if you have a connector an will prompt you for permission. Read the “Claude Cowork Safety”official doc if you plan to use this. Here I’m using dispatch via Claude cowork to search and export one of the videos I edited locally in CapCut 🤯 (It did prompt me for specific permissions) It can open your apps, navigate your browser, fills in spreadsheets….anything you’d do sitting at your desk. Currently works on Mac for both Claude Cowork & Claude Code [ai engineer, tech news, agentic ai]
1.01M
23.9K
259
5mo ago
lindavivah
👀 NEW Claude can now control your computer: Mouse, keyboard, and screen, giving it the ability to use any app without an MCP or connector. It does first check if you have a connector an will prompt you for permission. Read the “Claude Cowork Safety”official doc if you plan to use this. Here I’m using dispatch via Claude cowork to search and export one of the videos I edited locally in CapCut 🤯 (It did prompt me for specific permissions) It can open your apps, navigate your browser, fills in spreadsheets….anything you’d do sitting at your desk. Currently works on Mac for both Claude Cowork & Claude Code [ai engineer, tech news, agentic ai]
Context vs Memory vs Harness engineering explained in 40 seconds by Richmond Alake ⚡️ 💡These 3 disciplines are core to building agents that can actually remember and reason over time Most agents work well within a single session but lose everything the moment it ends. Memory engineering treats long-term memory as first-class infrastructure. Richmond Alake (Director of AI DevEx at Oracle) walked me through all three in NYC🗽 ✈️ I’m PSYCHED to be heading to an offsite with the Oracle developer team very soon to go even deeper on agent harnesses & excited to share learnings with y’all! If you want to learn how to build memory-aware agents, Richmond has a free short DeepLearning.AI course in collaboration with Oracle that he co-taught with his colleague Nacho! 📚 Comment ✨DEVELOPER✨ and I’ll DM you the link to the free DeepLearning agent memory course & the AI Developer GitHub repo by Oracle to help you start building 💻
743K
26.5K
1.36K
4mo ago
lindavivah
Context vs Memory vs Harness engineering explained in 40 seconds by Richmond Alake ⚡️ 💡These 3 disciplines are core to building agents that can actually remember and reason over time Most agents work well within a single session but lose everything the moment it ends. Memory engineering treats long-term memory as first-class infrastructure. Richmond Alake (Director of AI DevEx at Oracle) walked me through all three in NYC🗽 ✈️ I’m PSYCHED to be heading to an offsite with the Oracle developer team very soon to go even deeper on agent harnesses & excited to share learnings with y’all! If you want to learn how to build memory-aware agents, Richmond has a free short DeepLearning.AI course in collaboration with Oracle that he co-taught with his colleague Nacho! 📚 Comment ✨DEVELOPER✨ and I’ll DM you the link to the free DeepLearning agent memory course & the AI Developer GitHub repo by Oracle to help you start building 💻
Why do the best ideas always hit when you are away from your desk 🌱 I was in Central Park and was able to tag Devin (@trycognition ) in Slack with my prompt to built AgentGeoScore, a site where you can check if your site is optimized for agent search Comment ✨DEVIN✨ & I’ll DM you the link to the GitHub repo & Devin to try it out for yourself! I also open sourced the code for agentgeoscore & will be maintaining it so feel free to contribute! I was super impressed but Devin’s native slack integration and how so many features are built-in and enterprise grade + easy to use out of the box. I was able to build so much just in the slack thread and get everything from screen recordings of the site, automatic security scans, merge from a button in the thread, Devin deploy right in the thread to see the site easily from anywhere & so much more! & since I used it via slack on my phone, context is never lost. If you try it out would love to hear your thoughts! & as always happy building!
494K
307
53
3mo ago
lindavivah
Why do the best ideas always hit when you are away from your desk 🌱 I was in Central Park and was able to tag Devin (@trycognition ) in Slack with my prompt to built AgentGeoScore, a site where you can check if your site is optimized for agent search Comment ✨DEVIN✨ & I’ll DM you the link to the GitHub repo & Devin to try it out for yourself! I also open sourced the code for agentgeoscore & will be maintaining it so feel free to contribute! I was super impressed but Devin’s native slack integration and how so many features are built-in and enterprise grade + easy to use out of the box. I was able to build so much just in the slack thread and get everything from screen recordings of the site, automatic security scans, merge from a button in the thread, Devin deploy right in the thread to see the site easily from anywhere & so much more! & since I used it via slack on my phone, context is never lost. If you try it out would love to hear your thoughts! & as always happy building!
7 core Claude Code features explained in 90 seconds.. let’s go! ⚡ To unlock Claude Code’s full potential you need to know what’s available to you. Here’s the TLDR: 🔷 CLAUDE.md → a markdown file Claude loads as context each session 🔷 Skills → packaged instructions Claude loads when the task matches 🔷 MCP → standard protocol for connecting Claude to external tools and data 🔷 Hooks → commands that run automatically at points in Claude’s lifecycle 🔷 Subagents → isolated Claude instances with their own context and tool access 🔷 Plugins → skills, hooks, and MCP configs bundled into one installable unit 🔷 Agent Teams → parallel Claude sessions with a lead, messaging each other directly
250K
8.95K
158
4mo ago
lindavivah
7 core Claude Code features explained in 90 seconds.. let’s go! ⚡ To unlock Claude Code’s full potential you need to know what’s available to you. Here’s the TLDR: 🔷 CLAUDE.md → a markdown file Claude loads as context each session 🔷 Skills → packaged instructions Claude loads when the task matches 🔷 MCP → standard protocol for connecting Claude to external tools and data 🔷 Hooks → commands that run automatically at points in Claude’s lifecycle 🔷 Subagents → isolated Claude instances with their own context and tool access 🔷 Plugins → skills, hooks, and MCP configs bundled into one installable unit 🔷 Agent Teams → parallel Claude sessions with a lead, messaging each other directly
Principal AI Architect & Engineer @codewithbrij walks through the 8 layers from LLM ➡️ Agentic AI Summary of the stack: 🧠 LLM → predicts the next word. Smart, but frozen. 📚 + RAG → reads your docs before answering. 🔧 + Tool Calling → now it can DO things. Call APIs, run code, query DBs. 💾 + Memory → remembers yesterday. Learns what works. 🤖 = AI Agent → LLM + RAG + Tools + Memory. 🤝 + Agentic AI → agents delegating to agents. Planning. Self-correcting. 🧩 + Skills & Hooks → modular know-how + lifecycle triggers. 🛡️ + Governance & Observability → traces, guardrails, audit. This is what makes it production. It was SO great getting to meet in person a few weeks back at the Oracle dev offsite! Check out Brij’s page @codewithbrij for the best technical infographics + AI education! And he is also one of the nicest people!
132K
3.28K
35
2mo ago
lindavivah
Principal AI Architect & Engineer @codewithbrij walks through the 8 layers from LLM ➡️ Agentic AI Summary of the stack: 🧠 LLM → predicts the next word. Smart, but frozen. 📚 + RAG → reads your docs before answering. 🔧 + Tool Calling → now it can DO things. Call APIs, run code, query DBs. 💾 + Memory → remembers yesterday. Learns what works. 🤖 = AI Agent → LLM + RAG + Tools + Memory. 🤝 + Agentic AI → agents delegating to agents. Planning. Self-correcting. 🧩 + Skills & Hooks → modular know-how + lifecycle triggers. 🛡️ + Governance & Observability → traces, guardrails, audit. This is what makes it production. It was SO great getting to meet in person a few weeks back at the Oracle dev offsite! Check out Brij’s page @codewithbrij for the best technical infographics + AI education! And he is also one of the nicest people!
Context Engine Architecture explained in 2 min ⏱️ .. walk with us in SF! Love how the Head of Context Engine @ Redis, Simba Khadder explains why we need this architecture: “Now we have agents that have hands. They need to be able to get data, act on data, search for more data.” Here’s the Context Engine Architecture breakdown: 🔹 Systems of record: your CRMs, databases, all the places your data already lives (you don’t want to wire an agent into 55 of them) 🔹 ETL: pulls it all into one materialized view, basically one live copy of your data that agents can actually use 🔹 Semantic layer: describes that data the way you’d explain it to a person: orders, users, items, not fields and tables 🔹 MCP: the open standard that lets the agent go grab that context on its own 🔹 Internal context: the agent also remembers what it’s done and caches answers it already figured out, so it doesn’t solve the same thing twice 💡 Put together, context stays fresh, navigable, and fast, and it compounds as the agent works. That’s the general pattern, whatever stack you use. Redis ships it as Redis Iris: RDI, Context Retriever, Agent Memory, and LangCache. Comment ✨CONTEXT✨ & I’ll send you the link to try Redis Iris for yourself for free
125K
2.59K
202
1w ago
lindavivah
Context Engine Architecture explained in 2 min ⏱️ .. walk with us in SF! Love how the Head of Context Engine @ Redis, Simba Khadder explains why we need this architecture: “Now we have agents that have hands. They need to be able to get data, act on data, search for more data.” Here’s the Context Engine Architecture breakdown: 🔹 Systems of record: your CRMs, databases, all the places your data already lives (you don’t want to wire an agent into 55 of them) 🔹 ETL: pulls it all into one materialized view, basically one live copy of your data that agents can actually use 🔹 Semantic layer: describes that data the way you’d explain it to a person: orders, users, items, not fields and tables 🔹 MCP: the open standard that lets the agent go grab that context on its own 🔹 Internal context: the agent also remembers what it’s done and caches answers it already figured out, so it doesn’t solve the same thing twice 💡 Put together, context stays fresh, navigable, and fast, and it compounds as the agent works. That’s the general pattern, whatever stack you use. Redis ships it as Redis Iris: RDI, Context Retriever, Agent Memory, and LangCache. Comment ✨CONTEXT✨ & I’ll send you the link to try Redis Iris for yourself for free
🎮NVIDIA & Microsoft brought a hands-on arcade for AI developers to Microsoft Build, & it’s available on-demand! If you didn’t get a chance to be in the room, this is a fantastic self-paced way to go from your first inference all the way to production-ready deployment. Comment ✨ARCADE✨& ill DM you the link! @nvidia @microsoft
103K
2.49K
1.34K
2mo ago
lindavivah
🎮NVIDIA & Microsoft brought a hands-on arcade for AI developers to Microsoft Build, & it’s available on-demand! If you didn’t get a chance to be in the room, this is a fantastic self-paced way to go from your first inference all the way to production-ready deployment. Comment ✨ARCADE✨& ill DM you the link! @nvidia @microsoft
🤩 Claude Code just launched Channels! Let’s set it up together 🎉 Channels allow you to control your Claude Code sessions through select MCP’s, starting with Telegram and Discord Comment ✨CHANNELS✨ & i’ll send the doc to your DM [AI Engineer, agentic AI, coding]
99.5K
2.73K
528
5mo ago
lindavivah
🤩 Claude Code just launched Channels! Let’s set it up together 🎉 Channels allow you to control your Claude Code sessions through select MCP’s, starting with Telegram and Discord Comment ✨CHANNELS✨ & i’ll send the doc to your DM [AI Engineer, agentic AI, coding]
Traditional RAG vs Graph RAG explained in 60 seconds by Nacho Martínez ⚡ 💡 Both pull external knowledge into an LLM. The difference is whether what comes back is isolated, or actually connected. 🔷 Traditional RAG chunks your docs, vectorizes each chunk, similarity search returns the top matches. Each piece stands alone. 🔷 Graph RAG organizes knowledge as a graph with edges between related items. Retrieval can follow those edges, so you get a match plus what it connects to. Some implementations store chunks as nodes and pull in neighbors. Others build a graph of entities and their relationships pulled from your docs. Same idea, different units. 🏢 i recently got to visit the Oracle office and spend the day with their amazing devrel team going deep on the Oracle AI Database, learning about their agentic AI work, and doing hands-on workshops. SO much good stuff. One thing that genuinely blew me away was that the Oracle AI database has JSON Relational Duality. You store your data once and access it as both relational rows AND JSON documents. No sync, no duplication 🔥 📚 Nacho Martínez (Data Scienctist Advocate at Oracle) shared a fantastic open source AI Developer Hub the team’s been building, includes notebooks on agentic RAG with hybrid search, RAG with evals, RAG zero-to-hero, and more. 💻 Comment ✨DEVELOPER✨ and I’ll DM you the link to repo to start building
94.7K
3.57K
69
3mo ago
lindavivah
Traditional RAG vs Graph RAG explained in 60 seconds by Nacho Martínez ⚡ 💡 Both pull external knowledge into an LLM. The difference is whether what comes back is isolated, or actually connected. 🔷 Traditional RAG chunks your docs, vectorizes each chunk, similarity search returns the top matches. Each piece stands alone. 🔷 Graph RAG organizes knowledge as a graph with edges between related items. Retrieval can follow those edges, so you get a match plus what it connects to. Some implementations store chunks as nodes and pull in neighbors. Others build a graph of entities and their relationships pulled from your docs. Same idea, different units. 🏢 i recently got to visit the Oracle office and spend the day with their amazing devrel team going deep on the Oracle AI Database, learning about their agentic AI work, and doing hands-on workshops. SO much good stuff. One thing that genuinely blew me away was that the Oracle AI database has JSON Relational Duality. You store your data once and access it as both relational rows AND JSON documents. No sync, no duplication 🔥 📚 Nacho Martínez (Data Scienctist Advocate at Oracle) shared a fantastic open source AI Developer Hub the team’s been building, includes notebooks on agentic RAG with hybrid search, RAG with evals, RAG zero-to-hero, and more. 💻 Comment ✨DEVELOPER✨ and I’ll DM you the link to repo to start building
Andrew Ng & the @deeplearningai team analyzed 10,000+ job postings + expert interviews & just shared the skills that matter most in AI engineering right now for developers 📚 The 4 skills: 🔹 Building & deploying AI applications: AI systems have unpredictable outputs, so the work is learning the building blocks (RAG, evals, agentic workflows, context engineering) and using them to measure, steer, and govern how the system behaves 🔹 Software engineering fundamentals: so much of software engineering is actually trade-offs (cost, speed, scalability, reliability, security). It’s making decisions, and if you don’t know the trade-offs, it’s hard to make those decisions 🔹 Using coding agents: building a mental model of what agents can and can’t do, managing context, balancing planning vs execution, and keeping current as the tools evolve 🔹 Shaping the build: participating in the spec decisions themselves, which takes product sense and an understanding of business context and customer goals. Part of the skill is knowing when to spin up an MVP and when to build carefully Comment SKILLS and I’ll send you the link to the report 📩
81.7K
1.81K
379
3d ago
lindavivah
Andrew Ng & the @deeplearningai team analyzed 10,000+ job postings + expert interviews & just shared the skills that matter most in AI engineering right now for developers 📚 The 4 skills: 🔹 Building & deploying AI applications: AI systems have unpredictable outputs, so the work is learning the building blocks (RAG, evals, agentic workflows, context engineering) and using them to measure, steer, and govern how the system behaves 🔹 Software engineering fundamentals: so much of software engineering is actually trade-offs (cost, speed, scalability, reliability, security). It’s making decisions, and if you don’t know the trade-offs, it’s hard to make those decisions 🔹 Using coding agents: building a mental model of what agents can and can’t do, managing context, balancing planning vs execution, and keeping current as the tools evolve 🔹 Shaping the build: participating in the spec decisions themselves, which takes product sense and an understanding of business context and customer goals. Part of the skill is knowing when to spin up an MVP and when to build carefully Comment SKILLS and I’ll send you the link to the report 📩
Love the way @gregisenberg phrased it 💡 Comment ✨OPTIMIZE✨ and I’ll send you 5 prompts for your vibe coding tool of choice to help your site get read and cited by AI agents 🌐
75.5K
2.39K
1.68K
4mo ago
lindavivah
Love the way @gregisenberg phrased it 💡 Comment ✨OPTIMIZE✨ and I’ll send you 5 prompts for your vibe coding tool of choice to help your site get read and cited by AI agents 🌐
There has been an 800% increase in FDE (forward deployed engineer) job postings in the past year 🤯 So I had to ask the INCREDIBLE Leah McGowen-Hare, SVP of Forward Deployed Engineering @salesforce , whose team tripled in just six months, how they define the role and what they look for when they hire Last month I attended Agentforce World Tour NY and Leah’s keynote was absolutely fantastic! One of the best speakers I’ve seen. I was fangirling 🥹🤍 An FDE is a deep technical expert across the Agentforce suite, part tech guru, part business consultant, the person who can make or break an AI agent launch. Leah’s take: they’re the unicorns on the front line with customers, with a direct line back to product so what they learn in the field shapes the roadmap. And who they hire for it? The curious ones. The constant learners and tinkerers who want to stay on the brink of the newest tech #SalesforcePartner
74.2K
1.49K
50
3mo ago
lindavivah
There has been an 800% increase in FDE (forward deployed engineer) job postings in the past year 🤯 So I had to ask the INCREDIBLE Leah McGowen-Hare, SVP of Forward Deployed Engineering @salesforce , whose team tripled in just six months, how they define the role and what they look for when they hire Last month I attended Agentforce World Tour NY and Leah’s keynote was absolutely fantastic! One of the best speakers I’ve seen. I was fangirling 🥹🤍 An FDE is a deep technical expert across the Agentforce suite, part tech guru, part business consultant, the person who can make or break an AI agent launch. Leah’s take: they’re the unicorns on the front line with customers, with a direct line back to product so what they learn in the field shapes the roadmap. And who they hire for it? The curious ones. The constant learners and tinkerers who want to stay on the brink of the newest tech #SalesforcePartner
Let’s see if I can cover the ML pipeline in 60 seconds ⏰😅 Machine learning isn’t just training a model. A production ML lifecycle typically looks like this: 1️⃣ Define the problem & objective 2️⃣ Collect and (if needed) label data 3️⃣ Split into train / validation / test sets 4️⃣ Data preprocessing & feature engineering 5️⃣ Train the model (forward pass + backpropagation in deep learning) 6️⃣ Evaluate on held-out data to measure generalization 7️⃣ Hyperparameter tuning (learning rate, architecture, etc.) 8️⃣ Final testing before release 9️⃣ Deploy (batch inference or real-time serving behind an API) 🔟 Monitor for data drift, concept drift, latency, cost, and reliability 1️⃣1️⃣ Retrain when performance degrades Training updates weights. Evaluation measures performance. Deployment serves predictions. Monitoring keeps the system healthy. It’s not linear. It’s a loop. And once you move beyond a single experiment, that loop becomes a systems problem. At scale, the challenge isn’t just modeling … it’s building reliable, scalable infrastructure that supports the entire lifecycle. Curious if this type of content is helpful! Lmk in the comments & as always Happy Building! 🤍
64.2K
3.81K
60
6mo ago
lindavivah
Let’s see if I can cover the ML pipeline in 60 seconds ⏰😅 Machine learning isn’t just training a model. A production ML lifecycle typically looks like this: 1️⃣ Define the problem & objective 2️⃣ Collect and (if needed) label data 3️⃣ Split into train / validation / test sets 4️⃣ Data preprocessing & feature engineering 5️⃣ Train the model (forward pass + backpropagation in deep learning) 6️⃣ Evaluate on held-out data to measure generalization 7️⃣ Hyperparameter tuning (learning rate, architecture, etc.) 8️⃣ Final testing before release 9️⃣ Deploy (batch inference or real-time serving behind an API) 🔟 Monitor for data drift, concept drift, latency, cost, and reliability 1️⃣1️⃣ Retrain when performance degrades Training updates weights. Evaluation measures performance. Deployment serves predictions. Monitoring keeps the system healthy. It’s not linear. It’s a loop. And once you move beyond a single experiment, that loop becomes a systems problem. At scale, the challenge isn’t just modeling … it’s building reliable, scalable infrastructure that supports the entire lifecycle. Curious if this type of content is helpful! Lmk in the comments & as always Happy Building! 🤍
Comment “MCP” & I’II send you the links via DM ✨ In late 2024, Anthropic introduced MCP (Model Context Protocol) because LLMs needed a cleaner, safer way to interact with the outside world. In just a year it already has over 97 million SDK downloads and 2 weeks ago Anthropic announced it’s donating MCP to the Linux Foundation. MCP is like giving models a shared language to access tools, trigger workflows, and pull data. The entire point of MCP is to make LLM’s more capable in a standardized way. These are some of the resources I found helpful when starting to build MCP servers & clients. I limited it to beginner friendly resources I thought were great but Imk if it would be helpful to share more advanced finds as well. Hope this helps others! Are there others you would add to the list? Lmk in the comments & as always Happy Building! Relevant tags 🏷️ [ai engineer, genai career, software engineer, software developer, MCP roadmap, how to learn ai, python for ai, lim from scratch, build in public, ai agent builder, deep learning 2025, ai portfolio project, ml roadmap, ai learning journey, agentic ai]
58.8K
1.31K
1.04K
8mo ago
lindavivah
Comment “MCP” & I’II send you the links via DM ✨ In late 2024, Anthropic introduced MCP (Model Context Protocol) because LLMs needed a cleaner, safer way to interact with the outside world. In just a year it already has over 97 million SDK downloads and 2 weeks ago Anthropic announced it’s donating MCP to the Linux Foundation. MCP is like giving models a shared language to access tools, trigger workflows, and pull data. The entire point of MCP is to make LLM’s more capable in a standardized way. These are some of the resources I found helpful when starting to build MCP servers & clients. I limited it to beginner friendly resources I thought were great but Imk if it would be helpful to share more advanced finds as well. Hope this helps others! Are there others you would add to the list? Lmk in the comments & as always Happy Building! Relevant tags 🏷️ [ai engineer, genai career, software engineer, software developer, MCP roadmap, how to learn ai, python for ai, lim from scratch, build in public, ai agent builder, deep learning 2025, ai portfolio project, ml roadmap, ai learning journey, agentic ai]
AI Engineer vs ML Engineer explained (while my youngest naps in Central Park 😂👶🍃) 🧠 ML engineers primarily focus on model training and performance optimization. That typically includes: • Data preprocessing and feature engineering • Designing and maintaining training pipelines • Selecting architectures and loss functions • Running experiments and tracking metrics • Hyperparameter tuning • Evaluating generalization performance • Scaling distributed training workloads Their center of gravity is improving how a model is trained and how well it performs. 🏗️ AI engineers primarily focus on system design and production deployment of AI capabilities. That typically includes: • Integrating trained or foundation models into applications • Designing RAG pipelines and agent architectures • Orchestrating tools, APIs, and external services • Managing state, retries, and failure handling • Implementing guardrails and evaluation frameworks • Optimizing latency, throughput, and cost • Scaling inference and serving infrastructure Their center of gravity is ensuring the AI system behaves reliably, safely, and efficiently in real-world environments. 🎯 Same end goal: production-ready AI. But they operate at different layers of the stack. 💡If you want a sticky way to remember it: ML engineers build and tune the brain. AI engineers build the nervous system and body around it. One optimizes how intelligence is trained. The other optimizes how intelligence is expressed and delivered. 🏷️ #AIEngineer #MLEngineer #DistributedSystems #LLMs #AgenticAI AIInfrastructure MachineLearning
49.5K
2.17K
72
6mo ago
lindavivah
AI Engineer vs ML Engineer explained (while my youngest naps in Central Park 😂👶🍃) 🧠 ML engineers primarily focus on model training and performance optimization. That typically includes: • Data preprocessing and feature engineering • Designing and maintaining training pipelines • Selecting architectures and loss functions • Running experiments and tracking metrics • Hyperparameter tuning • Evaluating generalization performance • Scaling distributed training workloads Their center of gravity is improving how a model is trained and how well it performs. 🏗️ AI engineers primarily focus on system design and production deployment of AI capabilities. That typically includes: • Integrating trained or foundation models into applications • Designing RAG pipelines and agent architectures • Orchestrating tools, APIs, and external services • Managing state, retries, and failure handling • Implementing guardrails and evaluation frameworks • Optimizing latency, throughput, and cost • Scaling inference and serving infrastructure Their center of gravity is ensuring the AI system behaves reliably, safely, and efficiently in real-world environments. 🎯 Same end goal: production-ready AI. But they operate at different layers of the stack. 💡If you want a sticky way to remember it: ML engineers build and tune the brain. AI engineers build the nervous system and body around it. One optimizes how intelligence is trained. The other optimizes how intelligence is expressed and delivered. 🏷️ #AIEngineer #MLEngineer #DistributedSystems #LLMs #AgenticAI AIInfrastructure MachineLearning
The beauty about tech is there is no one path. 🌱 One of the biggest lessons throughout my journey has been that what felt like the hardest parts often involved “figuring out my next growth step”. The decision is sometimes harder than the execution. ⚙️ Overtime, I learned those phases of “going in circles” are totally normal & actually a lot of the work within your journey. 🔁 For example, it took me a while to figure out that I would like to go in to SRE from webdev etc. 🔁 the same thing happened when I decided it was time to go to a startup and the AI infra end. Have you experienced something similar? Lmk in comments 🤎 ⬇️ 💡 Remember, YOU are the artist of your own life 🎨 Summary of my Untraditional Journey in to Tech & Cloud & AI: 💻 2013: graduated BA in Philosophy & started working in media 💻 2015: started teaching myself how to code & a few months later attended a coding bootcamp (@flatironschool Fullstack Web Dev immersive) 💻 2016: started working as a javaScript Web Developer in media 💻 2018: Started teaching myself Cloud Computing via certs & projects, specifically AWS 💻 2020: Shifted in to an SRE role to work in Cloud on Infra end & later infrastructure/devops 💻 2022: Started working as a cloud Developer Advocate @ AWS 💻 2023: When chatGPT launched late 2022 overtime that year upskilled and kept experimenting 💻 2024: my role at AWS officially focused on AI developer advocacy & AWS genAI services + kept upskilling in AI/ML, AI engineering 💻2025: Started to work as a Staff AI infra developer advocate at Anyscale (distributed computing). This was also a shift from corporate to startup for me and I wanted to go to the AI infra end. Currently get to work on Ray which is an open source distributing compute engine that is especially suited for AI/ML workloads (Batch Inf, Distributed Training, etc..) Relevant tags: [ AI engineer, career journey, machine learning, cloud computing, programmer, computer science, devops, MLOps, coding, setup inspiration, tech career ]
47.5K
799
67
6mo ago
lindavivah
The beauty about tech is there is no one path. 🌱 One of the biggest lessons throughout my journey has been that what felt like the hardest parts often involved “figuring out my next growth step”. The decision is sometimes harder than the execution. ⚙️ Overtime, I learned those phases of “going in circles” are totally normal & actually a lot of the work within your journey. 🔁 For example, it took me a while to figure out that I would like to go in to SRE from webdev etc. 🔁 the same thing happened when I decided it was time to go to a startup and the AI infra end. Have you experienced something similar? Lmk in comments 🤎 ⬇️ 💡 Remember, YOU are the artist of your own life 🎨 Summary of my Untraditional Journey in to Tech & Cloud & AI: 💻 2013: graduated BA in Philosophy & started working in media 💻 2015: started teaching myself how to code & a few months later attended a coding bootcamp (@flatironschool Fullstack Web Dev immersive) 💻 2016: started working as a javaScript Web Developer in media 💻 2018: Started teaching myself Cloud Computing via certs & projects, specifically AWS 💻 2020: Shifted in to an SRE role to work in Cloud on Infra end & later infrastructure/devops 💻 2022: Started working as a cloud Developer Advocate @ AWS 💻 2023: When chatGPT launched late 2022 overtime that year upskilled and kept experimenting 💻 2024: my role at AWS officially focused on AI developer advocacy & AWS genAI services + kept upskilling in AI/ML, AI engineering 💻2025: Started to work as a Staff AI infra developer advocate at Anyscale (distributed computing). This was also a shift from corporate to startup for me and I wanted to go to the AI infra end. Currently get to work on Ray which is an open source distributing compute engine that is especially suited for AI/ML workloads (Batch Inf, Distributed Training, etc..) Relevant tags: [ AI engineer, career journey, machine learning, cloud computing, programmer, computer science, devops, MLOps, coding, setup inspiration, tech career ]
Google engineer explains Agent Evaluation vs Model Evaluation in 30 seconds ⚡ 🚙 Think of getting your driver’s license. First there’s the theory test, where you’re assessed on knowledge and getting the right answers. Then there’s the road test, where you’re out in the real world actually using tools and doing things to get around. That sequence of steps out on the road has a name. It’s called the trajectory, and evaluating it is one of the things that makes agent evaluation different from model evaluation. Getting an agent from your laptop to production has stayed stubbornly fragmented, which is exactly what Agents CLI is built to fix. It works with your coding agent (Claude Code, Gemini CLI, Codex) across the whole lifecycle: It’s the programmatic backbone for the whole agent lifecycle, and it works with your coding agent (Claude Code, Gemini CLI, Codex): 🔹 Scaffold a new agent project 🔹 Build on ADK, Google’s open source agent framework 🔹 Evaluate: generate runs, grade them, optimize, repeat 🔹 Deploy and add observability 💡 Once you’ve built and deployed your agent, it can integrate right into the Gemini Enterprise Agent Platform, Google’s platform to build, scale, govern, and optimize enterprise-grade agents. That’s where it runs and scales across your org. Comment ✨AGENTS✨ & I’ll DM you the links Thank you to @pier_paolo28 for joining me on a Tech Walk and breaking this down so clearly!
41.4K
1.21K
59
1mo ago
lindavivah
Google engineer explains Agent Evaluation vs Model Evaluation in 30 seconds ⚡ 🚙 Think of getting your driver’s license. First there’s the theory test, where you’re assessed on knowledge and getting the right answers. Then there’s the road test, where you’re out in the real world actually using tools and doing things to get around. That sequence of steps out on the road has a name. It’s called the trajectory, and evaluating it is one of the things that makes agent evaluation different from model evaluation. Getting an agent from your laptop to production has stayed stubbornly fragmented, which is exactly what Agents CLI is built to fix. It works with your coding agent (Claude Code, Gemini CLI, Codex) across the whole lifecycle: It’s the programmatic backbone for the whole agent lifecycle, and it works with your coding agent (Claude Code, Gemini CLI, Codex): 🔹 Scaffold a new agent project 🔹 Build on ADK, Google’s open source agent framework 🔹 Evaluate: generate runs, grade them, optimize, repeat 🔹 Deploy and add observability 💡 Once you’ve built and deployed your agent, it can integrate right into the Gemini Enterprise Agent Platform, Google’s platform to build, scale, govern, and optimize enterprise-grade agents. That’s where it runs and scales across your org. Comment ✨AGENTS✨ & I’ll DM you the links Thank you to @pier_paolo28 for joining me on a Tech Walk and breaking this down so clearly!
⚡What are Declarative Pipelines in < 90 seconds? Let’s walk with Michael Armbrust, Distinguished Engineer at @databricksinc who led the design & development of Declarative Pipelines + created Spark SQL, Structured Streaming, Delta Lake, & much more as he breaks it down! 💡 TLDR: instead of telling the system HOW to do every step, you just tell it WHAT you want to exist. Spark figures out the how. The technology itself is open source in Apache Spark, and Databricks offers a managed version on top called Lakeflow Spark Declarative Pipelines. 💻 Want to get started with Declarative Pipelines? Comment ✨Databricks✨ & I’ll send you the resources: an intro hands-on tutorial + Michael’s recorded deep dive talk from the Data + AI Summit 2026. It was such a blast getting to chat with Michael! Did you know he was also the 9th employee at Databricks?! As always, Happy Building! 😊 #DatabricksPartner
41.0K
811
84
2mo ago
lindavivah
⚡What are Declarative Pipelines in < 90 seconds? Let’s walk with Michael Armbrust, Distinguished Engineer at @databricksinc who led the design & development of Declarative Pipelines + created Spark SQL, Structured Streaming, Delta Lake, & much more as he breaks it down! 💡 TLDR: instead of telling the system HOW to do every step, you just tell it WHAT you want to exist. Spark figures out the how. The technology itself is open source in Apache Spark, and Databricks offers a managed version on top called Lakeflow Spark Declarative Pipelines. 💻 Want to get started with Declarative Pipelines? Comment ✨Databricks✨ & I’ll send you the resources: an intro hands-on tutorial + Michael’s recorded deep dive talk from the Data + AI Summit 2026. It was such a blast getting to chat with Michael! Did you know he was also the 9th employee at Databricks?! As always, Happy Building! 😊 #DatabricksPartner
Claude Chat vs Claude Code vs Claude Cowork - when do you use what? I got you👇 It comes down to two things: 1️⃣ How much access Claude has? 2️⃣ How much YOU want to stay in the loop vs delegate? 🍪 Quick preface though…. no one eats an Oreo the same way these 3 have overlap by design especially Claude Code and Cowork. Best way is to try it out 💬 Chat is what most people start with. You’re driving every step. Web search, connectors, MCP, the whole thing. It’s great for thinking together. And if you want to share a workspace with your team, Projects in Chat is still the only place where that’s actually shareable. 💻Claude Code is the most powerful, and honestly the most flexible. It lives wherever you do, terminal, IDE, the desktop app, the web, even your phone. Channels lets you text it from Telegram or Discord, which is wild. Full filesystem, full codebase, edits across files, runs tests, opens PRs. You can spin up agent teams in parallel. And since I filmed this, Routines also shipped, which means Code can now run on a schedule, an API call, or a GitHub event in Anthropic’s cloud, even when your laptop is closed. If the output is code, this is your surface. 💼 Cowork is on the desktop app. Same engine as Code, no terminal, no setup. You give it a goal and it works through your local files and apps and comes back with a finished doc, report, or spreadsheet. Dispatch feature lets you message it from your phone but the work still runs on your desktop. ✨ The coolest thing about AI is personalization & there are constant updates but there is no right or wrong. It takes time to find a routine and i would first approach it as experimentation with no pressure of choosing 😊 [AI engineer, anthropic, coding]
35.9K
1.13K
33
4mo ago
lindavivah
Claude Chat vs Claude Code vs Claude Cowork - when do you use what? I got you👇 It comes down to two things: 1️⃣ How much access Claude has? 2️⃣ How much YOU want to stay in the loop vs delegate? 🍪 Quick preface though…. no one eats an Oreo the same way these 3 have overlap by design especially Claude Code and Cowork. Best way is to try it out 💬 Chat is what most people start with. You’re driving every step. Web search, connectors, MCP, the whole thing. It’s great for thinking together. And if you want to share a workspace with your team, Projects in Chat is still the only place where that’s actually shareable. 💻Claude Code is the most powerful, and honestly the most flexible. It lives wherever you do, terminal, IDE, the desktop app, the web, even your phone. Channels lets you text it from Telegram or Discord, which is wild. Full filesystem, full codebase, edits across files, runs tests, opens PRs. You can spin up agent teams in parallel. And since I filmed this, Routines also shipped, which means Code can now run on a schedule, an API call, or a GitHub event in Anthropic’s cloud, even when your laptop is closed. If the output is code, this is your surface. 💼 Cowork is on the desktop app. Same engine as Code, no terminal, no setup. You give it a goal and it works through your local files and apps and comes back with a finished doc, report, or spreadsheet. Dispatch feature lets you message it from your phone but the work still runs on your desktop. ✨ The coolest thing about AI is personalization & there are constant updates but there is no right or wrong. It takes time to find a routine and i would first approach it as experimentation with no pressure of choosing 😊 [AI engineer, anthropic, coding]
3 things you can start building with right now 👇 1. The GitHub Copilot app, an agent-native desktop experience built on GitHub, is now in an expanded technical preview. You decide what agents tackle, how much autonomy each agent gets, and what ships. Go from issue to merged pull request without leaving the app. 2. An optimized Windows 11 experience to help developers build and ship faster including: • Coreutils for Windows - a set of Linux-like command line utilities that run natively on Windows • WSL containers - a built-in way to create, run and interact with Linux containers using familiar CLI & API • Intelligent Terminal - intentionally brings context-aware intelligence to your favorite agents directly into a terminal based experience to help debug errors and run multi-step tasks so you can stay in your flow • Windows Developer Configurations - powered by WinGet, sets up a distraction-free dev environment with VS Code, GitHub Copilot, WSL, PowerShell 7 and developer-optimized settings with one command on any Windows 11 device 3. OpenClaw now runs the node and gateway securely on Windows leveraging Microsoft Execution Containers (MXC), a cross-platform, policy-driven execution layer that lets developers declare what an agent can access, with containment boundaries enforced at runtime.
34.6K
438
27
2mo ago
lindavivah
3 things you can start building with right now 👇 1. The GitHub Copilot app, an agent-native desktop experience built on GitHub, is now in an expanded technical preview. You decide what agents tackle, how much autonomy each agent gets, and what ships. Go from issue to merged pull request without leaving the app. 2. An optimized Windows 11 experience to help developers build and ship faster including: • Coreutils for Windows - a set of Linux-like command line utilities that run natively on Windows • WSL containers - a built-in way to create, run and interact with Linux containers using familiar CLI & API • Intelligent Terminal - intentionally brings context-aware intelligence to your favorite agents directly into a terminal based experience to help debug errors and run multi-step tasks so you can stay in your flow • Windows Developer Configurations - powered by WinGet, sets up a distraction-free dev environment with VS Code, GitHub Copilot, WSL, PowerShell 7 and developer-optimized settings with one command on any Windows 11 device 3. OpenClaw now runs the node and gateway securely on Windows leveraging Microsoft Execution Containers (MXC), a cross-platform, policy-driven execution layer that lets developers declare what an agent can access, with containment boundaries enforced at runtime.

Linda Y (@lindavivah) Instagram Stats & Analytics

Linda Y (@lindavivah) has 114K Instagram followers with a 2.71% engagement rate over the past 12 months. Across 120 posts, Linda Y received 123K total likes and 4.75M impressions, averaging 1.02K likes per post. This page tracks Linda Y's performance metrics, top content, and engagement trends — updated daily.

Linda Y (@lindavivah) Instagram Analytics FAQ

How many Instagram followers does Linda Y have?+
Linda Y (@lindavivah) has 114K Instagram followers as of September 2026.
What is Linda Y's Instagram engagement rate?+
Linda Y's Instagram engagement rate is 2.71% over the last 12 months, based on 120 posts.
How many likes does Linda Y get on Instagram?+
Linda Y received 123K total likes across 120 posts in the last 12 months, averaging 1.02K likes per post.
How many Instagram impressions does Linda Y get?+
Linda Y's Instagram content generated 4.75M total impressions over the last 12 months.