<?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: Emir Baycan</title>
    <description>The latest articles on DEV Community by Emir Baycan (@kalenux).</description>
    <link>https://dev.to/kalenux</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%2F3961037%2Faf5f710c-eecd-4346-a998-df508064a019.png</url>
      <title>DEV Community: Emir Baycan</title>
      <link>https://dev.to/kalenux</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kalenux"/>
    <language>en</language>
    <item>
      <title>Build and operate: why running your own software changes how you engineer it</title>
      <dc:creator>Emir Baycan</dc:creator>
      <pubDate>Sun, 31 May 2026 13:28:33 +0000</pubDate>
      <link>https://dev.to/kalenux/build-and-operate-why-running-your-own-software-changes-how-you-engineer-it-1b5k</link>
      <guid>https://dev.to/kalenux/build-and-operate-why-running-your-own-software-changes-how-you-engineer-it-1b5k</guid>
      <description>&lt;p&gt;A lot of software is built to be handed off. A team ships it, signs off, and moves on. At Kalenux we don't hand off — we build our products, then we run them in production for the long haul. That single choice changes how the whole team engineers.&lt;/p&gt;

&lt;h2&gt;
  
  
  You optimize for the next two years, not the demo
&lt;/h2&gt;

&lt;p&gt;When the finish line is a handoff, you optimize for the moment of delivery: it looks done, it passes review, it ships. When you know your team will still be running this in two years, the incentives invert. You optimize for the day a dependency breaks, the week traffic spikes, the month someone needs to change code written long ago.&lt;/p&gt;

&lt;p&gt;"Done" stops meaning "shipped" and starts meaning "still good a year from now" — across 10+ products and 500,000+ users who notice when something breaks.&lt;/p&gt;

&lt;h2&gt;
  
  
  You feel your own decisions
&lt;/h2&gt;

&lt;p&gt;Operating your own software creates a feedback loop a build-and-handoff shop never gets:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Slow builds?&lt;/strong&gt; The team feels them on every publish — which is exactly why we built our own incremental build system.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Painful localization?&lt;/strong&gt; We run products in 15+ languages, so the tooling has to handle it cleanly, not heroically.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sloppy output?&lt;/strong&gt; It shows up in our own search results and our own support load, so correctness gets built in, not bolted on.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Nobody files a ticket about these. The people who feel the pain are the people who fix the cause.&lt;/p&gt;

&lt;h2&gt;
  
  
  Specialists, not generalists spread thin
&lt;/h2&gt;

&lt;p&gt;Our products lead their categories because they are built by people who understand the domain — engineers, domain researchers, and product specialists, not a generic feature factory. A privacy-first file converter is built by people who care about client-side guarantees; a cognitive assessment is built with input from researchers. Depth is the point.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build and operate is a discipline
&lt;/h2&gt;

&lt;p&gt;It is easy to say you care about quality. Operating your own software forces it: you can't walk away from a shortcut, it waits for you in production. So you stop taking it.&lt;/p&gt;

&lt;p&gt;Software that works. Products that last.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Kalenux is a software powerhouse from Istanbul building web and mobile products at scale, and the open-source Kalenuxer build system. Founded and led by Emir Baycan. &lt;a href="https://kalenux.com.tr" rel="noopener noreferrer"&gt;kalenux.com.tr&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>softwaredevelopment</category>
      <category>architecture</category>
      <category>career</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Why we built our own Node.js website build system</title>
      <dc:creator>Emir Baycan</dc:creator>
      <pubDate>Sun, 31 May 2026 13:21:00 +0000</pubDate>
      <link>https://dev.to/kalenux/why-we-chose-a-rust-template-engine-and-go-apis-390m</link>
      <guid>https://dev.to/kalenux/why-we-chose-a-rust-template-engine-and-go-apis-390m</guid>
      <description>&lt;p&gt;Across our portfolio at Kalenux, most pages are content: articles, guides, localized variants, category pages. They change when we publish, not on every request. So instead of rendering them per-request, we treat building the site as a step that runs when content changes — and we built our own tool to do it.&lt;/p&gt;

