<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Muktar SayedSaleh | مختار سيد صالح on Medium]]></title>
        <description><![CDATA[Stories by Muktar SayedSaleh | مختار سيد صالح on Medium]]></description>
        <link>https://medium.com/@muktar-sayedsaleh?source=rss-e449325e2d64------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Gnp0k1ixfGPPpRN2TQlcbQ.jpeg</url>
            <title>Stories by Muktar SayedSaleh | مختار سيد صالح on Medium</title>
            <link>https://medium.com/@muktar-sayedsaleh?source=rss-e449325e2d64------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:24:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@muktar-sayedsaleh/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[AWS just notified me that I owe $8,695,161.75.]]></title>
            <link>https://muktar-sayedsaleh.medium.com/aws-just-notified-me-that-i-owe-8-695-161-75-c2b3f2ee0e5b?source=rss-e449325e2d64------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2b3f2ee0e5b</guid>
            <category><![CDATA[ai-assisted-coding]]></category>
            <category><![CDATA[billing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[incident-response]]></category>
            <dc:creator><![CDATA[Muktar SayedSaleh | مختار سيد صالح]]></dc:creator>
            <pubDate>Fri, 17 Jul 2026 11:37:10 GMT</pubDate>
            <atom:updated>2026-07-17T11:37:10.369Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E3dfcml1XBTh0csshvsY9A.png" /></figure><p>The account in question is a personal one I created 11 years ago. It’s been dormant for seven of them, with a monthly invoice of $0.00. The only reason it’s still alive is that it holds twenty image files from two old side projects I forgot to kill. Total size: under one megabyte.</p><p>Here’s how my Friday went, and what it reminded me about incident response.</p><p>1:24 PM Dubai time. A budget alert lands: “actual cost $8,695,161.75” against the $30 monthly budget alarm I’d set. First reaction: the usual phishing. But the sender checked out as genuinely AWS, and my mind jumped to worse scenarios. Someone mining Bitcoin on my account?!</p><p>Not the proudest moment for an AWS-certified Solutions Architect, Developer, and DevOps Engineer. But very human. We all forget a dormant account, an old access key that might have leaked somewhere along the way. So the immediate next step: hunt for anything suspicious in the account.<br>There was nothing. At all. Still, I rotated the root credentials, enabled MFA, and audited IAM. Clean: no foreign keys, no unknown users, no attacker buckets.</p><p>Cost Explorer told the real story. The entire charge was S3: sixteen identical daily line items of $543,445.33 each. Not a cent of variation. No request charges. Real workloads don’t produce flat lines; broken pricing computations do. The math implied roughly 700 petabytes of storage I don’t have.<br>So I filed a billing case with the CSV evidence attached.</p><p>Then came the reveal. AWS’s Health Dashboard posted a global incident: “Inaccurate Estimated Billing Data,” a unit-pricing bug in the estimated billing subsystem, running since July 16. Their words: the displayed estimates don’t reflect actual charges, and no customer action is required. Hacker News already has someone staring at a $1.7 BILLION estimate on an account that normally spends less than a dollar a month.</p><p>What I’m taking away: AI and vibe coding are real. Nobody’s questioning that anymore. But this week proved that even one of the biggest companies in the world can still ship the kind of bug we’d catch in a junior developer’s first pull request. Hallucination, it turns out, isn’t exclusive to AI.</p><p>If a heart-stopping AWS number landed in your inbox this week: breathe, and check the Health Dashboard before you do anything else.</p><p><a href="https://www.linkedin.com/search/results/all/?keywords=%23aws&amp;origin=HASH_TAG_FROM_FEED">#AWS</a> <a href="https://www.linkedin.com/search/results/all/?keywords=%23finops&amp;origin=HASH_TAG_FROM_FEED">#FinOps</a> <a href="https://www.linkedin.com/search/results/all/?keywords=%23incidentresponse&amp;origin=HASH_TAG_FROM_FEED">#IncidentResponse</a> <a href="https://www.linkedin.com/search/results/all/?keywords=%23cloudcomputing&amp;origin=HASH_TAG_FROM_FEED">#CloudComputing</a> <a href="https://www.linkedin.com/search/results/all/?keywords=%23ruinedfridays&amp;origin=HASH_TAG_FROM_FEED">#RuinedFridays</a></p><p><strong>Muktar SayedSaleh @ 2026</strong><br><a href="https://github.com/muktarsayedsaleh">GitHub</a><br><a href="https://www.linkedin.com/in/muktarsayedsaleh/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2b3f2ee0e5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What We Delegate to AI Agents, and What We Never Will]]></title>
            <link>https://muktar-sayedsaleh.medium.com/what-we-delegate-to-ai-agents-and-what-we-never-will-d9980c67b09c?source=rss-e449325e2d64------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9980c67b09c</guid>
            <category><![CDATA[cto]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[claude-code]]></category>
            <category><![CDATA[vp-of-engineering]]></category>
            <dc:creator><![CDATA[Muktar SayedSaleh | مختار سيد صالح]]></dc:creator>
            <pubDate>Thu, 09 Jul 2026 17:52:36 GMT</pubDate>
            <atom:updated>2026-07-09T17:52:36.649Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UeST3FzK-_LU1Rrt" /></figure><p>I’ve been using AI coding agents every day for months now. First on my own, then across an engineering team I lead. In that time I’ve read a lot of writing on the subject, and almost all of it falls into one of two buckets. Vendors telling me my engineers are 10x now. Skeptics telling me it’s all garbage.</p><p>Neither matches what I’ve actually seen, so I wrote down what did.</p><h3>Start with accountability, not tooling</h3><p>When I introduce agents to a team, the first conversation is not about models or prompts. It’s a single expectation that everything else depends on:</p><p><strong>No matter who, or what, writes the code, you are still its accountable owner.</strong></p><p>You may not be typing it anymore. Fine. You are still the one who signs it off. If you can’t explain a line you’re about to ship, don’t merge it. Review the agent’s output with the same suspicion you’d apply to a pull request from a new hire. Your name on the PR means you vouch for it, and that didn’t change when the typing got automated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/260/0*a7Pyg1u-iVcurYHb.gif" /></figure><p>I keep repeating this because every failure I’ve seen with agentic coding, on my team and elsewhere, traces back to the same moment: someone approved a diff they hadn’t really read.</p><h3>We keep the agent out of git</h3><p>This is where I disagree with most of what gets published on the topic.</p><p>On my teams, the agent never touches version control. It doesn’t commit. It doesn’t push. It doesn’t open pull requests, and it certainly never merges one, even when the tooling makes that possible. The most I allow is read access, so it can look at a diff or check status.</p><p>A human stages. A human commits. A human opens the PR and a human merges it.</p><p>The reasoning is simple. The commit is the moment where responsibility becomes permanent. Before the commit, everything is a suggestion. After it, it’s part of the company’s history, and writing that history should stay in human hands. The industry is currently sprinting in the opposite direction, toward agents that ship their own PRs end to end. I expect a lot of teams will relearn this lesson the expensive way.</p><h3>Are we actually faster?</h3><p>Yes. Also no. The question is badly posed, because the variance between tasks is so large that any average is meaningless. The same tool that feels like a 100x multiplier on Monday feels like a 0.5x tax on Tuesday.</p><p>Where it genuinely flies: repetition. You build one endpoint by hand, validate it properly, then tell the agent to produce the same thing for five other entities. Near perfect output, and cheap to review because you already trust the pattern. Same story for mechanical cleanups, where you fix one instance yourself and let the agent apply the fix everywhere. Tests are another big one. Extending a suite, or turning a bug report and a log file into a regression test, works remarkably well. And onboarding into an unfamiliar codebase has been transformed for us. What used to be days of reading is now a conversation. Trace this feature for me. Draw me a diagram of this module. Where would I change X?</p><p>All of these share one property: the task is well defined, with obvious inputs and outputs.</p><p>Now the other column of the ledger. Hand the agent a vague problem, the kind where a human engineer would clarify requirements as they go, and it will not clarify anything. It fills every gap with something plausible, and you pay for all of it during review. Big restructures are worse. The agent patches and piles on top of what exists. It will not rework the shape of a system unless you push it there explicitly, and pushing it there is where things get risky.</p><p>After enough daily use, I’ve come to believe the models follow two unwritten rules: do the minimum needed to complete the task, and avoid touching code you don’t have to. From the model’s perspective that’s rational. It maximizes the chance the task “succeeds.” From the codebase’s perspective, it’s how architectural rot accumulates while everyone’s dashboards say productivity is up.</p><p>The discipline that follows from all this is to stay atomic. One function. One bug. One endpoint. Verify, commit, build on it. The bigger and vaguer the request, the more confident and wrong the output. Ask for a whole system and you get something impressive looking that nobody can review. Ask for one small step and you get something correct.</p><h3>Cognitive debt</h3><p>Here’s the cost I didn’t see coming, and the one I now spend the most time managing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-A2LbK-iRKfIaY0k" /></figure><p>We can produce code faster than our brains can absorb it. The bottleneck of this job used to be writing. It isn’t anymore. The bottleneck is reading and understanding, and when the volume of output exceeds what a person can actually digest, they don’t slow down. They skim. They approve things they never internalized.</p><p>I’ve started calling this cognitive debt, and it compounds the way technical debt does. Every diff you didn’t truly read is a problem deferred to your future self: a bug you’ll investigate with no context, a module that nobody on the team understands anymore, a rewrite that’s already inevitable but not yet visible. Push a team on AI throughput without managing this and you end up with two problems at once. A codebase no one comprehends, and engineers who are exhausted from living in permanent skim mode.</p><p>So the rule I give my team is unpopular but honest: you can only go as fast as you can follow. If reading properly caps your velocity below whatever number the vendor benchmarks promise, then that number was fiction.</p><p>There’s a related effect worth naming. Agents make it very cheap to start things. One more idea, one more branch, a quick experiment on the side. I catch myself juggling more parallel threads than I ever did before, and losing track of them more often. My mitigations are embarrassingly old fashioned. Good commit messages. Written notes. A deliberate work rhythm. None of it is new advice, but the tool will not impose any discipline on you, so you have to bring your own.</p><h3>The gains live in your setup, not in the tool</h3><p>If you asked me to predict whether a given team will benefit from agentic coding, I wouldn’t ask which model they use. I’d ask about their test suite.</p><p>Agents perform dramatically better inside a codebase with sound architecture, documentation that lives next to the code, real CI, strong typing, and tests you can trust. Each of those does double duty. It narrows the space of plausible mistakes the agent can make, and it catches the mistakes that get through before a human has to.</p><p>Run the same tools on a messy system, no tests, weak types, architecture that exists only in one senior engineer’s head, and the agent amplifies the mess. Confidently, and at scale.</p><p>This is the part that most AI adoption conversations skip, probably because it’s the least exciting part. The productivity was never in the tool. It’s in the engineering foundation around the tool. Teams that invested in fundamentals over the years are now collecting compound interest. Teams that didn’t are discovering that AI is a mirror.</p><h3>Ergonomics for the mind</h3><p>One last thing that has been on my mind lately.</p><p>We bought standing desks to protect our backs. We bought split keyboards to avoid RSI. Nobody considers physical ergonomics a soft topic anymore.</p><p>Heavy daily AI use has cognitive effects that I think deserve the same seriousness. Sustained focus gets harder. Hands-on skills get rusty when they’re never exercised. The muscle that thinks through a hard problem unassisted weakens if the assistant is always there. I notice this in myself, and when I raised it with my team, it turned out most of them had noticed it too and were dealing with it in silence.</p><p>I don’t have a full answer for what mind ergonomics should look like. I’m only sure the question is legitimate, and that leaders who dismiss it will pay for that in their teams’ capability a few years from now. We take care of our bodies so we can keep working. Our minds deserve at least the same.</p><h3>The short version</h3><p>Delegate what’s well defined and repetitive. Never delegate accountability, and keep the agent’s hands off your git history. Measure speed by comprehension, not output volume. Fix your foundations first, because AI amplifies whatever it finds. And talk about all of this openly with your team. The job is changing for everyone, and it changes better for teams that face it out loud.</p><p><strong>Muktar SayedSaleh @ 2026</strong><br><a href="https://github.com/muktarsayedsaleh">GitHub</a><br><a href="https://www.linkedin.com/in/muktarsayedsaleh/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9980c67b09c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The perfect pre-commit hooks config for your Python projects]]></title>
            <link>https://muktar-sayedsaleh.medium.com/the-perfect-pre-commit-hooks-config-for-your-python-projects-4f56152247fd?source=rss-e449325e2d64------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f56152247fd</guid>
            <dc:creator><![CDATA[Muktar SayedSaleh | مختار سيد صالح]]></dc:creator>
            <pubDate>Thu, 15 May 2025 09:48:45 GMT</pubDate>
            <atom:updated>2025-07-28T10:41:00.640Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*7oKkZtszBK0IePqCfS-jMQ.png" /></figure><p><strong>Original Blog: </strong><a href="https://muktar.tech/improve-your-code-quality-and-development-workflow-with-pre-commit-hooks-5bc73fd48c65">https://muktar.tech/improve-your-code-quality-and-development-workflow-with-pre-commit-hooks-5bc73fd48c65</a></p><p><strong><em>Disclaimer</em></strong><em>: This is intended to be a quick “copy-paste” guide for those searching for this answer, not a full-fledged blog post.</em></p><pre>repos:<br>    - repo: https://github.com/pre-commit/pre-commit-hooks<br>      rev: v4.4.0<br>      hooks:<br>          - id: check-yaml<br>          - id: trailing-whitespace<br>          - id: end-of-file-fixer<br>          - id: debug-statements<br>          - id: requirements-txt-fixer<br>    - repo: https://github.com/astral-sh/ruff-pre-commit<br>      rev: v0.1.8<br>      hooks:<br>        - id: ruff<br>          args: [ --fix ]<br>        - id: ruff-format<br>    - repo: https://github.com/asottile/reorder-python-imports<br>      rev: v3.10.0<br>      hooks:<br>          - id: reorder-python-imports<br>            args: [--py310-plus]<br>            stages: [commit]<br>    - repo: https://github.com/asottile/add-trailing-comma<br>      rev: v3.0.1<br>      hooks:<br>          - id: add-trailing-comma<br>            stages: [commit]<br>    - repo: https://github.com/asottile/pyupgrade<br>      rev: v3.10.1<br>      hooks:<br>          - id: pyupgrade<br>            args: [--py310-plus]<br>            stages: [commit]<br>    - repo: https://github.com/pre-commit/mirrors-autopep8<br>      rev: v2.0.2<br>      hooks:<br>          - id: autopep8<br>            stages: [commit]<br>    - repo: https://github.com/PyCQA/flake8<br>      rev: 6.1.0<br>      hooks:<br>          - id: flake8<br>            stages: [commit]</pre><p>Muktar SayedSaleh @ 2025<br><a href="https://github.com/muktarsayedsaleh">GitHub</a><br><a href="https://www.linkedin.com/in/muktarsayedsaleh/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f56152247fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[قصيدة: صاحبة الجلالة]]></title>
            <link>https://muktar-sayedsaleh.medium.com/%D9%82%D8%B5%D9%8A%D8%AF%D8%A9-%D8%B5%D8%A7%D8%AD%D8%A8%D8%A9-%D8%A7%D9%84%D8%AC%D9%84%D8%A7%D9%84%D8%A9-4f31e4abc9e5?source=rss-e449325e2d64------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f31e4abc9e5</guid>
            <category><![CDATA[مختار-سيد-صالح]]></category>
            <category><![CDATA[صاحبة-الجلالة]]></category>
            <category><![CDATA[اللغة-العربية]]></category>
            <category><![CDATA[قصيدة]]></category>
            <category><![CDATA[sam-altman]]></category>
            <dc:creator><![CDATA[Muktar SayedSaleh | مختار سيد صالح]]></dc:creator>
            <pubDate>Wed, 13 Nov 2024 12:02:25 GMT</pubDate>
            <atom:updated>2024-11-14T12:59:25.631Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fz-VQWq-7igFCmNsGKXQMQ.png" /></figure><p>لها ما لها،</p><p>و بها ما بها</p><p>فكيفَ ستدنو لِأَعتابِها؟</p><p>و كيفَ ستقحَمُ أسوارَها و أنتَ تهيَّبتَ مِنْ بابِها؟</p><p>و مِـمَّ -و كَـرْمُــكَ مَحْضُ العَواطِفِ-</p><p>تَعْصِرُ خمراً لِأَعنابِها؟</p><p>و هَبْكَ مَلأتَ دِنانَ البيانِ و أغدَقْتَ مِنها لِشُرَّابِها</p><p>فَأُعْطِيتَ مِنْ سِحرِها ما تطيرُ الـعقولُ بهِ فَرْطَ إعجابِها</p><p>و أدركتَ مِنْ سِرِّها ما يُحَيّرُ أَهلَ نُهَاها و أَلبابِها</p><p>و حلّقتَ ..</p><p>حلّقتَ ..</p><p>حتَّى ظَنَنْتَ أنَّكَ تعلو فتحظى بِها</p><p>رؤًى ناضحاتٍ بماءِ الخُلودِ تديرُ اللَّيالي بدولابِها</p><p>إذنْ عندَها تغتدي والهاًَ جديداً يضافُ لأحبابِها!</p><p>و رُبَّتَما تنتهي خَاطِباً أخيراً</p><p>بطابورِ خُطَّابِها!</p><p>*</p><p>سلامٌ على الضَّادِ أُمِّ اللُّغاتِ بإيجازِها و بإطنابِها</p><p>سلامٌ عليها، على الـمُنتَمينَ إليها بها و بأسبابِها</p><p>سلامٌ عليها، على النَّاطقينَ بها مِنْ ذويها و أنسابِها</p><p>بما اختارَها اللهُ مِنْ أجلِهِ لِقُرْآنِهِ دونَ أترابِها</p><p>بما منحتْ أرضُها من ثمارِ المجازِ لأقلامِ كُتَّابها</p><p>بأيَّامِنا و بتأريخِنا و أخبارِنا بينَ أصلابِها</p><p>بما شَرَّفَتْ أهلَها في الورى و قَدْ شُرِّفَتْ حينَ أَوحَى بِها!</p><p>*</p><p>لَئِنْ ظُنَّ أنَّ العلومَ الحديثةَ،</p><p>أو (سام آلتمان) أودى بِها</p><p>أُطَمْئِنُكُمْ،</p><p>إنَّ في جوفَها ينابيعَ يُسعى لإنضابِها</p><p>و حاشا، الذي ذخرَ الماءَ فيها و أودَعَهُ تحتَ أثوابِها</p><p>لها هيَّأَ الهِمَمَ العالياتِ التي لا تُضارُ بِمُغْتابِها</p><p>إذا علّموها لجيلٍ جديدٍ فَقَدْ حصَّنوها بِطُلَّابِها</p><p>كثيرونَ هُمْ</p><p>و أثيرونَ هُمْ</p><p>يضيؤونَ كوكبَ آدابِها</p><p>*</p><p>فشُكراً مِنَ القلبِ للعاقدينَ نِياطَ القلوبِ بمحرابِها</p><p>لِمَنْ رضعوا حُبَّها فتيةً</p><p>و ها هم فحولٌ كأربابِها</p><p>يصونونها مِنْ أذى العابثينَ بما خيَّلوا للورى،</p><p>لا بِها</p><p>شَكَرتُهُمُ شُكرَ أُسْدِ الشّرى، تحنّ حنيناً إلى غابها</p><p>و قد بتُّ في بلدٍ أجنبيٍّ بعيدٍ</p><p>أكنّي المنادى بها</p><p>هيَ اللُّغةُ العربيَّةُ</p><p>تبقى المليكَةَ حُفَّتْ بِحُجَّابِها</p><p>جميع الحقوق محفوظة</p><h3>مختار سيّد صالح</h3><p>شاعر عربي يحمل درجة الماجستير في هندسة البرمجيّات (<a href="https://muktar.tech/about">اقرأ سيرتي الذاتية</a>)</p><p><a href="https://github.com/MuktarSayedSaleh">GitHub</a><br><a href="https://www.linkedin.com/in/muktarsayedsaleh//">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f31e4abc9e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Developers Should Perform Self Code Reviews Before Submitting PRs]]></title>
            <link>https://muktar-sayedsaleh.medium.com/why-developers-should-perform-self-code-reviews-before-submitting-prs-23492d15edd3?source=rss-e449325e2d64------2</link>
            <guid isPermaLink="false">https://medium.com/p/23492d15edd3</guid>
            <dc:creator><![CDATA[Muktar SayedSaleh | مختار سيد صالح]]></dc:creator>
            <pubDate>Tue, 08 Oct 2024 13:33:27 GMT</pubDate>
            <atom:updated>2024-10-08T13:33:27.083Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3fABt9OQPLxejTZL" /></figure><p>As a developer, I believe that self code reviews are an essential practice that can greatly enhance the quality of our work. Here are a few reasons why I make it a point to review my own code before submitting a pull request (PR).</p><p><strong>1. Catch My Own Mistakes</strong></p><p>Even the most experienced developers can overlook errors while writing code. Taking the time for a self-review allows me to catch logical errors, typos, or performance issues that I might have missed. It’s my chance to fix mistakes before my peers see them.</p><p><strong>2. Improve Code Quality</strong></p><p>Revisiting my code gives me the opportunity to refine it for readability, maintainability, and efficiency. I often ask myself questions like, “Can someone else understand this code?” and “Is there a more efficient way to implement this?” This reflective practice leads to cleaner, more polished code.</p><p><strong>3. Reduce My Team’s Load</strong></p><p>Submitting a clean, well-reviewed PR eases the burden on my teammates. They can focus on more complex logic or architecture instead of pointing out basic mistakes or asking for improvements. This not only speeds up the review process but also fosters a more collaborative environment.</p><p><strong>4. Learn and Grow as a Developer</strong></p><p>Self code reviews encourage me to critically analyze my work and reflect on my coding decisions. Over time, this habit helps improve my problem-solving skills and enables me to write better code from the start. Every review becomes a learning opportunity.</p><p><strong>In a nutshell: </strong>Incorporating self code reviews into my workflow is a simple yet powerful habit that enhances both my work and my team’s efficiency. Before I submit my next PR, I’ll take that moment to review my own code — it’s definitely worth the effort!</p><p>Muktar SayedSaleh @ 2024<br><a href="https://github.com/muktarsayedsaleh">GitHub</a><br><a href="https://www.linkedin.com/in/muktarsayedsaleh/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23492d15edd3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[قصيدة: يا سادن الماء]]></title>
            <link>https://muktar-sayedsaleh.medium.com/%D9%82%D8%B5%D9%8A%D8%AF%D8%A9-%D9%8A%D8%A7-%D8%B3%D8%A7%D8%AF%D9%86-%D8%A7%D9%84%D9%85%D8%A7%D8%A1-e1c58c16832f?source=rss-e449325e2d64------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1c58c16832f</guid>
            <category><![CDATA[يا-سادن-الماء]]></category>
            <category><![CDATA[جائزة-سعاد-الصباح]]></category>
            <category><![CDATA[جائزة-الشارقة]]></category>
            <category><![CDATA[شعر]]></category>
            <category><![CDATA[رثاء]]></category>
            <dc:creator><![CDATA[Muktar SayedSaleh | مختار سيد صالح]]></dc:creator>
            <pubDate>Tue, 27 Aug 2024 10:26:04 GMT</pubDate>
            <atom:updated>2025-08-12T11:14:57.316Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ABx-XF2LIbG5TlP2" /></figure><p>تَمَهَّلْ</p><p>و لا تَمْتَحِنِّي بما لا أُطيقُ</p><p>*</p><p>تمهَّــلْ</p><p>فَلَمْ نُنْهِ ترتيبَ أحلامِنا بعدُ،</p><p>ثمَّةَ حُلْمٌ خفيفٌ يجيءُ إلينا على مَهْلِهِ،</p><p>هكذا وعدَتْنا الطَّريقُ</p><p>*</p><p>تمهَّــلْ</p><p>فــ”ريمةُ” للآنَ واقفةٌ في انتظارِكَ،</p><p>و هْيَ تُحِبُّكَ مِنْ يومِ صارحْتَها باحتراقِكَ،</p><p>لكنَّها فضَّلتْ أنْ تُشَاغِلَ فِتْنَتَها بالدَّلالِ ثلاثَ سنينٍ،</p><p>و ترنو إليكَ و أنتَ تجيءُ موارَبَةً كلَّ حينٍ،</p><p>على أملٍ أنْ تراها</p><p>و تَلْمِسَ ضِلْعَيْكَ منْ دهشةٍ</p><p>فَرِحَاً أنَّ بينَهما خافِقاً</p><p>يستفيقُ</p><p>*</p><p>تمهَّلْ</p><p>غداً سوفَ يأتيْ إليكَ “حَمَدْ”</p><p>و سوفَ معاً نتواطؤُ</p><p>كي تعتلي وجهَهُ بسمةٌ يائِسَةْ</p><p>سنقولُ لهُ : “لا تُخَلِّ سَعَدْ</p><p>يتزوَّجُ قبلَكَ،</p><p>لا تَكُ أوَّلَ مَنْ يَصِمُ الجيلَ بالآنِسةْ” !</p><p>و سوفَ يفورُ و يكظِمُ،</p><p>سوفَ يفورُ و يكظِمُ،</p><p>لكنَّنا مثلَ عادتِنا سنعيدُ إليهِ تفاؤلَهُ،</p><p>ثمَّ نُقْنِعُهُ أنَّهُ للحياةِ صديقُ</p><p>تَمَهَّلْ</p><p>و لا تَمْتَحِنِّي بما لا أُطيقُ</p><p>*</p><p>تمهَّلْ</p><p>سَيَنْقُصُنا “لاعبٌ رابعٌ” لا يغشُّ</p><p>و لكنَّهُ عندَما بدهاءٍ يفوزُ</p><p>يقولُ لنا كلَّنا: “لا تبوقوا” !! <a href="#_ftn1">[1]</a></p><p>تَمَهَّلْ</p><p>و لا تَمْتَحِنِّي بما لا أُطيقُ</p><p>*</p><p>تمهَّلْ</p><p>دمشقُ القديمةُ دونَ أحاديثِنا مُرَّةٌ،</p><p>و كلُّ شوارِعِها اختَنَقَتْ بالحنينِ إلى الخطواتِ السَّريعَةِ،</p><p>هل تتذكَّرُ كيفَ بدأنا نحرِّرُ أقدامَنا ثمَّ نتبَعُها حاملينَ نقاشاتِنا</p><p>عَنْ قصائدِ محمودِ درويشَ أو عَنْ جَمالِ بناتِ القُرَى ؟</p><p>تُرَى كنتَ مثلي أنا لا تَرَى</p><p>في المدينةِ إلَّا الذي جمَّلَتْهُ الفُروقُ ؟!</p><p>تَمَهَّلْ</p><p>و لا تَمْتَحِنِّي بما لا أُطيقُ</p><p>*</p><p>تَمَهَّلْ</p><p>فبي خجلٌ منكَ يا صاحبي</p><p>قلتَ لي ذاتَ وَجْدٍ: “أريدُكَ أنْ تحفظَ الجملَةَ التَّالِيَةْ</p><p>لِتَنْقُلَها إذْ أموتُ ففيها رؤايَ عَنِ الفكرةِ العالِيَةْ”</p><p>و لكنَّني كنتُ مُنشغِلاً عنكَ بالجملةِ الألفِ</p><p>كي أنتَ تنقلَها مثلَما قلتُ لكْ</p><p>تُرى</p><p>كيفَ لمْ أنتَبِهْ مرَّةً واحدَةْ ؟!</p><p>و هلْ سيخفِّفُ عنِّيَ أنْ أتعلَّلَ بالسَّنواتِ الطِّوالِ</p><p>و ذاكرتي البارِدَةْ</p><p>و هذا الكلامِ الذي لا يليقُ ؟!!</p><p>تَمَهَّلْ</p><p>و لا تَمْتَحِنِّي بما لا أُطيقُ</p><p>*</p><p>تمهَّلْ</p><p>تمهَّلْ</p><p>تمهَّلْ</p><p>فليسَ بِمَقدورِ هذي القصيدةِ لو رحتَ أنْ تُرْجِعَكْ</p><p>تمهَّلْ إذنْ يا ابنَ أمِّي</p><p>أو ارحمْ ندائي الفقيرَ</p><p>و خذني مَعَكْ !</p><p>*</p><p>*</p><p>أبا جُليبيبَ” … أيُّ جِلْبابِ”</p><p>علَّقْتَهُ اليومَ فوقَ أهْدابي ؟!</p><p>أيُّ خُشوعِ الرِّثاءِ أبقيتَ لي</p><p>يا صاحبي و الدُّموعُ مِحرابي</p><p>و ها نحيبي قد انتهى نغَماً</p><p>ما مرَّ يوماً ببالِ زِرْيَابِ ؟!!</p><p>*</p><p>قصيدتي في الرِّثاءِ تكتُبُني</p><p>مواجِعاً إذْ أبثّها ما بي</p><p>كُلُّ “تَمَهَّلْ” أقولُها أَجَلٌ</p><p>يخْطِفُ روحَي منْ بَيْنِ أثْوابي</p><p>فهل أقولُ: الحروبُ قاسِيَةٌ</p><p>قَدْ أَكَلَتْ إخوتي و أحبابي ؟!</p><p>و هلْ يعيدُ الرِّثاءُ خيرَهُمُ</p><p>مُتَّزِنَ القَولِ، ضاحِكَ النَّابِ ؟!</p><p>يا أكملَ العارفينَ خُذْ بِيَدي</p><p>كي لا يُقالَ : الحريقُ أودى بي !!</p><p>*</p><p>ها غُرفَتي و الشِّتاءُ صيَّرَها</p><p>خناجراً تستبيحُ أعصابي</p><p>نافذتي عرَّشَ الحنينُ بها</p><p>و عشَّشَ الوجدُ خلفَ أبوابي</p><p>فيا أخي في المياهِ مَعْذِرَةً</p><p>سفينَتي الآنَ مَحْضُ أخشابِ !!</p><p>***</p><p>[1] “لا تبوقوا”: باللهجة المحكيّة لمدينتنا و تعني لا تسرقوا.</p><p>البوكمال ٢٠١٣</p><p>جميع الحقوق محفوظة</p><h3>مختار سيّد صالح</h3><p>شاعر عربي يحمل درجة الماجستير في هندسة البرمجيّات (<a href="https://muktar.tech/about">اقرأ سيرتي الذاتية</a>)</p><p><a href="https://github.com/MuktarSayedSaleh">GitHub</a><br><a href="https://www.linkedin.com/in/muktarsayedsaleh//">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1c58c16832f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Remove All Git Branches Except main and dev?]]></title>
            <link>https://muktar-sayedsaleh.medium.com/how-to-remove-all-git-branches-except-main-and-dev-6ca105431705?source=rss-e449325e2d64------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ca105431705</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[how-to]]></category>
            <dc:creator><![CDATA[Muktar SayedSaleh | مختار سيد صالح]]></dc:creator>
            <pubDate>Sat, 10 Aug 2024 09:51:05 GMT</pubDate>
            <atom:updated>2024-08-10T09:51:05.421Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GSKgOWWq4d1GvTkq" /></figure><p><strong><em>Disclaimer</em></strong><em>: This is intended to be a quick “how-to” guide for those searching for this answer, not a full-fledged blog post.</em></p><pre>git branch | grep -v &quot;main\|dev&quot; | xargs git branch -D</pre><h4>Explanation:</h4><p><strong>git branch:</strong> Lists all local branches.</p><p><strong>grep -v “main\|dev”</strong>: Filters out the <strong>main</strong> and <strong>dev</strong> branches from the list.</p><p><strong>xargs git branch -D</strong>: Deletes the branches that were filtered.</p><p>Muktar SayedSaleh @ 2024<br><a href="https://github.com/muktarsayedsaleh">GitHub</a><br><a href="https://www.linkedin.com/in/muktarsayedsaleh/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ca105431705" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[زوّادة للسَّفر الأبديّ]]></title>
            <link>https://muktar-sayedsaleh.medium.com/%D8%B2%D9%88%D9%91%D8%A7%D8%AF%D8%A9-%D9%84%D9%84%D8%B3%D9%91%D9%8E%D9%81%D8%B1-%D8%A7%D9%84%D8%A3%D8%A8%D8%AF%D9%8A%D9%91-e2ccc642f771?source=rss-e449325e2d64------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2ccc642f771</guid>
            <category><![CDATA[جائزة-سعاد-الصباح]]></category>
            <category><![CDATA[شعر]]></category>
            <category><![CDATA[أمير-الشعراء]]></category>
            <category><![CDATA[جائزة-الشارقة-للإبداع]]></category>
            <dc:creator><![CDATA[Muktar SayedSaleh | مختار سيد صالح]]></dc:creator>
            <pubDate>Thu, 18 Jul 2024 09:45:44 GMT</pubDate>
            <atom:updated>2024-07-18T09:46:18.939Z</atom:updated>
            <content:encoded><![CDATA[<h3>قصيدة: زوّادة للسَّفر الأبديّ</h3><p><strong>٢٠١٣ — دمشق</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bUKYput7yIrD7XxT" /></figure><p>الآنَ</p><p>أنا نَهْرُ الدَّمْعِ المُتَخَفِّي</p><p>خَلْفَ قِنَاعِ المُبتَسِمِ المُتَفَائِلِ بالأيَّامِ القادِمَةِ،</p><p>أسيرُ وحيداً في حاراتِ دمشقَ لِأَملأَ عينيَّ،</p><p>و أملأَ كلَّ حواسي الخمسِ مِنَ:</p><p>الطُّرُقاتِ — الغُرُفاتِ — الشُّرفاتِ</p><p>الحاراتِ — الدَّاراتِ — الجاراتِ</p><p>الأحجارِ — الأشجارِ — الأقمارِ</p><p>الأطباقِ — الأسواقِ — الأعراقِ</p><p>صراخِ الباعةِ — أحداثِ الساعةِ</p><p>قَلَقِ الماشينَ — عيونِ الواشينِ</p><p>الإعلاناتِ — الدَّعواتِ — النَّعواتِ — القِطَطِ — الخُططِ</p><p>نساءِ الحَيِّ — دكاكينِ التَّمرِ الهنديِّ — مآذنِ جامعِها الأُمَويِّ</p><p>مقاهيها — بيتي المُستَأجَرِ فيها — الحمَّاماتِ</p><p>محلَّاتِ الألبسةِ المُستعملةِ — الأبوابِ السَّبعةِ — سورِ دمشقَ</p><p>المتحفِ — بردى الباكي — كورنيشِ المعرضِ</p><p>طاوِلَتي في مقهى الشّعراءِ المغمورينَ — الجامعةِ — العينِ الدّامعةِ</p><p>الحُبِّ الأوَّلِ صارَ قصائدَ صارتْ كُتُباً فوقَ رصيفٍ للغُيَّابِ</p><p>نفقِ الآدابِ — ملاعب كرة القدم — مكاتبِ هيئةِ أُمَمِ</p><p>سفاراتِ بلادٍ جَهِدَتْ كي تَقِفَ طوابيرُ الأحلامِ هناكَ</p><p>مكاتبِ شركاتٍ لَمْ تقرأْ يوماً سيرَتِيَ الذَّاتِيَّةَ</p><p>.. و إلى آخرِ هذي الأشياءْ،</p><p>أحتاجُ حياةً أخرى كي أحصيَ هذي الأشياءْ!</p><p>*</p><p>آهٍ يا بصري ساعدني،</p><p>آهٍ يا سمعي ساعدني،</p><p>آهٍ يا دمعي ساعدني،</p><p>وسطَ الشَّارعِ و الأسواقِ تجلَّدْ، لا تفضحني،</p><p>كَمْ أحتاجُ إلى ذاكِرَةٍ لا تثقُبُها الحَرْبُ</p><p>تُعَوِّضُ ما لَمْ يَتَمَعَّنْهُ القلبُ مِنَ المُدُنِ الأخرى</p><p>قدْ يأتي يومٌ لا يُبقي مِنْ هذا الوطنِ الغالي</p><p>إلَّا الذِّكرى!</p><p>*</p><p>*</p><p><em>(فلاش باك — البوكمال ٢٠٠٨)</em></p><p>دَرَجٌ على جُرْفِ الفُراتِ يُضَمِّدُ الرُّوحَ اليتيمَةَ،</p><p>كنتُ طولَ اللَّيلِ أبكي، لَمْ يَكُنْ في القلبِ أطلالٌ</p><p>و لكنِّي بكيتُ كأنَّني في حضنِ أمِّي،</p><p>زَفْرَتَا وَجَعٍ هُنَاكَ</p><p>سَتَكْفِيَانِ لِكَي أُرَمِّمَ قلبيَ المَهجورَ</p><p>مِنْ قَلَقِ المُرَاهِقِ ثُمَّ أمضي للحياةِ</p><p>مُطبِّبَاً و مجرِّباً، و قصيدتي الأملُ الوحيدْ</p><p>*</p><p>*</p><p>الآنَ</p><p>لا جُرْفُ الفُرَاتِ يليقُ بالمَبْكَى</p><p>و لا غَدُكَ الشَّريدْ</p><p>فاملَأْ عيونَكَ بالأماكنِ كلِّها و املأ حواسَكْ،</p><p>و ابكِ الدُّموعَ، ابكِ العيونَ و لا تَماسَكْ!</p><p>و احملْ منَ الوطنِ المُقَدَّسِ في الحقائبِ</p><p>ما استطعتَ من الدُّموعِ و من ضبابِ الذِّكرياتِ،</p><p>فرُبَّما تحتاجُها إنْ باغَتَ القلبَ البكاءُ</p><p>هناكَ</p><p>في المنفى البعيدْ،</p><p>آهٍ منَ المنفى البعيدْ!</p><p>جميع الحقوق محفوظة</p><h3>مختار سيّد صالح</h3><p>شاعر عربي يحمل درجة الماجستير في هندسة البرمجيّات (<a href="https://muktar.tech/about">اقرأ سيرتي الذاتية</a>)</p><p><a href="https://github.com/MuktarSayedSaleh">GitHub</a><br><a href="https://www.linkedin.com/in/muktarsayedsaleh//">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2ccc642f771" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploy Resources to Alibaba Cloud Seamlessly using Azure DevOps]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://muktar-sayedsaleh.medium.com/deploy-resources-to-alibaba-cloud-seamlessly-using-azure-devops-e96dc177b61a?source=rss-e449325e2d64------2"><img src="https://cdn-images-1.medium.com/max/750/0*7FSuRUnETQZAazXt.jpg" width="750"></a></p><p class="medium-feed-snippet">As organizations look to expand their operations in the Chinese market, adopting a hybrid cloud environment that combines a global cloud&#x2026;</p><p class="medium-feed-link"><a href="https://muktar-sayedsaleh.medium.com/deploy-resources-to-alibaba-cloud-seamlessly-using-azure-devops-e96dc177b61a?source=rss-e449325e2d64------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://muktar-sayedsaleh.medium.com/deploy-resources-to-alibaba-cloud-seamlessly-using-azure-devops-e96dc177b61a?source=rss-e449325e2d64------2</link>
            <guid isPermaLink="false">https://medium.com/p/e96dc177b61a</guid>
            <category><![CDATA[alibabacloud]]></category>
            <category><![CDATA[azure-devops]]></category>
            <dc:creator><![CDATA[Muktar SayedSaleh | مختار سيد صالح]]></dc:creator>
            <pubDate>Thu, 18 Jul 2024 09:39:51 GMT</pubDate>
            <atom:updated>2024-07-18T09:39:51.257Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Building an Enterprise Cloud-based File Sharing Platform between the US and Mainland China]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://muktar-sayedsaleh.medium.com/building-an-enterprise-cloud-based-file-sharing-platform-between-the-us-and-mainland-china-c4b88213968e?source=rss-e449325e2d64------2"><img src="https://cdn-images-1.medium.com/max/1600/0*h1IQuJNE9fTmKP-t" width="1600"></a></p><p class="medium-feed-snippet">In today&#x2019;s fast-changing world, businesses are no longer limited by borders. Thanks to advanced technology and the rise of multinational&#x2026;</p><p class="medium-feed-link"><a href="https://muktar-sayedsaleh.medium.com/building-an-enterprise-cloud-based-file-sharing-platform-between-the-us-and-mainland-china-c4b88213968e?source=rss-e449325e2d64------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://muktar-sayedsaleh.medium.com/building-an-enterprise-cloud-based-file-sharing-platform-between-the-us-and-mainland-china-c4b88213968e?source=rss-e449325e2d64------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4b88213968e</guid>
            <category><![CDATA[alibabacloud]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[mainland-china]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[us-and-mainland-china]]></category>
            <dc:creator><![CDATA[Muktar SayedSaleh | مختار سيد صالح]]></dc:creator>
            <pubDate>Mon, 15 Jul 2024 12:23:36 GMT</pubDate>
            <atom:updated>2024-07-15T12:29:03.261Z</atom:updated>
        </item>
    </channel>
</rss>