<?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 Amir R Muntasser on Medium]]></title>
        <description><![CDATA[Stories by Amir R Muntasser on Medium]]></description>
        <link>https://medium.com/@arkmuntasser?source=rss-1a4bd017d73a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FZ1CKluoZ39RMrWCglyN5g.jpeg</url>
            <title>Stories by Amir R Muntasser on Medium</title>
            <link>https://medium.com/@arkmuntasser?source=rss-1a4bd017d73a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:06:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arkmuntasser/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[Phobia and the Mislabeling of Hate]]></title>
            <link>https://medium.com/@arkmuntasser/phobia-and-the-mislabelling-of-hate-e881dfd40b51?source=rss-1a4bd017d73a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e881dfd40b51</guid>
            <category><![CDATA[islamophobia]]></category>
            <category><![CDATA[bigotry]]></category>
            <category><![CDATA[language]]></category>
            <category><![CDATA[racism]]></category>
            <category><![CDATA[anti-semitism]]></category>
            <dc:creator><![CDATA[Amir R Muntasser]]></dc:creator>
            <pubDate>Sat, 21 Apr 2018 21:00:49 GMT</pubDate>
            <atom:updated>2018-04-21T21:17:50.130Z</atom:updated>
            <content:encoded><![CDATA[<p>This week I read something that stuck with me. It gnawed at me and it took me a long time to figure out exactly why it bothered me. It was a tweet by J.K. Rowling, who has <a href="https://medium.com/@Phaylen/j-k-rowling-the-blatant-transphobia-of-a-beloved-social-justice-hero-a26b67b83be5">grown increasingly problematic</a> lately.</p><p><a href="https://twitter.com/jk_rowling/status/986638227506450432?ref_src=twsrc%5Etfw">https://twitter.com/jk_rowling/status/986638227506450432</a></p><p>“The ‘Arabs are semitic too’ hot takes have arrived.” This was part of a larger conversation she was having with people about anti-semitism and the Jewish people. My problem with her tweet is that it isn’t a “hot take”. Arabs <em>are</em> semitic. I <em>am</em> semitic. I understand the point she was trying to make; though both Arabs and Jews are semitic, the term “anti-semitism” has evolved to be strictly in reference to Jews. And it made me jealous.</p><p>It made me jealous because where is my word for bigotry aimed at me? I don’t have one. I could use “anti-arab,” but that’s not something you really hear anyone say when someone starts spouting some racist nonsense towards Arabs. The only word I get is “islamophobe.” And that doesn’t really work. Not all Arab’s are muslim and most muslims are not Arab. But “islamophobe” gets used interchangeably with the concept of “anti-arab” all the time. Look no further than Trump’s Muslim Ban: it only targeted Arab countries even though most of the world’s muslims come from Indonesia. Because the Arab muslim is the bad muslim.</p><p>So an argument could be made that I have my word. And it applies to me fully as an Arab muslim. But let’s break down the word “islamophobe” and “islamophobia.” We have two parts: Islam, that part is easy, and phobia, or fear. It literally means a fear of Islam and muslims. This doesn’t describe the problem. People don’t fear me. No one is afraid of me. No, they hate me. And by us refusing to acknowledge that fact with our language and intentionally mislabelling it as fear we give these racists and bigots the freedom to continue spreading their bile. Because fear is natural. Everyone has their own fears. And we should never begrudge anyone their fear. The term “islamophobia” implies that it’s okay and that it’s natural when that couldn’t be further from the truth.</p><p>And this isn’t limited to me. “Homophobia” and “transphobia” suffer from the exact same problem. Linguistically, we’ve decided that we, as a English-speaking nations, are not willing to address the hatred individuals in our community spread. And so, I’m jealous. I wish when some politician says something racist and bigoted towards Arabs and muslims that it was met with the same furor in the media as it when something anti-semitic is said. I wish I had a specific label to mark those who would target me and my family that would denote them as the vile people they are. But I don’t. I get told they’re just scared.</p><p>They aren’t afraid of me, they’re assholes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e881dfd40b51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On “Real” Developers]]></title>
            <link>https://medium.com/@arkmuntasser/on-real-developers-bce45aec39c9?source=rss-1a4bd017d73a------2</link>
            <guid isPermaLink="false">https://medium.com/p/bce45aec39c9</guid>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Amir R Muntasser]]></dc:creator>
            <pubDate>Mon, 02 Apr 2018 01:11:47 GMT</pubDate>
            <atom:updated>2018-04-02T01:11:47.137Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*VGj7TMNYJTSQHANGLss7jQ.gif" /></figure><p>Real developers.</p><p>What even is a real developer? It’s a concept I have to battle a lot as a developer myself and as a manager and trainer of other devs. As with everything, there are gatekeepers; people who feel it is their duty to separate the wheat from the chaff based on arbitrary “rules” and the possession of arcane knowledge.</p><p>Allow me to set the record straight. If you code, you’re a real developer. Backend? Real. Frontend? Real. Full-stack? Real. It doesn’t matter; it’s all real and valid.</p><p>This absurd idea that only certain developers (often full-stack) are real developers hinders our ability to grow new people in the field. And it disproportionately impacts women and minority groups! It’s a ridiculous unattainable standard that leaves our juniors unable to recognize their successes and appreciate how far they’ve come from when they started. I have a dev who is always so wrapped up in what she doesn’t know, that she fails to see how much she’s learned even though I rely on her to handle the day-to-day of running the team.</p><p>I see it constantly, online and in real life.</p><p>If you work in software, of any kind, it is your responsibility to push back again this insidious gatekeeping in our field. This industry is best when everyone can participate and learn from on another.</p><p>Let’s keep coding open and accessible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bce45aec39c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Laying Out the Future in CSS Grid]]></title>
            <link>https://medium.com/@arkmuntasser/laying-out-the-future-in-css-grid-97224e4e07ef?source=rss-1a4bd017d73a------2</link>
            <guid isPermaLink="false">https://medium.com/p/97224e4e07ef</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[css-grid]]></category>
            <dc:creator><![CDATA[Amir R Muntasser]]></dc:creator>
            <pubDate>Sun, 11 Feb 2018 20:28:57 GMT</pubDate>
            <atom:updated>2018-02-13T02:18:50.144Z</atom:updated>
            <content:encoded><![CDATA[<p>What if you could write less code, more semantic code, and more refactor-able code with one weird trick?</p><p>Well, there’s no trick, but there is CSS Grid! And while it’s not a trick it is magical in what it empowers us to do.</p><p>Consider this widget.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UNxHl5_hxUI9RInGuiNvLg.png" /><figcaption>Example 1 — <a href="https://glitch.com/edit/#!/ui-playground-grid-demo">https://glitch.com/edit/#!/ui-playground-grid-demo</a></figcaption></figure><p>Nothing special; we’ve seen designs like this countless times on the web. If we look under the hood at the HTML you’ll likely see something this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iwovMrzZGvcIrB0-." /></figure><p>There’s a lot of divs and a lot of classes and underlying all that is a bunch of float-based CSS.</p><p>This works! But it’s messy. It’s complicated. It’s hard to read. And there’s design work baked right into the structure; what if you need to completely restyle this widget?</p><p>HTML should be expressive. You should be able look at the HTML and get an immediate understanding of the type of content you’re dealing with. Not only should you understand, but so should a screen reader. Accessibility is something we should always be thinking about when we build something.</p><p>So how should we restructure this HTML? Well, if we think about it, it’s really just a list. A collection of related content. So let’s shove it in a ul.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vz9G2krA-QlPrFJu." /></figure><p>Doesn’t that look nicer? So much easier to read and the focus is all on the content.</p><p>Now we just need to style it. Designs like this used to be very hard to do and necessitated the use of a framework like Booststrap or Foundation, but now are extremely easy with CSS Grid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*se9ADusYrQP24jkQ." /></figure><p>With just a few lines of CSS we were able to fully recreate the original design. Less, but more expressive HTML. And much less CSS. It’s simple, clean, and easy for anyone to understand and maintain.</p><p>And because we’re not making any design determinations in the HTML, we can restyle it indefinitely!</p><p>With just a couple changes in the CSS we can get this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ql1Qe8Wwxwc6mpNcPb0KZg.png" /><figcaption>Example 2 — <a href="https://glitch.com/edit/#!/ui-playground-grid-demo">https://glitch.com/edit/#!/ui-playground-grid-demo</a></figcaption></figure><p>Or this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ysy7Ooi_8bGrRKKB5kuGsg.png" /><figcaption>Example 3 — <a href="https://glitch.com/edit/#!/ui-playground-grid-demo">https://glitch.com/edit/#!/ui-playground-grid-demo</a></figcaption></figure><p>Or even this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h33rpmG7dEMBq8rCwf5HHw.png" /><figcaption>Example 4 — <a href="https://glitch.com/edit/#!/ui-playground-grid-demo">https://glitch.com/edit/#!/ui-playground-grid-demo</a></figcaption></figure><p>In each case, we never altered the HTML. This is the power of CSS Grid.</p><p>Simpler. Faster. Cleaner. Semantic. Endlessly re-styleable.</p><p>Start using CSS Grid today.</p><p>Play with the code! <a href="https://glitch.com/edit/#!/ui-playground-grid-demo">Remix on Glitch</a>.</p><p>Start using CSS Grid today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97224e4e07ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build a Better Nav with Animation]]></title>
            <link>https://medium.com/@arkmuntasser/build-a-better-nav-with-animation-13bd67994f1b?source=rss-1a4bd017d73a------2</link>
            <guid isPermaLink="false">https://medium.com/p/13bd67994f1b</guid>
            <category><![CDATA[css-animation]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[navigation]]></category>
            <dc:creator><![CDATA[Amir R Muntasser]]></dc:creator>
            <pubDate>Wed, 27 Dec 2017 20:04:09 GMT</pubDate>
            <atom:updated>2018-01-14T10:06:21.819Z</atom:updated>
            <content:encoded><![CDATA[<p>Navs! Websites need them, you have to build them, and typically they blow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sXtjxr9nB1DCwulTRgVSUw.png" /></figure><p>Often, nav looks something like the one below. It’s a simple nav that when you hover over an item a dropdown appears. It works well enough, but the problem comes in when I try to move the mouse in a diagonal to a sub-item on the left or right. This deactivates the hover and makes the dropdown disappear. I am forced to move in rigid straight lines that are completely unnatural.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Farkmuntasser%2Fembed%2Fpreview%2FvpxBJz%3Fheight%3D600%26slug-hash%3DvpxBJz%26default-tabs%3Dcss%2Cresult%26host%3Dhttps%3A%2F%2Fcodepen.io%26embed-version%3D2&amp;url=https%3A%2F%2Fcodepen.io%2Farkmuntasser%2Fpen%2FvpxBJz&amp;image=https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fi.cdpn.io%2F1659874.vpxBJz.small.c7415c56-946d-42d9-ad1a-3c132f12a081.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/438f50b0d9082d3827811b4567c4352b/href">https://medium.com/media/438f50b0d9082d3827811b4567c4352b/href</a></iframe><p>Luckily, this is easily solved. We could use some JS, but I’m personally all about stuntin’ with CSS. We can get the desired effect with just 3 additional CSS rules.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/47b1219e5066dc517b4e6e30612d0797/href">https://medium.com/media/47b1219e5066dc517b4e6e30612d0797/href</a></iframe><p>Why does this work? What I want, really, is a hover-able triangle going from the top corner of the triggering item in the nav to the top corner of the dropdown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IoLADsUWtgVeeUJhmvMctg.png" /></figure><p>But triangles are hard to make a I would definitely need to use JS to give it the right dimensions and place it properly. Instead of a real triangle, we create the effect of a triangle.</p><p>On hover we create a rectangle that fills the main nav area. Once we hover off the trigger item, in this case an a tag, we set a transition and scale the rectangle down to 0. This means that as we move to the left or right the rectangle is getting shorter over time. If we want to stay within the coverable area then we need to move the mouse in a diagonal fashion. This gives us a triangle to move in.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Farkmuntasser%2Fembed%2Fpreview%2FaEJbaM%3Fheight%3D600%26slug-hash%3DaEJbaM%26default-tabs%3Dcss%2Cresult%26host%3Dhttps%3A%2F%2Fcodepen.io%26embed-version%3D2&amp;url=https%3A%2F%2Fcodepen.io%2Farkmuntasser%2Fpen%2FaEJbaM&amp;image=https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fm.cdpn.io%2Fscreenshot-coming-soon-small.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd764024a1d88313502585fc2f68d2cd/href">https://medium.com/media/dd764024a1d88313502585fc2f68d2cd/href</a></iframe><p>This has a number of advantages.</p><p>First, since this is bound by time that means I can simply move my mouse to the right to a sibling nav item and actually interact with that nav item.</p><p>Second, it’s extremely simple to add to nearly any existing nav without much effort.</p><p>Third, there’s no additional JS to load or burden the user with, it’s just 3 more short CSS rules.</p><p>Here’s the final product.</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fcodepen.io%2Farkmuntasser%2Fpen%2FWdpNaZ&amp;src=https%3A%2F%2Fcodepen.io%2Farkmuntasser%2Fembed%2Fpreview%2FWdpNaZ%3Fheight%3D600%26slug-hash%3DWdpNaZ%26default-tabs%3Dcss%2Cresult%26host%3Dhttps%3A%2F%2Fcodepen.io%26embed-version%3D2&amp;type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/927ce9c8852c10d777679fe3b23f0178/href">https://medium.com/media/927ce9c8852c10d777679fe3b23f0178/href</a></iframe><p>A designer at my work challenged me to find a simple solution for this problem. This is not a solution I’ve seen elsewhere. Most other nav solved it having the dropdown work on click rather than hover, they only had top-level nav items, or they had a bunch of nasty looking JS to achieve the same effect.</p><p>I wanted something that was as low impact to the user and developer as possible and I thought it would be fun to solve in pure CSS. You can see this working on a couple of my sites already: <a href="https://www.visitrhodeisland.com/">Visit Rhode Island</a> and <a href="https://www.neworleans.com/">Visit New Orleans</a>.</p><p>If you want to play with solution more, I have them up on Glitch. I have the <a href="https://challenge-nav-css.glitch.me/">“broken” version</a> I use to challenge and train my devs and the <a href="https://challenge-nav-css-key.glitch.me/">“answer key” </a>version as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13bd67994f1b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>