Uploaded October 2026 | Updated November 2026, 3 days ago
I know someone who got laid off, and not because AI replaced him. It was because he didn't use AI enough.
We spend a lot of time worrying about AI taking our jobs, but the reality is more complicated. Companies are expecting smaller teams to do more, with each person using AI to amplify their output. Managers see AI and set higher performance targets, and the people who build AI into how they work set the new baseline. My friend is one example: he couldn't keep up with those metrics because he wasn't using AI effectively, and by the time he started, it was too late.
I also talk about:
• How my company (an AI-first company) factors meaningful AI use into performance
• Why job postings now ask for "AI-powered workflows" as a requirement
• The AI team app we built that connects tools like HubSpot and GitHub and frees up 2–3 hours a day
• Why automation doesn't mean layoffs, if your company is growing
• Why you still need to understand the fundamentals, even when you delegate to AI
So are we being replaced by AI, or by people who use AI better than us? Let me know what you think in the comments. I'm just the messenger.
⏱️ Chapters
0:00 Fired for not using AI?
1:19 AI is a tool, not magic
1:35 How my company measures AI use
2:18 Job postings that require AI workflows
3:11 The AI workflow app our team built
5:14 "We could replace teammates…"
6:11 Your new value: building your own AI systems
7:03 Growing vs. stagnant companies
8:31 Back to my friend's layoff
9:06 Still learn the skills behind the AI
10:12 Replaced by AI, or by people using AI?
#AI #Careers #SoftwareEngineering #DeveloperProductivity #FutureOfWork
I know someone who got laid off, and not because AI replaced him. It was because he didn't use AI enough.
We spend a lot of time worrying about AI taking our jobs, but the reality is more complicated. Companies are expecting smaller teams to do more, with each person using AI to amplify their output. Managers see AI and set higher performance targets, and the people who build AI into how they work set the new baseline. My friend is one example: he couldn't keep up with those metrics because he wasn't using AI effectively, and by the time he started, it was too late.
I also talk about:
• How my company (an AI-first company) factors meaningful AI use into performance
• Why job postings now ask for "AI-powered workflows" as a requirement
• The AI team app we built that connects tools like HubSpot and GitHub and frees up 2–3 hours a day
• Why automation doesn't mean layoffs, if your company is growing
• Why you still need to understand the fundamentals, even when you delegate to AI
So are we being replaced by AI, or by people who use AI better than us? Let me know what you think in the comments. I'm just the messenger.
⏱️ Chapters
0:00 Fired for not using AI?
1:19 AI is a tool, not magic
1:35 How my company measures AI use
2:18 Job postings that require AI workflows
3:11 The AI workflow app our team built
5:14 "We could replace teammates…"
6:11 Your new value: building your own AI systems
7:03 Growing vs. stagnant companies
8:31 Back to my friend's layoff
9:06 Still learn the skills behind the AI
10:12 Replaced by AI, or by people using AI?
#AI #Careers #SoftwareEngineering #DeveloperProductivity #FutureOfWork






![Strapi v5 Crash Course 2025 [ Part 4 learning populate and filtering in Strapi ]
Strapi tutorial part 4, we will learn about Strapis populate and filtering to only get the data we need from our API.
👉 Lesson Notes: https://www.codingafterthirty.com/courses/strapi-5-crash-course-2025/introduction-to-strapi-s-populate-and-filtering
👉 Learn more about Strapi: https://strapi.link/learn-more
Welcome back to Part 4 of our Strapi Crash Course! This tutorial will dive deep into how data population and filtering work in Strapi, ensuring you have the tools to manage your content effectively.
📚 What You’ll Learn:
- Understanding Top-Level Fields: In Strapi, top-level fields like title and description automatically populate, while relational fields require explicit queries.
- Creating Collection Types: Learn how to create new collection types and understand the significance of different field types in your data structure.
- Utilizing Components and Relations: Discover how to properly implement components and relationships to enhance your content architecture.
- Constructing Queries for Data Retrieval: Get hands-on with building queries to fetch nested data using both shorthand and object notation in Strapi.
🛠️ Key Takeaways:
- Master the basics of data population and filtering in Strapi.
- Gain hands-on experience with Strapis query syntax.
- Optimize your API calls to improve performance and efficiency.
💬 Join the Discussion. Have questions or need clarification? Drop your comments below, and dont forget to subscribe for more Strapi tutorials! Strapi v5 Crash Course 2025 [ Part 4 learning populate and filtering in Strapi ]](https://i.ytimg.com/vi/tAGNDGrVJfk/mqdefault.jpg)
![Building My Project with Next.js and Strapi [ Learning to code by building projects ]
#learntocode2023 #webdevelopment #buildinpublic
Friday Night Hangout 8:00 PM CST. Its Friday night, I am single, so I might as well do some coding. Building a profile page in my LMS project built with Next.js 15 and Strapi 5.
- Watch me try to code
- Ask questions
- Share some thoughts and ideas
Streaming my progress as I learn to code by building apps with Next.js and Strapi. Building My Project with Next.js and Strapi [ Learning to code by building projects ]](https://i.ytimg.com/vi/tMtm1jghGhk/mqdefault.jpg)
![Building a Dynamic Blog Website with Next.js and Strapi | Starter Project Walkthrough
Getting Started With Next.js 15 and Strapi 5 Headless CMS Project Overview [ All Code Included ]
Strapi 5 docs: https://strp.cc/3yHOhAw
Project Repo: https://github.com/PaulBratslavsky/strapi-5-next-js-starter-project
In todays video, I wanted to share a project Ive been working on—a simple blog website with dynamic content powered by Next.js on the front end and Strapi headless CMS on the back end.
Ill walk you through the basic features and how to set up the project locally so you can have all the code and run it on your computer.
Project includes:
- Dynamic landing page
- Header and Footer
- Blog section with pagination and search
- Single post view
- Login and Register page
- Middleware for protecting the routes
- Dashboard placeholder page
Project tech:
- Next.js 15
- Shadcn UI
- Tailwind
- Strapi
Ill also show you step-by-step instructions on how to set up the project on your local machine.
Although this is a starter demo project, its perfect for jumpstarting your blog website.
Key Topics Summary:
- Simple blog website project with dynamic content
- Next.js front end and Strapi headless CMS back end
- Blog section with posts, search, pagination, and user authentication
- Starter demo project for viewers to build upon
- Local setup process with repository cloning and setup script
- Use of Shadcn UI components and ReWeb page builder
- Strapi admin dashboard and content management
- Custom fetch function for data retrieval Building a Dynamic Blog Website with Next.js and Strapi | Starter Project Walkthrough](https://i.ytimg.com/vi/tRF_kjt0e4w/mqdefault.jpg)

![Building My Project with Next.js and Strapi [ Learning to code by building projects ]
#learntocode2025 #webdevelopment #buildinpublic
Friday Night Hangout 8:00 PM CST. Its Friday night, I am single, so I might as well do some coding. Building a profile page in my LMS project built with Next.js 15 and Strapi 5.
- Watch me try to code
- Ask questions
- Share some thoughts and ideas
Streaming my progress as I learn to code by building apps with Next.js and Strapi. Building My Project with Next.js and Strapi [ Learning to code by building projects ]](https://i.ytimg.com/vi/uAuP1b-c2Cs/mqdefault.jpg)