<?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: LkSvn</title>
    <description>The latest articles on DEV Community by LkSvn (@lksvn).</description>
    <link>https://dev.to/lksvn</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F205286%2Fd72b44d2-fe1e-45a9-acef-646a13cf818b.gif</url>
      <title>DEV Community: LkSvn</title>
      <link>https://dev.to/lksvn</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lksvn"/>
    <language>en</language>
    <item>
      <title>Old projects</title>
      <dc:creator>LkSvn</dc:creator>
      <pubDate>Mon, 13 Jul 2026 03:17:25 +0000</pubDate>
      <link>https://dev.to/lksvn/old-projects-kf9</link>
      <guid>https://dev.to/lksvn/old-projects-kf9</guid>
      <description>&lt;p&gt;I recently found an old project I built with a friend around 2017–2018: a perk calculator for the game Firefall.&lt;/p&gt;

&lt;p&gt;The application allowed players to browse perks by category, drag them into a build, track the available perk points and automatically filter incompatible options based on the selected class.&lt;/p&gt;

&lt;p&gt;Looking at the code today, there are many things I would structure differently. The JavaScript could be better organised, responsibilities could be clearer, and the overall architecture would benefit from more modern practices.&lt;/p&gt;

&lt;p&gt;Still, I decided to preserve it as it is.&lt;/p&gt;

&lt;p&gt;Older projects are useful reminders that progress is not only visible in the technologies we use, but also in how we model problems, organise code and make technical decisions.&lt;/p&gt;

&lt;p&gt;It is not a showcase of how I would build the same application today. It is a snapshot of how I approached a real problem at that point in my career.&lt;/p&gt;

&lt;p&gt;Repository: &lt;a href="https://github.com/lksvn/firefall-perk-calculator" rel="noopener noreferrer"&gt;https://github.com/lksvn/firefall-perk-calculator&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>showdev</category>
      <category>learning</category>
    </item>
    <item>
      <title>Learning Typescript</title>
      <dc:creator>LkSvn</dc:creator>
      <pubDate>Mon, 13 Jul 2026 03:07:52 +0000</pubDate>
      <link>https://dev.to/lksvn/learning-typescript-5g26</link>
      <guid>https://dev.to/lksvn/learning-typescript-5g26</guid>
      <description>&lt;p&gt;I've recently started learning TypeScript as part of my journey into the modern React ecosystem.&lt;/p&gt;

&lt;p&gt;One thing that surprised me is how quickly the focus shifts away from syntax and toward modeling the business domain correctly.&lt;/p&gt;

&lt;p&gt;While building a simple Candidate Tracker, I found myself asking questions like:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;When does a freelance opportunity actually become a project?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A client saying "yes" isn't necessarily enough. Maybe it only becomes a project after a signed contract.&lt;/p&gt;

&lt;p&gt;It seems like a small detail, but those decisions directly influence how the application is designed.&lt;/p&gt;

&lt;p&gt;So far, my biggest takeaway is that TypeScript isn't just about adding types to JavaScript—it encourages you to think more carefully about the rules that define your domain.&lt;/p&gt;

&lt;p&gt;Looking forward to continuing this project and sharing more along the way.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>typescript</category>
      <category>beginners</category>
      <category>learning</category>
    </item>
  </channel>
</rss>
