<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>My Perspective on Kianoosh's Blog</title><link>https://kianoosh.dev/tags/my-perspective/</link><description>Recent content in My Perspective on Kianoosh's Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 13 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kianoosh.dev/tags/my-perspective/index.xml" rel="self" type="application/rss+xml"/><item><title>TypeScript: The Illusion of Structure</title><link>https://kianoosh.dev/posts/2026-02-13-typescript-the-illusion-of-structure/</link><pubDate>Fri, 13 Feb 2026 00:00:00 +0000</pubDate><guid>https://kianoosh.dev/posts/2026-02-13-typescript-the-illusion-of-structure/</guid><description>&lt;p>It’s been around seven years since I started coding with JavaScript, and for the last two years I’ve been working almost exclusively with TypeScript for backend development. Sometimes relationships just don’t work out — and I’m starting to feel that JavaScript and TypeScript are simply not a good fit for backend systems when projects become serious and complex 🔒&lt;/p>
&lt;p>As soon as you try to do anything non-trivial with your ORM, things start getting messy — and it doesn’t really matter whether you’re using TypeORM or Prisma. The moment you need “ORM magic” like sharing transactions across repositories, handling nested soft deletes, or coordinating complex lifecycle behavior, you find yourself fighting the abstractions rather than benefiting from them.&lt;/p></description></item><item><title>Discipline Under Pressure: Shipping Without Messing Up</title><link>https://kianoosh.dev/posts/2025-08-20-discipline-under-pressure-shipping-without-messing-up/</link><pubDate>Wed, 20 Aug 2025 00:00:00 +0000</pubDate><guid>https://kianoosh.dev/posts/2025-08-20-discipline-under-pressure-shipping-without-messing-up/</guid><description>&lt;p>&lt;img src="https://kianoosh.dev/images/squid-game-umbrella-cookie-1536x913.jpg" alt="squid game umbrella cookie">&lt;/p>
&lt;h2 id="the-reality-of-urgency-in-startups">The Reality of Urgency in Startups&lt;/h2>
&lt;p>It’s crucial for every senior software engineer, technical leader, or anyone accountable for delivering technical solutions to know how to handle urgent tasks wisely. Let’s call this person a &lt;em>leader&lt;/em> — and today, that’s you.&lt;/p>
&lt;p>In some industries, or at certain stages of a company’s lifecycle, urgent requirements hit technical teams constantly. I currently work as a technical lead at a startup (&lt;a href="https://www.linkedin.com/company/donetech/">Done&lt;/a>), where the rules of the game seem to change every other week.&lt;/p></description></item></channel></rss>