<?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 bishal on Medium]]></title>
        <description><![CDATA[Stories by bishal on Medium]]></description>
        <link>https://medium.com/@bishaller?source=rss-9f48957820d6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*K0A8AP6V1WN_1anxXLuANQ.jpeg</url>
            <title>Stories by bishal on Medium</title>
            <link>https://medium.com/@bishaller?source=rss-9f48957820d6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:17:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bishaller/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[Impact-Centered Designer?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@bishaller/impact-centered-designer-3a12e159d8e8?source=rss-9f48957820d6------2"><img src="https://cdn-images-1.medium.com/max/1470/1*zwna4Rx0oAdX11AOxCOCMQ.png" width="1470"></a></p><p class="medium-feed-snippet">The designer&#x2019;s goal is not just to do design for their users but to drive real impact within the product, team, and users of them.</p><p class="medium-feed-link"><a href="https://medium.com/@bishaller/impact-centered-designer-3a12e159d8e8?source=rss-9f48957820d6------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@bishaller/impact-centered-designer-3a12e159d8e8?source=rss-9f48957820d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a12e159d8e8</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-careers]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[bishal]]></dc:creator>
            <pubDate>Sun, 23 Feb 2025 07:13:11 GMT</pubDate>
            <atom:updated>2025-02-23T07:13:11.438Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Career Trap: Why Staying Too Long at One Job Could Hurt You]]></title>
            <link>https://medium.com/@bishaller/the-career-trap-why-staying-too-long-at-one-job-could-hurt-you-1ce41bac63cf?source=rss-9f48957820d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ce41bac63cf</guid>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[workplace]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[bishal]]></dc:creator>
            <pubDate>Mon, 06 Jan 2025 10:08:19 GMT</pubDate>
            <atom:updated>2025-01-06T10:08:19.931Z</atom:updated>
            <content:encoded><![CDATA[<p><em>TLDR: If you feel stagnant in your current situation, you should consider taking potential risks and the returns it could bring in.</em></p><p>In a world driven by constant innovation and intense competition, staying too long in a single company can sometimes hinder both your personal and professional growth.</p><p>I spent seven years working full-time at a small company, followed by a few years of part-time contributions. While this journey took me from Intern Designer to Product Lead, offering incredible opportunities for horizontal and vertical growth, I now wonder if diversifying my experience sooner could have placed me on an even more progressive career path.</p><p>While loyalty and stability are admirable qualities, when I look back, I can find compelling reasons why you should think twice before committing to a single employer for an extended period. Let me outline some key reasons why prolonged tenure at one org may not be in your best interest.</p><h3>1. Stagnation in Learning and Growth</h3><p>Initially, the learning curve was steep. Every project felt exciting; I even learned things outside my core skills like coding, business perspective, a little bit of people management, etc. But there came a point where I knew everything we did in the company, and now I was moving nowhere.</p><ul><li><strong>Tech limitation:</strong> Despite being a designer, I was sneaky in learning other aspects of product development, but it became pretty apparent that we could only work with a few stacks, and that never expanded in terms of projects or teams, so my tech knowledge was limited.</li><li><strong>Less motivation:</strong> I had reached a point where I had mastered my role, and then I couldn’t see things forward for a long time. Most things were repetitive and monotonous.</li><li><strong>Missing out:</strong> I have this habit of surfing LinkedIn and the internet daily before/after and between work. This would lead me to learn a lot of stuff outside work, but I also always created this FOMO to learn from diverse teams and the industry, and I would always be anxious about it.</li></ul><h3>2. Comfort is a slow poison</h3><p>Comfort can silently undermine our growth. I experienced this firsthand at work — without realizing it, I had settled into familiar patterns that made me resistant to change.</p><p>While this comfort provided temporary satisfaction, it gradually eroded my willingness to take risks and push boundaries. As I was well settled within the company, and no signs could shake my position, the job felt safe, but it was actually holding me back from reaching my full potential.</p><p>A dangerous complacency set in, dulling my drive to innovate and excel. Even worse, I found myself interacting with the same small circle of colleagues, missing chances to build new relationships and discover fresh opportunities.</p><h3>3. Market Value Decreases Over Time</h3><p>It took me too long to realize that my value in the job market depends heavily on my ability to adapt and bring fresh perspectives. While I had much experience, it was too consolidated for the broader market need.</p><p>Once, a recruiter asked me why I had worked at the same company for so long. I paused, realizing I didn’t have a compelling answer. That moment made me reflect on whether I had truly challenged myself to grow or if I had become too comfortable in a familiar setting. He then softly raised a concern about whether I am truly adaptable to a different workplace culture or not. That gave me a little heartache.</p><p>Without exposure to diverse challenges, I wondered if my skills might just be stagnant or outdated. There’s also the risk that potential employers would doubt my ability to navigate and thrive in varied environments.</p><p>This realization has made me more conscious of how my long tenure in one place might be perceived despite my years of experience.</p><h3>4. Lack of Diverse Experiences</h3><p>Most career advisors suggest that your “optimal” time to work at a company is generally between 3 and 5 years. I now understand that staying in one place for over seven years has limited my exposure to diverse experiences.</p><p>By not switching jobs, I’ve missed tons of opportunities. Each company has its unique way of tackling challenges, and I could have learned multiple approaches to problem-solving and different business models. Most importantly, job changes could have helped me build a more compelling resume that showcases my adaptability and ability to thrive in different environments.</p><p>These varied experiences aren’t just resume points — they’re valuable learning opportunities that shape a more well-rounded professional perspective.</p><h3>5. Potential for Burnout</h3><p>I’ve discovered that spending too many years in the same environment isn’t just about career stagnation — it’s also taking a toll on my well-being.</p><p>The constant exposure to familiar challenges, unchanging team dynamics, years and years of biases piling up, and predictable office politics had slowly drained my enthusiasm. I found myself going through the motions.</p><p>My creative spark had definitely dimmed, and I was solving problems with old solutions rather than innovative approaches. I wonder even if I was solving problems.</p><p>Most concerning is how this stagnation had begun affecting my mental health and overall satisfaction with work. What once felt like stability had transformed into a subtle but persistent drain on my professional fulfillment.</p><h3>6. 🤑 Financial Advancement &amp; Other Benefits</h3><p>While my internal promotions were great, I now realize that stepping outside my comfort zone could have led to even greater growth. For instance, exploring opportunities in larger organizations or startups might have exposed me to different challenges and innovative ways of thinking. Taking calculated risks, like switching industries or roles, could have expanded my skill set and accelerated my career progression.</p><p>Most of the time, companies hiring externally often offer more competitive pay. There were times when I was offered a handsome increment from big companies around me. In addition, I could see that new roles frequently included enhanced perks. Considering that I did fairly well, I could have negotiated those perks, too.</p><h3>Conclusion</h3><p>While working at the same company has many advantages, I would suggest otherwise to keep yourself sharp. To ensure continuous growth, personally, professionally, and financially, it’s essential to assess your career trajectory regularly. Don’t let fear or comfort hold you back from exploring new opportunities. After all, the world outside your current company might just offer the challenge and growth you have always been waiting for.</p><p>Hi, I’m Bishal, a product designer trying to write some articles by sharing thoughts and opinions. <a href="https://medium.com/@bishaller">Follow me here for more</a>.</p><p>Or, find me on <a href="https://www.linkedin.com/in/bishaller/">LinkedIn</a> or my website: <a href="https://bishal.cc/">https://bishal.cc/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ce41bac63cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why do you fail as a Frontend Developer?]]></title>
            <link>https://medium.com/@bishaller/why-do-you-fail-as-a-frontend-developer-ab90e1de373a?source=rss-9f48957820d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab90e1de373a</guid>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[bishal]]></dc:creator>
            <pubDate>Wed, 10 Jun 2020 14:56:55 GMT</pubDate>
            <atom:updated>2020-06-10T15:01:55.239Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G5CCzWC0ne4-yzOd6_GW3g.png" /></figure><p><em>“Frontend Developer” (or a UI Developer) sums a lot of stuff within the title. By this term, I mean those developers who work around Web HTML, CSS, Javascript. Those who work on iOS &amp; Android App Development can find this article useful.</em></p><h3>#1. You Lack Planning</h3><p>Most of us are in a hurry to go nowhere but in a rush to wrap up that project, which you haven’t started yet. Sometimes, you know nothing about the project, but you’ve reached the halfway and probably stuck. That restless behavior leads you to poke the Designer or the Project Lead to ask stuff they should have explained before or you should have asked. That’s pathetic; you keep on revolving around or redoing things. However, you are not alone in this downhill race; this is the most common mistake FrontEnd Developers make.</p><blockquote>“Give me six hours to chop down a tree, and I will spend the first four sharpening the axe.” — Abraham Lincoln</blockquote><p>Planning brings magic to your table. It might be a tedious thing to do, But in the long run, you’ll save much time, write less code, act smart, speed up your workflow, may get promoted, and so on. The idea here is to evolve yourself in every possible angle.</p><p>It would help if you learned to play smart. First of all, analyze the project on your own. If you’re a lucky developer, your Designer may have explained to you with plenty of notes and a smooth hand-off. Whether or not, try understanding the project and list out your assumptions and questions and how you’re going to plan out the project. Have a conversation with your fellow Designer before you start the project and make sure you know everything about the project. Get your stuff ready and get to work. Working on a team is no different. More the coders, more ideas, better code, and a responsible you lead by healthy communication. Create your process and never jump off. Better for you.</p><h3>#2. You Hate Designers.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*UhwpDS67bI26mYeKwwMelw.gif" /><figcaption>I hate you GIF from Tenor.</figcaption></figure><blockquote>If you’re a Front-End Developer, you’re not a Front-End Developer. And, that’s not a joke.</blockquote><p>The above statement may sound crazy, but that’s the truth. You’re a Designer who Designs with HTML, CSS, &amp; Javascript rather than using those fancy tools, Sketch, Figma, Invision, XD, and so on. It’s evident that whatever you code, whether it’s semantic or a mess, the end user always cares about the experience, visuals, or the actual Design elements on the screens that serve value.</p><p>You may be asking yourself, What the hell has this Designer made? There are Designers who off-the-grid Designs. But is it worth screaming? What if I can give a thought from a Designer’s perspective? Is there a solution? Or should I break his nose?</p><p>This unusual co-working behavior is a common problem in a Designer — Coder world. Every one or the other is there to make a mistake. Rather than misunderstandings, you should embrace the good stuff each makes and focus on improvising the errors, all of which depend on your communication skills.</p><p>On the other hand, even if you’re a Frontend Developer, you should know Design. The basics or the concept, how Design works is more than enough. It will help us to build better products and makes life easier not only for Designer/Developer but also for the users who use our products. However, this is not mandatory. If only you understand Design, Designers would love you.</p><h3>#3. You know less &amp; do more.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nwMF9B9ZZBfRgN2Ud9U5Rg.jpeg" /><figcaption>Image Source: <a href="https://www.reddit.com/r/ProgrammerHumor/comments/852og2/only_god_knows/">https://www.reddit.com/r/ProgrammerHumor/comments/852og2/only_god_knows/</a></figcaption></figure><p>To call yourself a Frontend Developer — you must be proficient with the basics and know the root of HTML, CSS &amp; JS. And I’m not talking Foundation, Bootstrap, HAML or SASS. Just Plain HTML &amp; CSS that made those frameworks? Question yourself, Can I build or engineer anything- Frontend without a framework? Or, Can I stop copying the code from Stackoverflow? Most of the Frontenders I have faced in my life kick-off by watching a few tutorials and then a Full Full Full Stop. Learning should never stop. Mastering your code is the most. The only suggestion is — Read about everything, Learn and use selectively.</p><h3>#4. Your Interface is Dead.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*ipzxdJxTKgzM75pYxvzR5w.gif" /><figcaption>A GIF from giphy</figcaption></figure><h4>Users don’t just see your website and go. They put opinions, observe, feel, create assumptions, keep expectations, and react! — They Interact.</h4><p>Stop styling dead buttons and blame the Designer for not providing the states. If you still want to, bye-bye. That’s why you fail. There are Designers whom you’d love to hate around, and please don’t try to copy their habit. Googling “button hover” will throw you trillions of examples on what a hover state could look like. Turn yourself into an Interaction Superstar.</p><h3>#5. You Don’t Cope with Criticism</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*rQy--vLQ_H4GDCqc_04BiQ.gif" /><figcaption>A GIF from giphy</figcaption></figure><p>None of us enjoy getting criticized. Human beings have a built-in feature to enjoy being right and feel a sense of hurt when we’re wrong. Although we’re generally drawn to like-minded people, criticism is something that can help you grow and raise to a Mark. Never take the QA’s feedback as an insult. Take is as a compliment to improve yourself. If someone’s wrong, make an effort to explain what’s right. Or, even if you don’t do so, at least don’t harm your mental state and instead keep the same effort to craft a better you.</p><h3>Conclusion</h3><p>And, hundred of thousand reasons more.</p><p>It’s okay if you fail, we all should learn from our mistakes. If you wish to see a version of How to succeed as a Frontend Developer, hit me up with a few claps.</p><p>Thanks!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab90e1de373a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>