<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Frameworks on Omid Farhang</title><link>https://omid.dev/tags/frameworks/</link><description>Recent content in Frameworks on Omid Farhang</description><generator>Hugo -- 0.152.2</generator><language>en-US</language><copyright>2025 Omid Farhang | All rights reserved.</copyright><lastBuildDate>Thu, 04 Jul 2024 01:50:50 +0330</lastBuildDate><atom:link href="https://omid.dev/tags/frameworks/index.xml" rel="self" type="application/rss+xml"/><item><title>Avoiding Framework Lock-in: A Frontend Team Leader's Guide</title><link>https://omid.dev/2024/07/04/breaking-free-from-framework-constraints/</link><pubDate>Thu, 04 Jul 2024 01:50:50 +0330</pubDate><guid>https://omid.dev/2024/07/04/breaking-free-from-framework-constraints/</guid><description>&lt;p&gt;As a frontend team leader, one of your most crucial responsibilities is ensuring your team remains adaptable and forward-thinking in an ever-evolving technological landscape. While standardizing on a single framework can provide short-term efficiency, it risks limiting your team&amp;rsquo;s growth and flexibility in the long run. Let&amp;rsquo;s explore strategies to avoid this pitfall, complete with real-world examples.&lt;/p&gt;
&lt;h2 id="focus-on-core-principles"&gt;Focus on Core Principles&lt;/h2&gt;
&lt;p&gt;At the heart of frontend development lie the fundamental web technologies: HTML, CSS, and JavaScript. These form the bedrock upon which all frameworks are built. By emphasizing mastery of these core technologies, you equip your team with transferable skills that transcend any single framework.&lt;/p&gt;</description></item></channel></rss>