&lt;p&gt;That tool is &lt;strong&gt;Kalenuxer&lt;/strong&gt;, our open-source, Node.js-based website build system. Here is why it exists and what it does.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why build our own
&lt;/h2&gt;

&lt;p&gt;We tried existing static-site generators. Each did part of what we needed, none did all of it — fast incremental builds, real multilingual support, and automated deployment, together, across many large sites. So we built one in-house.&lt;/p&gt;

&lt;p&gt;It is written in Node.js because the team lives in JavaScript and TypeScript daily, the ecosystem for parsing, templating, and asset handling is deep, and it keeps the build tooling in the same language as much of our frontend work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Incremental builds
&lt;/h2&gt;

&lt;p&gt;The feature that matters most at scale: Kalenuxer only rebuilds what changed. CSS, JS, and HTML are tracked separately with timestamp-based invalidation. Edit one article and you rebuild one page, not the whole site.&lt;/p&gt;

&lt;p&gt;On a site with thousands of pages, that is the difference between a build measured in minutes and one measured in seconds. When you publish often, that compounds into real time saved every day.&lt;/p&gt;

&lt;h2&gt;
  
  
  Multilingual by default
&lt;/h2&gt;

&lt;p&gt;Our content products run in 15+ languages. Kalenuxer has i18n built in: JSON data files per language, no external translation service or third-party dependency. Adding a language is adding a data file, not re-architecting the site.&lt;/p&gt;

&lt;h2&gt;
  
  
  Template-based, automated deploy
&lt;/h2&gt;

&lt;p&gt;Pages are composed from templates, so structure stays consistent across a product and changes propagate cleanly. Deployment is automated off the build, so shipping content is not a manual ritual.&lt;/p&gt;

&lt;h2&gt;
  
  
  The point
&lt;/h2&gt;

&lt;p&gt;Kalenuxer is not the product — it is the tooling that lets a focused team ship and maintain 10+ live products without the build process becoming the bottleneck. Sometimes the highest-leverage thing you can build is the thing that builds everything else.&lt;/p&gt;

&lt;p&gt;Software that works. Products that last.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Kalenux is a software powerhouse from Istanbul building web and mobile products at scale, and the open-source Kalenuxer build system. Founded and led by Emir Baycan. &lt;a href="https://kalenux.com.tr" rel="noopener noreferrer"&gt;kalenux.com.tr&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>node</category>
      <category>javascript</category>
      <category>webdev</category>
      <category>opensource</category>
    </item>
    <item>
      <title>How a focused team builds and operates 10+ products at scale</title>
      <dc:creator>Emir Baycan</dc:creator>
      <pubDate>Sun, 31 May 2026 13:03:39 +0000</pubDate>
      <link>https://dev.to/kalenux/how-we-build-and-operate-7-products-with-one-in-house-framework-42nd</link>
      <guid>https://dev.to/kalenux/how-we-build-and-operate-7-products-with-one-in-house-framework-42nd</guid>
      <description>&lt;p&gt;Kalenux is a software powerhouse from Istanbul, founded in 2021. We build, ship, and operate production-grade products: 10+ live platforms used by 500,000+ people across 40+ countries, on both web and mobile.&lt;/p&gt;

&lt;p&gt;Here is how a focused team builds and runs a portfolio that most companies would split across several departments.&lt;/p&gt;

&lt;h2&gt;
  
  
  The numbers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;10+ products in production&lt;/strong&gt; — live platforms, not demos&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;500,000+ users&lt;/strong&gt; worldwide&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;40+ countries&lt;/strong&gt; reached&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;5 published Android apps&lt;/strong&gt;, 60,000+ downloads&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;15+ languages&lt;/strong&gt; per content product&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;99.9% uptime&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The portfolio
&lt;/h2&gt;

