<?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>Performance on Rafiul Alam</title>
    <link>https://alamrafiul.com/categories/performance/</link>
    <description>Recent content in Performance on Rafiul Alam</description>
    <image>
      <title>Rafiul Alam</title>
      <url>https://alamrafiul.com/papermod-cover.png</url>
      <link>https://alamrafiul.com/papermod-cover.png</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 31 Dec 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://alamrafiul.com/categories/performance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Netflix&#39;s Freedom and Responsibility: No Rules, High Expectations, Brutal Honesty</title>
      <link>https://alamrafiul.com/blogs/netflix-freedom-responsibility/</link>
      <pubDate>Tue, 31 Dec 2024 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/blogs/netflix-freedom-responsibility/</guid>
      <description>&lt;p&gt;No vacation policy.&lt;/p&gt;
&lt;p&gt;No expense policy.&lt;/p&gt;
&lt;p&gt;No approval process.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Just one rule: Act in Netflix&amp;rsquo;s best interest.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;In 2009, Netflix published a culture deck that became legendary. Sheryl Sandberg called it &amp;ldquo;the most important document ever to come out of Silicon Valley.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;It laid out a radical philosophy:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Give people freedom. Expect extraordinary results. Fire quickly if they don&amp;rsquo;t deliver.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s provocative. Some love it. Some hate it. But everyone talks about it.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Data-Oriented Design: Implementing ECS (Entity Component System) with Go Generics</title>
      <link>https://alamrafiul.com/posts/go-ecs-pattern/</link>
      <pubDate>Mon, 08 Jul 2024 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/posts/go-ecs-pattern/</guid>
      <description>&lt;h2 id=&#34;from-object-oriented-to-data-oriented&#34;&gt;From Object-Oriented to Data-Oriented&lt;/h2&gt;
&lt;p&gt;Traditional object-oriented programming (OOP) encourages you to model game entities as objects with inheritance hierarchies. While intuitive, this approach leads to poor cache locality, rigid hierarchies, and performance bottlenecks. Data-oriented design, particularly the Entity Component System (ECS) pattern, flips this on its head.&lt;/p&gt;
&lt;p&gt;With Go 1.18+ generics, we can now build type-safe ECS architectures that deliver both performance and flexibility. Let me show you how.&lt;/p&gt;
&lt;h3 id=&#34;the-oop-problem&#34;&gt;The OOP Problem&lt;/h3&gt;
&lt;p&gt;Here&amp;rsquo;s the typical OOP approach to game entities:&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Flow State: The Science of Peak Performance</title>
      <link>https://alamrafiul.com/blogs/flow-state/</link>
      <pubDate>Mon, 22 Apr 2024 00:00:00 +0000</pubDate>
      
      <guid>https://alamrafiul.com/blogs/flow-state/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s 2 AM. You&amp;rsquo;ve been coding for six hours straight. You haven&amp;rsquo;t eaten. You forgot to check your phone. You have no idea where the time went.&lt;/p&gt;
&lt;p&gt;But you just built the most elegant solution you&amp;rsquo;ve ever created. The code is clean, the logic is tight, and everything just&amp;hellip; works.&lt;/p&gt;
&lt;p&gt;You snap out of it and realize: you were completely immersed. Time disappeared. Effort felt effortless. You were operating at a level you rarely achieve.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
