<?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 Alhassan Mohammed on Medium]]></title>
        <description><![CDATA[Stories by Alhassan Mohammed on Medium]]></description>
        <link>https://medium.com/@bigboss200535?source=rss-d9147c193ff0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uFxhQlu07gmfwXYCocV-kw@2x.jpeg</url>
            <title>Stories by Alhassan Mohammed on Medium</title>
            <link>https://medium.com/@bigboss200535?source=rss-d9147c193ff0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:50:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bigboss200535/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[Why developers engage with ChatGPT in Issue-Tracker in 2026]]></title>
            <link>https://medium.com/@bigboss200535/why-developers-engage-with-chatgpt-in-issue-tracker-in-2026-c705a7a08c21?source=rss-d9147c193ff0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c705a7a08c21</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[illumination]]></category>
            <dc:creator><![CDATA[Alhassan Mohammed]]></dc:creator>
            <pubDate>Mon, 26 Jan 2026 22:03:09 GMT</pubDate>
            <atom:updated>2026-01-26T22:03:09.304Z</atom:updated>
            <content:encoded><![CDATA[<p>Modern software teams rely heavily on issue trackers; whether that’s GitHub Issues, Jira, Linear, YouTrack, or GitLab. But a surprising trend is emerging: developers are increasingly inviting ChatGPT into the issue-tracking workflow itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9inMyCTGerPiML-f" /><figcaption>Photo by <a href="https://unsplash.com/@siva_photography?utm_source=medium&amp;utm_medium=referral">Levart_Photographer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>And it’s not because they’re lazy. It’s because AI is changing <em>how</em> we understand problems, communicate solutions, and accelerate development cycles. This shift is so significant that it’s reshaping the future of engineering teams.</p><h3>1. ChatGPT Helps Developers Understand Issues Faster</h3><p>A typical issue might look like this:</p><blockquote><em>“Unexpected token error in </em><em>OrderController.php when saving bulk invoices.”</em></blockquote><p>This sounds simple, but often the root cause hides behind logs, stack traces, or poorly written descriptions.</p><h4>How ChatGPT helps</h4><p>Developers paste the issue description into ChatGPT and ask:</p><blockquote><em>“Explain what this issue might mean and list possible causes.”</em></blockquote><p>ChatGPT can:</p><ul><li>translate unclear descriptions into plain English</li><li>identify probable root causes</li><li>provide context for new team members</li><li>highlight missing details</li></ul><p>This saves hours of back-and-forth clarifications.</p><h4>Real example</h4><p><strong>Issue:</strong> “Queue worker stalls on large imports.”<br><strong>ChatGPT output:</strong> “Likely memory exhaustion, blocking I/O, or an unhandled exception inside the import job. Check your chunk size, retry logic, and queue driver configuration.”</p><h3>2. It Writes Clearer, More Structured Issue Descriptions</h3><p>Poorly written issues slow down teams. Developers now drop raw notes or chaotic bug descriptions into ChatGPT and instruct:</p><blockquote><em>“Rewrite this as a clean issue with steps to reproduce, expected behavior, actual behavior, and logs.”</em></blockquote><p>Suddenly, what was once messy becomes professional and ready for action.</p><h4>Example</h4><p><strong>Before:</strong></p><blockquote><em>“Login breaks sometimes, user can’t get in, happens randomly.”</em></blockquote><h4><strong>After ChatGPT formatting:</strong></h4><ul><li>Steps to Reproduce</li><li>Environment</li><li>Expected Behavior</li><li>Actual Behavior</li><li>Possible Impact</li></ul><p>Issues become easier to triage, assign, and fix.</p><h3>3. It Suggests Solutions Inside the Issue Thread</h3><p>Instead of waiting for a senior engineer to review the problem, developers ask:</p><blockquote><em>“Based on this issue thread, what are some solutions and which is most efficient?”</em></blockquote><p>ChatGPT then analyzes:</p><ul><li>logs</li><li>previous comments</li><li>code snippets</li><li>discussion history</li></ul><p>…and produces actionable recommendations.</p><h4>Example</h4><p><strong>Issue:</strong> Laravel job keeps retrying and never fails.<br><strong>ChatGPT suggestion:</strong><br> “Add fail() inside the catch block, implement retryUntil() for job expiration, and verify that the exception is not being swallowed by a custom trait.”</p><p>This level of insight boosts productivity immediately.</p><h3>4. ChatGPT Helps Devs Generate Reproduction Code Quickly</h3><p>Many bugs require a reproducible environment to fix.<br> Developers now ask:</p><blockquote><em>“Generate a minimal reproduction using Laravel + MySQL for this bug.”</em></blockquote><p>ChatGPT provides:</p><ul><li>a model</li><li>migration</li><li>controller</li><li>route</li><li>sample data</li></ul><p>In minutes, developers get a project-ready test case that would otherwise take hours.</p><h3>5. It Acts as a Neutral “Third Reviewer” in Issue Discussions</h3><p>Sometimes developers disagree.</p><ul><li>“Is this a bug or intended behavior?”</li><li>“Should we redesign this function?”</li><li>“Which approach is better?”</li></ul><p>Instead of escalating, they ask ChatGPT for rationale.</p><h4>Example</h4><p><strong>Debate:</strong> “Use events or observers for user registration triggers?”<br> <strong>ChatGPT:</strong></p><ul><li>Events → more flexibility, better for multiple listeners</li><li>Observers → easier for simple model logic</li><li>Recommendation → events if scaling, observers if only one triggered action</li></ul><p>This helps issues move forward without friction.</p><h3>6. ChatGPT Saves Time During Triage Meetings</h3><p>Product managers and tech leads use ChatGPT to:</p><ul><li>summarize long issue threads</li><li>categorize issues</li><li>estimate complexity</li><li>detect duplicates</li></ul><h4>Example prompt</h4><blockquote><em>“Summarize these 15 issues and group them by feature, urgency, and difficulty.”</em></blockquote><p>What used to take hours now takes seconds.</p><h3>7. It Helps New Developers Understand Legacy Code Faster</h3><p>Every team has a legacy module nobody wants to touch.<br> Developers paste chunks of code into ChatGPT:</p><blockquote><em>“Explain what this function does and how it relates to the issue.”</em></blockquote><p>ChatGPT breaks it down line by line and clarifies the logic behind the old implementation.</p><h3>Example</h3><p>A legacy PaymentService.php with 500 lines becomes:</p><ul><li>a readable explanation</li><li>a dependency map</li><li>a diagram of data flow</li></ul><p>This accelerates onboarding dramatically.</p><h3>Real-World Workflow Developers Use Today</h3><p>Here is the modern, AI-powered issue-tracking workflow:</p><ol><li>Developer encounters a bug</li><li>Raw notes copied into ChatGPT</li><li>ChatGPT formats the issue professionally</li><li>Issue posted in tracker</li><li>ChatGPT is used to analyze logs</li><li>ChatGPT gives solution suggestions</li><li>Developer posts final fix</li><li>ChatGPT generates documentation for the resolution</li></ol><p>This creates a loop where development becomes smoother, faster, and more efficient.</p><h3>Conclusion: AI Is Becoming a Core Member of the Development Team</h3><p>Developers aren’t using ChatGPT inside issue trackers because it’s trendy — they’re using it because it genuinely improves productivity, communication, and software quality.</p><p>Issue trackers haven’t fundamentally changed in over a decade.<br> But AI is transforming them into living, intelligent systems that help teams diagnose, clarify, and resolve issues at unprecedented speed.</p><p>We are officially in the era where ChatGPT is more than a tool, <strong>it’s a collaborator.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c705a7a08c21" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recovering a Critical MSSQL Database from a Failing Non-RAID Drive: A Real-World Hospital Case]]></title>
            <link>https://medium.com/@bigboss200535/recovering-a-critical-mssql-database-from-a-failing-non-raid-drive-a-real-world-hospital-case-b46ea5ee44ef?source=rss-d9147c193ff0------2</link>
            <guid isPermaLink="false">https://medium.com/p/b46ea5ee44ef</guid>
            <category><![CDATA[database]]></category>
            <category><![CDATA[query]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Alhassan Mohammed]]></dc:creator>
            <pubDate>Sat, 24 Jan 2026 13:33:33 GMT</pubDate>
            <atom:updated>2026-01-24T13:33:33.857Z</atom:updated>
            <content:encoded><![CDATA[<p>In healthcare IT, downtime isn’t just inconvenient; it can directly impact patient care. Recently, I faced a situation that many system administrators dread: a <strong>production database running on a failing disk with no RAID redundancy</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7fWopq4GsnjjIDqN" /><figcaption>Photo by <a href="https://unsplash.com/@jandira_sonnendeck?utm_source=medium&amp;utm_medium=referral">Jandira Sonnendeck</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The Situation</h3><p><strong>Environment:</strong> the system was running on Windows Server with Microsoft SQL Server, A Windows-based hospital application with a Single physical drive (No RAID)</p><p><strong>The symptoms were alarming: </strong>The database <strong>could not be backed up and </strong>the database files <strong>could not be copied </strong>either. Any attempt to back up or copy resulted in I/O errors. However, the hospital application was still able to <strong>read from </strong>and<strong> write to the database. </strong>At this point, a full disk failure was clearly imminent.</p><h3>Why Traditional Recovery Options Failed</h3><p>Normally, the first instinct is to:</p><ul><li>Run a full SQL backup</li><li>Copy .mdf / .ldf files</li><li>Snapshot the disk</li></ul><p>None of these worked.</p><p>The reason was simple: <strong>backup and copy operations trigger large sequential disk reads</strong>, which the failing drive could no longer handle reliably.</p><p>However, the application was still functioning because:</p><ul><li>SQL Server was serving data <strong>already cached in memory</strong></li><li>Normal transactional reads/writes were still succeeding</li><li>The disk was failing under <em>stress</em>, not total load</li></ul><p>This distinction mattered.</p><h3>The Key Insight</h3><blockquote><em>If SQL Server can still </em><strong><em>read rows</em></strong><em>, then data can still be </em><strong><em>logically extracted</em></strong><em>, even if the disk can’t survive a backup.</em></blockquote><p>Instead of trying to copy the database as a file, the solution was to <strong>move the data row by row</strong>.</p><h3>The Recovery Strategy</h3><h4>1. Introduce a Healthy Storage Target</h4><p>A <strong>USB external drive</strong> was connected to the server. While not ideal for production, it provided:</p><ul><li>A physically separate disk</li><li>Stable write capability</li><li>Immediate availability without rebooting</li></ul><h4>2. Create a New Database on the USB Drive</h4><p>A new empty database was created on the USB disk and attached to the <strong>same SQL Server instance</strong>.</p><p>This ensured:</p><ul><li>No network overhead</li><li>Minimal CPU usage</li><li>No need for additional SQL services</li></ul><h4>3. Recreate the Schema</h4><p>Using existing scripts and metadata:</p><ul><li>Tables were recreated manually</li><li>Indexes and constraints were added <strong>after</strong> data transfer</li><li>Triggers were temporarily excluded to reduce overhead</li></ul><p>This step was intentionally lightweight.</p><h4>4. Perform Logical Data Migration</h4><p>Instead of backups or exports, we used:</p><pre>INSERT INTO NewDatabase.dbo.TableName<br>SELECT * FROM OldDatabase.dbo.TableName</pre><p>Why this worked:</p><ul><li>SQL Server handled reads incrementally</li><li>No large sequential scans were forced</li><li>Data was transferred in controlled logical operations</li><li>SQL Server’s buffer cache absorbed much of the load</li></ul><p>Tables were migrated <strong>one by one</strong>, starting with the most critical.</p><h4>5. Validate Data Integrity</h4><p>After migration:</p><ul><li>Row counts were compared</li><li>Spot checks were performed on critical patient and transaction data</li><li>Application queries were tested against the new database</li></ul><p>Once validated, the application was pointed to the new database.</p><h3>The Outcome</h3><ul><li>No data loss</li><li>No emergency shutdown</li><li>No forced reboot</li><li>No disk cloning</li><li>Minimal additional stress on the failing drive</li></ul><p>Most importantly: <strong>clinical operations continued uninterrupted</strong>.</p><h3>Lessons Learned</h3><h4>1. RAID Is Not Optional</h4><p>This incident reinforced that <strong>single-disk databases in healthcare are unacceptable</strong>. RAID is not a performance feature, <strong>it’s a safety requirement.</strong></p><h4>2. Backups Can Fail When You Need Them Most</h4><p>A “working” database does not guarantee a “<em>backuppable</em>” database. Backup failures often appear <strong>late in disk failure timelines</strong>.</p><h4>3. Logical Extraction Can Save You</h4><p>When physical methods fail:</p><ul><li>SELECT still working = data is still accessible</li><li>Logical migration is often safer than forcing backups</li><li>SQL Server memory caching can buy you time</li></ul><h4>4. Stay Calm, Reduce Disk Stress</h4><p>Avoid:</p><ul><li>Reboots</li><li>CHKDSK</li><li>Repeated backup retries</li><li>Disk-intensive tools</li></ul><p>Every unnecessary operation increases failure risk.</p><h3>Final Thoughts</h3><p>This wasn’t a textbook recovery, it was a <strong>real-world, time-critical decision</strong> made under pressure in a healthcare environment. The solution worked because it respected one core principle:</p><blockquote><em>When hardware is failing, </em><strong><em>do less</em></strong><em>, not more.</em></blockquote><p>If you’re a system administrator responsible for critical systems, I hope this experience helps you think differently when backups fail but the database is still alive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b46ea5ee44ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Laravel App Won’t Survive 10,000 Users. Here’s How to Scale It to 1 Million]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@bigboss200535/your-laravel-app-wont-survive-10-000-users-here-s-how-to-scale-it-to-1-million-0658518bd91b?source=rss-d9147c193ff0------2"><img src="https://cdn-images-1.medium.com/max/2600/0*CL44vV_nBlKPEQaZ" width="6048"></a></p><p class="medium-feed-snippet">So, you built an amazing web app with Laravel. It&#x2019;s sleek, fast, and users are signing up. Then, the nightmare scenario: a tweet goes&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@bigboss200535/your-laravel-app-wont-survive-10-000-users-here-s-how-to-scale-it-to-1-million-0658518bd91b?source=rss-d9147c193ff0------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@bigboss200535/your-laravel-app-wont-survive-10-000-users-here-s-how-to-scale-it-to-1-million-0658518bd91b?source=rss-d9147c193ff0------2</link>
            <guid isPermaLink="false">https://medium.com/p/0658518bd91b</guid>
            <category><![CDATA[illumination]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[write-a-catalyst]]></category>
            <category><![CDATA[laravel]]></category>
            <dc:creator><![CDATA[Alhassan Mohammed]]></dc:creator>
            <pubDate>Wed, 14 Jan 2026 23:15:41 GMT</pubDate>
            <atom:updated>2026-01-14T23:15:41.789Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Exposed: How Hackers Breached WhatsApp with Just a Phone Number; Secure Your Laravel App Before…]]></title>
            <link>https://medium.com/@bigboss200535/exposed-how-hackers-breached-whatsapp-with-just-a-phone-number-secure-your-laravel-app-before-a3047a5410ad?source=rss-d9147c193ff0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3047a5410ad</guid>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[illumination]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[write-a-catalyst]]></category>
            <dc:creator><![CDATA[Alhassan Mohammed]]></dc:creator>
            <pubDate>Fri, 19 Dec 2025 15:12:22 GMT</pubDate>
            <atom:updated>2025-12-19T15:12:22.785Z</atom:updated>
            <content:encoded><![CDATA[<h2>Exposed: How Hackers Breached WhatsApp with Just a Phone Number; Secure Your Laravel App Before It’s Too Late!</h2><p>In a world where your phone number is your digital identity, one massive flaw turned billions of WhatsApp users into sitting ducks. Imagine hackers scanning through tens of billions of phone numbers, pinpointing exactly who’s on WhatsApp ; all without breaking a sweat. This isn’t sci-fi; it’s the chilling reality of a recent WhatsApp security blunder that exposed 3.5 billion active accounts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*WUHW9n_8HbsRRI-_i7YCtQ.jpeg" /></figure><p>If you’re building apps with Laravel that rely on phone numbers for authentication, this could be your wake-up call. Stick around as we dive into why this happened and, more importantly, how to bulletproof your Laravel application against similar attacks. Your users’ data and your reputation depends on it!</p><h3><strong>The WhatsApp Nightmare: A Phone Number Fiasco Unveiled</strong></h3><p>Picture this: You’re sipping your morning coffee when news breaks that WhatsApp, the messaging giant with over 2 billion users, has a gaping hole in its armor. Researchers discovered a simple API vulnerability allowing anyone to query billions of phone numbers and identify active WhatsApp accounts. By exploiting WhatsApp’s contact discovery feature, attackers could automate checks on 63 billion numbers, flagging 3.5 billion as registered users. This isn’t just a privacy leak; it’s a goldmine for cybercriminals.</p><p>But that’s not all. Enter the “GhostPairing” attack, a sneaky phishing scheme where hackers lure victims to fake websites mimicking WhatsApp’s device pairing process. Users enter their phone number thinking they’re verifying a new device, but boom ; attackers gain full access to chats, contacts, and more. And let’s not forget invisible tracking tools that exploit delivery receipts to monitor users’ online status via phone numbers alone.</p><p>These incidents highlight a core weakness: WhatsApp’s heavy reliance on phone numbers as the primary identifier for accounts. Phone numbers are easy to guess, buy in bulk, or steal through SIM swaps and social engineering. Once hackers have one, they can attempt verifications, intercept SMS codes, or exploit API endpoints. The result? Widespread account takeovers, spyware installations, and data breaches that make headlines.</p><h3>Why Phone Numbers Are the Achilles’ Heel of Modern Apps</h3><p>Phone numbers seem convenient; they’re unique, memorable, and tied to real people. But in the hands of hackers, they’re a liability:</p><ul><li>Enumeration Attacks: Like WhatsApp’s flaw, attackers can brute-force check if a number is registered, building massive databases for spam, phishing, or targeted hacks.</li><li>SMS Vulnerabilities: Verification codes sent via text are interceptable through carrier hacks, man-in-the-middle attacks, or even cheap SS7 exploits.</li><li>Phishing Paradise: Fake sites trick users into handing over numbers, as seen in GhostPairing.</li><li>Privacy Erosion: Leaked numbers lead to doxxing, stalking, or worse.</li></ul><p>If your Laravel app uses phone-based login, registration, or two-factor authentication (2FA), you’re playing with fire. But fear not, Laravel’s robust ecosystem offers tools to fight back.</p><h3>From WhatsApp’s Mistake to Your Laravel Win: Bridging the Gap</h3><p>Many Laravel developers integrate phone number auth for user verification, password resets, or multi-factor security. Think e-commerce sites, social platforms, or fintech apps where a quick SMS OTP seals the deal. But emulating WhatsApp’s pitfalls could expose your users to the same risks.</p><p>The good news? Laravel makes it straightforward to implement secure alternatives. By learning from WhatsApp’s phone number debacle, you can harden your app against enumeration, phishing, and interception attacks.</p><h3>Fortify Your Laravel App: 7 Proven Steps to Prevent Phone Number Hacks</h3><p>Ready to level up your security game? Here’s a step-by-step guide to safeguarding phone number authentication in Laravel. We’ll focus on best practices, packages, and code snippets to make it actionable.</p><h4>1. Ditch SMS-Only Verification; Embrace App-Based 2FA</h4><p>SMS is hackable; authenticator apps aren’t. Integrate time-based one-time passwords (TOTP) using packages like laravel/fortify or bacon/bacon-qr-code.</p><ul><li>Install: composer require bacon/bacon-qr-code</li><li>Enable 2FA in your User model and generate QR codes for apps like Google Authenticator.</li><li>Why it works: No phone number dependency means no SIM swap risks.</li></ul><p>For phone-inclusive 2FA, use services like Vonage or Twilio for voice calls instead of SMS; harder to intercept.</p><h4>2. Implement Rate Limiting on Auth Endpoints</h4><p>Prevent brute-force enumeration by throttling API calls.</p><ul><li>Use Laravel’s built-in ThrottleRequests middleware: In routes/api.php, add -&gt;middleware(‘throttle:60,1&#39;) to limit 60 attempts per minute.</li><li>For phone verifications: Track attempts per IP or number using Redis.</li></ul><p>This stops hackers from querying billions of numbers like in WhatsApp’s case.</p><h4>3. Prevent User Enumeration</h4><p>Don’t reveal if a phone number is registered during login or signup.</p><ul><li>In your controller: Instead of “Number not found,” use generic errors like “Invalid credentials.”</li><li>Hash Phone Numbers: Store them encrypted with Laravel’s Crypt facade or hash for lookups.</li></ul><pre>// In migration<br>$table-&gt;string(&#39;phone&#39;)-&gt;index();<br><br>// Storing<br>$user-&gt;phone = Hash::make($request-&gt;phone);</pre><h4>4. Add CAPTCHA to Verification Flows</h4><p>Combat phishing and bots with Google reCAPTCHA or hCaptcha.</p><ul><li>Install: composer require anhskohbo/no-captcha</li><li>In forms: Add @captcha directive.</li><li>Apply to phone input fields to ensure humans, not scripts, are entering numbers</li></ul><h4>5. Use Secure Third-Party Services for Phone Auth</h4><p>Leverage Firebase or Vonage for robust verification.</p><ul><li>Firebase Phone Auth: Integrate with kreait/laravel-firebase for seamless OTPs.</li></ul><pre>$auth = app(&#39;firebase.auth&#39;);<br>$verification = $auth-&gt;sendVerificationCode($phoneNumber);</pre><ul><li>Benefits: Built-in fraud detection and global reach without exposing your API.</li></ul><h4>6. Enforce HTTPS and Secure Sessions</h4><p>Always use SSL to encrypt data in transit.</p><ul><li>In .env: Set APP_URL=https://yourdomain.com</li><li>Middleware: Force HTTPS with App\Http\Middleware\ForceHttps.</li><li>Combine with role-based access control (RBAC) using spatie/laravel-permission to limit sensitive actions.</li></ul><h4>7. Mask and Protect Stored Phone Numbers</h4><p>For privacy, mask numbers in displays and logs.</p><p>Use Laravel to show +1********23</p><pre>Str::mask: Str::mask($phone, &#39;*&#39;, 3, -4);</pre><p>Regularly audit with tools like Laravel Telescope or external scanners to catch vulnerabilities early.</p><h3>The Bottom Line: Don’t Be the Next WhatsApp Headline</h3><p>WhatsApp’s phone number hack serves as a stark reminder that convenience often comes at security’s expense. By implementing these Laravel strategies, you’re not just preventing hacks; you’re building trust with your users. Start small: Enable 2FA today and audit your auth flows.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3047a5410ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Multi-Language Applications with Laravel: A Practical Guide for Modern Developers]]></title>
            <link>https://medium.com/@bigboss200535/building-multi-language-applications-with-laravel-a-practical-guide-for-modern-developers-bcea70bd5be3?source=rss-d9147c193ff0------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcea70bd5be3</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Alhassan Mohammed]]></dc:creator>
            <pubDate>Tue, 02 Dec 2025 19:12:47 GMT</pubDate>
            <atom:updated>2025-12-02T19:12:47.181Z</atom:updated>
            <content:encoded><![CDATA[<p>As businesses scale globally, offering content in multiple languages is no longer optional, it’s a competitive requirement. Whether you’re building an e-commerce platform, SaaS dashboard, or community portal, providing localized content increases engagement, improves user experience, and expands your reach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A7dP01q1v6sM8v_g" /><figcaption>Photo by <a href="https://unsplash.com/@bsod?utm_source=medium&amp;utm_medium=referral">Taewoo Kim</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Laravel makes this easier than many frameworks thanks to its rich localization features, intuitive structure, and clean syntax.</p><h3>Why Multi-Language Support Matters</h3><p>Multi-language applications offer several advantages:</p><h4>1. Wider Audience</h4><p>A localized product can instantly reach new markets. For instance, supporting <strong>English</strong>, <strong>Spanish</strong>, and <strong>Arabic</strong> makes your app accessible to over <strong>1.2 billion</strong> speakers.</p><h4>2. Increased Revenue</h4><p>Users are more likely to purchase products or stay subscribed when content is in their native language.</p><h4>3. Better SEO</h4><p>Search engines prioritize content that matches the visitor’s language, allowing you to rank higher in multiple regions.</p><h3>How Laravel Approaches Localization</h3><p>Laravel uses a simple, file-based approach to manage translations. All translation files reside in the resources/lang/ directory:</p><pre>resources/<br>   lang/<br>      en/<br>         messages.php<br>      fr/<br>         messages.php<br>      es/<br>         messages.php</pre><p>Each language has its own folder containing the same set of files for consistency.</p><h4>Step 1: Creating Translation Files</h4><p>Let’s create a translation file called messages.php.</p><p><strong>English version (</strong><strong>resources/lang/en/messages.php):</strong></p><pre>return [<br>    &#39;welcome&#39; =&gt; &#39;Welcome to our platform!&#39;,<br>    &#39;login&#39;   =&gt; &#39;Login to continue&#39;,<br>];</pre><p><strong>French version (</strong><strong>resources/lang/fr/messages.php):</strong></p><pre>return [<br>    &#39;welcome&#39; =&gt; &#39;Bienvenue sur notre plateforme !&#39;,<br>    &#39;login&#39;   =&gt; &#39;Connectez-vous pour continuer&#39;,<br>];</pre><p><strong>Spanish version (</strong><strong>resources/lang/es/messages.php):</strong></p><pre>return [<br>    &#39;welcome&#39; =&gt; &#39;¡Bienvenido a nuestra plataforma!&#39;,<br>    &#39;login&#39;   =&gt; &#39;Inicia sesión para continuar&#39;,<br>];</pre><p>As soon as these files exist, Laravel can serve any of them.</p><h4>Step 2: Displaying Translated Text in Blade Templates</h4><p>Using translations in Blade is simple:</p><pre>&lt;h1&gt;{{ __(&#39;messages.welcome&#39;) }}&lt;/h1&gt;<br>&lt;p&gt;{{ __(&#39;messages.login&#39;) }}&lt;/p&gt;</pre><p>Laravel automatically finds the correct message based on the active language.</p><h4>Step 3: Changing the Application Language</h4><p>You can change the language at runtime.<br> Example: switch the current locale using a simple controller method.</p><pre>public function switchLanguage($locale)<br>{<br>    if (in_array($locale, [&#39;en&#39;, &#39;fr&#39;, &#39;es&#39;])) {<br>        session([&#39;locale&#39; =&gt; $locale]);<br>        app()-&gt;setLocale($locale);<br>    }<br><br>    return redirect()-&gt;back();<br>}</pre><p>Add routes:</p><pre>Route::get(&#39;lang/{locale}&#39;, [LanguageController::class, &#39;switchLanguage&#39;]);</pre><p>Create simple links in Blade:</p><pre>&lt;a href=&quot;/lang/en&quot;&gt;English&lt;/a&gt; |<br>&lt;a href=&quot;/lang/fr&quot;&gt;Français&lt;/a&gt; |<br>&lt;a href=&quot;/lang/es&quot;&gt;Español&lt;/a&gt;</pre><p>Now your app can switch languages instantly without reloading data.</p><h4>Step 4: Localizing Validation Messages</h4><p>Laravel ships with many built-in translations for validation errors.</p><p>For custom ones, you can edit:</p><pre>resources/lang/en/validation.php<br>resources/lang/fr/validation.php<br>resources/lang/es/validation.php</pre><p>Example entry:</p><pre>&#39;email&#39; =&gt; &#39;Please enter a valid email address.&#39;,</pre><h4>Step 5: Localizing Dynamic Content</h4><p>Sometimes you need placeholders:</p><pre>return [<br>    &#39;greeting&#39; =&gt; &#39;Hello, :name!&#39;,<br>];</pre><p>Usage:</p><pre>{{ __(&#39;messages.greeting&#39;, [&#39;name&#39; =&gt; &#39;Daniel&#39;]) }}</pre><p>Output:</p><pre>Hello, John!</pre><p>This works seamlessly across all languages.</p><p>Multi-language support in Laravel is not only achievable, it’s elegant, scalable, and developer-friendly. With just a few translation files and minimal configuration, you can reach global audiences and improve engagement across your platform.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcea70bd5be3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Laravel Caching: Boost Your App’s Performance Effortlessly]]></title>
            <link>https://medium.com/@bigboss200535/mastering-laravel-caching-boost-your-apps-performance-effortlessly-bcf051d61f22?source=rss-d9147c193ff0------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcf051d61f22</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[cache]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[laravel]]></category>
            <dc:creator><![CDATA[Alhassan Mohammed]]></dc:creator>
            <pubDate>Mon, 01 Dec 2025 17:54:27 GMT</pubDate>
            <atom:updated>2025-12-01T17:54:27.287Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s fast-paced digital world, speed and efficiency aren’t just<br>perks; they’re necessities. Caching can drastically reduce load times,<br>decrease server strain, and deliver a smoother experience to your<br>users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uVtSoiT710T-sSix" /><figcaption>Photo by <a href="https://unsplash.com/@luangjokaj?utm_source=medium&amp;utm_medium=referral">Luan Gjokaj</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What Is Laravel Caching?</h3><p>At its core, caching stores data temporarily so that future requests<br>for that data can be served faster. Instead of querying the database<br>or performing complex calculations repeatedly, Laravel caching allows<br>you to ‘remember’ the results and quickly serve them next time.</p><p>Laravel supports multiple cache drivers; from popular options like<br>Redis and Memcached to simple file-based caching, making it flexible<br>for any project size or hosting environment.</p><h3>Why Use Caching?</h3><p>Imagine your site has a blog feed with hundreds of posts. Each time a<br>user visits, fetching data from the database and rendering it can<br>consume time. With caching, you can store the rendered output or the<br>query result and deliver it instantly on subsequent visits.</p><p><strong>Example scenario:</strong> Your application fetches featured product lists,<br>blog posts, or user settings on every page load. Caching removes this<br>repetitive database hit, accelerating response times dramatically.</p><h3>How to Implement Caching in Laravel</h3><p>Laravel’s Cache facade makes caching intuitive. Here’s a quick primer:</p><pre>use Illuminate\Support\Facades\Cache;<br><br>// Storing data in cache for 10 minutes<br>Cache::put(&#39;key&#39;, &#39;value&#39;, now()-&gt;addMinutes(10));<br><br>// Retrieving data from cache<br>$value = Cache::get(&#39;key&#39;);<br><br>// Retrieving data or running a closure if key doesn&#39;t exist<br>$value = Cache::remember(&#39;users&#39;, 60, function () {<br>    return DB::table(&#39;users&#39;)-&gt;get();<br>});</pre><p>The above example uses <strong>Cache::remember</strong> to fetch users from the<br>database only if they’re not already cached, storing the result for 60<br>minutes. This approach significantly reduces load on the database for<br>frequently requested data.</p><h3>Advanced Caching Techniques</h3><ul><li><strong>Tagging:</strong> Laravel supports cache tagging, allowing you to group<br>related cache items and clear them all at once. For example, tag all<br>blog-related caches with <strong>blog</strong> and invalidate them easily after a<br>post update.</li></ul><pre>Cache::tags([&#39;blog&#39;])-&gt;put(&#39;featured_posts&#39;, $posts, 30);</pre><ul><li><strong>Cache Events</strong>: You can listen for cache hits or misses to analyze<br>performance or trigger other parts of your app dynamically.</li><li><strong>Cache Drivers:</strong> Redis or Memcached can be used for<br>high-performance, distributed cache stores, ideal for load-balanced<br>environments.</li></ul><h3><strong>Real-World Example: Caching a Blog Sidebar</strong></h3><p>Many websites have a blog sidebar displaying categories and recent<br>posts. These rarely change but are accessed on nearly every page.<br>Instead of querying the database each time, cache the sidebar data.</p><pre>$sidebarData = Cache::remember(&#39;blog_sidebar&#39;, 60, function () {<br> return [<br> &#39;categories&#39; =&gt; Category::all(),<br> &#39;recent_posts&#39; =&gt; Post::latest()-&gt;take(5)-&gt;get(),<br> ];<br>});<br>// Return to view<br>return view(&#39;layouts.sidebar&#39;, $sidebarData);</pre><p>By caching the sidebar, your pages load faster and the database<br>workload is reduced.</p><h3>Take Your Laravel Apps to the Next Level With Caching</h3><p>Implementing caching in Laravel isn’t just about speed; it’s about<br>scalability, efficiency, and a better user experience. Dive into<br>Laravel caching today and watch your apps perform like never before.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcf051d61f22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Laravel Eloquent ORM: Tricks for Optimized
Database Queries]]></title>
            <link>https://medium.com/@bigboss200535/mastering-laravel-eloquent-orm-tricks-for-optimized-database-queries-cb2f098b64e5?source=rss-d9147c193ff0------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb2f098b64e5</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[illumination]]></category>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Alhassan Mohammed]]></dc:creator>
            <pubDate>Fri, 28 Nov 2025 09:59:30 GMT</pubDate>
            <atom:updated>2025-11-28T09:59:30.297Z</atom:updated>
            <content:encoded><![CDATA[<p>Laravel’s Eloquent ORM (Object-Relational Mapper) is a powerful and elegant way to interact with your database. It simplifies database operations by allowing developers to work with database records and relationships using expressive, human-readable syntax. However, like any tool, it’s crucial to use it efficiently to ensure your application performs well, especially as it scales.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WvDRQ0yrnpD-Xsks" /><figcaption>Photo by <a href="https://unsplash.com/@austindistel?utm_source=medium&amp;utm_medium=referral">Austin Distel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Understanding Eloquent ORM Basics</h3><p>Eloquent uses <strong><em>models</em></strong> to represent database tables. Each model<br>corresponds to a table and allows you to perform CRUD (Create, Read,<br>Update, Delete) operations effortlessly.</p><p>For example, if you have a User model, you can retrieve all users with:</p><pre>$users = User::all();</pre><p>However, retrieving all users may not always be the best choice in<br>terms of performance, especially if the database contains thousands of<br>records.</p><h4>1. Use Eager Loading to Prevent N+1 Query Problem</h4><p>When working with related models, Eloquent executes additional queries<br>to fetch related data. For instance, if you want to get all posts<br>along with their authors, doing this naively:</p><pre>$posts = Post::all();<br><br>foreach ($posts as $post) {<br>    echo $post-&gt;author-&gt;name;<br>}</pre><p>This will trigger an extra query for each post to get the author,<br>resulting in the infamous N+1 query problem that drastically affects<br>performance.</p><p>The solution? Eager loading.</p><pre>$posts = Post::with(&#39;author&#39;)-&gt;get();<br><br>foreach ($posts as $post) {<br>    echo $post-&gt;author-&gt;name;<br>}</pre><p>With eager loading, Laravel fetches all related authors in a single<br>query, reducing the total number of queries executed.</p><h4>2. Select Only the Columns You Need</h4><p>By default, Eloquent fetches all columns from the database table. For<br>large tables, this can be inefficient. Use `select()` to fetch only<br>the necessary columns:</p><pre>$users = User::select(&#39;id&#39;, &#39;name&#39;, &#39;email&#39;)-&gt;get();</pre><p>This reduces memory usage and speeds up query execution.</p><h4>3. Use Chunking for Large Datasets</h4><p>If you need to process large amounts of data, loading everything at<br>once may crash your server or use excessive memory. Laravel’s<br>`chunk()` method allows you to process records in smaller batches:</p><pre>User::chunk(100, function ($users) {<br>    foreach ($users as $user) {<br>        // Process each user...<br>    }<br>});</pre><p>This approach is effective when performing operations such as sending<br>emails or data transformations on large datasets.</p><h4>4. Indexing Your Database Columns</h4><p>While this is not a direct Eloquent optimization, ensuring your<br>database columns used in WHERE clauses, JOINs, and ORDER BY are<br>properly indexed can drastically improve performance.</p><p>For example, in a migration:</p><pre>$table-&gt;string(&#39;email&#39;)-&gt;index();<br></pre><p>Mastering Laravel’s Eloquent ORM is a vital skill for backend<br>developers. Using eager loading to avoid N+1 problems, selecting only<br>the required columns, chunking large datasets, and properly indexing<br>database columns are simple yet effective ways to boost performance.<br>Moreover, tools like Laravel Telescope make debugging and optimization<br>straightforward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*29v92PzUSDA49MaRiOyKmQ@2x.jpeg" /><figcaption>Photo by <a href="https://linktr.ee/mktography">Maksym Kaharlytskyi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>By optimizing your Laravel applications, you not only improve user<br>experience through faster loading times but also reduce server costs,<br>ultimately increasing your project’s profitability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb2f098b64e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Deleting Users Is a Mistake and How Laravel Breeze Can Save Your App]]></title>
            <link>https://medium.com/@bigboss200535/why-deleting-users-is-a-mistake-and-how-laravel-breeze-can-save-your-app-118853d165b9?source=rss-d9147c193ff0------2</link>
            <guid isPermaLink="false">https://medium.com/p/118853d165b9</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[illumination]]></category>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[write-a-catalyst]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Alhassan Mohammed]]></dc:creator>
            <pubDate>Thu, 09 Oct 2025 20:03:17 GMT</pubDate>
            <atom:updated>2025-10-09T20:03:17.960Z</atom:updated>
            <content:encoded><![CDATA[<p>Managing user accounts isn’t just about letting people sign up and log in. Sooner or later, you will face <strong>“that one user”</strong> who violates the rules, posts harmful content, or spams your platform like it’s their full-time job. Your first reaction? Probably to delete them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Eq_ibYHQAFmjbkb_" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>But here is the problem</strong></h4><p>Deleting a user <strong>distorts historical data</strong>. Posts vanish, review counts change, statistics break, and your analytics dashboard suddenly makes zero sense. That is why smart developers don’t delete users. They <strong>block and unblock</strong> them.</p><h4>The best part</h4><p>If you’re using Laravel with Laravel Breeze, implementing this is <em>ridiculously simple</em>.</p><h3>Why Blocking Beats Deleting</h3><p>Blocking allows you to:</p><ul><li>Preserve existing content and relationships (posts, reviews, comments).</li><li>Prevent the blocked user from logging in or interacting.</li><li>Easily reverse the action if needed.</li><li>Keep your database clean and analytics accurate.</li></ul><p>This means your system remains <strong>transparent and stable</strong>, even when dealing with problematic accounts.</p><h3>Let’s Build It: User Blocking in Laravel Breeze</h3><p>We’ll start from a typical Breeze authentication setup. If you don’t have it yet, install it quickly:</p><pre>composer require laravel/breeze --dev<br>php artisan breeze:install<br>npm install &amp;&amp; npm run dev<br>php artisan migrate</pre><p>Done. You’ve got a working authentication system.</p><h4>Step 1: Add a blocked Column to the Users Table</h4><p>Run a migration to track blocked users:</p><pre>php artisan make:migration add_blocked_to_users_table --table=users</pre><p>Then edit the migration:</p><pre>public function up(): void<br>{<br>    Schema::table(&#39;users&#39;, function (Blueprint $table) {<br>        $table-&gt;boolean(&#39;blocked&#39;)-&gt;default(false);<br>    });<br>}<br><br>public function down(): void<br>{<br>    Schema::table(&#39;users&#39;, function (Blueprint $table) {<br>        $table-&gt;dropColumn(&#39;blocked&#39;);<br>    });<br>}</pre><p>Run it:</p><pre>php artisan migrate</pre><p>Now each user has a <strong>blocked status</strong>.</p><h4>Step 2: Prevent Blocked Users from Logging In</h4><p>Open app/Http/Controllers/Auth/AuthenticatedSessionController.php (or use a custom middleware if you prefer) and add a quick check:</p><pre>if ($user-&gt;blocked) {<br>    throw ValidationException::withMessages([<br>        &#39;email&#39; =&gt; __(&#39;Your account has been blocked. Please contact support.&#39;),<br>    ]);<br>}</pre><p>This ensures blocked users can’t log in, no matter what.</p><h4>Step 3: Create Routes to Block/Unblock</h4><p>In routes/web.php:</p><pre>Route::middleware([&#39;auth&#39;, &#39;can:block-users&#39;])-&gt;group(function () {<br>    Route::post(&#39;/users/{user}/block&#39;, [UserController::class, &#39;block&#39;])-&gt;name(&#39;users.block&#39;);<br>    Route::post(&#39;/users/{user}/unblock&#39;, [UserController::class, &#39;unblock&#39;])-&gt;name(&#39;users.unblock&#39;);<br>});<br><br>//(Tip: use proper authorization gates to restrict who can block users.)</pre><h4>Step 4: Implement Controller Logic</h4><p>In app/Http/Controllers/UserController.php:</p><pre>public function block(User $user)<br>{<br>    $user-&gt;update([&#39;blocked&#39; =&gt; true]);<br>    return back()-&gt;with(&#39;status&#39;, &#39;User has been blocked&#39;);<br>}<br><br>public function unblock(User $user)<br>{<br>    $user-&gt;update([&#39;blocked&#39; =&gt; false]);<br>    return back()-&gt;with(&#39;status&#39;, &#39;User has been unblocked&#39;);<br>}</pre><p>Simple. Fast. Reversible.</p><h4>Step 5: Add Block/Unblock Buttons in the UI</h4><p>In your Blade template (e.g., resources/views/users/index.blade.php):</p><pre>@if(!$user-&gt;blocked)<br>    &lt;form action=&quot;{{ route(&#39;users.block&#39;, $user) }}&quot; method=&quot;POST&quot;&gt;<br>        @csrf<br>        &lt;button class=&quot;bg-red-500 text-white px-3 py-1 rounded&quot;&gt;Block&lt;/button&gt;<br>    &lt;/form&gt;<br>@else<br>    &lt;form action=&quot;{{ route(&#39;users.unblock&#39;, $user) }}&quot; method=&quot;POST&quot;&gt;<br>        @csrf<br>        &lt;button class=&quot;bg-green-500 text-white px-3 py-1 rounded&quot;&gt;Unblock&lt;/button&gt;<br>    &lt;/form&gt;<br>@endif</pre><p>A single click and you control user access without touching their data.</p><h4>Tip: Add Middleware for Extra Protection</h4><p>You can also stop blocked users from accessing other routes even if they’re somehow still authenticated.</p><p>Create middleware:</p><pre>php artisan make:middleware BlockedUser</pre><p>In handle method:</p><pre>if (auth()-&gt;check() &amp;&amp; auth()-&gt;user()-&gt;blocked) {<br>    auth()-&gt;logout();<br>    return redirect(&#39;/&#39;)-&gt;withErrors([&#39;Your account is blocked.&#39;]);<br>}<br>return $next($request);</pre><p>Register it in app/Http/Kernel.php and apply globally or to sensitive routes.</p><h3>Conclusion</h3><p>Blocking users instead of deleting them is like putting a noisy guest on mute instead of burning down your house.</p><p>With Laravel Breeze, this feature takes just a few lines of code and <strong>your data stays intact, your analytics stay accurate, and your sanity stays safe</strong>.</p><h3>Key Takeaways</h3><ul><li>Never delete users unless absolutely necessary.</li><li>Use a <strong>blocked </strong>column for reversible access control.</li><li>Protect login and routes with checks or middleware.</li><li>Keep your UI simple for admins.</li></ul><p>If you found this useful, give this article a clap, it helps more devs like you build smarter apps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=118853d165b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Best Middleware Practices That Make Laravel Unstoppable]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@bigboss200535/5-best-middleware-practices-that-make-laravel-unstoppable-9b9b16f0322f?source=rss-d9147c193ff0------2"><img src="https://cdn-images-1.medium.com/max/2600/1*34IdrbswzFWP2UZIBUftZw@2x.jpeg" width="3240"></a></p><p class="medium-feed-link"><a href="https://medium.com/@bigboss200535/5-best-middleware-practices-that-make-laravel-unstoppable-9b9b16f0322f?source=rss-d9147c193ff0------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@bigboss200535/5-best-middleware-practices-that-make-laravel-unstoppable-9b9b16f0322f?source=rss-d9147c193ff0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b9b16f0322f</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Alhassan Mohammed]]></dc:creator>
            <pubDate>Mon, 18 Aug 2025 20:28:34 GMT</pubDate>
            <atom:updated>2025-08-18T20:28:34.004Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Lazy Loading Images: Why & How to Implement It]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@bigboss200535/lazy-loading-images-why-how-to-implement-it-b0a8a3cc18a2?source=rss-d9147c193ff0------2"><img src="https://cdn-images-1.medium.com/max/2600/0*bKUUb97M13L6dsOK" width="6048"></a></p><p class="medium-feed-snippet">In today&#x2019;s fast-paced digital world, website performance is crucial. Users expect pages to load quickly, and search engines like Google&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@bigboss200535/lazy-loading-images-why-how-to-implement-it-b0a8a3cc18a2?source=rss-d9147c193ff0------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@bigboss200535/lazy-loading-images-why-how-to-implement-it-b0a8a3cc18a2?source=rss-d9147c193ff0------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0a8a3cc18a2</guid>
            <category><![CDATA[html]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Alhassan Mohammed]]></dc:creator>
            <pubDate>Sun, 17 Aug 2025 19:26:56 GMT</pubDate>
            <atom:updated>2025-08-17T19:26:56.387Z</atom:updated>
        </item>
    </channel>
</rss>