<?xml version="1.0" encoding="UTF-8"?>
	<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
		<channel>
			<title>Devollox</title>
			<link>https://devollox.com</link>
			<description>Writing on development, design decisions, and building in public.</description>
			<language>en</language>
			<atom:link href="https://devollox.com/rss.xml" rel="self" type="application/rss+xml" />
			
		<item>
			<title>TypeScript: from friend to nightmare in one step</title>
			<link>https://devollox.com/blog/typescript-friend-and-nightmare</link>
			<guid isPermaLink="true">https://devollox.com/blog/typescript-friend-and-nightmare</guid>
			<description>typescript is a friend until it suddenly becomes a nightmare. One step. At first TypeScript feels like pure benefit. You brand variables, describe contracts, and the compiler protects you from stupid mistakes. In a large project with shared types you actually start understanding what is allowed and what is not. This is the real power of the language. Problems begin the moment you try to change something that already exists. Suddenly a small edit produces dozens of red errors. The desire to close the editor and go make tea becomes very strong.</description>
			<pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate>
			<author>Devollox</author>
			
		</item>

		<item>
			<title>Thoughts on Void Presence and why I&apos;m not trying to promote it</title>
			<link>https://devollox.com/blog/thoughts-on-void-presence</link>
			<guid isPermaLink="true">https://devollox.com/blog/thoughts-on-void-presence</guid>
			<description>While developing new updates or void-presence itself, I never really thought about where this could lead me. Starting from version, I didn&apos;t set any plans for this application. The goal was simple: build a nice-looking profile for myself, nothing more. I didn&apos;t think about how it would look in the future. It was rough, but it worked. There were bugs and errors, but nothing critical. Essentially, I was the only one using it. If you observe my development process, you might conclude that I&apos;m doing overhead, or so-called overengineering. I realized this when I started thinking about customizing the builder and bootstrap installer. That&apos;s when I understood: everything I&apos;m building has long outgrown my personal project and become something more.</description>
			<pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate>
			<author>Devollox</author>
			
		</item>

		<item>
			<title>Void Presence: shipping the first real thing</title>
			<link>https://devollox.com/blog/void-presence</link>
			<guid isPermaLink="true">https://devollox.com/blog/void-presence</guid>
			<description>void-presence was the first thing I shipped that real people actually used. Not a hobby project, not a portfolio piece — something people paid attention to, downloaded, reported bugs on. That changes you. A desktop application that controls your Discord Rich Presence with status cycles, custom images, and smart filtering. Built as local-first: no mandatory cloud login, your data stays on your machine. The core is written in Electron and TypeScript, with a Go microservice handling auto-updates and releases. Simple idea. Complicated execution.</description>
			<pubDate>Sat, 01 Aug 2026 00:00:00 +0000</pubDate>
			<author>Devollox</author>
			<enclosure url="https://devollox.com/og/void-presence.webp" type="image/webp" />
		</item>

		<item>
			<title>Three portfolios</title>
			<link>https://devollox.com/blog/three-portfolios</link>
			<guid isPermaLink="true">https://devollox.com/blog/three-portfolios</guid>
			<description>I have rebuilt my personal site three times. Not because any version was broken, but because each one stopped feeling honest. The first version was called modern-portfolio. It was everything a portfolio was supposed to be: OAuth login, a Firebase-powered signature wall where visitors could leave their mark, a cmdk command palette, theme switching, a blog, a detailed uses page. The stack was Next.js, NextAuth, Firebase, SCSS. It looked good. It did a lot. But it felt like a product demo, not a place. Every feature was there to signal capability. The signatures were charming, the command palette was clever — but nothing was quiet. Nothing breathed.</description>
			<pubDate>Sat, 01 Aug 2026 00:00:00 +0000</pubDate>
			<author>Devollox</author>
			<enclosure url="https://devollox.com/og/portfolio-preview.webp" type="image/webp" />
		</item>
		</channel>
	</rss>