<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Posts on Saheb&#39;s AI Journey</title>
		<link>https://saheb.github.io/blog/posts/</link>
		<description>Recent content in Posts on Saheb&#39;s AI Journey</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 27 Jun 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://saheb.github.io/blog/posts/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>On failing at my first Kaggle competition (3/n)</title>
				<link>https://saheb.github.io/blog/posts/failing-at-my-first-kaggle-competition-3/</link>
				<pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://saheb.github.io/blog/posts/failing-at-my-first-kaggle-competition-3/</guid>
				<description>&lt;p&gt;In the second part we talked about transformer heads and features.&lt;/p&gt;&#xA;&lt;p&gt;In this part, we will dive into credit assignment and reward hacking problems that I faced.&lt;/p&gt;&#xA;&lt;p&gt;Giving +1 reward when you win a game and -1 when you lose is clean and eventually you want to reach that state where it suffices but before you get there, you need more signals, i.e. dense rewards to teach the agent the behavior you want.&lt;/p&gt;</description>
			</item>
			<item>
				<title>On failing at my first Kaggle competition (2/n)</title>
				<link>https://saheb.github.io/blog/posts/failing-at-my-first-kaggle-competition-2/</link>
				<pubDate>Fri, 26 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://saheb.github.io/blog/posts/failing-at-my-first-kaggle-competition-2/</guid>
				<description>&lt;p&gt;In the first part, we discussed self play and the equilibrium our agent gets stuck in.&lt;/p&gt;&#xA;&lt;p&gt;In this part, we will talk about features that model takes as input, and how model uses them to learn strategies.&lt;/p&gt;&#xA;&lt;p&gt;Theme and tone will be the same, more on what not to do.&lt;/p&gt;&#xA;&lt;p&gt;In Orbit Wars, features fell into 4 categories, planets, fleets, global, and pairwise features.&lt;/p&gt;&#xA;&lt;p&gt;Planet features will tell the model everything about the planet, its position, owner, radius, production, orbit info, capture cost, distance to nearest owned planet, etc.&lt;/p&gt;</description>
			</item>
			<item>
				<title>On failing at my first Kaggle competition (1/n)</title>
				<link>https://saheb.github.io/blog/posts/failing-at-my-first-kaggle-competition/</link>
				<pubDate>Thu, 25 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://saheb.github.io/blog/posts/failing-at-my-first-kaggle-competition/</guid>
				<description>&lt;p&gt;I had a lot of fun building an AI agent for Orbit Wars.&lt;/p&gt;&#xA;&lt;p&gt;But I failed, according to my own standards, and naive high expectations.&lt;/p&gt;&#xA;&lt;p&gt;I wanted to be in top 10. I didn’t even end up in top 1000.&lt;/p&gt;&#xA;&lt;p&gt;The final scoreboard: a rating of 995, ranked 1060 out of 4729. Top 25%, but nowhere near the top 10.&lt;/p&gt;&#xA;&lt;p&gt;Getting there took over 90 training runs across a month, and about $700 worth of GPU compute across GCP, AWS, and Jarvis Labs.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The Day My AI Editor Went Silent: Debugging Git Worktrees, Phantom Configs, and Lost Weights</title>
				<link>https://saheb.github.io/blog/posts/git-worktree-unset/</link>
				<pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate>
				<guid>https://saheb.github.io/blog/posts/git-worktree-unset/</guid>
				<description>&lt;p&gt;Building reinforcement learning environments is already a complex exercise in managing state, rewards, and training loops. You expect the agent you are training to act unpredictably. You don&amp;rsquo;t expect the AI agent writing your code to completely flatline.&lt;/p&gt;&#xA;&lt;p&gt;While working on some recent RL projects, my AI code editor—Google Antigravity—just gave up. Every time I hit send, it would emit a single beep. No error message. No spinning loader. Just a beep and a dead UI.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Reinforcement Learning with Snake (1)</title>
				<link>https://saheb.github.io/blog/posts/reinforcement-learning-snake-1/</link>
				<pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate>
				<guid>https://saheb.github.io/blog/posts/reinforcement-learning-snake-1/</guid>
				<description>&lt;p&gt;Reinforcement learning is interesting because it is intuitive and it aligns with how we learn naturally. You touch hot water, you feel the burn, you don&amp;rsquo;t touch it again. You learn by trial and error; you learn from experience. By interacting with the world, you get feedback in the form of reward or punishment, and that defines your behaviour.&lt;/p&gt;&#xA;&lt;p&gt;You notice there is a knob next to the water tap. It has a red arrow and a blue arrow on it. You press it — nothing happens. You pull it — nothing happens. You turn it and voila, the water starts again. You dare to touch it again, and this time it&amp;rsquo;s slightly less hot … and that&amp;rsquo;s how you learn by exploring. Either you can do this yourself, or someone teaches you and robs you of the opportunity of figuring it out on your own.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
