<?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 Nayra Hashem on Medium]]></title>
        <description><![CDATA[Stories by Nayra Hashem on Medium]]></description>
        <link>https://medium.com/@hashem.nayra?source=rss-f310d4bfdc8f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uWZ-irdTVRAXDhJGZHx5YA.jpeg</url>
            <title>Stories by Nayra Hashem on Medium</title>
            <link>https://medium.com/@hashem.nayra?source=rss-f310d4bfdc8f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 07:05:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hashem.nayra/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[Google’s Gemini-4 Family: Hydrogen, Argon, and Carbon. Three Models, Three Different Jobs!]]></title>
            <link>https://medium.com/@hashem.nayra/googles-gemini-4-family-hydrogen-argon-and-carbon-three-models-three-different-jobs-eac361115551?source=rss-f310d4bfdc8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/eac361115551</guid>
            <category><![CDATA[hydrogen]]></category>
            <category><![CDATA[carbon]]></category>
            <category><![CDATA[gemini-4-argon]]></category>
            <category><![CDATA[google-gemini]]></category>
            <category><![CDATA[gemini]]></category>
            <dc:creator><![CDATA[Nayra Hashem]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 16:59:16 GMT</pubDate>
            <atom:updated>2026-11-13T16:59:16.667Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZYcDvCISL_VrUoKGCtqEhA.png" /></figure><p>The future of AI might not be about building one super-intelligent model, but about making different models that works together!</p><p>For a while now, the AI industry has been following a pretty familiar pattern: a company releases a powerful model, everyone gets excited, benchmarks start flying around, and a few months later, an even more powerful model arrives! But Google’s latest Gemini-4 family is telling a different story, instead of focusing on one AI model that do everything, Google has introduced three models with different strengths: <strong>Argon, Carbon, and the newly released Hydrogen</strong>.</p><p><strong>And here’s the interesting part</strong>: <em>Hydrogen</em>, the model that designed for speed and efficiency, actually manages to outperform <em>Argon</em> on one major intelligence benchmark! Wait, what?</p><p>Yes, a faster, more affordable model scoring higher than its more powerful sibling! Let’s explore what’s happening here, and what all of this could mean for us as developers.</p><h3>First, Meet the Gemini 4 Family</h3><p>Let’s check this timeline first:</p><ul><li><strong>September 30, 2026:</strong> Google introduced Gemini-4 Argon, later making it broadly available on October 13.</li><li><strong>October 28, 2026:</strong> Google announced Gemini-4 Carbon, initially focusing on selected cybersecurity defenders.</li><li><strong>November 10, 2026:</strong> Carbon became available to paying developers, enterprises, and eligible subscribers.</li><li><strong>November 12, 2026:</strong> Google introduced Gemini-4 Hydrogen, bringing Gemini-4 capabilities to a much wider audience.</li></ul><p>So, although Carbon was originally the upcoming model everyone was watching, it has now officially arrived! But why do we need three different models?</p><h3>1. Gemini-4 Argon: The Reliable Problem Solver 🧠</h3><p>Gemini-4 Argon actually focuses on complex professional tasks, especially software engineering, knowledge work, and multi-step reasoning, it is designed to reason through larger problems, understand context, and help solve them systematically, Google positions Argon as the practical choice for most serious software engineering and professional knowledge tasks.</p><blockquote><em>Argon is the experienced engineer on your team who can understand the bigger picture.</em></blockquote><h3>2. Gemini-4 Hydrogen: The Fast Developer Who Gets Things Done</h3><p>Now imagine that the architecture is already decided and you have twenty UI components to implement, several functions to test, repetitive code to refactor, and a collection of bugs waiting for attention. Do you really need your most computationally intensive AI model to handle every single task Probably not. This is where Gemini-4 Hydrogen comes in. Released on November 12, Hydrogen is designed for <strong>speed, efficiency, coding, tool usage, and agentic workflows</strong>.</p><p>Hydrogen also offers four thinking levels: low, medium, high, and x-high, this allows developers to adjust how much reasoning effort they want for different tasks.</p><blockquote><em>Hydrogen is the efficient developer who handles everyday implementation work quickly, without needing the whole engineering department involved.</em></blockquote><h3>3. Gemini-4 Carbon: The Deep Thinker</h3><p>Carbon is Google’s most capable Gemini-4 model, developed for problems that require extended reasoning and more complicated workflows. It’s not just intended to answer difficult questions., it’s rather designed to investigate problems through multiple steps, explore possible solutions, and verify its work.</p><blockquote><em>Carbon is the specialist you call when a problem is complicated enough to require deeper investigation, not just a quick answer.</em></blockquote><h3>What If These Models Worked Together?</h3><p>What if instead of choosing one AI model, we could assign different responsibilities to different models? Google is exploring exactly that with <strong>Orchestrator in Google Antigravity</strong>.</p><p>Imagine you’re building a large application, you ask an AI agent to add a new feature, integrate it with your backend, write automated tests, and review the implementation for security issues. Instead of having one expensive model perform everything, the system could distribute the work as:</p><ol><li><strong>Argon</strong> investigates the requirements, plans the architecture, and coordinates the difficult decisions.</li><li><strong>Hydrogen</strong> implements code, executes tests, fixes straightforward issues, and verifies changes.</li><li><strong>Carbon</strong> could be particularly valuable for extended analysis, comparing hypotheses, and reasoning through complex technical evidence.</li></ol><h3>Finally, We Should Stop Asking Which AI Is the Smartest</h3><p>Instead of one incredibly expensive AI trying to solve everything, we may increasingly build software with small teams of specialized AI agents, for developers, this raises an interesting question:</p><p><strong>Will the next essential engineering skill be knowing how to write code with AI — or knowing how to coordinate multiple AI models to build reliable systems?</strong></p><p>What do you think? Would you prefer one powerful AI model for your entire development workflow, or a team of specialized models working together?</p><h3>References</h3><ol><li><a href="https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-4-argon/">Google — Gemini 4 Argon: Our Next Era of Frontier Intelligence</a></li><li><a href="https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-4-carbon-now-available/">Google — Gemini 4 Carbon Is Now Available</a></li><li><a href="https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-hydrogen/">Google — Introducing Gemini 4 Hydrogen</a></li><li><a href="https://deepmind.google/models/model-cards/gemini-4-hydrogen/">Google DeepMind — Gemini 4 Hydrogen Model Card</a></li><li><a href="https://deepmind.google/models/model-cards/gemini-4-carbon/">Google DeepMind — Gemini 4 Carbon Model Card</a></li></ol><p><em>Published: November 2026</em></p><p>#GeminiAI #GoogleDeepMind #ArtificialIntelligence #SoftwareDevelopment #AIModels #starCode ⭐️💙</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eac361115551" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Touch is officially a part of the interaction model | Mac did it!]]></title>
            <link>https://medium.com/@hashem.nayra/touch-is-officially-a-part-of-the-interaction-model-mac-did-it-c2fc98da196e?source=rss-f310d4bfdc8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2fc98da196e</guid>
            <category><![CDATA[desktops-apps]]></category>
            <category><![CDATA[touch]]></category>
            <category><![CDATA[mac]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Nayra Hashem]]></dc:creator>
            <pubDate>Fri, 30 Oct 2026 18:01:46 GMT</pubDate>
            <atom:updated>2026-10-30T18:01:46.385Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G0tsxQi0L0UhXAbHNvr84A.png" /></figure><p>With the new MacBook Pro with Touch, users can scroll, pinch to zoom, drag and drop, interact with windows, draw directly on screen, and use touch alongside the keyboard and trackpad. Apple also says developers can now test touch behavior in their iOS and iPadOS apps directly on the MacBook Pro display.</p><p>But for developers, the BIG question is:</p><p><strong>Does your existing Mac app actually feel good when someone touches it? </strong>Because “it responds to a tap” and “it was designed for touch” are two very different things.</p><h3>1. Stop designing tiny click targets</h3><p>A mouse pointer can accurately hit very small controls, but afinger cannot.</p><p>Buttons, icons, dropdown triggers, close actions, toolbars, and custom controls now need enough physical space to be comfortably tapped, Apple specifically recommends reviewing <strong>touch target sizing and spacing</strong>, while still keeping interfaces efficient for pointer and keyboard users.</p><p>Not because macOS should suddenly look like iPadOS, but because the same interface now needs to work with two very different precision levels:</p><p>🖱 Pointer = high precision<br>👆 Finger = lower precision</p><p>Good UI needs to support both!.</p><h3>2. Hover can no longer be required</h3><p>Desktop interfaces have relied on hover for years, hover to reveal:</p><ul><li>actions, tooltips, edit buttons, previews, menus, contextual controls.</li></ul><p>But a finger does not naturally have the same hover interaction as a mouse pointer. So if an important action appears <strong>only when the user hovers</strong>, developers should reconsider it.</p><p>Apple’s new Touch guidance specifically calls out adapting hover-based interactions for touch. A good rule will be:</p><p><strong>Hover can enhance an experience, but it should not be the only way to discover something important.</strong></p><h3>3. Think in gestures, not only clicks</h3><p>A touch screen introduces interaction patterns such as:</p><ul><li>tap, double tap, pinch, pan, swipe, drag, potentially multi-touch gestures.</li></ul><p>Apple recommends moving custom interaction logic toward modern <strong>gesture recognizers</strong> instead of relying only on older mouse-tracking behavior. That becomes especially useful for apps involving:</p><p>🎨 Design<br>🗺 Maps<br>📊 Data visualization<br>🎵 Music<br>🧊 3D content<br>📷 Photo editing</p><p>Imagine rotating or manipulating a 3D object directly on a Mac display instead of translating every movement through a mouse, that can completely change the interaction model.</p><h3>4. Do not remove keyboard and mouse support</h3><p>This is probably the most important point. Touch does <strong>not</strong> mean developers should redesign Mac apps as oversized iPad apps, Apple is positioning touch as an additional input method working together with the keyboard and trackpad.</p><p>A professional Mac workflow might now look like:</p><p>⌨️ Keyboard shortcuts for speed<br>🖱 Trackpad or mouse for precision<br>👆 Touch for direct manipulation</p><p>The developer’s job is therefore not:</p><blockquote><em>“Convert everything to touch.”</em></blockquote><p>It is:</p><blockquote><strong><em>Make every important workflow work naturally across all available input methods.</em></strong></blockquote><h3>5. Expand the hit area without ruining the design</h3><p>One interesting technique Apple highlights is expanding the <strong>hit target</strong> of an element, the visible icon can remain small and elegant while the invisible touchable area around it becomes larger.</p><h3>7. Be careful with system gestures</h3><p>There is another new problem: Your app’s gesture may conflict with macOS itself. For example, a swipe inside your canvas might mean one thing to your application while macOS interprets it as a system interaction.</p><p>Apple’s updated APIs include ways to manage gesture exclusivity and, in appropriate cases, control system gesture behavior. This means gesture design now needs to consider not only:</p><p><strong>“What does my app want to do?”</strong></p><p>and:</p><p><strong>“What will macOS think the user is trying to do?”</strong></p><h3>8. Test with an actual finger</h3><p>A UI can look perfectly reasonable in Xcode, then you touch it, and suddenly:</p><ul><li>The buttons feel too small.</li><li>Controls are too close together.</li><li>Dragging behaves strangely.</li><li>Scrolling conflicts with another gesture.</li><li>Something that looked obvious with a mouse becomes difficult to discover.</li></ul><p>Apple has already introduced developer resources, videos, Group Labs, and tools specifically for optimizing apps for Touch on Mac, so touch testing should eventually become part of normal Mac QA.</p><p>The interesting part is that Apple did <strong>not</strong> turn macOS into iPadOS. Instead, developers now have another input layer to think about.</p><p>#Apple #macOS #MacBookPro #SoftwareDevelopment #UIDesign #UXDesign #Developer #TouchInterface ⭐️💙</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2fc98da196e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PHP’s Critical Security Incident: What Happened on October 21, 2026, and Why Developers Should Care]]></title>
            <link>https://medium.com/@hashem.nayra/phps-critical-security-incident-what-happened-on-october-21-2026-and-why-developers-should-care-5a7875c88461?source=rss-f310d4bfdc8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a7875c88461</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Nayra Hashem]]></dc:creator>
            <pubDate>Wed, 21 Oct 2026 20:50:30 GMT</pubDate>
            <atom:updated>2026-10-21T20:50:30.837Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*FP0NTo9hyFodwj-R82m70A.jpeg" /></figure><p><strong>Two critical vulnerabilities, a 9.2/10 severity score, and emergency updates. Let’s understand what happened, why it matters, and what we can do to stay safe!</strong></p><p><strong>October 21, 2026 | Cybersecurity • Web Development • PHP</strong></p><p>Imagine spending months building a website, you carefully validate user input, protect your database, hash passwords, and follow security best practices, everything looks secure, right?</p><p>Well, what if the programming language running your website has a vulnerability that allows someone to execute malicious code on your server without even logging in?! ..</p><p>That’s exactly the kind of risk PHP developers and server administrators are facing today ..</p><p>On October 21, 2026, the PHP development team released emergency security updates addressing two critical vulnerabilities:</p><ul><li><strong>CVE-2026–109618</strong></li><li><strong>CVE-2026–109619</strong></li></ul><p>Both carry a severity rating of <strong>9.2 out of 10</strong> under CVSS v4.0.</p><p>Let’s break down what that actually means without making things unnecessarily complicated ..</p><h3>First, what exactly happened?</h3><p>PHP is a server-side programming language powering millions of websites and web applications, including systems built with WordPress, Laravel, and many other technologies. When someone visits a PHP-powered website, the server uses PHP to process requests, communicate with databases, and generate responses ..</p><p>Under normal circumstances, that process should be controlled and secure. However, security researchers discovered two vulnerabilities in PHP’s internal handling of memory and requests! ..</p><p>Those vulnerabilities could potentially allow an attacker to execute unauthorized code on an affected server, even without a valid username or password. This type of security issue is known as <strong>Remote Code Execution (RCE)</strong>. And it’s one of the more dangerous categories of software vulnerabilities! ..</p><h3>What is Remote Code Execution? A simple example</h3><p>Imagine your website is a restaurant, customers can place orders, ask about the menu, and pay their bills, but they’re not allowed inside the kitchen to control how everything operates ..</p><p>Now imagine someone discovers a hidden flaw that lets a customer send a special request and trick the restaurant’s internal systems into following unauthorized instructions ..</p><p>That’s roughly what an RCE vulnerability can enable. In a website, an attacker might be able to:</p><ul><li>Access sensitive files or information available to the PHP process ..</li><li>Steal application secrets or database credentials ..</li><li>Modify website content or data ..</li><li>Install malicious scripts or backdoors ..</li><li>Disrupt services or make the website unavailable ..</li></ul><p>The exact damage depends on the server’s permissions and configuration! ..</p><p><strong>Important:</strong> An RCE vulnerability doesn’t automatically mean the attacker gains complete administrator access. Their initial access generally operates with the privileges of the affected PHP worker. Still, that’s dangerous enough to take seriously ..</p><h3>So, why did this happen?</h3><p>The problem isn’t necessarily in a website’s PHP code, it’s inside PHP’s own internal engine. Both vulnerabilities involve problems with <strong>memory management</strong>, particularly how PHP handles unexpected failures and information retained between requests ..</p><h3>1. CVE-2026–109618: When PHP runs out of memory</h3><p>Computers use memory to store temporary information while programs run. PHP has mechanisms for handling situations where it cannot allocate the memory it needs, normally, the program should stop the affected operation and clean up safely. But researchers found that, under certain conditions, PHP’s out-of-memory handling could interrupt an operation before its internal data had been properly initialized ..</p><p>The cleanup process could then treat invalid memory as if it were legitimate. Think of someone assembling a machine, stopping halfway through, and leaving a maintenance system to operate on parts that were never installed correctly, with carefully constructed requests, an attacker could exploit this mistake to achieve remote code execution ..</p><h3>2. CVE-2026–109619: When old memory is used again</h3><p>This vulnerability involves a problem known as <strong>Use-After-Free </strong>..</p><p>Imagine a hotel room, aguest checks out, but the receptionist accidentally keeps an old room reference in the system. Later, when another guest arrives, the system uses that outdated reference as though it were still valid. Something similar can happen inside PHP.</p><p>A PHP worker may retain references to information belonging to an earlier request even after that information’s memory has been released, a later request can interact with that outdated state before PHP properly resets it ..</p><p>Under the right conditions, an attacker can manipulate this behavior and execute unauthorized code.</p><h3>Why is this incident particularly serious?</h3><p><strong>First: Attackers may not need to log in</strong></p><p>Both vulnerabilities can lead to unauthenticated remote code execution. A successful attack may not require stolen credentials or an existing account ..</p><p><strong>Second: The issue affects PHP itself</strong></p><p>This isn’t simply a vulnerability in one WordPress plugin or one Laravel application. The vulnerable component sits beneath those applications ..</p><p>In fact, researchers demonstrated an attack against Apache’s mod_php integration that could be triggered before the application&#39;s PHP code even began running. That means writing secure application code alone cannot fix the underlying issue! ..</p><p><strong>Third: PHP is widely used</strong></p><p>A vulnerability in a popular runtime can potentially affect many different websites, organizations, and hosting environments. However, exposure isn’t the same as compromise ..</p><p><strong>Not every PHP website has been hacked, and not every configuration is equally exploitable.</strong> The vulnerability’s practical impact depends on the affected version, runtime configuration, and available attack conditions ..</p><h3>Which PHP versions need updating?</h3><p>The PHP project released the following security updates on October 21, 2026:</p><p>PHP Update:</p><p>PHP 8.5: <strong>8.5.12</strong></p><p>PHP 8.4: <strong>8.4.27</strong></p><p>PHP 8.3: <strong>8.3.36</strong></p><p>PHP 8.2: <strong>8.2.35</strong></p><p>Earlier versions within these branches are vulnerable. PHP 8.1 and older branches are no longer supported by the PHP project and did not receive new official patches. Administrators using them should migrate to a supported release or obtain an appropriate vendor-supported security backport ..</p><p>Also worth knowing: PHP 8.2 reaches its official end of life on December 31, 2026.</p><h3>How can we protect our websites?</h3><h3>1. Update your PHP runtime immediately</h3><p>The primary solution is to install the patched PHP release for your supported branch. If you manage your own server, update the actual PHP packages and restart or recycle the affected PHP workers so that the fixed code is running ..</p><p>If you’re using shared hosting, check your hosting control panel or contact your provider. Don’t assume the update happened automatically! ..</p><h3>2. Check which PHP version your server uses</h3><p>If you have terminal access, you can start with:</p><pre>php -v</pre><p>But here’s a small detail developers sometimes forget:</p><p>The PHP version in your terminal isn’t necessarily the same PHP version your website uses. Your server might run a different PHP-FPM pool, Apache module, or container. Make sure you’re checking the version serving real web requests ..</p><p>WordPress administrators can find their PHP version under:</p><p><strong>Tools → Site Health → Info → Server</strong></p><h3>3. Don’t confuse updating your framework with updating PHP</h3><p>Updating Laravel, WordPress, or your website’s plugins is good security hygiene. But it doesn’t replace the PHP runtime security update, the issue is in the underlying PHP engine. You need to update that component! ..</p><h3>4. Use additional security controls</h3><p>A Web Application Firewall (WAF), intrusion detection, input size restrictions, and network-level protections can help reduce exposure ..</p><p>But there’s an important warning here:</p><p><strong>The PHP project says there is no complete configuration-based mitigation for these vulnerabilities.</strong></p><p>A firewall or configuration change should not be treated as a guaranteed replacement for updating PHP. If a high-risk public service cannot be patched promptly, consider temporarily restricting access or taking it offline until reliable remediation is available.</p><h3>5. Follow the principle of least privilege</h3><p>Your PHP process should only have access to the files, databases, and system resources it actually needs ..</p><p>Why? Because even if an attacker manages to exploit a vulnerability, limited permissions can reduce how much damage they can cause. Use separate application credentials, restrict file-writing permissions, and avoid running PHP workers with unnecessary privileges ..</p><h3>6. Monitor your servers for suspicious activity</h3><p>Patching closes the vulnerability, but it doesn’t automatically remove malware if a server was already compromised. Review relevant logs, unexpected file modifications, new administrator accounts, unfamiliar processes, and abnormal network activity. If compromise is suspected, isolate the affected systems where possible, preserve evidence, and follow an incident-response process ..</p><h3>Could developers have prevented the vulnerabilities?</h3><p>Most developers could not have prevented these specific flaws simply by writing better Laravel or PHP application code. The bugs originated in PHP’s internal implementation. However, software teams can reduce their exposure to vulnerabilities like these by:</p><ul><li>Keeping runtimes, frameworks, and dependencies updated ..</li><li>Testing new security releases before and during deployment ..</li><li>Using supported software versions ..</li><li>Applying least-privilege access controls ..</li><li>Maintaining reliable backups and a recovery plan ..</li><li>Monitoring official security advisories ..</li><li>Treating the entire software stack as part of their security responsibility ..</li></ul><p>Security isn’t only about preventing SQL injection, XSS, or weak authentication. It also means understanding and protecting the technologies your application depends on ..</p><h3>Final thoughts: Your code isn’t the whole application</h3><p>One thing was interesting about this incident, is how it reminds us of the layers behind every website. You may write secure PHP code, carefully configure your authentication, and protect your database, but your application still depends on a programming-language runtime, a web server, an operating system, libraries, and third-party components ..</p><p>A security weakness in any one of these layers can affect the entire system. The October 21 PHP incident is a clear example ..</p><p>So, remember:</p><blockquote>Security doesn’t end when our code works correctly. It extends to everything that makes our code run ..</blockquote><p>So, if you manage a PHP-powered website, check your PHP version today. Sometimes, one small version update is the difference between a vulnerability being exploitable and being fixed ..</p><p>Stay curious, keep learning, and be secure! 💙</p><h3>References</h3><ul><li><a href="https://www.php.net/">PHP official security announcements</a></li><li><a href="https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w">PHP Security Advisory — CVE-2026–109618</a></li><li><a href="https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp">PHP Security Advisory — CVE-2026–109619</a></li><li><a href="https://wordpress.org/news/2026/10/critical-php-security-release/">WordPress official security notice</a></li></ul><p><em>#PHP #Cybersecurity #WebDevelopment #SoftwareSecurity #ApplicationSecurity #SecurityUpdates #starCode #nayra_hashem</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a7875c88461" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Face ID or Fingerprint? How Security Teams Decide What to Trust]]></title>
            <link>https://medium.com/@hashem.nayra/face-id-or-fingerprint-how-security-teams-decide-what-to-trust-de6761617804?source=rss-f310d4bfdc8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/de6761617804</guid>
            <category><![CDATA[face-id]]></category>
            <category><![CDATA[andorid]]></category>
            <category><![CDATA[starcodes]]></category>
            <category><![CDATA[mobile-security]]></category>
            <category><![CDATA[iphone]]></category>
            <dc:creator><![CDATA[Nayra Hashem]]></dc:creator>
            <pubDate>Fri, 09 Oct 2026 18:53:49 GMT</pubDate>
            <atom:updated>2026-10-09T18:53:49.011Z</atom:updated>
            <content:encoded><![CDATA[<p>When we talk about mobile security, we often ask which is more secure?<strong> Face ID or fingerprint authentication?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*977ijAQxqjg8UuOI9ecoAA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@marcohaenssgen?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">https://unsplash.com/@marcohaenssgen</a> Marco J Haenssgen on Unsplash</figcaption></figure><h3>But security teams usually ask a very different question</h3><p><strong>What authentication system gives us the right balance of security, usability, hardware capability, privacy, and resistance to attack?</strong></p><p>As we may notice, Apple chose to make Face ID the primary biometric system on most modern iPhones, while many Android devices continue to rely on fingerprint authentication, and even sometimes alongside facial recognition! ..</p><p>At first glance, that may look like two companies disagreeing about which biometric is safer, but it is actually more complicated. Let’s breaks this down ..</p><h3>First: Android does not have one biometric strategy</h3><p>One important distinction is that Apple and Android are not equivalent ecosystems, Apple controls the operating system, processor, biometric hardware, secure hardware, and device design of the iPhone. Android, on the other hand, runs across devices produced by many manufacturers, meaing, they are not only having Andorid for only one type of mobile phones ..</p><p>Android currently defines biometric authenticators using categories including <strong>Class 3 (Strong), and Class 2 (Weak),</strong> knowing that applications can even request a particular strength through Android’s BiometricPrompt APIs ..</p><p>And this is a very important security-engineering idea, that Android is interested not only in what biometric you use, but in how securely that biometric is implemented, that:</p><p>A fingerprint system can be strong, and on the other side, a facial recognition system can be strong too ..</p><p>And either one of them can also be poorly used in the system! ..</p><p>Google describes two major considerations when evaluating biometrics: the security of the biometric architecture itself and its resistance to spoofing attacks.</p><h3>Second: Apple’s approach controls the entire authentication chain</h3><p>Apple approaches the same problem from a different position, because Apple controls both the hardware and software of the iPhone, it can design an authentication system as one integrated security architecture, meaning, Face ID does not simply take a normal selfie and compare it with another photo! Apple’s TrueDepth system projects and analyzes thousands of infrared points to construct depth information about the face. Then the resulting mathematical representation is processed and protected by the <a href="https://support.apple.com/guide/security/the-secure-enclave-sec59b0b31ff/web">Secure Enclave</a>. Apple also uses anti-spoofing mechanisms designed to resist attempts involving photographs or masks ..</p><p>Apple says that, for Face ID with a single enrolled appearance, the probability of a random person being accepted is less than <strong>1 in 1,000,000</strong>. And for Apple’s Touch ID, the corresponding figure published by Apple is approximately <strong>1 in 50,000</strong> for one enrolled fingerprint ..</p><p>But that does not automatically mean face recognition is always twenty times more secure than fingerprint recognition, those numbers describe Apple’s particular implementations under Apple’s stated conditions! ..</p><h3>Then why do many Android phones still use fingerprints?</h3><p>Because fingerprint authentication has some very attractive properties, it can be fast, inexpensive to integrate, familiar to users, and practical in many environments, and it also does not require a complex 3D facial-sensing array ..</p><p>Google’s Pixel devices, for example, support fingerprint authentication, and newer Pixel devices can also support Face Unlock. Google stores biometric information locally and protects fingerprint processing within secure hardware environments rather than sending fingerprint information to Google or applications ..</p><h3>THEN THE REAL QUESTIONS ARE</h3><p>What security architecture do we have?</p><p>How much battery will the authentication system consume?</p><p>How much space will its sensors require?</p><p>Will it work in darkness?</p><p>Will it work when someone is wearing gloves?</p><p>Will it work when the user is wearing a facial mask?</p><p>How expensive is the sensor?</p><p>Can it fit inside hundreds of different phone designs?</p><h3>Apple’s question may be different from Google’s</h3><p>Apple may ask this question: <strong>We control the device, then what biometric architecture do we want this device to have?</strong></p><p>And Android will ask something closer to: <strong>How do we create security requirements that can work across many hardware manufacturers?</strong></p><h3>But CAUTION, your biometric is not actually your password!</h3><p>Neither Apple nor Android treats biometrics exactly like an ordinary password, because:</p><ul><li>Your password is something you know ..</li><li>Your phone is something you have ..</li><li>Your fingerprint or face is something you are ..</li></ul><p><a href="https://www.nist.gov/">NIST</a> explicitly notes that biometric characteristics are <strong>not secrets,</strong> faces can be photographed, fingerprints can be left on surfaces. Android describes biometrics as a secondary authentication tier, while the user’s PIN, pattern, or password remains primary authentication, and Apple follows a similar principle, that Face ID and Touch ID improve convenient access, but they do not eliminate the device passcode ..</p><h3>Convenience is part of security</h3><p>Shouldn’t security teams simply choose the strictest possible authentication system? Not necessarily! ..</p><p>Imagine a phone that required a 30-character password every time you opened WhatsApp, technically, that might increase authentication friction, but in reality, users would probably find ways around it, like:</p><ul><li>They might choose weaker passwords ..</li><li>They might disable protections ..</li><li>Or they might avoid locking the device frequently ..</li></ul><p>Security engineers therefore care about something called <strong>usable security</strong>. Apple itself explains biometrics partly in these terms: users may access their devices more than one hundred times per day, so biometric authentication makes strong device protection practical without requiring the password every time ..</p><p>That’s why, a good security engineer will ask:</p><blockquote>What security will people actually use?</blockquote><p>And not only:</p><blockquote>What is theoretically strongest?</blockquote><h3>Security standards define outcomes, not always technologies</h3><p>This is one of my favorite lessons from this comparison, standards organizations often avoid saying: <strong><em>You must use fingerprint authentication</em></strong><em>, </em>or<em> </em><strong><em>You must use facial recognition</em></strong><em>, i</em>nstead, they define measurable security properties. For example, NIST’s current digital identity guidance specifies requirements around biometric false-match rates and presentation-attack detection. For facial recognition, presentation-attack detection is explicitly required in the relevant authentication guidance ..</p><h3>So ASKING now: Apple or Android approach?</h3><p>But this is probably the wrong question to be asked! Apple and Android are solving slightly different engineering problems, Apple operates a tightly controlled hardware and software ecosystem, and that allows the company to build specialized hardware such as <a href="https://apple.fandom.com/wiki/TrueDepth">TrueDepth</a> and integrate it directly with the Secure Enclave and operating system.</p><p>While Android operates a much more diverse ecosystem, its security framework therefore needs to support fingerprints, or faces while evaluating them according to their actual security strength.</p><h3><strong>So the real ANSWER is</strong></h3><p>Security decisions are made by examining the entire system:</p><ul><li>The hardware ..</li><li>The operating system ..</li><li>The attacker possible methods ..</li><li>The user ..</li><li>And the cost of failure ..</li></ul><p>And that is where security engineering becomes much more interesting than a settings screen! ..</p><p>#flutterPavilion #state02 #starCode #hashem_nayra 💙✨</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de6761617804" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Malicious Flutter Package while it have a Clean Code?]]></title>
            <link>https://medium.com/@hashem.nayra/malicious-flutter-package-while-it-have-a-clean-code-90e4ee9f2b99?source=rss-f310d4bfdc8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/90e4ee9f2b99</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[dart]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[malware]]></category>
            <dc:creator><![CDATA[Nayra Hashem]]></dc:creator>
            <pubDate>Fri, 02 Oct 2026 12:15:11 GMT</pubDate>
            <atom:updated>2026-10-02T12:15:11.490Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Flutter Pavilion — State 01 🦋</strong></p><p>When Flutter developers choose a new package, we usually ask familiar questions:</p><ul><li>Does it have good pub points?</li><li>Is it actively maintained?</li><li>How many downloads does it have?</li><li>Does the source code look reasonable?</li></ul><p>Those are good questions, but a security incident discovered in September 2026 added another question in mind:</p><p><strong>What else is actually inside this package?</strong></p><p>On September 8, 2026, Aikido Security reported finding a variant of <strong>XCSSET malware</strong> inside version 0.1.5 of the Flutter package universal_file_viewer on pub.dev, while at the time of reporting, the package already had <strong>500 downloads </strong>..</p><p>What makes this case particularly interesting is that the package’s main Dart library was apparently <strong>not malicious at all! </strong>..</p><h3>A Clean lib/ Directory Wasn&#39;t Enough</h3><p>According to Aikido’s analysis report, the Dart code inside: lib/ was clean, the infected files were instead in:example/</p><p>When developers add a Flutter package normally through pubspec.yaml, the example project is not compiled as part of their application, so simply writing:universal_file_viewer: ^0.1.5and running a normal Flutter build did <strong>not</strong> automatically trigger the malware! ..</p><blockquote>The dangerous scenario was different this time!</blockquote><p>A developer had to clone the repository and explicitly build the included example application locally for the malicious code to be activated ..</p><h3>So, What Was XCSSET Doing There?</h3><p>XCSSET is a macOS-focused malware family known for targeting software developers and, specially, <strong>Xcode projects </strong>..</p><p>Microsoft has documented XCSSET variants that infect Xcode projects and execute malicious code when developers build those projects. The malware has also evolved with techniques for persistence, obfuscation, data theft, and propagation between development projects <em>[Read the full technical analysis in the </em><a href="https://www.microsoft.com/en-us/security/blog/2025/03/11/new-xcsset-malware-adds-new-obfuscation-persistence-techniques-to-infect-xcode-projects/"><em>Microsoft Security Blog on XCSSET</em></a><em>]</em> ..</p><p>In the Flutter package investigated by Aikido, several development configurations inside the example project had been modified, with Aikido reporting infections involving:example/android/app/build.gradle.ktsas well as the example application’s iOS and macOS Xcode project configurations ..</p><p>For instance, Flutter may gave us a single cross-platform development experience, but inside a Flutter application we still have native ecosystems:</p><p><strong>Android + iOS + macOS + Xcode + Git .. and more</strong></p><h3>It Wasn’t Necessarily a Malicious Package Author</h3><p>There is another important part of this story. According to Aikido’s investigation, this was not believed to be a case where someone deliberately created a malicious Flutter package and uploaded it to pub.dev. Instead, the maintainer’s development machine was reportedly already infected with XCSSET.</p><p>The malware then modified development files on that machine, that when a new version of the package was published, those infected files were packaged and distributed with that new version ..</p><h3>Build Systems Are Code Too</h3><blockquote><em>Anything capable of executing instructions deserves security attention, regardless of whether the filename ends in </em><em>.dart..</em></blockquote><p>Our machines often contain many repositories, credentials, package-manager tokens, Git access, signing configurations, API keys, and development tools, meaning that a compromised developer environment can therefore be extremely valuable to an attacker ..</p><h3>What Should Flutter Developers Do?</h3><p>This incident doesn’t mean developers should stop using packages, Flutter’s package ecosystem is one of the reasons we can build applications so efficiently ..</p><p>The better lesson is to become a little more intentional about what we bring into our projects, before adopting an unfamiliar package, take a few minutes to inspect more than its README file, look at the repository structure, check recent releases, look at the publisher, inspect unusual native files, pay attention to unexpected build scripts or hooks, and check what changed between versions ..</p><h3>What Happened to the Package?</h3><p>The current pub.dev listing shows versions 0.1.5 and 0.1.6 as<strong> retracted</strong>, for more information check here [<a href="https://pub.dev/packages/universal_file_viewer/versions">pub.dev universal_file_viewer Versions Page</a>] ..</p><p>On version 0.1.7 lists a security update stating that unauthorized Xcode build rules and script phases were removed from the example iOS and macOS project configurations ..</p><blockquote>Trust is useful, but verification is better .. 🦋</blockquote><p><strong>This is my Flutter Pavilion 🦋: </strong>A small series exploring Flutter, Dart, development practices, and the cybersecurity lessons that matters ..</p><p>#Flutter #Dart #CyberSecurity #AppSecurity #OpenSourceSecurity</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90e4ee9f2b99" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Code Is Not Just Your Code: Understanding Software Supply Chain Security]]></title>
            <link>https://medium.com/@hashem.nayra/your-code-is-not-just-your-code-understanding-software-supply-chain-security-1915b2baa291?source=rss-f310d4bfdc8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1915b2baa291</guid>
            <category><![CDATA[software-security]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-supply-chain]]></category>
            <dc:creator><![CDATA[Nayra Hashem]]></dc:creator>
            <pubDate>Fri, 18 Sep 2026 18:37:29 GMT</pubDate>
            <atom:updated>2026-09-18T18:37:29.471Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Photo by: hazwan-kosni-zueads from -unsplash" src="https://cdn-images-1.medium.com/max/1024/1*SWEMjGDfIY-ELYtOAN_4fQ.jpeg" /><figcaption>An Example of Supply Chain Security (a metal rope with locks on it)</figcaption></figure><p>In every day development process, almost all developers uses flutter pub get, npm install, pip install or any other package installing methods to add external open-source code to our project, but that added package introduces a code that we probably didn’t write, right?</p><p>The question is: how much do we <em>trust</em> it?</p><p>Modern software development is built on reuse, meaning, when we need authentication, networking, date formatting, state management, encryption, logging, or almost anything else, we rarely implement everything from scratch, instead, we install a package to do the work for us, so we don’t re-invent the wheel! ..</p><p>Open-source ecosystems have made development faster, more accessible, and more collaborative than ever, but there is another side of this story:</p><h3><strong>Every dependency we add, becomes a part of our software supply chain!</strong></h3><p>And sometimes, the weakest part of an application is not the code we wrote, it is the code we trusted! ..</p><h3>So, What Is a Software Supply Chain (SSC)?</h3><p>To make this easier to understand, think of it as a physical product, when a company manufacture a laptop, it doesn’t manufacture every screw, chip, battery, and cable itself, instead, it relies on suppliers that already built this ..</p><p>Software works in a similar way, a modern application may depend on only 20 packages, but those 20 packages may also depend on another 100 packages, which depend on hundreds more … and so on ..</p><p>This dependency tree is our <strong>software supply chain ..</strong></p><p>In other words:</p><blockquote><em>We do not only trust the package we install, we also trust everything it depends on! ..</em></blockquote><h3>The Problem is not About the Open Source!</h3><p>The security problem comes from <strong>implicit trust at scale</strong>, developers routinely run commands like:</p><pre>npm install package-name</pre><p>Within seconds, code written by someone we may never met can become a part of our application, and depending on the ecosystem, code associated with installation may even execute on a developer’s machine! ..</p><p>Usually, everything works exactly as expected, but attackers only need the package to be installed for their malicious code to run in the background! ..</p><h3>Sometimes the Package Name Is the Attack</h3><p>Attackers do not always need advanced malware, sometimes they simply need a developer to mistype a bengin package name ..</p><p>Imagine a legitimate package called:</p><pre>request</pre><p>An attacker might publish something with a deceptively similar name, this technique is commonly known as <strong>typosquatting </strong>..</p><p>A developer who installs the wrong package may unknowingly execute malicious code, what makes these attacks particularly interesting is that the malicious behavior can enter a project through perfectly normal developer workflows, there does not need to be a suspicious .exe..</p><h3>Then, What Developers Can Do Today</h3><p>A developer do not need to become a malware researcher before installing a package, but a few habits can simply improve their security posture:</p><h3>1. Know What You Are Installing</h3><p>Before adding a package, look at its:</p><ul><li>publisher,</li><li>repository,</li><li>maintenance activity,</li><li>release history,</li><li>documentation,</li><li>dependency count,</li><li>and community adoption ..</li></ul><h3>2. Check the Name Twice</h3><p>Especially when copying package names manually, one character can be the difference between the project you wanted and something pretending to be it ..</p><h3>3. Remove Packages You Do Not Use</h3><p>Every package has a maintenance cost, and every package potentially increases attack surface. Do you really need a third-party package for something you could safely implement in five lines?</p><p>Sometimes yes. Sometimes absolutely not. So only use packages when it’s needed to ..</p><h3>4. Update Carefully</h3><p>“Never update” is not a security strategy, neither is “automatically trust every update.” Updates may contain important security patches, but package changes should still be reviewed and tested ..</p><h3>The Biggest Lesson: Trust, but Verify</h3><p>Software development has changed, twenty years ago, security discussions often concentrated mainly on the code developers wrote themselves, but today, an application may contain far more third-party code than our normal code ..</p><p>So that changes the question of:</p><blockquote><em>“Is my code secure?”</em></blockquote><p>to:</p><blockquote><em>“Where did all the other code came from?”</em></blockquote><blockquote><em>“Who can change it?” and “What happens when it is updated?”</em></blockquote><p>So the next time we develop any software, we need to make sure our code and “the others code” is safe too! ..</p><p>Happy and Safe coding to you all ..</p><p>💙</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1915b2baa291" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevFest Around the World: Why Every Developer Should Experience It at Least Once]]></title>
            <link>https://medium.com/@hashem.nayra/devfest-around-the-world-why-every-developer-should-experience-it-at-least-once-268c6f9edb34?source=rss-f310d4bfdc8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/268c6f9edb34</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[devfest]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[gdg]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Nayra Hashem]]></dc:creator>
            <pubDate>Fri, 11 Sep 2026 17:38:30 GMT</pubDate>
            <atom:updated>2026-09-11T17:48:18.048Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="devfest-2022-gdg-aden" src="https://cdn-images-1.medium.com/max/1024/1*ILZtPFOtdJy8W1Ew--SBgQ.jpeg" /><figcaption>DevFest 2022 GDG Aden</figcaption></figure><p>You are a developer? Then you do:</p><ul><li>Read documentation ..</li><li>Open another 17 tabs ..</li><li>Wondering about your career ..</li><li>Finally fixed a bug ..</li><li>And vibe-coding sometimes 😁</li></ul><p>That is just a part of being a developer!</p><blockquote>But there is another side of being a developer that we sometimes forget about: <strong><em>getting out from behind the screen and becoming part of the developer community!</em></strong></blockquote><p>And one of the most amazing opportunities to do so, is <strong>DevFest</strong></p><h3>So .. what exactly a DevFest?</h3><p>DevFest is a global series of community-driven technology conferences organized by <strong>Google Developer Groups (GDGs)</strong> around the world.</p><h3>BUT</h3><h4>There isn’t just <em>one</em> DevFest!</h4><p>You can find DevFest events happening in different cities, countries, languages, and communities around the world!</p><p>For this year 2026, the official DevFest season will be from <strong>October 1 to December 31</strong>, with happening in around <strong>115 countries, 500 cities, and 700 events.</strong></p><p>A DevFest in Cairo may have a different atmosphere from one in Aden, London, Berlin, Bangalore, and so on ..</p><p>The speakers change, topics vary, sizes not the same, even the languages ..</p><p>But the idea remains the same:</p><p><strong>Learn. Build. Grow.</strong></p><p>Each event is independently organized by its local GDG community, which means the content can reflect what developers in that particular community actually care about.</p><p>Check the community near you, here: <a href="https://gdg.community.dev/">https://gdg.community.dev/</a></p><h3>It is not just another “talking” conference</h3><p>When people hear “tech conference,” they sometimes imagine sitting in a chair for eight hours while someone changes PowerPoint slides</p><p>DevFest is much more than that, you may find technical talks, panel discussions, Q&amp;A sessions, coding workshops, project showcases, mentorship sessions, debugging activities, codelabs, and full hands-on workshops!</p><p>Topics can include things such as:</p><ul><li>AI and machine learning</li><li>Google Cloud</li><li>Android development</li><li>Flutter</li><li>Firebase</li><li>Web development</li><li>Application security</li></ul><p>.. And more</p><p>DevFest is also designed for students, beginners, experienced developers, AI builders, designers, product people, and technology enthusiasts</p><p>So if you’re thinking:</p><p><em>“I’m still learning. Maybe I’m not ready for something like this.”</em></p><p>Check belw, and read what actually you can gain from attending?</p><h3>1. Learning things outside the box</h3><p>As developers, we naturally build our own little technology box, a Flutter developer follows Flutter news, a cybersecurity person follows security news, and a web developer watches JavaScript frameworks every three weeks 😅</p><p>At an event like DevFest, suddenly you are exposed to things you wouldn’t normally search for, you might attend a session about AI agents and discover an idea you can integrate into your mobile application ..</p><p>Also You might see a Firebase feature that saves you hours on your next project, or you might hear an engineer explain how they solved a scalability problem that looks similar to the one your team is struggling with .. !</p><h3>2. Meeting developers outside your LinkedIn feed</h3><p>This might actually be the biggest benefit 🛎</p><p>We spend a lot of time talking about <strong>networking</strong>, but sometimes networking sounds like:</p><p><em>“Hello, here is my business card. Please increase my career opportunities.”</em></p><p>That’s not really the point, good networking starts much more naturally. Imagine the scenario below:</p><blockquote>You sit next to someone before a session, you talk about the technology they use, then you discover they are building an interesting project, someone asks about your project, and you exchange LinkedIn or GitHub profiles. After three months, that person sends you a conference opportunity, recommends a tool, invites you to contribute to a project, or even tells you about a job .. !</blockquote><p>Google itself describes the wider GDG community in three ideas:</p><p><strong>Learn, Connect, and Grow</strong>.</p><h3>3. Finally LinkedIn connections are real people!</h3><p>You know that developer whose posts you’ve been seeing for the last year Imagine suddenly meeting them at DevFest!</p><blockquote>“Wait .. you’re the person whose Flutter posts I keep saving!”</blockquote><p>And once you’ve spoken to someone face-to-face, your future interactions online feel completely different.</p><h3>4. You get ideas for your own projects</h3><p>One of my favorite parts of developer events is seeing what other people are building, not just huge products, sometimes a small demo can trigger a big idea.</p><p>You see someone combine AI with an ordinary application, someone else builds something useful for their local community, and another developer shows an automation you could adapt for your workplace.</p><p>You go home thinking:</p><blockquote>“Hmm… I could build something like that.”</blockquote><p>And suddenly your GitHub has a new repository.</p><h3>5. You can be the next speaker</h3><p>This is something developers often underestimate.</p><p>Your first DevFest might look like this:</p><p><strong>Year 1:</strong> You attend.</p><p><strong>Year 2:</strong> You volunteer.</p><p><strong>Year 3:</strong> You give a lightning talk.</p><p>And eventually:</p><p><strong>You become one of the people teaching others !</strong></p><p>You don’t need to invent a new programming language to have something worth sharing, maybe you solved a difficult Flutter architecture problem, or you learned how to secure an API properly.</p><p>That can be a talk, the official DevFest guidance even encourages developers interested in speaking to contact their local GDG chapter about opportunities !</p><h3>And yes, DevFest really is global</h3><p>Google’s DevFest 2025 recap reported <strong>790 DevFest events across 114 countries</strong>, reaching more than <strong>635,000 people</strong>,<strong> </strong>also it reported that <strong>95% of attendees would recommend DevFest</strong>, while <strong>88.6% planned to implement something they learned there</strong>.</p><p>Developers aren’t attending only for stickers and free coffee, although, to be fair, developers do have a mysterious weakness for tech stickers ! 😄</p><p>But people attend because community events can genuinely change how they learn and grow 💙</p><h3>How to get the most from your first DevFest</h3><p>When attending, give yourself a small mission: Meet three new developers, and ask a speaker one or two questions, or attend one session outside your main specialization, and maybe you can show someone your project !</p><p>More intersting thing to do are: Connecting with people on LinkedIn, and following one interesting person or project on GitHub !</p><p>And Don’t Forget:</p><h3><strong>TALK TO PEOPLE</strong></h3><p>The presentation you watch might teach you something useful for a week, and the person sitting beside you might become part of your professional network for years !</p><h3>And finally, remember</h3><p>Your career is not just coding, it is also shaped by:</p><p><strong>The people you meet,<br>The ideas you’re exposed to,<br>The projects you build,<br>and the communities you are a part of !</strong></p><p>DevFest brings all four together.</p><p>So if there is a DevFest happening near you this year, do the following:</p><p>Pack your laptop,</p><p>Charge your phone,</p><p>Update your LinkedIn profile,</p><p>Maybe clean your GitHub profile a little, 👀</p><p>And go meet your developer community !</p><p>You never know what one day at DevFest might start 💙</p><p>#DevFest #GDG #GoogleDevelopers #DeveloperCommunity #starCode #nayChan #flutter #dart #build_learn ⭐️💙</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=268c6f9edb34" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello Folks! Flutter 3.35 and Dart 3.9 will boost your coding journy ]]></title>
            <link>https://medium.com/@hashem.nayra/hello-folks-flutter-3-35-and-dart-3-9-will-boost-your-coding-journy-c724ec793458?source=rss-f310d4bfdc8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c724ec793458</guid>
            <dc:creator><![CDATA[Nayra Hashem]]></dc:creator>
            <pubDate>Fri, 15 Aug 2025 12:07:13 GMT</pubDate>
            <atom:updated>2025-08-15T12:25:20.552Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello Folks! Flutter 3.35 and Dart 3.9 will boost your coding journy 🎉</p><h3>AMAZING UPDATES</h3><p>Let’s dive into the updates:</p><h4>1# 🔥 Blazing Fast Web Development</h4><p>Stateful hot reload is now enabled by default for the web. This has been a fan-favorite feature on mobile for years, and now it brings the same incredible productivity to your <strong>web</strong> projects. Change your code, save, and watch your UI update instantly while preserving its state.</p><h4>2# 🎨 Flowless UI Control and Flexibility</h4><p>Flutter 3.35 introduces major enhancements that gives you more control over your application’s UI and UX. More Powerful Slivers<br>Creating complex, custom scrolling animations is now easier than ever. The updates to slivers provide more power and flexibility, allowing you to build truly dynamic and engaging scrollable content.<br>Multi-Window Support for Desktop:<br>This is a big step for desktop app developers. You can now create and manage multiple windows in your desktop applications. This is perfect for building complex productivity tools, editors, or any app that benefits from a multi-window feature.<br>Here’s an example look at how you might create a new window:</p><pre><br>// Note: This is a simplified, conceptual example.<br>// The actual API may differ.<br>import package:flutter/material.dart&#39;;<br><br>void main() {<br>  runApp(const MyApp());<br>}<br><br>class MyApp extends StatelessWidget {<br>  const MyApp({super.key});@override<br>  Widget build(BuildContext context) {<br>    return MaterialApp(<br>      home: Scaffold(<br>        appBar: AppBar(title: const Text(’Main Window’)),<br>        body: Center(<br>          child: ElevatedButton(<br>            child: const Text(’Open New Window’),<br>            onPressed: () async {<br>              // Hypothetical API to create and run a new window<br>              // final newWindow = await Window.create();<br>              // newWindow.runApp(const NewWindowApp());<br>            },<br>          ),<br>        ),<br>      ),<br>    );<br>  }<br>}<br><br>// The app to be run in the new window<br>class NewWindowApp extends StatelessWidget {<br>  const NewWindowApp({super.key});@override<br>  Widget build(BuildContext context) {<br>    return const MaterialApp(<br>      home: Scaffold(<br>        body: Center(child: Text(’This is a secondary window!’)),<br>      ),<br>    );<br>  }<br>}</pre><h4>3# ♿ Major Accessibility Upgrades</h4><p>Making apps accessible for everyone is a core principle of Google (Flutter owner). This release includes huge updates to help you build more inclusive applications.</p><p><strong>* Richer Semantics on Web</strong>: Assistive technologies like screen readers can now better understand and describe your app’s UI.</p><p><strong>* New Accessibility Tools:</strong> Building accessible custom widgets is now easy.</p><p><strong>* Platform Polish:</strong> Core widgets have been improved to be more accessible.</p><h4>4# 📝 The Future is Modular: Material &amp; Cupertino as Packages</h4><p>The Material and Cupertino design libraries are beginning their journey out of core Flutter framework and into their standalone packages.<br><strong>Why</strong>? This separation will allow the design libraries to evolve faster and more independently. It also opens the door for greater community collaboration, ensuring Flutter’s UI components stay modern, and feature-rich.</p><h4>5# 🤖 Laying the Groundwork for AI-Assisted Development</h4><p>The experimental Dart and Flutter MCP Server is now available on the stable channel. <strong>MCP</strong> (<em>Multi-platform Compilation and Protocol</em>) is a new backend for Dart’s tooling.<br>This isn’t just a technical change; it’s a foundational step towards a future of highly productive, AI-assisted development. This server will power the next generation of intelligent tools, from advanced code completion to AI-powered debugging assistants, for every Dart and Flutter developer.</p><h4>6# 🎉 Experimental Widget Previews</h4><p>One of the most requested features is here for you to try! Experimental <strong>Widget</strong> Previews allows you to see and test your widgets in <strong>isolation</strong> without needing to run the entire application. This speeds up the UI development cycle, letting you iterate on individual components quickly, similar to other tools previews.<br>This example will let you see how custom button can look in different states right inside your IDE:</p><pre>// Note: This is an example to illustrate the feature.<br>// The syntax might use other IDE integrations.<br><br>import &#39;package:flutter/material.dart’;<br><br>class MyCustomButton extends StatelessWidget {<br>final String text;<br>final VoidCallback onPressed;<br><br>const MyCustomButton({<br>    super.key,<br>    required this.text,<br>    required this.onPressed,<br>  }); @override<br>  Widget build(BuildContext context) {<br>    return ElevatedButton(<br>      onPressed: onPressed,<br>      child: Text(text),<br>    );<br>  }<br>}<br><br>// --- PREVIEW ---<br>// This feature would allow the IDE to render this widget live.<br>@Preview<br>Widget myCustomButtonPreview() {<br>  return MyCustomButton(<br>    text: &#39;Preview Button’,<br>    onPressed: () {},<br>  );<br>}</pre><p>Have fun, enjoying the new Flutter features 🥳.</p><h3>A summary for Arabic readers:</h3><h3>📝 ملخص:</h3><p>يقدم تحديث Flutter 3.35 و Dart 3.9 مجموعة من الميزات الجديدة:</p><h4>1. التحديث الفوري للويب (Stateful Hot Reload):</h4><p>أصبح الآن مفعلاً بشكل افتراضي، مما يسرّع عملية تطوير تطبيقات الويب بشكل كبير.</p><h4>2. تحكم أفضل في واجهة المستخدم:</h4><p>تحسينات قوية على أدوات التمرير (<strong>slivers</strong>) ودعم رسمي لإنشاء تطبيقات <strong>سطح مكتب</strong> بنوافذ متعددة.</p><h4>3. تحسينات إمكانية الوصول لكل الفئات:</h4><p>أدوات جديدة ودعم أفضل لجعل التطبيقات سهلة الاستخدام للجميع، خاصة على <strong>الويب</strong>.</p><h4>4. فصل مكتبات التصميم:</h4><p>سيتم تحويل مكتبات Material و Cupertino إلى حزم منفصلة، مما يسمح بتطويرها بشكل أسرع وبمساهمة أكبر من المجتمع.</p><h4>5. التطوير بمساعدة الذكاء الاصطناعي:</h4><p>إطلاق خادم MCP الجديد يضع الأساس لأدوات تطوير ذكية مدعومة بالذكاء الاصطناعي.</p><h4>6. معاينة المكونات (Widget Previews):</h4><p>ميزة تجريبية جديدة تتيح لك رؤية وتجربة الـ <strong>Widgets</strong> بشكل منفصل دون تشغيل التطبيق بالكامل، مما يسهل ويسرع من عملية التصميم.</p><p>يمكنك الإطلاع على بعض الأمثلة في الجزء العلوي من المقالة 🥳.</p><p>💙</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c724ec793458" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Get your iMac (late 2012 serise) back to live ❤️‍]]></title>
            <link>https://medium.com/@hashem.nayra/get-your-imac-late-2012-serise-back-to-live-%EF%B8%8F-bd4e155c8f9b?source=rss-f310d4bfdc8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd4e155c8f9b</guid>
            <category><![CDATA[os]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[imac]]></category>
            <dc:creator><![CDATA[Nayra Hashem]]></dc:creator>
            <pubDate>Fri, 01 Aug 2025 05:29:45 GMT</pubDate>
            <atom:updated>2025-08-01T05:29:45.285Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oYj8XZlw4IZltM2V7FtX7A.jpeg" /><figcaption>iMac screen showing activities opend</figcaption></figure><p>Well, as a Flutter developer, I always wanted a mac pc to develop multiplatform apps (Android and iOS) on it.</p><p>So, a friend of mine recommended his -old- iMac to me in an awesome price that I could not resist to be honest, so I took it right away! at that time, I didn’t mind taking a 2012 iMac, cause I wasn’t really aware that *I wont be able to update its mac os anymore* 😬.</p><p>Plus, if you were wondering, why I have to update my iMac OS, I will tell you that if you are using an old version of macOS, you wont be able to update any of the softwares in it! I mean, you will not be able to even run Chrome or any other programms! The Apple store deny any update request because you OS is not updated, and ofcourse, it can’t be updated anymore due to it’s year of production.</p><h3>Re-launching</h3><p>I thought, is there a way to really use this iMac? I started to search the internet, and most of the suggestions were to (Open the pc, I mean like physically openning it) and upgrade my Hard Drive to a version that can handle the new macOS. Well, that was risky, plus I may break my pc screen during the proccess, so I thought of a turn around an it was successful!</p><h3>Ubuntu</h3><p>I focused my search this time about how to change the OS? Why not installing another OS that is upgraded already! I found that Ubuntu is a good option, since it’s lighter than most of the known OS, user-friendly, and a good fit for my Cybersecurity intrest too!.</p><h3>Installing Ubuntu</h3><p>To do so you will need a USB drive that have Ubuntu 22.0 already burned as a bootable USB, you can use alot of softwares to do so, but we often <a href="https://www.ventoy.net/en/index.html">ventoy</a>.</p><p>Now you got your USB ready, switch on your iMac and long-press the options button (shift button) after you hear the heem sound in iMac.</p><p>A boot menu will be opened, select to boot from your USB which alreay have the Ubuntu, follow the instractions, and wohoo 🥳 you got your Ubuntu on iMac! Light wieghted, cool UI, and fast in proccessing even if it is 2012.</p><h3>Things to consider</h3><p>You may need to install Ubuntu multiple times for it to work (I did it twice).</p><p>You may feel a little bit of lag at the beganning when Ubuntu starts, but it come smoother and smoother after a time.</p><p>I used Ubuntu 22.0 cause I didn’t wanted to take the risk and install 24.0, if anyone did tried 24.0 on their old iMac, please let me know.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd4e155c8f9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Udemy or Coursera?]]></title>
            <link>https://medium.com/@hashem.nayra/udemy-or-coursera-13dee2ab927c?source=rss-f310d4bfdc8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/13dee2ab927c</guid>
            <category><![CDATA[udemy-or-coursera]]></category>
            <category><![CDATA[coursera]]></category>
            <category><![CDATA[udemy]]></category>
            <category><![CDATA[comparison]]></category>
            <dc:creator><![CDATA[Nayra Hashem]]></dc:creator>
            <pubDate>Wed, 19 Mar 2025 10:15:31 GMT</pubDate>
            <atom:updated>2025-03-19T10:15:31.686Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1t9j8zUZOntdXTeLYKdCkw.png" /></figure><p>First of all, let’s admit that both Coursera and Udemy are the most known online courses platform on the web (at least from my perspective).</p><p>As this article will be short and to the point, below I will write some of the main consideration any online student should think of before taking online courses.</p><h3>Coursera</h3><ol><li>Only big companies and universities will be found here.</li><li>Grades in this platform are collected and calculated for the final grade.</li><li>You can join the community of the course.</li><li>Your track on studying is WATCHED! Meaning, if you missed your assignment date, you will get notified.</li><li>Coursera is a real course bases platform, there is a mini assignment, and a final exams too.</li><li>Congratulations! After you got you Coursera certificate, you can share it anywhere, and you can add it as a new studying milestone in your <a href="https://linkedin.com/">LinkedIn </a>profile.</li><li>Prices are a little bit high, specially for people who don’t get paid in USD.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*B-aLpJvtzpEqs55pXAFVuQ.png" /></figure><p><a href="https://www.coursera.org/">Coursera | Degrees, Certificates, &amp; Free Online Courses</a></p><h3>Udemy</h3><ol><li>Any coach/instructor can add their course.</li><li>There is no grade collection.</li><li>This platform is more friendly as you get to know your instructor and reach out to them on social media.</li><li>There is no achievement or studying milestone to be watched.</li><li>No assignments, but sometimes there is tasks that the instructor put them to make you more engaged in the learning phases.</li><li>Congratulations! After reaching to the certificate download phase, you can share it anywhere, but you can’t see Udemy in <a href="https://linkedin.com/">LinkedIn</a> list of schools.</li><li>Prices are great, and many times there’s offers and discounts.</li></ol><p><a href="https://udemy.com/">https://udemy.com</a></p><h3>Summary</h3><p>Coursera or Udemy are both a great platforms for online studying, Coursera is more like you are in an online college, with assignments, grades and a proved certificate, with of course, a high-value content. While Udemy is better for studying a light-weighted courses, in a no-tracking time to finish, and there is a verity of the content, from a light to an amazing.</p><p>I have studied Flutter course in Udemy, and now I’m a Flutter coach!.</p><p>I have studied Google Professional UX design in Coursera, and I can say proudly the I’m a UX designer.</p><p>This is only my humble perspective of view, you may agree and my not. Maybe you will add more points to mine too! Let me know down below =).</p><p>Stay happy and curious 😊.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13dee2ab927c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>