<?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 Shreyas Deshpande on Medium]]></title>
        <description><![CDATA[Stories by Shreyas Deshpande on Medium]]></description>
        <link>https://medium.com/@deshpandeshreyas434?source=rss-997facf947d4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*78_nNntijKpDuq2J</url>
            <title>Stories by Shreyas Deshpande on Medium</title>
            <link>https://medium.com/@deshpandeshreyas434?source=rss-997facf947d4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:41:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@deshpandeshreyas434/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[You Don’t Need More Time — You Need Better Control Over It]]></title>
            <link>https://medium.com/@deshpandeshreyas434/you-dont-need-more-time-you-need-better-control-over-it-ad763b0569f6?source=rss-997facf947d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad763b0569f6</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[soft-skills]]></category>
            <dc:creator><![CDATA[Shreyas Deshpande]]></dc:creator>
            <pubDate>Wed, 07 Jan 2026 17:45:36 GMT</pubDate>
            <atom:updated>2026-01-07T17:45:36.580Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/275/0*-j0unoEiXjD0Hwni" /></figure><h3>You Don’t Need More Time — You Need Better Control Over It</h3><p>Everyone believes they are running out of time. Students feel it before exams, professionals feel it before deadlines, and creators feel it when consistency breaks. The truth is, time itself is never the enemy. The real struggle comes from how unplanned decisions slowly take control of our day.</p><p>Consider a common example. You open your laptop to complete an important task, thinking it will take only thirty minutes. A notification appears, you reply quickly, then another message comes in. After checking emails and scrolling for a few minutes, an hour passes. The task is still incomplete, and stress quietly replaces focus. This happens not because the task was difficult, but because time was never protected.</p><p>One of the simplest ways to manage time better is to decide your priority before the day begins. When you start a day without clarity, urgent tasks steal attention from important ones. For example, finishing one high-impact task early in the morning often brings a sense of control for the entire day. Many people notice that when the most demanding task is done first, smaller tasks feel easier and less overwhelming.</p><p>Another real-life situation appears during meetings or group work. Poor time management shows up as last-minute preparation or delayed responses. On the other hand, someone who sets aside focused time to prepare in advance speaks with confidence and finishes work without panic. This habit builds trust. People begin to rely on you, not because you work longer hours, but because you respect deadlines.</p><p>Managing time also means learning when to stop. Many professionals burn out because they stretch work into late nights, believing it proves dedication. In reality, productivity drops when rest is ignored. A simple but effective tip is to define a clear end to the workday. Even stepping away for a short walk or break can reset the mind and improve focus when you return.</p><p>Distractions are another silent challenge. Social media and constant notifications break concentration into pieces. One practical approach is to silence notifications for a fixed time and work without interruptions. Even sixty minutes of deep focus can achieve more than three distracted hours. People who practice this regularly often feel less exhausted, despite working fewer hours.</p><p>Time management is not about controlling every minute; it is about reducing regret at the end of the day. When you plan realistically, forgive delays, and improve slowly, discipline becomes natural. Small habits, repeated daily, create long-term balance and growth.</p><p>In the end, managing time is an act of self-respect. It reflects how seriously you take your goals, your energy, and your future. When time is handled with intention, progress stops feeling forced and starts feeling steady.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad763b0569f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Your Frontend Breaks on Mobile — Common Responsive Mistakes]]></title>
            <link>https://medium.com/@deshpandeshreyas434/why-your-frontend-breaks-on-mobile-common-responsive-mistakes-2f53aa4071d3?source=rss-997facf947d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f53aa4071d3</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[responsive-web-design]]></category>
            <category><![CDATA[mobile-friendly]]></category>
            <dc:creator><![CDATA[Shreyas Deshpande]]></dc:creator>
            <pubDate>Sat, 06 Dec 2025 09:22:40 GMT</pubDate>
            <atom:updated>2025-12-06T09:22:40.027Z</atom:updated>
            <content:encoded><![CDATA[<p>ux</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5b3U2rnlAw8t5BQ1bgygXQ.png" /></figure><h3>Why Your Frontend Breaks on Mobile — Common Responsive Mistakes</h3><p>If you’ve ever built a website and opened it on your phone only to see things <strong>overlapping, overflowing, or misaligned</strong>, you know the frustration.</p><p>Responsive design isn’t just a buzzword — it’s how you ensure your site works <strong>on every screen</strong>, from tiny mobile phones to huge desktop monitors.</p><p>I’ve made all the mistakes so you don’t have to. Here’s a deep dive into why frontends break on mobile and how to fix them.</p><h3>1. Fixed Widths</h3><p>Many beginners set containers with <strong>fixed pixel widths</strong>, like:</p><pre>.container {<br>  width: 1200px;<br>}</pre><p><strong>Problem:</strong> On a phone, 1200px is wider than the screen, causing horizontal scrolls or clipped content.</p><p><strong>Solution:</strong> Use <strong>relative units</strong>:</p><pre>.container {<br>  max-width: 100%;<br>  padding: 0 15px;<br>}</pre><p>Or use vw (viewport width) to scale dynamically:</p><pre>.container {<br>  width: 90vw;<br>}</pre><p><strong>Tip:</strong> Always combine max-width with relative units for better flexibility.</p><h3>2. Ignoring Media Queries</h3><p>Without media queries, your design <strong>looks perfect on desktop but breaks on mobile</strong>.</p><p><strong>Example:</strong></p><pre>nav ul {<br>  display: flex;<br>  justify-content: space-between;<br>}</pre><p>This works on wide screens but on mobile, menu items overflow.</p><p><strong>Solution:</strong></p><pre>@media (max-width: 768px) {<br>  nav ul {<br>    flex-direction: column;<br>    gap: 10px;<br>  }<br>}</pre><p><strong>Pro Tip:</strong> Start <strong>mobile-first</strong>: write styles for small screens first, then enhance for larger screens.</p><h3>3. Images Not Responsive</h3><p>Using fixed-width images breaks layouts on smaller screens:</p><pre>&lt;img src=&quot;banner.jpg&quot; width=&quot;600&quot;&gt;</pre><p><strong>Problem:</strong> The image doesn’t shrink, causing overflow.</p><p><strong>Solution:</strong> Use CSS to make images scale:</p><pre>img {<br>  max-width: 100%;<br>  height: auto;<br>  display: block;<br>}</pre><p>This ensures images resize proportionally on all devices.</p><h3>4. Overuse of Floats</h3><p>Floats were common in old layouts but are <strong>unreliable for responsiveness</strong>.</p><p><strong>Problem:</strong> Nested floats often collapse, causing broken layouts.</p><p><strong>Solution:</strong> Use <strong>Flexbox</strong> or <strong>CSS Grid</strong>.</p><p><strong>Flexbox Example:</strong></p><pre>.card-container {<br>  display: flex;<br>  flex-wrap: wrap;<br>  gap: 15px;<br>}<br>.card {<br>  flex: 1 1 200px; /* grow, shrink, base width */<br>}</pre><p><strong>Result:</strong> Cards adjust automatically based on screen size.</p><h3>5. Fixed Font Sizes</h3><p>Using px for font sizes often leads to <strong>tiny text on mobile</strong>:</p><pre>h1 {<br>  font-size: 32px;<br>}</pre><p><strong>Better:</strong> Use rem or em:</p><pre>h1 {<br>  font-size: 2rem; /* scales with root font size */<br>}</pre><p>Or use <strong>media queries</strong> to adjust font size:</p><pre>@media (max-width: 480px) {<br>  h1 {<br>    font-size: 1.5rem;<br>  }<br>}</pre><h3>6. Ignoring Viewport Meta Tag</h3><p>Many beginners forget this <strong>critical HTML tag</strong>:</p><pre>&lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1.0&quot;&gt;</pre><p>Without it, mobile browsers <strong>zoom out</strong>, making your responsive CSS useless.</p><h3>7. Large Fixed Margins or Padding</h3><p>Margins/padding in px that work on desktop may <strong>push content off-screen</strong> on mobile.</p><p><strong>Solution:</strong> Use relative units or media queries:</p><pre>.container {<br>  padding: 5%;<br>}</pre><h3>8. Testing on Only One Device</h3><p>A common mistake is testing on your laptop only.</p><p><strong>Tip:</strong></p><ul><li>Use Chrome DevTools → Toggle Device Toolbar</li><li>Test on multiple devices, screen sizes, and orientations</li><li>Check landscape and portrait modes</li></ul><h3>9. Common Quick Fix Checklist</h3><p>When your layout breaks:</p><ol><li>Check <strong>viewport meta tag</strong></li><li>Use <strong>relative widths</strong> (%, vw)</li><li>Replace floats with <strong>Flexbox/Grid</strong></li><li>Make images <strong>max-width: 100%</strong></li><li>Adjust font sizes with rem or em</li><li>Add <strong>media queries</strong> for small screens</li><li>Test <strong>actual devices or simulators</strong></li></ol><h3>Key Takeaway</h3><p>Responsive design isn’t just adding a few @media rules. It’s a <strong>mindset</strong>:</p><ul><li>Think about <strong>small screens first</strong></li><li>Use flexible units</li><li>Test constantly</li></ul><p>Once you master these, your frontend will work <strong>smoothly on any device</strong>, avoiding frustration for both you and your users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f53aa4071d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HTML, CSS, JavaScript — What Actually Matters for Beginners?]]></title>
            <link>https://medium.com/@deshpandeshreyas434/html-css-javascript-what-actually-matters-for-beginners-04bd03a61bf4?source=rss-997facf947d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/04bd03a61bf4</guid>
            <category><![CDATA[html]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[js]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Shreyas Deshpande]]></dc:creator>
            <pubDate>Sat, 06 Dec 2025 08:00:46 GMT</pubDate>
            <atom:updated>2025-12-06T08:00:46.990Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e1MDluwbwd2cvawjP2MsOg.jpeg" /></figure><h3>HTML, CSS, JavaScript — What Actually Matters for Beginners?</h3><p>If you’re starting your web development journey, you’ve probably heard this advice a thousand times:</p><p><strong>“Learn HTML, CSS, and JavaScript.”</strong></p><p>But nobody explains <strong>which parts actually matter</strong>, or what beginners should focus on first.<br> When I started, I wasted weeks learning things that never helped me in real projects.</p><p>Later — after building real websites and client projects — I realized something important:</p><p><strong>You don’t need to learn everything.<br> You need to learn the right things.</strong></p><p>This blog is exactly that:<br> the clear, practical roadmap I wish I had on Day 1.</p><h3>1. HTML — The Structure (Not Design)</h3><p>HTML is simply the skeleton of your webpage.<br> Most beginners waste time memorizing 200+ tags. You only need a few.</p><h3>What actually matters:</h3><ul><li>Semantic tags</li><li>Basic structure</li><li>Forms</li><li>IDs &amp; classes</li><li>Accessibility basics</li></ul><h3>Simple mental model:</h3><pre>&lt;html&gt;<br>  &lt;head&gt; = SEO, links, metadata<br>  &lt;body&gt; = Everything users see<br>&lt;/body&gt;</pre><h3>Useful semantic tags:</h3><pre>&lt;header&gt; &lt;nav&gt; &lt;main&gt; &lt;section&gt;<br>&lt;article&gt; &lt;footer&gt; &lt;form&gt; &lt;button&gt;</pre><p>If your HTML structure is clean, everything else becomes easier.</p><h3>2. CSS — Layout First, Fancy Later</h3><p>CSS feels confusing until you stop trying to learn everything.<br> Focus on layouts and responsive design first.</p><h3>Core CSS concepts that matter:</h3><ul><li>Flexbox</li><li>Grid</li><li>Media queries</li><li>Positioning</li><li>Box model</li><li>Responsive units (%, rem, vw, vh)</li></ul><p>These are used in <strong>every</strong> real project.</p><h3>Visual diagram (Medium-friendly):</h3><pre>[ main container ]<br>|------------------------------------------------|<br>|  item 1   item 2   item 3   item 4             |<br>|------------------------------------------------|<br>        (flex-direction: row)</pre><p>Ignore animation, shadows, or advanced selectors in the beginning.<br> Master <strong>layout</strong>, and the rest becomes easy.</p><h3>3. JavaScript — The Brain of Your Page</h3><p>JavaScript controls how your page behaves.<br> It’s powerful but not as scary as it looks.</p><h3>The parts that actually matter:</h3><ul><li>Variables</li><li>Functions</li><li>Events</li><li>DOM manipulation</li><li>Arrays &amp; Objects</li><li>Fetch API</li><li>Basic conditions &amp; loops</li></ul><h3>A simple example:</h3><pre>&lt;p id=&quot;msg&quot; style=&quot;display:none;&quot;&gt;Hello Developer 👋&lt;/p&gt;<br>&lt;button onclick=&quot;toggle()&quot;&gt;Show/Hide&lt;/button&gt;</pre><pre>&lt;script&gt;<br>  function toggle() {<br>    const m = document.getElementById(&quot;msg&quot;);<br>    m.style.display = (m.style.display === &quot;none&quot;) ? &quot;block&quot; : &quot;none&quot;;<br>  }<br>&lt;/script&gt;</pre><p>This tiny example shows the real power of HTML + CSS + JS together.</p><h3>4. How These Three Work Together</h3><p>Think of a webpage like building a house:</p><pre>HTML = structure / walls<br>CSS  = design / paint<br>JS   = electricity / switches</pre><h3>Simple diagram:</h3><pre>[ HTML ] → creates the button<br>[ CSS ] → styles the button<br>[ JS  ] → makes the button work</pre><p>They are three tools, not three separate subjects.</p><h3>5. What I Wish I Knew Earlier</h3><p>Here are honest lessons from my early days:</p><ul><li>You don’t need to master everything.</li><li>Build small projects from Day 1.</li><li>Google is part of the job, not cheating.</li><li>Your first 20 projects will look ugly. That’s normal.</li><li>You get better by doing, not by watching tutorials.</li><li>Don’t compare your code with senior developers.</li></ul><p>Learning becomes easier when you stop chasing perfection.</p><h3>6. A Beginner-Friendly Roadmap</h3><p>Here’s a simple 2-month roadmap you can follow.</p><h3>Weeks 1–2 → HTML</h3><ul><li>Basic tags</li><li>Semantic structure</li><li>Forms</li><li>Accessibility</li></ul><h3>Weeks 3–4 → CSS</h3><ul><li>Flexbox</li><li>Grid</li><li>Media queries</li><li>Common layouts</li></ul><h3>Weeks 5–6 → JavaScript</h3><ul><li>DOM</li><li>Functions</li><li>Events</li><li>Arrays &amp; Objects</li><li>fetch()</li></ul><h3>Weeks 7–8 → Build 3 small projects</h3><ul><li>A responsive website</li><li>A card/dashboard layout</li><li>A JavaScript app (todo, booking, calculator)</li></ul><p>This is enough to start doing freelance work or applying for internships.</p><h3>Final Thoughts</h3><p>HTML, CSS, and JavaScript aren’t difficult — they’re simply misunderstood.<br> Most beginners jump into frameworks too early, and end up overwhelmed.</p><p>If you focus on:</p><ul><li><strong>HTML → structure</strong></li><li><strong>CSS → layout</strong></li><li><strong>JavaScript → behavior</strong></li></ul><p>…you’ll progress faster than most beginners.</p><p>Once your foundations are solid, picking up frameworks like React or Node becomes 10× easier.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=04bd03a61bf4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>