My tech stack for 2025

Summary

In this insightful video, the speaker discusses their evolving approach to web development for 2025, advocating for the use of various technologies based on project needs. They favor Next.js for frontend-heavy applications, while recommending Elixir with Phoenix for backend-heavy projects. The speaker emphasizes the importance of cost-effective deployment strategies, highlighting alternatives like Fly.io over Vercel for resource-intensive applications. They also explore hybrid solutions, suggesting the use of REST APIs with modern frontend frameworks. Open to future learning, they reflect on their current tech stack and potential expansions, encouraging a versatile, context-driven development mindset.

Takeaways

• 😀 Embrace versatility: It's beneficial to know and use multiple technologies instead of focusing on just one.
• 🛠️ Explore various frameworks: Familiarity with frameworks like Next.js, Remix, and React Router enhances a developer's toolkit.
• 🌐 Different applications require different tools: Use specific technologies based on whether your application is frontend-heavy or backend-heavy.
• 💸 Be cautious with hosting costs: Platforms like Vercel are convenient but can become expensive, especially for resource-intensive applications.
• 📊 For frontend-heavy apps, Next.js is a solid choice, particularly if resource usage is low.
• 🔧 Elixir and Phoenix excel in backend-heavy applications, particularly for complex features like authentication and database management.
• 🚀 Consider using Fly.io for deploying Elixir applications to better manage costs and resources.
• 📅 Implementing incremental static regeneration can help keep static sites fresh without excessive resource use.
• 📡 Combining a Phoenix REST API with a Next.js frontend allows for flexibility and efficiency in handling complex projects.
• 🌱 Continuous learning is key: The speaker expresses interest in exploring new technologies, reflecting the ever-evolving nature of web development.

Q & A

What key realization did the speaker have about using multiple technologies?

The speaker learned that it's beneficial to be familiar with multiple technologies and to use them in different contexts, rather than being limited to just one.

What technologies does the speaker feel comfortable using?

The speaker is comfortable using various technologies including Next.js, Remix, React Router for front-end development, and Elixir with Phoenix for back-end applications.

What is the speaker's preferred hosting platform for front-end heavy applications?

The speaker prefers using Vercel for hosting front-end heavy applications but advises caution due to its potentially high costs.

What alternative does the speaker suggest for hosting when dealing with resource-intensive tasks?

The speaker suggests using Fly.io as an alternative hosting solution when resource-intensive tasks may lead to high costs on Vercel.

What type of application does the speaker use as an example of a good use case for Vercel?

The speaker mentions their personal website, which is mostly static and relies on APIs for dynamic content, as a good use case for Vercel.

What features does Phoenix offer that benefit back-end development?

Phoenix offers built-in features such as authentication generation and an integrated ORM, which simplify back-end development.

How does the speaker approach the combination of front-end and back-end technologies?

The speaker often combines a Phoenix REST API for the back-end with Next.js for the front-end, leveraging the strengths of both technologies.

What is the speaker's stance on learning new JavaScript frameworks?

The speaker expresses reluctance to learn new JavaScript frameworks due to their current focus on mastering Next.js, although they acknowledge the appeal of other frameworks like Inertia.js.

What deployment strategy does the speaker consider for single-page applications?

The speaker considers deploying a single-page application using React Router directly within a Phoenix application to simplify deployment and reduce costs.

What is the speaker's future outlook regarding new technologies?

The speaker is open to learning new frameworks and languages in the future, potentially adding Go to their tech stack for 2026.