Uploaded March 2025 | Updated September 2026, 2 weeks ago
Why Next.js Became My Go-To Framework for Web Projects π
π Website: codingafterthirty.com
π New Next.js github.com/PaulBratslavsky/coding-after-thirty-next
π Old Remix github.com/PaulBratslavsky/remix-project-starter
π Backend (Strapi): github.com/PaulBratslavsky/strapi-lms-course-managment
π₯ Why did I switch to Next.js for all my web projects?
In this video, I explain why Next.js has become my go-to framework for building production-ready applications. I'll share:
β The struggles of juggling multiple frameworks π€―
β How sticking to one framework has made me WAY more productive πͺ
β Why I chose Next.js over Remix for long-term maintainability
β The challenges of migrating and why Strapi is still my backend of choice
If you've ever debated which JavaScript framework is right for you, this video will give you some insights to help you decide!
β³ Timestamps:
00:00 - Why I switched to Next.js (and why itβs a game-changer) π₯
01:54 - The power of consistency: No more context switching!
03:57 - Next.js for all production apps: My experience with framework migration
06:23 - Keeping Strapi as my backend while enjoying Next.js perks π€
08:04 - Stability, performance, and the reality of Next.js limitations
11:08 - Picking the right framework: Stability over Hype
13:15 - Back to building my website β got topic ideas? Drop them in the comments! β¬οΈ
14:37 - Using AI to boost productivity and free up time for real learning π€
π‘ Key Takeaways:
π Framework Overload? The danger of using too many frameworks at once.
βοΈ Choosing Wisely: Pick a framework based on productivity, not just trends.
π Consistency is Key: Sticking to one framework = smoother development & maintenance.
π¨ Future Playground: Iβm planning a side project to explore other frameworks without the stress of production!
By the end of this video, you'll have a better framework strategy and understand why maintainability matters in web development. Letβs build smarter! π»
π¬ Whatβs your go-to framework? Let me know in the comments! β¬οΈ
#NextJS #Remix #WebDevelopment #JavaScript #CodingAfter30
Why Next.js Became My Go-To Framework for Web Projects π
π Website: codingafterthirty.com
π New Next.js github.com/PaulBratslavsky/coding-after-thirty-next
π Old Remix github.com/PaulBratslavsky/remix-project-starter
π Backend (Strapi): github.com/PaulBratslavsky/strapi-lms-course-managment
π₯ Why did I switch to Next.js for all my web projects?
In this video, I explain why Next.js has become my go-to framework for building production-ready applications. I'll share:
β The struggles of juggling multiple frameworks π€―
β How sticking to one framework has made me WAY more productive πͺ
β Why I chose Next.js over Remix for long-term maintainability
β The challenges of migrating and why Strapi is still my backend of choice
If you've ever debated which JavaScript framework is right for you, this video will give you some insights to help you decide!
β³ Timestamps:
00:00 - Why I switched to Next.js (and why itβs a game-changer) π₯
01:54 - The power of consistency: No more context switching!
03:57 - Next.js for all production apps: My experience with framework migration
06:23 - Keeping Strapi as my backend while enjoying Next.js perks π€
08:04 - Stability, performance, and the reality of Next.js limitations
11:08 - Picking the right framework: Stability over Hype
13:15 - Back to building my website β got topic ideas? Drop them in the comments! β¬οΈ
14:37 - Using AI to boost productivity and free up time for real learning π€
π‘ Key Takeaways:
π Framework Overload? The danger of using too many frameworks at once.
βοΈ Choosing Wisely: Pick a framework based on productivity, not just trends.
π Consistency is Key: Sticking to one framework = smoother development & maintenance.
π¨ Future Playground: Iβm planning a side project to explore other frameworks without the stress of production!
By the end of this video, you'll have a better framework strategy and understand why maintainability matters in web development. Letβs build smarter! π»
π¬ Whatβs your go-to framework? Let me know in the comments! β¬οΈ
#NextJS #Remix #WebDevelopment #JavaScript #CodingAfter30






![Things Have Changed About Coding Advice: learn to code in 2025 fast? [truth about learning to code]
Happy New Year to you and your families, may 2025 be your best. I revisit 4 year old advice about learning to code fast, does it still apply? The truth about learning to code.
Key takeaways:
My Coding Journey: I began learning to code at 35 and didnβt land my first job until I was 39βits been a challenging yet rewarding path.
The 3-Month Myth: Many people promote the idea of becoming job-ready in just a few months, but I explain why thatβs unrealistic.
The Importance of Commitment: Success in coding requires dedication and timeβlearning the basics is just the beginning.
Market Realities: I discuss how the tech job market has changed and why itβs crucial to stay engaged and keep learning.
Finding Joy in Coding: I emphasize the importance of passion over money and how pursuing what you love can lead to fulfillment.
Introduction
In this video, I take a trip down memory lane to rewatch my older video discussing whether you can learn to code in just three months. Spoiler alert: itβs not as simple as it seems!
My Personal Journey
I started coding at 35, faced countless challenges, and finally got my first job at 39. Ill share insights from my journey and how I feel about the quick-fix mentality that often surrounds learning to code. Things Have Changed About Coding Advice: learn to code in 2025 fast? [truth about learning to code]](https://i.ytimg.com/vi/d_IlAhy5i2E/mqdefault.jpg)



