<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software on Mohseen</title><link>https://www.mohseen.dev/tags/software/</link><description>Recent content in Software on Mohseen</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 02 Oct 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://www.mohseen.dev/tags/software/index.xml" rel="self" type="application/rss+xml"/><item><title>Taming the Beast: Unravelling Anti-Patterns in TypeScript</title><link>https://www.mohseen.dev/post/2023-10-02-taming-the-beast-unravelling-anti-patterns-in-typescript/</link><pubDate>Mon, 02 Oct 2023 00:00:00 +0000</pubDate><guid>https://www.mohseen.dev/post/2023-10-02-taming-the-beast-unravelling-anti-patterns-in-typescript/</guid><description>&lt;p&gt;When it comes to software development, TypeScript has gained a unique foothold in new and evolving tech stacks by offering added security layers in JavaScript development—including richer type checks, optional strict compiling, and enhanced code navigation. In other words, TypeScript is simply JavaScript that knows what types of data it&amp;rsquo;s processing.&lt;/p&gt;
&lt;p&gt;Yet, despite its features and benefits, certain TypeScript practices can inculcate problematic patterns, commonly known as anti-patterns—essentially practices that seem helpful initially but prove unproductive or counterproductive in the long run.&lt;/p&gt;</description></item></channel></rss>