<?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>DEV Community: Gee-Wey Yue</title>
    <description>The latest articles on DEV Community by Gee-Wey Yue (@geewey).</description>
    <link>https://dev.to/geewey</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%2F319735%2F563632fd-bb96-455f-8782-5763eafb1a80.jpeg</url>
      <title>DEV Community: Gee-Wey Yue</title>
      <link>https://dev.to/geewey</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/geewey"/>
    <language>en</language>
    <item>
      <title>Learnings from 2026 January 3-9</title>
      <dc:creator>Gee-Wey Yue</dc:creator>
      <pubDate>Fri, 09 Jan 2026 06:45:55 +0000</pubDate>
      <link>https://dev.to/geewey/learnings-from-2026-january-3-9-1be6</link>
      <guid>https://dev.to/geewey/learnings-from-2026-january-3-9-1be6</guid>
      <description>&lt;p&gt;After my previous post from October 2025 about Learning in Public, I achieved a number of milestones that I had not posted. Brief recap to catch up to the present:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;participated in my first hackathon in San Francisco, building an edtech tool for homeless youth in California during &lt;a href="https://www.hackforsocialimpact.com/" rel="noopener noreferrer"&gt;Hack for Social Impact 2025&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;dug into some HTML tidbits I was unfamiliar with, such as &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/fieldset" rel="noopener noreferrer"&gt;fieldset&lt;/a&gt; and &lt;a href="https://developer.mozilla.org/en-US/docs/Glossary/Character_reference" rel="noopener noreferrer"&gt;entities / character references&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;learned about the core logic of LLMs, thanks to renowned AI researcher Andrej Karpathy's free YouTube series called &lt;a href="https://www.youtube.com/playlist?list=PLAqhIrjkxbuWI23v9cThsA9GvCAUhRvKZ" rel="noopener noreferrer"&gt;Neural Networks: Zero to Hero&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;shipped a frontend MVP for a stealth startup in the power tech space, helping them secure their first paying customer&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;This week, I had a few learnings:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Did you know a &lt;code&gt;Promise&lt;/code&gt; is prioritized over &lt;code&gt;setTimeout&lt;/code&gt; in JavaScript? It turns out the JavaScript event loop has two types of queues: macro task queue and micro task queue. Synchronous code executes first, then tasks in the micro task queue, followed at the end by tasks in the macro task queue.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;I heard a software engineer speak about her focus on the "joy of experimentation," which is distinct from the results-driven development of "having to ship." I love the reminder to leave room for joy in spite of requirements and deadlines.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;I started digging into how to better utilize Claude code and will begin implementing ideas from &lt;a href="https://sdeaton.com/blog/claude-code-beyond-prompting/" rel="noopener noreferrer"&gt;Sarah Deaton's post&lt;/a&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;To close out, I realized how I might want to use this space as not only a place to share my learnings but also as a "professional diary" of sorts. I appreciate having this space where clout and engagement are not the priority. The act of me capturing reflections is valuable enough feedback to me. Happy 2025 and onward to a great 2026.&lt;/p&gt;

</description>
      <category>learninpublic</category>
    </item>
    <item>
      <title>Learn in Public (thanks swyx)</title>
      <dc:creator>Gee-Wey Yue</dc:creator>
      <pubDate>Thu, 30 Oct 2025 21:17:09 +0000</pubDate>
      <link>https://dev.to/geewey/learn-in-public-thanks-swyx-51d2</link>
      <guid>https://dev.to/geewey/learn-in-public-thanks-swyx-51d2</guid>
      <description>&lt;p&gt;Lately, I have been dabbling across a number of topics, ping ponging back and forth across tech concepts, specific tools and platforms, and trends.  From past experience, I realize that this approach is ineffective for me.&lt;/p&gt;

&lt;p&gt;According to swyx's &lt;a href="https://www.swyx.io/big-l-notation" rel="noopener noreferrer"&gt;Big L notation&lt;/a&gt; for learning, I am learning at the scale of L(log N) Lossy Learner.&lt;/p&gt;

&lt;p&gt;I want to make better use of the time and energy I apply toward learning, practicing, and doing. I want to shift up the curve. &lt;/p&gt;

&lt;p&gt;So how am I going to approach it? Currently, I am at the &lt;a href="https://www.swyx.io/learning-gears" rel="noopener noreferrer"&gt;Explorer gear&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Each week, I will microblog here about topics and challenges I've encountered.&lt;/p&gt;

&lt;p&gt;If nothing else, this will be a record of my struggles and growth (failure is learning).&lt;/p&gt;




&lt;p&gt;For anyone who is interested in joining, I encourage you to check out swyx's structured thoughts regarding #LearnInPublic: &lt;a href="https://www.swyx.io/learn-in-public" rel="noopener noreferrer"&gt;https://www.swyx.io/learn-in-public&lt;/a&gt;&lt;/p&gt;

</description>
      <category>devjournal</category>
      <category>learning</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
