Uploaded November 2026 | Updated November 2026, 3 hours ago
Your company is starting to grade you on how you use AI, whether you like AI or not. This year, "how did you use AI and how much did it improve your performance?" is part of the performance reviews where I work.
A friend of mine got laid off, and the reason he was given: he didn't use AI enough. My old roommate, a senior architect, asked to hire and was told to build AI workflows first. And someone who isn't even on the engineering team ended up in the top 10 contributors to a codebase with 30 PRs, which made the manager take a hard look at his own team.
This isn't about AI replacing developers. It's about the baseline moving. Companies exist to make money, and even a 2-5% productivity gain is worth it to them. So you're not compared to a good engineer anymore. You're compared to a good engineer who's good with AI.
And AI literacy doesn't mean prompting ChatGPT or Claude. It means building the workflows, internal tools and harnesses that make you and your team more productive. I'm no longer doing the thing. I'm building the thing that does the thing for me.
In this video:
- Why companies will push you to use AI
- What AI literacy means at work (it's not prompting)
- Getting laid off for not using AI enough
- "We're not hiring. Build AI workflows first."
- AI use in performance reviews
The video I mention at the start: The AI literacy gap is the new printing press moment
youtu.be/WX90CM3K-T8
One of the "laid off for not using AI" stories I mention: Laid off as an AI engineer (don't make my mistake) by Michael Hoff
youtu.be/vAzcFVSGGJM
Is AI use part of how you're measured at work yet, or is your company still on the fence? Tell me in the comments.
0:00 My last AI video flopped
0:43 Why your company will make you use AI
1:13 What AI literacy means (not just prompting)
1:43 Laid off for not using AI enough
2:12 Your AI use has to be trackable
3:24 Build the thing that does the thing
4:21 Why even a 2% gain matters
5:12 "We're not hiring. Build AI workflows first."
6:10 A non-engineer in the top 10 contributors
7:42 AI is now in performance reviews
#AI #SoftwareEngineering #Developers #AIatWork #Programming
Your company is starting to grade you on how you use AI, whether you like AI or not. This year, "how did you use AI and how much did it improve your performance?" is part of the performance reviews where I work.
A friend of mine got laid off, and the reason he was given: he didn't use AI enough. My old roommate, a senior architect, asked to hire and was told to build AI workflows first. And someone who isn't even on the engineering team ended up in the top 10 contributors to a codebase with 30 PRs, which made the manager take a hard look at his own team.
This isn't about AI replacing developers. It's about the baseline moving. Companies exist to make money, and even a 2-5% productivity gain is worth it to them. So you're not compared to a good engineer anymore. You're compared to a good engineer who's good with AI.
And AI literacy doesn't mean prompting ChatGPT or Claude. It means building the workflows, internal tools and harnesses that make you and your team more productive. I'm no longer doing the thing. I'm building the thing that does the thing for me.
In this video:
- Why companies will push you to use AI
- What AI literacy means at work (it's not prompting)
- Getting laid off for not using AI enough
- "We're not hiring. Build AI workflows first."
- AI use in performance reviews
The video I mention at the start: The AI literacy gap is the new printing press moment
youtu.be/WX90CM3K-T8
One of the "laid off for not using AI" stories I mention: Laid off as an AI engineer (don't make my mistake) by Michael Hoff
youtu.be/vAzcFVSGGJM
Is AI use part of how you're measured at work yet, or is your company still on the fence? Tell me in the comments.
0:00 My last AI video flopped
0:43 Why your company will make you use AI
1:13 What AI literacy means (not just prompting)
1:43 Laid off for not using AI enough
2:12 Your AI use has to be trackable
3:24 Build the thing that does the thing
4:21 Why even a 2% gain matters
5:12 "We're not hiring. Build AI workflows first."
6:10 A non-engineer in the top 10 contributors
7:42 AI is now in performance reviews
#AI #SoftwareEngineering #Developers #AIatWork #Programming
![Strapi v5 Crash Course 2025 [ Part 10 Building dynamic page with dynamic zones ]
In Strapi tutorial part 10, how to build dynamic pages in Strapi
👉 Lesson Notes: https://www.codingafterthirty.com/courses/strapi-5-crash-course-2025/building-our-landing-page-part-3
👉 Learn more about Strapi: https://strapi.link/learn-more
In this video, we’ll explore how to create dynamic pages in Strapi, giving you the ability to build a robust and flexible website. Say goodbye to static pages and hello to a content management system that empowers your editors!
Understanding Collection Types
We’ll start by explaining the difference between single types and collection types in Strapi. You’ll learn why collection types are crucial for dynamic page creation.
Setting Up Your Pages
Next, I’ll guide you through the setup process for a new page collection type. You’ll see how to include essential fields like title, description, and slug, as well as how to add dynamic blocks for content flexibility.
Testing with Postman
After creating our pages, we’ll jump into Postman to test our API endpoints. You’ll see how to query pages using slugs, ensuring that your dynamic content is accessible and functioning properly.
Keywords and Takeaways
- Dynamic Content Creation: Allows for the easy addition and management of multiple pages.
- User-Friendly for Editors: Non-technical content editors can build and customize pages without needing developer intervention.
- Enhanced Flexibility: The use of blocks allows for a variety of content types on each page.
- Efficient API Management: Testing with Postman ensures that your API is functioning correctly and efficiently.
- Scalability: As your website grows, adding new pages becomes a straightforward process. Strapi v5 Crash Course 2025 [ Part 10 Building dynamic page with dynamic zones ]](https://i.ytimg.com/vi/o9mGBGnvi8A/mqdefault.jpg)
![Building a Blog Website with TanStack Start and Strapi [ full project code included ]
Building a Blog Website with TanStack Start and Strapi - Landing Page, Blog, pages, auth and paginations.
👉 Project Repo: https://github.com/PaulBratslavsky/strapi-tanstack-start-starter
👉 Strapi Docs: https://strapi.link/444tROv
Hey everyone! In this video, I talk about building my first TanStack Start project, which I can use as a starting template to quickly jump up projects for freelancing.
This project focuses on creating a full dynamic landing page with a blog website perfect for informational websites. Includes:
- landing page
- pagination
- search
- auth
- comments
If you want to freelance learn web dev, are considering freelancing, or learn about headless CMS, this video is for you.
TanStack Start is a great alternative to Next.js and you can deploy it anywhere, not just Vercel. And its seamless integration with tools like Strapi. It makes it easy for users to build dynamic, SEO-friendly websites. Building a Blog Website with TanStack Start and Strapi [ full project code included ]](https://i.ytimg.com/vi/pFZi5xA4_7E/mqdefault.jpg)








![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)