<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dev on Mmoumni</title><link>https://mmoumni.com/categories/dev/</link><description>Recent content in Dev on Mmoumni</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 31 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://mmoumni.com/categories/dev/index.xml" rel="self" type="application/rss+xml"/><item><title>what I learned from the reimplementation of ping command in C</title><link>https://mmoumni.com/posts/reimplementation-ping-command-in-c/</link><pubDate>Wed, 31 Dec 2025 00:00:00 +0000</pubDate><guid>https://mmoumni.com/posts/reimplementation-ping-command-in-c/</guid><description>&lt;p&gt;I’ve always struggled to fully grasp the networking side of software development — especially when it comes to network programming concepts like sockets, binding, TCP/IP, and protocols.&lt;/p&gt;
&lt;p&gt;So, I decided to take on the challenge and fill in the gaps in my understanding. To do that, I chose to reimplement three well-known networking commands: &lt;code&gt;ping&lt;/code&gt;, &lt;code&gt;traceroute&lt;/code&gt;, and a simplified version of &lt;code&gt;nmap&lt;/code&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;blockquote&gt;
&lt;p&gt;In this series of articles, I’ll explain each command in detail — its use case and how it works under the hood.&lt;/p&gt;</description></item></channel></rss>