&lt;p&gt;Every product is a live, production-grade platform built by specialists who understand the domain from the ground up:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;When Notes Fly&lt;/strong&gt; — an editorial publication for in-depth, expert-written reads. Go, Gin, PostgreSQL, Redis, Docker, multilingual.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Whats Your IQ&lt;/strong&gt; — a rigorous, research-backed IQ assessment measuring 10+ cognitive domains, in 15+ languages.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;File Converter Free&lt;/strong&gt; — a privacy-first converter: 30+ formats, 100% client-side, zero uploads. 100,000+ users a month.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Strange Animals, Down Under Cafe, Evolang, Corpy, Pass4Sure&lt;/strong&gt; — content and discovery platforms, each authoritative in its niche.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;QR &amp;amp; Barcode Tool&lt;/strong&gt; — a PWA running in 40+ countries: all major formats, camera scanning, CSV batch mode.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Different domains, different stacks where it matters — mostly Go + PostgreSQL backends, with client-side WebAssembly tools where privacy demands it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The leverage: our own build system
&lt;/h2&gt;

&lt;p&gt;Much of the portfolio ships on &lt;strong&gt;Kalenuxer&lt;/strong&gt;, our open-source, Node.js-based website build system. It is template-based, multilingual, and does incremental builds — only rebuilding the files that changed. On large sites that cuts build time from minutes to seconds. We built it in-house because nothing else did everything we needed.&lt;/p&gt;

&lt;p&gt;That tooling is part of why a focused team can run this many products without drowning in busywork.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build to lead, not to demo
&lt;/h2&gt;

&lt;p&gt;Our products are meant to lead their categories. That means shipping things that are correct, fast, and maintained — and being the team that actually operates them in production, at scale, for the long run.&lt;/p&gt;

&lt;p&gt;Software that works. Products that last.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Kalenux is a software powerhouse from Istanbul building web and mobile products at scale, and the open-source Kalenuxer build system. Founded and led by Emir Baycan. &lt;a href="https://kalenux.com.tr" rel="noopener noreferrer"&gt;kalenux.com.tr&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>softwaredevelopment</category>
      <category>architecture</category>
      <category>webdev</category>
      <category>startup</category>
    </item>
    <item>
      <title>Exploring the Benefits of Batch Converting Image Files</title>
      <dc:creator>Emir Baycan</dc:creator>
      <pubDate>Sun, 31 May 2026 12:01:18 +0000</pubDate>
      <link>https://dev.to/kalenux/exploring-the-benefits-of-batch-converting-image-files-3457</link>
      <guid>https://dev.to/kalenux/exploring-the-benefits-of-batch-converting-image-files-3457</guid>
      <description>&lt;p&gt;How batch image conversion with ImageMagick, libvips, and ffmpeg cuts hours from web, print, and archival pipelines without sacrificing quality.&lt;/p&gt;

&lt;p&gt;Converting one image is trivial. Converting ten thousand, consistently, with the right format, color profile, and compression for each target, is where teams quietly lose hours. Batch conversion is the difference between a manual chore and a pipeline that just runs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why batch, not one-at-a-time
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Consistency.&lt;/strong&gt; Every file goes through the same settings, so output is uniform across a whole library.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Speed.&lt;/strong&gt; Tools like libvips stream large images with a low memory footprint; ffmpeg and ImageMagick parallelize cleanly across cores.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Repeatability.&lt;/strong&gt; A batch job is a script. Run it again next month and get identical results.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is the kind of workflow we build into our own tools at Kalenux, because we operate them ourselves and feel the cost of doing it the slow way.&lt;/p&gt;

&lt;p&gt;Full walkthrough on File Converter Free:&lt;br&gt;
&lt;a href="https://file-converter-free.com/en/articles/batch-conversion/benefits-batch-image-conversion-workflow-efficiency" rel="noopener noreferrer"&gt;https://file-converter-free.com/en/articles/batch-conversion/benefits-batch-image-conversion-workflow-efficiency&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Built and operated by &lt;a href="https://kalenux.com.tr" rel="noopener noreferrer"&gt;Kalenux&lt;/a&gt; — a software studio shipping products at scale. Software that works, products that last.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>imageprocessing</category>
      <category>productivity</category>
      <category>webdev</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
