<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Danilo Cvijetic</title><link>/posts/</link><description>Recent content in Blog on Danilo Cvijetic</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 29 Mar 2024 00:00:00 +0000</lastBuildDate><atom:link href="/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Load Forge: A Custom DSL for API Load Testing</title><link>/posts/load-forge/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>/posts/load-forge/</guid><description>Hey everyone!
Let&amp;rsquo;s talk about Load Forge, a project I built together with my friends as a university team project to make API load testing a lot more declarative and developer-friendly.
If you&amp;rsquo;ve ever set up load tests, you know that the logic often ends up scattered across multiple scripts, helper functions, and configuration files. This makes tests slower to author, harder to read, and difficult to review. I wanted a way to define load testing scenarios, authentication, and SLO thresholds using a simple, custom Domain-Specific Language (DSL) instead of writing repetitive, boilerplate code.</description></item><item><title>Building Gym Manager: An Offline-First Approach</title><link>/posts/gym-manager/</link><pubDate>Tue, 28 Oct 2025 00:00:00 +0000</pubDate><guid>/posts/gym-manager/</guid><description>Hey everyone! 👋
Recently, I built Gym Manager, a comprehensive fitness center management system. I actually developed this for my friend who just opened a gym, and it was a great chance to have some fun while solving a real-world problem.
If you&amp;rsquo;ve ever worked at or managed a gym, you know the struggles: manual member tracking is slow, physical membership cards get lost (and cost money to print), and lacking good analytics makes it hard to make business decisions.</description></item></channel></rss>