Uploaded October 2026 | Updated November 2026, 3 hours ago
Is software engineering dead? I don't think so. We were never paid to write code. We were paid to solve problems for businesses, and that part isn't going anywhere.
In this walk-and-talk, I share what I'm actually seeing in tech: AI isn't replacing developers; it's letting fewer developers get more done.
What I talk about:
→ Why friends who got laid off "because of AI" are all working again
→ Why the bar for junior developers is higher, and why breaking in was always hard
→ Weekend projects vs. real systems: who owns it when something breaks?
→ Why tokens and infrastructure costs can sink a vibe-coded SaaS
→ What a talk I gave in Japan taught me about what clients actually want
→ How domain knowledge turns code into value
→ My move from React front-end work to AI engineering
⏱️ Chapters
0:00 Is software engineering dead?
0:29 AI lets fewer developers do more
1:09 Friends who got laid off "because of AI"
1:28 The bar for junior developers is higher
1:52 Why you'll still need humans
2:10 Weekend projects vs. real systems
3:23 What you get from a supported open-source product
4:35 A human has to own the responsibility
5:15 Coding was never about buttons and widgets
6:02 Think in systems: architecture, DSA, infrastructure
6:40 The hidden cost of AI apps at scale
7:43 My talk in Japan: put the human first
9:17 Development is about solving business problems
9:57 Domain knowledge: the jiu-jitsu school example
10:52 The math genius who happened to use Python
11:28 Find your niche
12:46 From React to AI engineering
💬 Where do you see the shift happening? Tell me what you've struggled with in the comments. I want to keep this conversation realistic.
#AI #SoftwareEngineering #WebDevelopment #LearnToCode #AIEngineering #CareerAdvice
Is software engineering dead? I don't think so. We were never paid to write code. We were paid to solve problems for businesses, and that part isn't going anywhere.
In this walk-and-talk, I share what I'm actually seeing in tech: AI isn't replacing developers; it's letting fewer developers get more done.
What I talk about:
→ Why friends who got laid off "because of AI" are all working again
→ Why the bar for junior developers is higher, and why breaking in was always hard
→ Weekend projects vs. real systems: who owns it when something breaks?
→ Why tokens and infrastructure costs can sink a vibe-coded SaaS
→ What a talk I gave in Japan taught me about what clients actually want
→ How domain knowledge turns code into value
→ My move from React front-end work to AI engineering
⏱️ Chapters
0:00 Is software engineering dead?
0:29 AI lets fewer developers do more
1:09 Friends who got laid off "because of AI"
1:28 The bar for junior developers is higher
1:52 Why you'll still need humans
2:10 Weekend projects vs. real systems
3:23 What you get from a supported open-source product
4:35 A human has to own the responsibility
5:15 Coding was never about buttons and widgets
6:02 Think in systems: architecture, DSA, infrastructure
6:40 The hidden cost of AI apps at scale
7:43 My talk in Japan: put the human first
9:17 Development is about solving business problems
9:57 Domain knowledge: the jiu-jitsu school example
10:52 The math genius who happened to use Python
11:28 Find your niche
12:46 From React to AI engineering
💬 Where do you see the shift happening? Tell me what you've struggled with in the comments. I want to keep this conversation realistic.
#AI #SoftwareEngineering #WebDevelopment #LearnToCode #AIEngineering #CareerAdvice
![Building a Dynamic Website Landing Page With Next.js 15 and Strapi 5 Headless CMS [ Code Included ]
How to structure and manage your dynamic content in Next.js with Strapi.
👉🏻 Code on GitHub: https://github.com/PaulBratslavsky/strapi-blocks-demo-next-js
✨ Next.js 15 and Strapi Demo: https://strapi.link/strapi-and-nextjs
😅 My website: https://www.codingafterthirty.com
Chapters
00:00 Create a dynamic landing page using Next.js and Strapi.
03:11 Rendering Dynamic content in Next.js with block renderer component.
04:29 Focus on building and not on content management.
05:56 Build a dynamic website with Next.js and Strapi for easy content management.
06:48 Set up a Next.js and Strapi project.
Learn how to use Strapi 5s Dynamic Zones with Next.js 15 to build and render dynamic pages effortlessly. Strapi’s headless CMS makes content management easy for non-technical users, while Next.js dynamically renders components based on Strapi’s structured API data.
Strapi’s Collection Types organize content into reusable sections like Hero banners, headings, and carousels, which map directly to components in Next.js. Content updates in Strapi are instantly reflected in your application, streamlining collaboration between content creators and developers.
Key Highlights:
Manage dynamic content with Strapi’s Dynamic Zones and API integration.
Map Strapi blocks directly to Next.js components for efficient page building.
Easily update content in Strapi and see changes live in Next.js after publishing. Building a Dynamic Website Landing Page With Next.js 15 and Strapi 5 Headless CMS [ Code Included ]](https://i.ytimg.com/vi/YhEVIGzJD1Y/mqdefault.jpg)
![Freelancing vs Employment: Which Path Will Boost Your Career? [ For Self Taught Developers ]
Lets talk about freelancing vs employment and which is the right path and challenges with each.
Full episode 👉🏻https://www.youtube.com/watch?v=PPZxLGdunF0 with @coffeecodeandchat and @kizo-niklas
In today’s job market, the differences between freelancing and traditional employment can significantly influence your career trajectory. Join Paul and Nik as they delve into the mindset of freelancers, the importance of continuous learning, and how to embrace rapid iteration for personal growth.
Chapters
00:00 Freelancers need to constantly upskill due to instability, while employees enjoy security but may lack motivation to grow, making entrepreneurial skills valuable for all. Expand
01:42 Freelancers must constantly adapt their skills to market demands, while employees enjoy job security but may become complacent in their professional development.
02:27 Freelancing offers flexibility and independence but comes with increased stress and financial uncertainty compared to traditional employment.
02:59 Freelancing can be stressful and isnt for everyone, but it encourages creative thinking and problem-solving.
03:18 Freelancing offers flexibility and opportunities for side projects, but may lack job security, making it essential to consider personal circumstances before choosing this path.
04:09 Finding a career path that aligns with your mindset and passions is crucial for motivation and skill development.
04:49 Embracing rapid iteration and learning from failures enhances development skills and leads to better product outcomes.
05:48 Embracing a systematic approach in freelancing can enhance efficiency, but incorporating unique elements in each project fosters growth and learning.
5 Key Topics:
- The Freelance Mindset: Understanding the differences in job security and skill development between employees and freelancers.
- Continuous Learning: The necessity of investing time in skill enhancement as a freelancer.
- Rapid Iteration: Learning from failures and the value of building quickly to improve skills.
- Comfort Zone Expansion: The importance of stepping outside your comfort zone with each new project.
- Freelancing as a Safety Net: How freelancing can provide additional security in an unpredictable job market. Freelancing vs Employment: Which Path Will Boost Your Career? [ For Self Taught Developers ]](https://i.ytimg.com/vi/YsgXebtipSU/mqdefault.jpg)






![Strapi v5 Crash Course 2025 [ Part 12 Refactoring our Strapi middleware ]
In this Strapi tutorial part 12, we will refactor our middleware code.
In this final part, we will create a Featured Articles Component in Strapi and finalize our project.
👉 Lesson Notes: https://www.codingafterthirty.com/courses/strapi-5-crash-course-2025/middleware-refactor-in-strapi
👉 Learn more about Strapi: https://strapi.link/learn-more
In this video, we will examine how to improve our code by refactoring. If you ever find yourself repeating yourself, this is a good sign that we can improve or refactor our code. Strapi v5 Crash Course 2025 [ Part 12 Refactoring our Strapi middleware ]](https://i.ytimg.com/vi/bR16liDXyC8/mqdefault.jpg)

