<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Idlc on Mikolaj Karebski - Engineering Notes</title><link>https://blog.karebski.dev/tags/idlc/</link><description>Recent content in Idlc on Mikolaj Karebski - Engineering Notes</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 27 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.karebski.dev/tags/idlc/index.xml" rel="self" type="application/rss+xml"/><item><title>Why we need IDLC</title><link>https://blog.karebski.dev/posts/why-we-need-idlc/</link><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.karebski.dev/posts/why-we-need-idlc/</guid><description>One of the first important concepts many software engineers learn is the Software Development Life Cycle (SDLC).
SDLC breaks down the process of building software through planning, design, implementation, testing, deployment, and maintenance. The exact stages may differ depending on the definition, but the core idea is always similar.
Why does SDLC matter? Because it gives teams a shared way to think about how software moves from an idea to production and later maintenance.</description></item></channel></rss>