<?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 Misbah Rahman on Medium]]></title>
        <description><![CDATA[Stories by Misbah Rahman on Medium]]></description>
        <link>https://medium.com/@mrahman7749?source=rss-869fc5953b0a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uuc89I2ISAn_y8nf09FdYQ.jpeg</url>
            <title>Stories by Misbah Rahman on Medium</title>
            <link>https://medium.com/@mrahman7749?source=rss-869fc5953b0a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 28 May 2026 21:21:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mrahman7749/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[Ubuntu Screen Share Issue]]></title>
            <link>https://medium.com/@mrahman7749/ubuntu-screen-share-issue-b6e57622873e?source=rss-869fc5953b0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6e57622873e</guid>
            <category><![CDATA[ubuntu]]></category>
            <dc:creator><![CDATA[Misbah Rahman]]></dc:creator>
            <pubDate>Thu, 12 Sep 2024 02:55:04 GMT</pubDate>
            <atom:updated>2024-09-12T02:55:04.389Z</atom:updated>
            <content:encoded><![CDATA[<p>There is a significant issue with Ubuntu 22.04: the migration from the Xorg display server to Wayland has disabled screen sharing across all platforms, including Google Meet, Zoom, Microsoft Teams, and even AnyDesk and TeamViewer.</p><p>One solution that is commonly suggested is to disable Wayland and switch back to Xorg. However, this creates many unexpected and frustrating issues, such as malfunctioning audio drivers, monitor-related problems, and multiple GNOME extensions failing to work — all of which I encountered bit by bit.</p><p>Thankfully, there is a much better solution provided by Marcello Pozzessere in askubuntu.com.</p><p>The steps are as follows:</p><p>1. Install `xdg-desktop-portal-gnome`: This provides the GNOME implementation of xdg-desktop-portal, allowing sandboxed apps to interact with the GNOME desktop environment.<br>2. Install `gnome-remote-desktop`: This adds remote desktop functionality for GNOME, enabling you to share or access your desktop over a network.</p><p>You can install both packages with the following command:</p><pre>sudo apt install xdg-desktop-portal-gnome gnome-remote-desktop</pre><p>This solution worked like a charm for me, without disrupting Wayland or any GNOME extensions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6e57622873e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mercor AI interview Experience]]></title>
            <link>https://medium.com/@mrahman7749/mercor-ai-interview-experience-fa3e067e501c?source=rss-869fc5953b0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa3e067e501c</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[interview-experience]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[spring-boot]]></category>
            <dc:creator><![CDATA[Misbah Rahman]]></dc:creator>
            <pubDate>Mon, 15 Jan 2024 06:51:56 GMT</pubDate>
            <atom:updated>2024-01-15T06:51:56.556Z</atom:updated>
            <content:encoded><![CDATA[<p>So I applied for this company named Mercor for Engineering role, specifically in the backend and Spring Boot domain, and got a pretty awesome feedback from the recruiter (which I later realized was the AI bot itself🥹).It asked me to schedule a 20-minute interview. The email did mention that my interview would be with an AI interviewer from the company.</p><p>During the interview, I realized the interviewer was actually an AI bot and the same name who sent me the mail. Thoroughly reviewing my resume, it grilled me with follow-up questions about one of my backend projects , My previous Job , Internships and even skills mentioned.</p><p>The questions ranged from implementation details to why I chose a specific tech stack, focusing on databases, networking, optimization techniques, Spring Security, and SQL usage. Then, it moved on to concepts from my internships, asking smart follow-up questions. When the 20 minutes were up, the bot thanked me for the interview and signed off.</p><p>The entire process was so well-planned that it covered almost everything on my resume. I am amazed at how much could be asked and understood in a span of 20 minutes about a candidate. I was genuinely impressed by the technical depth of the experience. It was my first encounter with this kind of interview, and I found it fascinating. If this becomes more common, it could revolutionize technical interviewing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa3e067e501c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>