<?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 Eslam Shoaala on Medium]]></title>
        <description><![CDATA[Stories by Eslam Shoaala on Medium]]></description>
        <link>https://medium.com/@es1amaged?source=rss-65f5ccfeb229------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DYWKgMc3TvlZXQEJbunWpg.jpeg</url>
            <title>Stories by Eslam Shoaala on Medium</title>
            <link>https://medium.com/@es1amaged?source=rss-65f5ccfeb229------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:22:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@es1amaged/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[I Was Tired of Downloading My MBA Coursework Manually, So I Built GradPack With Codex]]></title>
            <link>https://medium.com/@es1amaged/i-was-tired-of-downloading-my-mba-coursework-manually-so-i-built-gradpack-with-codex-ab4f7c0e17a2?source=rss-65f5ccfeb229------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab4f7c0e17a2</guid>
            <category><![CDATA[study]]></category>
            <category><![CDATA[mba]]></category>
            <category><![CDATA[canvas]]></category>
            <category><![CDATA[xcode]]></category>
            <dc:creator><![CDATA[Eslam Shoaala]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 12:53:29 GMT</pubDate>
            <atom:updated>2026-08-31T12:53:29.529Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How one repetitive student problem became an open-source Chrome extension, installation videos for non-technical users, and a bigger lesson about building with AI.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4cdQgYSc0LPNNkmw" /><figcaption>Photo by <a href="https://unsplash.com/@imkirk?utm_source=medium&amp;utm_medium=referral">Iewek Gnos</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As I moved closer to the end of my MBA at Frankfurt School, I started thinking about what would happen to all the knowledge I had accumulated in Canvas.</p><p>Lecture slides, readings, files, course pages, and links were spread across different modules and courses. I could access them now, but that did not mean I would always have access to them.</p><p>The obvious solution was to download everything I wanted to keep.</p><p>The problem was the word <em>everything</em>.</p><p>Doing it manually meant opening every course, moving through its modules, finding the useful pages and files, downloading them one by one, and then recreating a sensible folder structure on my laptop. It was possible, but it was exactly the sort of repetitive task that is easy to postpone until it is too late.</p><p>I did not begin with an ambition to build a software product. I began with a much simpler thought:</p><blockquote>There must be a better way to do this in one go.</blockquote><p>That thought became <a href="https://github.com/Eslamunto/GradPack">GradPack</a>, a Chrome extension designed to turn the Canvas course materials a student can already access into useful local archives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*Qi6MSYo0XDhP0WgxVAyD7Q.png" /></figure><p>More importantly, the process changed how I think about building with AI.</p><h3>Starting with the problem, not the technology</h3><p>I did not approach Codex with a detailed technical specification. I approached it with the frustration I understood firsthand.</p><p>I wanted to select my courses, preserve the available material locally, and retain enough structure to make the archive useful later. I did not want to click through every item manually. I also did not want the solution to upload my coursework somewhere else or require me to provide my password, cookies, or other credentials.</p><p>Those boundaries mattered as much as the feature itself.</p><p>The first useful step, then, was not asking Codex to “build a Chrome extension.” It was explaining the situation:</p><ul><li>Canvas already knew which courses and materials I was allowed to access.</li><li>I was already signed in through Chrome.</li><li>The resulting files should stay on my computer.</li><li>The archive should be understandable without needing Canvas later.</li><li>The tool should not bypass permissions or attempt to retrieve anything unavailable to me.</li></ul><p>Once the problem was framed that way, Codex could help turn a vague frustration into smaller questions we could actually solve.</p><p>How should the extension discover courses? What should happen when a resource cannot be downloaded? Should several courses become one large archive or separate files? How should the student review what will happen before the download starts? What would make the result useful offline rather than merely a pile of files?</p><p>This was the real beginning of GradPack.</p><h3>It was not one magical prompt</h3><p>Stories about building with AI sometimes compress the entire process into a sentence: “I typed a prompt, and the app appeared.”</p><p>That was not my experience, and I think the real process is more interesting.</p><p>GradPack developed through many rounds of discussion, implementation, testing, and correction. I supplied the problem, priorities, and decisions. Codex helped me inspect how Canvas behaved, propose options, write the code, run tests, identify gaps, and document what we had learned.</p><p>We began narrowly. The early pilot focused on saving one accessible course at a time. That gave us a smaller real-world workflow to understand before expanding it.</p><p>Then the questions became more demanding.</p><p>Canvas is not simply a folder full of downloadable files. A course may organize material through modules, pages, files, and external links. Some sections may be disabled. Some resources may be unavailable. A signed-in session can expire, a browser tab can move, and a large course may not fit comfortably into one archive.</p><p>Each discovery forced us to make a product decision rather than merely add more code.</p><p>GradPack eventually grew to let a student select one or more displayed courses, including completed ones, and choose a combined archive or one archive per course. Before retrieving the material, it checks the selected courses and presents a review. Courses that are ready can continue; those that cannot be handled safely are clearly marked instead of silently disappearing.</p><p>The downloaded archive includes an offline interface for navigating the preserved material and an archive status that records what succeeded, what remained an external link, and what could not be retrieved. If some courses do not finish, the student can retry those courses without repeating the successful work.</p><p>These details may sound less exciting than generating an app in one prompt. But they are the difference between a demo and something another person might trust with a real task.</p><h3>Why local-first and open source mattered</h3><p>Coursework can contain personal, licensed, or institution-specific material. That made the architecture a question of trust.</p><p>GradPack uses the Canvas session already open in the student’s browser and works only with material that session can access. The current pilot has no analytics, telemetry, backend, or cloud upload. The archive is generated locally and downloaded to the student’s computer.</p><p>This does not give students new access or bypass Canvas controls. It helps them preserve material they can already view, for their own personal study. The responsibility not to redistribute course content remains important.</p><p>I also chose to make GradPack an open-source project under the Apache 2.0 license. That means the software does not have to be a black box. Others can inspect how it works, question its decisions, report problems, and eventually contribute improvements.</p><p>For a tool built around preserving personal access to educational material, transparency should be part of the product — not an afterthought.</p><h3>Working software was not enough</h3><p>Once the extension worked, I encountered another problem: installing an unpublished Chrome extension is not obvious to a non-technical user.</p><p>The current GradPack pilot is installed manually. A classmate has to extract the correct ZIP file, open Chrome’s extensions page, enable Developer mode, choose <strong>Load unpacked</strong>, select the extracted folder rather than the ZIP, sign in to Canvas, and keep the Canvas tab open while GradPack works.</p><p>None of those steps is especially difficult once you have seen them. But asking a classmate to follow unfamiliar browser instructions from a technical document creates unnecessary friction.</p><p>So Codex helped me work on both the onboarding and the software.</p><p>I created a short quick-start video and a slower, detailed installation guide with captions. The walkthroughs use recreated, privacy-safe screens rather than recordings of my real Canvas account. They contain no real course names, student identities, or Canvas URLs. Written installation and troubleshooting guidance accompany the videos for anyone who prefers to read.</p><p>Watch the video here: <a href="https://youtu.be/s-2Dxnll5j0">https://youtu.be/s-2Dxnll5j0</a></p><p>This part of the project taught me an important lesson: a solution is not finished when it works for the person who built it. It becomes useful when the intended user can understand it, install it, and recover when something goes wrong.</p><p>For technical builders, documentation and onboarding are often treated as the final layer. For non-technical users, they are part of the product itself.</p><h3>Where GradPack stands today</h3><p>GradPack is currently an alpha classmate pilot for Frankfurt School students using Canvas. It is distributed as an unpacked Chrome extension and is not yet available through the Chrome Web Store.</p><p>That distinction matters. Automated tests and a carefully prepared installation bundle provide useful evidence, but they are not the same as broad real-world acceptance. The next learning will come from classmates trying the extension in their own signed-in Canvas environments and reporting privacy-safe feedback.</p><p>The future plan is to make installation much easier by publishing GradPack through the Chrome Web Store. I also want to keep improving the offline archive experience and learn where the current workflow confuses or fails real students.</p><p>Frankfurt School is the starting point because it is the environment and student need I know. Canvas, however, is used by many educational institutions. If the pilot proves useful and the differences between institutions can be handled safely, GradPack could eventually support other students using the same platform.</p><p>That is a direction, not a promise. Expanding responsibly will require testing against real institutional configurations, respecting access boundaries, and avoiding the assumption that every Canvas environment behaves the same way.</p><h3>The bigger lesson: frame one problem well</h3><p>GradPack began with a task I was avoiding.</p><p>I did not need to know every component of a Chrome extension before starting. I needed to understand my own problem well enough to describe the desired outcome and recognize the decisions that mattered.</p><p>Codex reduced the distance between that understanding and working software. It could investigate, propose, implement, test, and explain at a speed I could not have achieved alone. But the collaboration still depended on my context, judgment, and real-world verification.</p><p>If you are curious about building with Codex but do not consider yourself technical, I would not begin by searching for an app idea. I would begin by noticing repetition.</p><p>Ask yourself:</p><ol><li><strong>What repeatedly frustrates me?</strong> Look for a task you delay because it is tedious, fragmented, or easy to get wrong.</li><li><strong>What outcome do I actually want?</strong> Describe the finished result rather than guessing which technology should create it.</li><li><strong>What must the solution protect or avoid?</strong> Think about privacy, permissions, cost, reliability, and the people affected.</li><li><strong>What is the smallest version that would already help?</strong> A narrow real solution teaches more than an ambitious imaginary platform.</li><li><strong>How will I test it in reality?</strong> A local demonstration is a beginning. The real environment and intended users provide the evidence that matters.</li></ol><p>Then bring that framed problem to Codex and work through it as a conversation.</p><p>You may not end up building a Chrome extension. You may create a small script, a better workflow, a personal tool, or simply a clearer understanding of what is possible.</p><p>But you will be starting in the right place: not with AI looking for a purpose, but with a real problem worth solving.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab4f7c0e17a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Back to Coding: Rebuilding My Mac Terminal from Scratch]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@es1amaged/getting-back-to-coding-rebuilding-my-mac-terminal-from-scratch-f77b29044775?source=rss-65f5ccfeb229------2"><img src="https://cdn-images-1.medium.com/max/1510/1*Y_-H9N1RX8U9XGLEt425wQ.png" width="1510"></a></p><p class="medium-feed-snippet">iTerm2 + Zsh + Powerlevel10k: the full walkthrough</p><p class="medium-feed-link"><a href="https://medium.com/@es1amaged/getting-back-to-coding-rebuilding-my-mac-terminal-from-scratch-f77b29044775?source=rss-65f5ccfeb229------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@es1amaged/getting-back-to-coding-rebuilding-my-mac-terminal-from-scratch-f77b29044775?source=rss-65f5ccfeb229------2</link>
            <guid isPermaLink="false">https://medium.com/p/f77b29044775</guid>
            <category><![CDATA[terminal]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[zsh]]></category>
            <category><![CDATA[mac]]></category>
            <category><![CDATA[developer-tools]]></category>
            <dc:creator><![CDATA[Eslam Shoaala]]></dc:creator>
            <pubDate>Sun, 17 May 2026 12:58:07 GMT</pubDate>
            <atom:updated>2026-05-17T12:58:07.947Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Privacy in the Age of AI: What Are We Giving Up?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@es1amaged/privacy-in-the-age-of-ai-what-are-we-giving-up-adc5313a0582?source=rss-65f5ccfeb229------2"><img src="https://cdn-images-1.medium.com/max/2600/0*ogikmb9obO-KYq_0" width="6000"></a></p><p class="medium-feed-snippet">In the age of AI, privacy isn&#x2019;t lost all at once&#x200A;&#x2014;&#x200A;it&#x2019;s given away in small, unnoticed moments.</p><p class="medium-feed-link"><a href="https://medium.com/@es1amaged/privacy-in-the-age-of-ai-what-are-we-giving-up-adc5313a0582?source=rss-65f5ccfeb229------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@es1amaged/privacy-in-the-age-of-ai-what-are-we-giving-up-adc5313a0582?source=rss-65f5ccfeb229------2</link>
            <guid isPermaLink="false">https://medium.com/p/adc5313a0582</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[responsible-ai]]></category>
            <category><![CDATA[ai-ethics]]></category>
            <category><![CDATA[tech-policy]]></category>
            <category><![CDATA[artificial-intelligence-i]]></category>
            <dc:creator><![CDATA[Eslam Shoaala]]></dc:creator>
            <pubDate>Fri, 25 Apr 2025 23:26:50 GMT</pubDate>
            <atom:updated>2025-04-25T23:26:50.221Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Who’s Responsible When AI Goes Wrong? Exploring Governance and Accountability in AI]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@es1amaged/whos-responsible-when-ai-goes-wrong-exploring-governance-and-accountability-in-ai-615b6b901488?source=rss-65f5ccfeb229------2"><img src="https://cdn-images-1.medium.com/max/2600/0*SEeBvmM9jhGEfi9m" width="5675"></a></p><p class="medium-feed-snippet">When AI fails, who gets accountable?</p><p class="medium-feed-link"><a href="https://medium.com/@es1amaged/whos-responsible-when-ai-goes-wrong-exploring-governance-and-accountability-in-ai-615b6b901488?source=rss-65f5ccfeb229------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@es1amaged/whos-responsible-when-ai-goes-wrong-exploring-governance-and-accountability-in-ai-615b6b901488?source=rss-65f5ccfeb229------2</link>
            <guid isPermaLink="false">https://medium.com/p/615b6b901488</guid>
            <category><![CDATA[responsible-ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai-ethics]]></category>
            <category><![CDATA[tech-policy]]></category>
            <category><![CDATA[ai-governance]]></category>
            <dc:creator><![CDATA[Eslam Shoaala]]></dc:creator>
            <pubDate>Tue, 08 Apr 2025 23:24:05 GMT</pubDate>
            <atom:updated>2025-04-08T23:24:05.883Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Black Box Problem: Why Transparency in AI Matters]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@es1amaged/the-black-box-problem-why-transparency-in-ai-matters-cbd256ba1d1f?source=rss-65f5ccfeb229------2"><img src="https://cdn-images-1.medium.com/max/2600/0*SPMFl-0WYPxgdAko" width="5812"></a></p><p class="medium-feed-snippet">If we can&#x2019;t explain how an AI system works, how can we trust it to make decisions that affect our lives?</p><p class="medium-feed-link"><a href="https://medium.com/@es1amaged/the-black-box-problem-why-transparency-in-ai-matters-cbd256ba1d1f?source=rss-65f5ccfeb229------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@es1amaged/the-black-box-problem-why-transparency-in-ai-matters-cbd256ba1d1f?source=rss-65f5ccfeb229------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbd256ba1d1f</guid>
            <category><![CDATA[ai-governance]]></category>
            <category><![CDATA[ai-ethics]]></category>
            <category><![CDATA[responsible-ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[explainable-ai]]></category>
            <dc:creator><![CDATA[Eslam Shoaala]]></dc:creator>
            <pubDate>Tue, 08 Apr 2025 01:22:44 GMT</pubDate>
            <atom:updated>2025-04-08T01:31:35.100Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Can AI Ever Be Fair? Unpacking Bias in Algorithms]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@es1amaged/can-ai-ever-be-fair-unpacking-bias-in-algorithms-5b95f274f7c6?source=rss-65f5ccfeb229------2"><img src="https://cdn-images-1.medium.com/max/2160/0*6Z4TqjX8W7_VNlq2" width="2160"></a></p><p class="medium-feed-snippet">When we think of technology, we often associate it with precision, logic, and objectivity. But what if the systems we trust to make&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@es1amaged/can-ai-ever-be-fair-unpacking-bias-in-algorithms-5b95f274f7c6?source=rss-65f5ccfeb229------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@es1amaged/can-ai-ever-be-fair-unpacking-bias-in-algorithms-5b95f274f7c6?source=rss-65f5ccfeb229------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b95f274f7c6</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[responsible-ai]]></category>
            <category><![CDATA[ai-ethics]]></category>
            <category><![CDATA[bias-in-technology]]></category>
            <category><![CDATA[technology-and-society]]></category>
            <dc:creator><![CDATA[Eslam Shoaala]]></dc:creator>
            <pubDate>Mon, 17 Mar 2025 09:17:14 GMT</pubDate>
            <atom:updated>2025-03-18T00:44:12.447Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why Responsible AI Is No Longer Optional In Tech]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@es1amaged/why-responsible-ai-is-no-longer-optional-in-tech-71d0c2fa0d47?source=rss-65f5ccfeb229------2"><img src="https://cdn-images-1.medium.com/max/2600/0*omWwZps-ASNqwWxO" width="4896"></a></p><p class="medium-feed-snippet">Imagine living in a world where machines decide whether you qualify for a job, get approved for a loan, or receive healthcare&#x200A;&#x2014;&#x200A;and you&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@es1amaged/why-responsible-ai-is-no-longer-optional-in-tech-71d0c2fa0d47?source=rss-65f5ccfeb229------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@es1amaged/why-responsible-ai-is-no-longer-optional-in-tech-71d0c2fa0d47?source=rss-65f5ccfeb229------2</link>
            <guid isPermaLink="false">https://medium.com/p/71d0c2fa0d47</guid>
            <category><![CDATA[ai-ethics]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-governance]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[responsible-ai]]></category>
            <dc:creator><![CDATA[Eslam Shoaala]]></dc:creator>
            <pubDate>Fri, 14 Mar 2025 00:49:40 GMT</pubDate>
            <atom:updated>2025-03-14T01:04:25.952Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[JS in 3 minutes]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://codeburst.io/js-in-3-minutes-221a58cec1fd?source=rss-65f5ccfeb229------2"><img src="https://cdn-images-1.medium.com/max/2600/0*lYmBfpp7W3QbIZtr" width="5184"></a></p><p class="medium-feed-snippet">Not a blog post, but rather self-study notes that others might find useful. I am coming from Java background and want to speedup with JS&#x2026;</p><p class="medium-feed-link"><a href="https://codeburst.io/js-in-3-minutes-221a58cec1fd?source=rss-65f5ccfeb229------2">Continue reading on codeburst »</a></p></div>]]></description>
            <link>https://codeburst.io/js-in-3-minutes-221a58cec1fd?source=rss-65f5ccfeb229------2</link>
            <guid isPermaLink="false">https://medium.com/p/221a58cec1fd</guid>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Eslam Shoaala]]></dc:creator>
            <pubDate>Mon, 12 Nov 2018 00:34:25 GMT</pubDate>
            <atom:updated>2018-11-12T16:29:27.104Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Stop using `created_at` with MongoDB]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@es1amaged/stop-using-created-at-with-mongodb-a9d03e6b5385?source=rss-65f5ccfeb229------2"><img src="https://cdn-images-1.medium.com/max/2600/1*av3MfP7tEC72pkPKkLAfeQ.jpeg" width="4272"></a></p><p class="medium-feed-snippet">Keeping track of when was your document created in your database is important for sure.</p><p class="medium-feed-link"><a href="https://medium.com/@es1amaged/stop-using-created-at-with-mongodb-a9d03e6b5385?source=rss-65f5ccfeb229------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@es1amaged/stop-using-created-at-with-mongodb-a9d03e6b5385?source=rss-65f5ccfeb229------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9d03e6b5385</guid>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Eslam Shoaala]]></dc:creator>
            <pubDate>Mon, 30 Apr 2018 20:10:12 GMT</pubDate>
            <atom:updated>2018-04-30T20:10:41.883Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Hash Table]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://codeburst.io/the-hash-table-51516f49f347?source=rss-65f5ccfeb229------2"><img src="https://cdn-images-1.medium.com/max/2600/1*TH85PsaD_PqrhfpnJgFrYw.jpeg" width="6000"></a></p><p class="medium-feed-snippet">In an attempt to prepare for software engineering positions once my mandatory army period is over, I started reading Cracking the Coding&#x2026;</p><p class="medium-feed-link"><a href="https://codeburst.io/the-hash-table-51516f49f347?source=rss-65f5ccfeb229------2">Continue reading on codeburst »</a></p></div>]]></description>
            <link>https://codeburst.io/the-hash-table-51516f49f347?source=rss-65f5ccfeb229------2</link>
            <guid isPermaLink="false">https://medium.com/p/51516f49f347</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[algorithms]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[data-structures]]></category>
            <dc:creator><![CDATA[Eslam Shoaala]]></dc:creator>
            <pubDate>Sat, 21 Apr 2018 11:46:56 GMT</pubDate>
            <atom:updated>2018-06-19T14:24:29.151Z</atom:updated>
        </item>
    </channel>
</rss>