<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Dheyn Michael Orlanda</title>
    <description>The latest articles on Forem by Dheyn Michael Orlanda (@necookie).</description>
    <link>https://forem.com/necookie</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3625914%2F4a36d8c9-98e7-4da7-977d-69b955e952f8.jpeg</url>
      <title>Forem: Dheyn Michael Orlanda</title>
      <link>https://forem.com/necookie</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/necookie"/>
    <language>en</language>
    <item>
      <title>Launching My Portfolio on necookie.dev</title>
      <dc:creator>Dheyn Michael Orlanda</dc:creator>
      <pubDate>Mon, 24 Nov 2025 14:28:15 +0000</pubDate>
      <link>https://forem.com/necookie/launching-my-portfolio-on-necookiedev-1jf6</link>
      <guid>https://forem.com/necookie/launching-my-portfolio-on-necookiedev-1jf6</guid>
      <description>&lt;p&gt;Yo! After a bit of late-night coding, trial-and-error with DNS, and some caffeine-fueled commits, my personal portfolio is finally live: necookie.dev&lt;br&gt;
. Thought I’d share the process for anyone thinking about hosting their own projects.&lt;/p&gt;

&lt;p&gt;Why I Built This&lt;/p&gt;

&lt;p&gt;I wanted a clean, fast place to show my work, side projects, and experiments — basically a space where my code meets a little personality.&lt;/p&gt;

&lt;p&gt;Stack: React + TypeScript&lt;/p&gt;

&lt;p&gt;Hosting: Vercel (automatic builds &amp;amp; deploys straight from GitHub)&lt;/p&gt;

&lt;p&gt;Domain: necookie.dev&lt;/p&gt;

&lt;p&gt;It’s simple: push to main, and Vercel does the rest. SSL? Auto. Preview URL for branches? Auto. Life is good.&lt;/p&gt;

&lt;p&gt;What I Learned&lt;/p&gt;

&lt;p&gt;DNS can be confusing at first — A records, CNAMEs, TTL… a bit of a headache until it clicks.&lt;/p&gt;

&lt;p&gt;Vercel is the plug — super easy for deploying React apps, handles SSL, and global CDN out of the box.&lt;/p&gt;

&lt;p&gt;Keep your repo clean — every commit matters because Vercel builds straight from GitHub.&lt;/p&gt;

&lt;p&gt;Plan for the future — I left room for subdomains like blog.necookie.dev for projects or writing.&lt;/p&gt;

&lt;p&gt;Next Moves&lt;/p&gt;

&lt;p&gt;Add more projects and blog content&lt;/p&gt;

&lt;p&gt;Optimize performance (lazy loading, code splitting)&lt;/p&gt;

&lt;p&gt;Track visitors with some analytics&lt;/p&gt;

&lt;p&gt;💡 TL;DR: necookie.dev is live, React + TS, Vercel-hosted, automatic deploys from GitHub, and ready for my projects &amp;amp; experiments.&lt;/p&gt;

</description>
      <category>portfolio</category>
      <category>typescript</category>
      <category>showdev</category>
      <category>react</category>
    </item>
    <item>
      <title>Chasing CodeChum Nationals 2025: Our Journey to the Group Stage 3 Semifinals</title>
      <dc:creator>Dheyn Michael Orlanda</dc:creator>
      <pubDate>Sun, 23 Nov 2025 17:23:34 +0000</pubDate>
      <link>https://forem.com/necookie/chasing-codechum-nationals-2025-our-journey-to-the-group-stage-3-semifinals-3k5k</link>
      <guid>https://forem.com/necookie/chasing-codechum-nationals-2025-our-journey-to-the-group-stage-3-semifinals-3k5k</guid>
      <description>&lt;p&gt;I joined CodeChum Nationals 2025 mainly to test my skills and sharpen my programming understanding. My goal was to gain firsthand competitive experience, push myself in a real contest environment, and make new connections along the way. Python isn’t new to me—I’m comfortable with methods and functions—but there’s still plenty to learn, and this competition is the perfect pressure cooker for growth.&lt;/p&gt;

&lt;p&gt;We’re a team of 10, and the scoring system sums the top 5 highest individual scores to represent the team. This adds a layer of strategy: everyone’s performance counts, but the best solutions really make the difference.&lt;/p&gt;

&lt;p&gt;For training, I spend 1–2 hours daily, using AI and LeetCode to practice. My strategy is to tackle the easiest problems first, secure points, and then move to the tougher ones. Even so, time pressure is real—one hour goes by faster than you think when coding under the clock.&lt;/p&gt;

&lt;p&gt;Reaching the Semifinals of Group Stage 3 ramps up the stakes, as more universities will be eliminated. I’m excited but also focused on improving: memorizing more Python methods, learning algorithms (my weak point), and staying sharp for the next round.&lt;/p&gt;

&lt;p&gt;Heading into the semifinals, my mindset is simple: have fun, enjoy the ride, and keep leveling up while it lasts. Every round is a learning experience, and our team is ready to give it our best.&lt;/p&gt;

</description>
      <category>programming</category>
      <category>python</category>
      <category>competativeprogramming</category>
      <category>career</category>
    </item>
  </channel>
</rss>
