<?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 Esho Temiloluwa on Medium]]></title>
        <description><![CDATA[Stories by Esho Temiloluwa on Medium]]></description>
        <link>https://medium.com/@eshotemiloluwa?source=rss-fb5aa404b353------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*aZ-I0eoa3B5TzFamm_IMtA.jpeg</url>
            <title>Stories by Esho Temiloluwa on Medium</title>
            <link>https://medium.com/@eshotemiloluwa?source=rss-fb5aa404b353------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:54:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eshotemiloluwa/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[Error Handling Like a Pro: How Frontend Devs Can Keep Their UI from Falling Apart]]></title>
            <link>https://medium.com/@eshotemiloluwa/error-handling-like-a-pro-how-frontend-devs-can-keep-their-ui-from-falling-apart-a6d6d09a078c?source=rss-fb5aa404b353------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6d6d09a078c</guid>
            <dc:creator><![CDATA[Esho Temiloluwa]]></dc:creator>
            <pubDate>Thu, 21 Aug 2025 22:53:20 GMT</pubDate>
            <atom:updated>2025-08-24T08:56:30.196Z</atom:updated>
            <content:encoded><![CDATA[<h4>Because APIs fail, networks drop, fields change, and runtime errors happen — but your app shouldn’t crumble with them.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Oe5xeMC-QrzQHTuD30xNA.png" /></figure><p>You’ve built the feature, hooked it up to the backend, and everything looks flawless… until it doesn’t.</p><p>Suddenly:</p><ul><li>The API times out.</li><li>A field name changes.</li><li>The user’s Wi-Fi drops mid-request.</li></ul><p>Your beautiful UI? Gone. In its place: a blank page, a cryptic console error, or worse — nothing at all.</p><p>Here’s the harsh truth: <strong>users don’t care why it broke — they just know it looks broken.</strong><br> That’s where error handling comes in.</p><p>As frontend developers, our job isn’t just to render data when things go right. It’s to keep the UI graceful when things go wrong.</p><p>Let’s talk about how.</p><h3>1. Expect Failure, Not Perfection</h3><p>APIs will fail. Networks will cut out. Endpoints will misbehave.</p><p>Instead of coding for a “perfect world,” design for failure.</p><p>💬 <strong>Bad UI:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tChR2HDmWj15hawAeMh4rA.png" /><figcaption>Blank screen</figcaption></figure><p>💬 <strong>Good UI:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8GZAZnfoZyB85GFmV6WczQ.png" /></figure><p>👉 Build with the assumption that something <em>will</em> go wrong, and your app won’t embarrass you when it does.</p><h3>2. Handle Network Issues Gracefully</h3><p>Not all users are on lightning-fast internet. Some are on spotty café Wi-Fi or that dreaded 3G edge network.</p><p>Make their lives easier by:</p><ul><li>Showing <strong>loading states</strong> instead of frozen UIs.</li><li>Timing out requests and giving users a retry option.</li><li>Always providing a way forward — not just a dead end.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/977/1*ne32S6K8KxVP3JsC8iNHig.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*z_amcEDGOehiKaxCvowv8A.png" /></figure><p>That tiny reload button might save you a support ticket (and your sanity).</p><h3>3. Defend Against API Changes</h3><p>Here’s the classic scenario: backend renames userName to fullName, and suddenly your whole profile page explodes.</p><p><strong>Defensive coding tactics:</strong></p><ul><li>Use optional chaining: response?.user?.name</li><li>Provide fallbacks:</li></ul><pre>const username = response?.user?.name ?? &quot;Guest&quot;;</pre><ul><li>Validate responses before you render them.</li></ul><p>That way, one renamed field doesn’t tank your whole UI.</p><h3>4. Make Errors User-Friendly</h3><p>Here’s what <em>not</em> to show users:</p><pre>{ &quot;error&quot;: &quot;500 Internal Server Error&quot; }</pre><p>Here’s what they actually need:</p><ul><li>A friendly message: <em>“Something went wrong on our side.”</em></li><li>A suggestion: <em>“Please refresh the page or try again later.”</em></li><li>Consistency: the same error pattern everywhere, so users don’t feel lost.</li></ul><p>Think of error states as part of your UI design — not an afterthought.</p><h3>5. Log Smart, Not Loud</h3><p>Your users don’t want stack traces (error logs). But you do.</p><ul><li>Show clean, friendly errors in the UI.</li><li>Send detailed logs (stack traces, API responses) to monitoring tools like <strong>Sentry, LogRocket, or Datadog</strong>.</li><li>Keep errors actionable.</li></ul><p>This way, the app stays calm on the surface while you get the data you need under the hood.</p><h3>6. Use Error Boundaries (React and Beyond)</h3><p>Not all errors come from APIs. Sometimes, your code just… blows up.</p><p>In React, ErrorBoundary components catch those unexpected runtime errors and let you show a fallback instead of a blank screen.</p><p>Example:</p><pre>&lt;ErrorBoundary fallback={&lt;p&gt;Something went wrong.&lt;/p&gt;}&gt;<br>  &lt;UserProfile /&gt;<br>&lt;/ErrorBoundary&gt;</pre><p>Instead of the whole app crashing, the user sees a graceful message. Other frameworks have similar patterns — the idea is the same: <strong>don’t let one broken piece take down the entire UI.</strong></p><h3>7. Smarter Retry Strategies</h3><p>A “Retry” button is great. But sometimes, the app can do better.</p><ul><li><strong>Automatic retries with exponential backoff</strong> → try again after 1s, then 2s, then 4s…</li><li><strong>Abort after a few attempts</strong> → don’t hammer the backend endlessly.</li><li><strong>Tell the user what’s happening</strong> → e.g., “Reconnecting (attempt 2 of 3)…”</li></ul><p>This keeps the experience smooth, especially for users on flaky connections.</p><h3>8. Don’t Block the Whole UI</h3><p>Error handling isn’t all-or-nothing. Just because one part of the app fails doesn’t mean everything should.</p><p>💬 Example 1: If the “related products” API fails, you can still show the main product details.</p><p>💬 Example 2: If the image or video of a post doesn’t load, you can still show the post details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/977/1*ne32S6K8KxVP3JsC8iNHig.png" /></figure><p>This is called <strong>graceful degradation</strong> — essential stuff works, “nice-to-haves” fail quietly. Users won’t even notice half the time.</p><h3>9. Test Your Error States (Seriously)</h3><p>Most of us only test the “happy path.” Everything looks perfect — until production.</p><p>👉 Flip it: test your <strong>unhappy paths</strong> too.</p><ul><li>Use tools like <strong>MSW (Mock Service Worker)</strong> to simulate failed requests.</li><li>Turn off your Wi-Fi for a minute to see what happens.</li><li>Mock 500 errors, 404s, and timeouts in dev.</li></ul><p>You’ll quickly spot weak error handling before your users do.</p><h3>10. Keep It Secure</h3><p>One last thing: be careful what you show in your error messages.</p><p>Users don’t need to see stack traces, SQL errors, or raw API payloads. That’s not just confusing — it can leak sensitive info.</p><p>Rule of thumb:</p><ul><li><strong>User-facing errors</strong> → simple, friendly, non-technical.</li><li><strong>Dev-facing logs</strong> → detailed and sent to monitoring tools (if any are present).</li></ul><h3>Wrapping It Up</h3><p>Error handling isn’t glamorous. You won’t brag about your null checks or retry logic in your portfolio.</p><p>But it’s the difference between an app that feels fragile and one that feels polished.</p><p>When you plan for API failures, network hiccups, and runtime errors, your users never see chaos — they just see a product that “always works.”</p><p>Because in the end, good frontend isn’t about perfection.<br> It’s about <strong>resilience.</strong></p><p>👉 <em>Your turn:</em> What’s the worst “unhandled error” you’ve seen tank a UI — and how would you design around it today? Drop your stories in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6d6d09a078c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Collaborate with Backend Teams Like a Pro (Without Losing Your Sanity)]]></title>
            <link>https://medium.com/@eshotemiloluwa/how-to-collaborate-with-backend-teams-like-a-pro-without-losing-your-sanity-6ce57d46b70f?source=rss-fb5aa404b353------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ce57d46b70f</guid>
            <dc:creator><![CDATA[Esho Temiloluwa]]></dc:creator>
            <pubDate>Fri, 08 Aug 2025 22:55:11 GMT</pubDate>
            <atom:updated>2025-08-08T23:54:14.587Z</atom:updated>
            <content:encoded><![CDATA[<h4>Lessons from real-world dev life on working with backend teams, avoiding last-minute breakages, and shipping faster.</h4><figure><img alt="Frontend vs Backend" src="https://cdn-images-1.medium.com/max/1024/1*iSy5XzYPPXph6PtNhsLuKg.jpeg" /></figure><p>If you’ve ever merged your frontend branch, tested it… and watched everything fall apart because of a backend change, you know the pain.</p><p>APIs break. Endpoints get renamed. Data comes in a format that makes your beautiful UI cry.</p><p>But here’s the thing — it’s not just about code. The difference between constant chaos and smooth releases often comes down to <strong>how well frontend and backend teams work together</strong>.</p><p>So how do you go from “everything’s broken” to “everything just works”?<br> It’s not magic — it’s a handful of habits that make working with backend teams smoother, faster, and (dare I say) enjoyable.</p><p>Here’s where to start.</p><h3>1. Understand the Backend Developer Mindset</h3><p>If frontend is about what users <em>see</em>, backend is about everything they <em>don’t</em> — the invisible engine that keeps the product running.</p><p>Backend developers are juggling their own set of challenges:</p><pre>[Backend Dev Brain]<br>| Performance | Security | Data Structure | Scaling | Maintenance |</pre><ul><li><strong>Performance</strong> — making sure your app can handle thousands (or millions) of requests without choking.</li><li><strong>Security</strong> — keeping out the bad actors without slowing down the good ones.</li><li><strong>Data structure</strong> — wrestling with databases that don’t always match your ideal UI flow.</li></ul><p>When you understand these constraints, your requests sound less like demands and more like solutions.</p><p>💡 <em>Pro tip:</em> In your next stand-up, ask your backend teammate what their biggest performance bottleneck is on that project you’re currently working on. You’ll instantly see what matters most to them — and they’ll notice you care.</p><h3>2. Learn a Little “Backend”</h3><p>Once you get their world, it helps to speak their language. You don’t have to write SQL queries, but dropping a few key terms shows you know what’s up:</p><ul><li><strong>Payload size</strong> — “Can we shrink this 5MB JSON down to something leaner?”</li><li><strong>Rate limiting</strong> — “How many calls per minute before we hit the wall?”</li><li><strong>Caching</strong> — “Can we store this response so we’re not fetching it every time?”</li></ul><p>💬 <strong>Real dev chat:</strong></p><pre>Frontend Dev: Why is the image taking forever to load?  <br>Backend Dev: Payload’s too big.  <br>Frontend Dev: Cool, let’s compress and lazy-load it.  <br>Backend Dev: …I like you.</pre><p>See? Speaking “backend” doesn’t just make conversations easier — it builds trust. And trust makes collaboration <em>so</em> much smoother.</p><h3>3. Join API Planning Conversations Early</h3><p>One of the biggest mistakes frontend developers make? Waiting until the backend team “finishes” the API before joining the conversation.</p><p>By that point, you might find:</p><ul><li>The data shape is awkward.</li><li>Pagination is missing.</li><li>You need three separate calls to get what you need.</li></ul><p>When you’re in the room early, you can help avoid those headaches. Ask questions like:</p><ul><li>“What does the response look like?”</li><li>“How will errors be handled?”</li><li>“Will we support filtering or search from the start?”</li></ul><p>Early input means fewer rewrites later — and a happier you.</p><h3>4. Mock It ’Til You Make It</h3><p>Waiting for an endpoint before starting your work is a rookie move.<br>Instead:</p><ul><li>Use <strong>OpenAPI/Swagger</strong> docs to understand the contract.</li><li>Set up a <strong>mock server</strong> with tools like Postman, JSON Server, or MSW.</li><li>Build your UI with mock data, then swap in real endpoints when they’re ready.</li></ul><p>This keeps both sides moving forward without bottlenecks.</p><pre>Backend Team:  [API in progress]  <br>Frontend Team: [Mock API -&gt; Build UI] -&gt; Swap in real API</pre><p>That way, when the real API lands, it’s just a matter of swapping URLs — not scrambling to finish.</p><h3>5. Have a Change Plan</h3><p>Here’s the truth: APIs <em>will</em> change. Fields will get renamed. Endpoints will be reorganized. Error codes will shift.</p><p>💬 <strong>Real dev chat👎:</strong></p><pre>Frontend Dev: Did the /user endpoint just… disappear?  <br>Backend Dev: Oh yeah, we renamed it to /account yesterday.  <br>Frontend Dev: [angry laughter]</pre><p>The problem isn’t change — it’s <em>surprise</em> change.</p><p>Agree with your backend team on:</p><ul><li>How changes will be communicated.</li><li>How much notice you’ll get.</li><li>Who’s responsible for fixes.</li></ul><p>💬 <strong>Real dev chat👍:</strong></p><pre>Backend Dev: Hey, heads-up — we’re planning to rename /user to /account for clarity.  <br>Frontend Dev: Got it. When’s the change going live?  <br>Backend Dev: Next Wednesday. I’ll keep both endpoints running for a week so you can transition.  <br>Frontend Dev: Perfect, I’ll update the frontend by Friday and test both versions.  <br>Backend Dev: Cool — I’ll send over the updated API docs.  <br>Frontend Dev: You’re a lifesaver.</pre><h3>6. Be a Partner, Not Just a Consumer</h3><p>The best frontend devs don’t just take what the backend sends — they help shape it.</p><ul><li>Suggest better naming or data structures.</li><li>Share real user feedback that could improve the API.</li><li>Flag performance wins like caching or trimming payloads.</li></ul><p>When backend developers see you as a collaborator instead of a ticket-pusher, you get better APIs, faster fixes, and stronger releases.</p><h3>Final Thought</h3><p>Great frontend-backend collaboration isn’t about learning to write server code.<br> It’s about <strong>understanding each other’s world</strong>, speaking the same language, and working in sync from day one.</p><p>Do that, and you won’t just ship better features — you’ll make the whole product (and the team) stronger.</p><p>And who knows? The next time you push a big release, maybe your backend teammate will even buy you coffee.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ce57d46b70f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Psychology of Procrastination (And How I’m Finally Beating It)]]></title>
            <link>https://medium.com/@eshotemiloluwa/the-psychology-of-procrastination-and-how-im-finally-beating-it-e2fd53de492c?source=rss-fb5aa404b353------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2fd53de492c</guid>
            <dc:creator><![CDATA[Esho Temiloluwa]]></dc:creator>
            <pubDate>Thu, 24 Jul 2025 22:56:45 GMT</pubDate>
            <atom:updated>2025-07-25T03:16:40.088Z</atom:updated>
            <content:encoded><![CDATA[<p>You’re not lazy. You’re just overwhelmed, and there’s a science-backed way out.</p><p>I used to think I was just lazy. No matter how many to-do lists I made or how many times I told myself “today is the day,” I’d still find myself endlessly scrolling through YouTube, watching movies, or falling asleep when a deadline was breathing down my neck.</p><p>The guilt would eat at me. Then came the familiar burst of last-minute panic work, staying up until 3 AM, sometimes I wouldn’t even sleep at all (for someone who likes sleep), just because the deadline was very near. The cycle would start all over again the next week.</p><p>If this sounds like your life, you’re not alone.</p><p>As Nigerians, we are taught that hard work conquers all. “No food for lazy man,” our parents say. But what if I told you that procrastination isn’t about being lazy? It’s something much deeper, and once you understand it, you can finally break free.</p><h3>The Thing Nobody Tells You About Procrastination</h3><p>So I was reading this psychology paper (because apparently I procrastinate by reading about procrastination), and I came across this line that got me:</p><p><strong>Procrastination isn’t about time management. It’s about emotion management.</strong></p><p>Wait, what?</p><p>You know that feeling when your mom calls and you see her name on your phone, but you don’t pick up because you know she wants to talk about when you’re getting married? You’re not avoiding your mom. You’re avoiding that uncomfortable conversation.</p><p>That’s exactly what happens with procrastination. A researcher named Dr. Fuschia Sirois discovered that our brains tend to prioritize short-term comfort over long-term benefits when a task feels emotionally threatening.</p><p><strong>Common scenarios that hit close to home:</strong></p><ul><li>Avoiding that job application because “what if they reject me?”</li><li>Putting off calling that client or friend back because you’re worried about their feedback</li><li>Delaying starting your side business because it might not work out</li><li>Scrolling through Instagram instead of working on that presentation</li></ul><p>We’re not avoiding the work itself. We’re avoiding how the work makes us feel.</p><h3>What Didn’t Work (The Hard Truth)</h3><p>Let me save you some time. I tried most things the productivity gurus recommended:</p><ul><li><strong>Pomodoro timers</strong> ⏱️ (worked for a week, then back to square one)</li><li><strong>“Eat the frog” technique</strong> 🐸 (didn’t work for me for the most part)</li><li><strong>Fancy planners and habit apps</strong> (became another thing to procrastinate on)</li><li><strong>Pure willpower and self-discipline</strong> (spoiler: willpower runs out)</li></ul><p>These techniques focus on the symptoms, not the root cause. It’s like taking paracetamol for malaria — might help temporarily, but won’t cure the real problem.</p><h3>What Finally Worked (The Game Changers)</h3><p>Once I stopped trying to “fix” myself and started understanding myself, everything shifted. Here’s my blueprint:</p><h4>1. Name Your Fear</h4><p>Before starting any task, I pause and ask: <strong>“What exactly am I feeling right now, and what am I trying to avoid?”</strong></p><p>Sometimes it’s:</p><ul><li>Fear of not meeting my own high standards</li><li>Anxiety about what others will think</li><li>Feeling overwhelmed by the size of the task</li><li>Resentment about having to do it at all</li></ul><p>Just naming the emotion cuts its power in half. It’s like turning on the light in a dark room; the mosquitoes disappear.</p><h4>2. The “Just 5 Minutes” Rule</h4><p>This is pure psychology magic. Instead of telling myself “I need to finish this report today,” I say: <strong>“I’ll just work on this for 5 minutes.”</strong></p><p>Five minutes feels safe. Non-threatening. And here’s the beautiful part….once you start, momentum often takes over. Starting is literally 80% of the battle.</p><h4>3. Remove the Friction</h4><p>Make it stupidly easy to start:</p><ul><li><strong>Phone on airplane mode</strong> (or in another room entirely)</li><li><strong>Workspace ready the night before</strong> (laptop charged, documents open)</li><li><strong>Snacks and water within reach</strong> (no excuses to get up)</li><li><strong>Body doubling</strong> — work “with” a friend on video call, even if you’re doing different tasks</li></ul><p>Assume your future self will find excuses not to start, and remove those excuses ahead of time.</p><h4>4. Rewrite Your Story</h4><p>This was the real breakthrough. I stopped saying:</p><ul><li>“I’m terrible at deadlines.”</li><li>“I always leave things to the last minute.”</li><li>“I’m just not disciplined”</li></ul><p>And started saying:</p><ul><li>“I’m learning to work with my emotions, not against them.”</li><li>“I take small, imperfect actions consistently.”</li><li>“I’m building trust with myself one task at a time.”</li></ul><p>Your internal narrative becomes your reality. Change the story, change the outcome.</p><h3>Tools That Actually Work</h3><h4>The Emotional Check-In</h4><p>Before any important task:</p><ol><li>Write down what you’re feeling (scared, excited, overwhelmed, etc.)</li><li>Write down what you’re worried might happen</li><li>Write down one small step you can take right now</li></ol><h4>The Village System</h4><p>Find your accountability village:</p><ul><li>Text a friend when you’re starting work</li><li>Join virtual coworking sessions</li><li>Use apps like <a href="https://www.focusmate.com/">Focusmate</a> for body doubling</li><li>Create a WhatsApp group with other goal-oriented friends</li></ul><h4>The Real Talk</h4><p>If you’re stuck in the procrastination cycle, the problem isn’t your productivity system. It’s your relationship with discomfort.</p><p>We live in a culture that celebrates “grinding” and pushing through pain. But sometimes, the most productive thing you can do is understand why you’re resisting in the first place.</p><p>Be curious about your resistance instead of fighting it. Build systems that support your emotions first, and watch your productivity follow naturally.</p><p>The goal isn’t to become a productivity machine. It’s to become someone who can be gentle with themselves while still getting important things done.</p><p><strong>What’s the emotion behind your procrastination?</strong> Drop a comment and let’s figure this out together. Sometimes all we need is to know we’re not alone in this struggle.</p><p><em>If this resonated with you, share it with that friend who’s always saying “I’ll do it tomorrow.” They might need to read this today.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2fd53de492c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>