You’ve probably felt that anxiety of seeing new technologies blowing up on X/Twitter or LinkedIn and thinking, “Do I need to learn this now? Will I fall behind if I don’t?” This feeling of tech FOMO (Fear of Missing Out) is real and can be paralyzing.

I’ve seen countless technologies born with revolutionary promises and die within a few months. Professionals invest hundreds of hours in frameworks that never gain market adoption. And people ignore genuine trends due to excessive cynicism, falling behind.

The truth is there’s no magic formula. But there are signs, patterns and strategies that can help us make more consistent decisions.

Signs of Real Traction vs. Hype

Let’s start with the most important thing: how do you differentiate between superficial social media buzz and genuine market adoption of technology?

The Social Media Theater

X/Twitter and LinkedIn have become stages for tech performance. Influencers gain followers by talking about the “next big thing.” Marketing companies pay for sponsored posts disguised as genuine opinions. Developers seek visibility by betting on technologies that seem innovative.

Note that these platforms have value. Often, that’s where we first hear about technologies that become important. The problem is that’s also where we hear about hundreds of others that never go beyond buzz.

Think about how many times you’ve seen enthusiastic posts about some technology that promised to “change everything” and, six months later, nobody was talking about it anymore.

We have a somewhat recent case with the metaverse: major initiatives, companies selling spaces, billions in investments, and when generative AI arrived, all that metaverse hype went down the drain. Nowadays, nobody even talks about it anymore. That’s the nature of social media; the attention cycle is short, and the next hype is always just one post away.

That’s why I developed the habit of not reacting immediately to what I see on social media. I used to panic when I noticed I was missing the train of modernity. Today, I’m more cautious; I take notes, observe, but don’t invest significant time until I see more concrete signs.

I remember the days of Visual Basic and the early days of C#, where I noticed an interesting pattern in Microsoft products. It was usually from version 6.0 that a tool reached maturity or disappeared.

Visual Basic 6.0, for example, was the peak and the end of the line for that VB model. C# followed a similar path; version 6.0 brought the stability the language needed. Then came a transition period with .NET Framework (up to version 7.3), followed by a “rebirth” in .NET Core starting with C# 8.0, and today we’re at C# 14 running on .NET 10.

Indicators of Genuine Adoption

I use two indicators about technology usage by observing the market:

Company Hiring

Companies don’t hire for technologies they don’t intend to use. When you start seeing job postings on platforms like LinkedIn, Indeed or Glassdoor asking for experience in a particular technology, it means there’s real demand.

But be careful. It’s not enough to see a few postings. What matters is observing the trend. Is technology appearing in more job postings over time? Is it being requested by companies from different sectors and sizes? Is it appearing in senior positions or just in startup experiments?

The 2-Year Filter

This is probably the most straightforward and most powerful strategy: wait at least two years before diving deep into any new technology.

Why 2 Years?

It’s not a magic number, but there’s logic behind it. The first year of any new technology is the honeymoon period. There will be enthusiasm, hype and excited early adopters. The real problems haven’t appeared yet because nobody has had enough time to find them.

In the second year, reality starts to show. The first production projects reveal limitations. Companies that adopted early begin sharing their experiences, including the pain points. Competitors have time to react and offer alternatives.

If technology is still growing and being adopted after two years, it has passed trial by fire. It survived the initial hype cycle, proved to have real value and developed a sustainable community. It’s a much safer bet.

Exceptions to the Rule

Of course, no rule is absolute. There are situations where it makes sense to adopt technology earlier:

• When you work in a cutting-edge field and being at the forefront is part of your competitive advantage, it may make sense to take more risks. AI startups, for example, frequently need to adopt emerging technologies before they mature.

• When technology solves a critical problem you have right now, and there are no mature alternatives, sometimes there’s no choice but to accept the risk.

• When you have resources to invest in learning, even if technology goes nowhere, like personal projects or hackathons, the cost of being wrong is low.

But for most professional decisions, especially those involving production projects or long-term career development, the two-year filter remains an excellent option.

How to Follow Without Diving In

Waiting two years doesn’t mean completely ignoring technology during that period. It means following from a distance, being aware of what’s happening, without investing significant time in deep learning.

In practice, this can mean reading introductory articles to understand the basic concepts, following the leading developers and the official account on X/Twitter, watching one or two introductory talks, adding some repositories to your favorites to keep track of, and participating in superficial discussions when the topic comes up.

This lighter following approach lets me stay informed as technology matures without wasting hundreds of hours if it doesn’t take off.

The Complexity Bias Trap

There’s a trap around our necks. Sometimes, we choose complex technologies because they seem more sophisticated or because they challenge us intellectually. But unnecessary complexity is a cost, not a benefit.

The right question isn’t “Is this technology impressive?” but “Is this technology appropriate for my problem?” Often, the simplest solution is the best.

Kubernetes is incredible, but do you need it for your application? Microservices are elegant, but does your project justify the complexity? The most advanced technology isn’t always the most suitable.

Conclusion

The best strategy for identifying technologies worth pursuing is to combine cautious observation, analysis of concrete adoption signals and patience to let time filter what’s truly relevant.

What we can always rely on is maintaining a growth mindset and learning from new technologies; even if they disappear, we’ll still carry a bit of their way of thinking into the next phase of life’s game.

And you? How many times have you seen technologies emerge, disappear or continue to this day?

I read a post on Reddit the other day from an enterprise UX designer. They’d just landed a new gig with more money and a lead title that felt like a promotion. On paper, it sounded like progress. But the reality hit fast. Just patch-and-fix work. Migrating Excel sheets into out-of-the-box tools and calling it innovation.

What they wrote stayed with me:

“My design soul feels like it’s dying. No passion, no creative spark. I feel like I’m drifting further and further from what drew me into UI/UX in the first place.”

That feeling is more common than people admit, and it often hits right after you climb the ladder.

The Climb That Feels Like Progress

Most designers climb the career ladder for understandable reasons. You get promoted into a lead position or move from startups into enterprise UX. You gain a bigger title, more stability, better pay and benefits.

With that comes the promise of impact and influence.

The early days seem fine. You’re suddenly exposed to large programs and complex systems. You deal with new domains and teams spread across regions. You sit in strategy meetings. You meet senior leaders. The climb gives you a sense of elevation. It feels like the right choice. It feels like progress.

You tell yourself you’re finally doing meaningful work. You’ve earned a seat at the table.

But there’s a quiet trade-off most people don’t notice. Only when you’re far enough up that you start feeling down.

The Valley of Despair

At first it’s the small things: more meetings, more alignment sessions and more approvals.

Your solution is defined by licensing agreements rather than user needs. Requests that are really just vendor configurations. Your influence shrinks even as your title grows. You feel the ceiling closing in.

The spark that pulled you into design—the curiosity, creativity and craft—starts to fade.

You still care. You still want to do great work. But the environment around you wants the result, not the process.

And then the questions arrive:

• Is this really how design works?
• Is this what I want to do?
• Where’s my passion?

It’s not a sign that something is wrong with you. It’s a sign that something’s happening to you.

And it has everything to do with scale.

The Mechanics of Scale

Enterprises operate very differently from individuals driven by craft.

At scale, companies optimize for predictability, repeatability and risk reduction.

• Unity over uniqueness.
• Stability over innovation.
• Delivery over craft.

Not because leaders hate your creativity. Not because designers aren’t valued or design isn’t wanted.

But because reducing variance makes it easier for thousands of people to move in the same way. Your passion—your desire to shape and craft—doesn’t fit easily into that machine.

The mechanics of scale lack the sensitivity for meaning. It feels like you’ve lost your passion or miscalculated your career. It’s easy to see this as a personal failure.

But the truth is you didn’t change. The environment did. And the way out begins with seeing it differently.

Back to Your Roots: Empathy

When designers feel lost, we often forget the tool that built our discipline: empathy.

Empathy is what lets you step out of your own head and see the world through someone else’s eyes. It’s how you reinterpret your reality, how you can recalibrate your perspective.

Empathy for the User

Start with someone else’s frustrations—your users’.

Their frustrations and needs give you back a sense of clarity about why your work matters. Their perspective lets you see who you’re really doing this for.

That Excel sheet, migrated into a cloud-based dashboard, might not change your life. But it can change theirs.

Users remind you that you still make an impact, even when it feels like you can’t fully practice your craft.

Empathy for the Business

Turning your empathy toward the business is less comfortable.

Understanding the business means acknowledging its constraints, priorities and pressures. It helps you see why innovation is slow, what the stakes are and what your boss is dealing with.

Empathy for the business doesn’t mean you capitulate. It lets you understand.

Understanding how the business works doesn’t fix everything, but it does reduce resentment. And resentment’s what holds you back.

When you see the system clearly, you stop interpreting constraints as personal attacks. You stop assuming incompetence. You recognize the environment around you.

And once you grasp that environment, you can design within it.

Empathy for Yourself

This is the hardest one.

Your own perspective is the one you can’t step away from. Your emotions are the ones you can’t ignore.

• Why does this feel frustrating?
• What exactly is painful here?
• Where am I feeling loss?

Self-empathy is more constructive than self-criticism. It makes you aware of your inner state.

And once you can see why you’re truly frustrated, you discover something greater than passion: purpose.

From Passion to Purpose

When you feel stuck, it’s tempting to think that “finding your passion” will fix everything. But passion alone won’t get you out.

The word pathos, the root in words like “empathy,” is about feeling and suffering—about what happens to you. It’s emotion.

And emotion comes from emovere: ex (out) + movere (move).

Emotion moves outward. It reacts. It signals. But emotion alone doesn’t move you forward. Purpose does.

Purpose comes from proponere—to put something forward. To place something ahead of you. To guide your next step.

Passion is what you feel in the moment. Purpose is what you do with that feeling.

And this is where empathy becomes a bridge. Empathy helps you look at the same reality and read it differently. It lets you recalibrate your perspective instead of staying locked in frustration. It shifts you from “how I feel” to “how I move.”

Once you understand the people you impact, the business you operate in and the reason you feel stuck, you have the first pieces of the puzzle that uncover your purpose.

Purpose isn’t a statement. It’s what moves you forward.

And once you see it, you can redesign your job, your role and your path. Even within constraints, you can bring that purpose forward.

Forward, Not Up

Early in my career, I saw the path the same way everyone else did: a ladder.

Later, when I was leading others on their path, I learned to nuance the direction. Not everybody thrives on an upward trajectory. Some are better off moving sideways. So I tailored progress and growth to the individual—vertical and lateral progressions.

But here’s the truth I learned far too late: Up, down, left or right don’t automatically mean forward.

I redesigned my career multiple times. Carved out new roles inside the same company. For years, it worked. Until it didn’t. My reality was defined by the mechanics of scale. I found myself stuck in the valley of despair.

So I left. No new job lined up. No master plan. Just space.

And in that space, I finally had enough room to look inward. To understand what I needed to do. To renew my perspective.

I rediscovered where I could move on purpose. I’m still defining that purpose. It’s still taking shape.

Closure

My career’s no longer about moving up. It’s about moving forward.

Not how I feel about what I do, but how I move with what I have to do.

That’s what progress is about: not just finding passion, but moving on purpose.

At 17, I picked up my first book on Neuro-Linguistic Programming (NLP). Not because a mentor recommended it or out of philosophical curiosity, but because I wanted to understand how I worked and what I could become. I found the world meaningless and thought my problems were too big for me to handle. The book introduced me to an idea that seemed too obvious to be true: If you have a problem, you can solve it. Life doesn’t hand you burdens you can’t carry.

It took me years to understand what that really meant. And even more years to realize that this lesson wasn’t just about fixing code bugs.

What I’m sharing here comes from my personal experience, mistakes included. It might not apply to you, but if even one of these reflections makes you pause and think, it’s worth it.

Know Thyself (Before Life Forces You To)

“Know thyself”: Socrates said this millennia ago, but nobody teaches you how to do it in school. And for developers, this self-knowledge isn’t a philosophical luxury. It’s a survival tool.

Today, I know what sets me off in a code review. I know how I react when someone questions my architecture. I understand why I prefer working on complex features alone before presenting them to the team. But it took me a long time to get here.

The problem is that we’re several different selves: The developer who defends their technical choices tooth and nail, the team member who needs to compromise in discussions, the professional who accepts projects they don’t like to pay the bills, the friend, the son, the father. Each of these selves has its own behavior patterns. And you only discover these patterns by going through experiences, preferably by seeking them out instead of just waiting for them to come.

Early in my career, conflict situations left me stunned: How can people not see the clarity of my idea, the way I see it? Defending a different technical idea seemed like arrogance. But over time, I learned something counterintuitive: I started to enjoy conflicts. Because it’s in friction that you discover what your ideas are really made of. It’s when people lose their cool that they show who they are, and so do you.

But this only makes sense when you know yourself. When you know what your path is.

And this is work only you can do. There’s no YouTube tutorial, no framework. It must come from within.

Some Questions That Helped Me (And Might Help You)

Is what I do/work aligned with what I feel?

Not in the romantic “do what you love” sense, but in the honest sense: Does this move me or anesthetize me?

Do my opportunities make me grow?

Or am I just repeating what I already know how to do because it’s comfortable?

What do I have to learn where I am today?

If the answer is “nothing,” you should have already left.

An important aside: There’s a dangerous belief that “doing what you like” is a privilege for billionaires. That you need to suffer first, make money later and only then can you afford the luxury of liking what you do. That’s a lie.

The point here is that successful people did do many things they didn’t like, yes. But that’s not why they succeeded; it’s despite it. And curiously, neuroscience shows that doing things you don’t like (like washing dishes) strengthens your ability to deal with adversity. Children who have household responsibilities develop greater resilience and entrepreneurial tendencies.

The point isn’t to avoid discomfort. It’s knowing why you’re doing what you don’t like, whether it’s a means to a clear end or just an escape from the decision to know yourself.

Solitude Isn’t the Enemy (It’s the Laboratory)

Developers have a strange relationship with solitude. Our profession pushes us toward it, hours in front of the screen, headphones on, immersed in problems that only exist in our heads. And at the same time, they tell us we must be “collaborative,” “work as a team” and “do pair programming” (which, personally, I think is excellent).

The truth I learned is that any person’s life, no matter how social they are, is fundamentally solitary. Nobody’s going to be responsible for your commitments, your architecture choices or your career. You must count on yourself most of the time.

This doesn’t mean you don’t need friends or a team. It means you need to learn to live with yourself first, and that’s a challenge.

And for developers, this skill is even more valuable. Because developing technically is more about thinking than acting. When you’re programming, solving a complex bug or architecting a solution, solitude isn’t isolation; it’s focus. You don’t need constant interaction to deliver. In fact, interruption is often the enemy.

But, and this is crucial, you can’t think everything through alone. A healthy dose of team interaction is necessary. The trick is knowing when to be alone and when to seek others out.

Things I did to master my relationship with solitude: Going to the movies alone, to restaurants, to concerts. It sounds silly, but it’s not. It’s about learning to appreciate your own company. It’s about creating inner life.

Artur da Távola, a Brazilian thinker, said: “Music is inner life, and whoever has inner life will never suffer from loneliness” (free translation).

Quality moments alone, without electronics, without notifications, just you, good music or a good book, make a difference. It’s in this silence that you process the day’s conflicts, understand why that meeting irritated you, and notice patterns in your behavior.

Solitude isn’t punishment. It’s the laboratory where you get to know yourself.

Early Success: The Invisible Trap

At 21, two years after entering the IT field, I started my own company. Money came fast. A lot of money. It seemed like I had cracked the code of life.

That success stagnated me.

Early success is a dangerous drug. It addicts your brain. It fills you with false confidence because you don’t yet understand that success has context, timing and luck. You think it was all competence.

The problem isn’t success itself; it’s not realizing that the premises that got you there won’t be present at the next level. You level up, but want to play with the same strategies.

I wasn’t prepared for the next level of growth. I didn’t know how to scale people, processes and complexity. And when a serious accident caused me to stagnate for nearly a decade, I realized I had built castles in the sand.

It was during this forced pause that I did the best work of my career. I focused on developing a legal system with features nobody else had: a complete change in history, field by field, and thousands of features meticulously thought out in the most minor details. Advocati was considered the best legal software in Brazil in 2007.

But it took me until 2011 to return strongly to the market.

Those years taught me something brutal: Enjoy your success, but don’t be blinded by it. Don’t become arrogant. Lower your expectations that everything will always work out. This gives you a more realistic view.

I’m not saying dream small. Dream big, but take solid, consistent steps. Our lives are increasingly fluid, and constantly changing goals and objectives get you nowhere. Having a fixed target and mapping out the right strategy to reach it, without illusions, is the safest path.

And there’s something else: You’ll repeat your mistakes until you learn the lesson. Your life is teaching you something. If you don’t understand or don’t even realize there’s a reason behind your challenge, you’ll keep repeating the same cycle.

Life isn’t a game where you pass levels. It’s more like debugging as you run the code, see where it breaks, adjust and then rerun it. The problem only disappears when you understand its root cause.

What to Do With All This?

Knowing yourself isn’t a destination. It’s a daily journey. It’s noticing when you’re reacting on autopilot. It’s questioning why that comment on PR irritated you so much. It’s having the courage to be alone with your thoughts. It’s celebrating success without thinking you’ve become invincible.

When the next conflict comes, the subsequent failure, the next success, you’ll have something most developers never build: clarity about who you are when nobody’s watching.

What I’ve shared here comes from decades of learning. Your journey will be different. But if you start getting to know yourself now, maybe you won’t have to wait for an accident to learn what took me decades to understand.

What’s Next for Me?

Having learned my lesson, I’m always looking for new ways to challenge myself.

Today I’m working on an exciting AI project that’s pushing the boundaries of modern development, an intelligent SaaS platform creator powered by natural language prompts. This innovative tool leverages .NET 10 for a robust backend, Microsoft SQL Server for enterprise-grade data management, and React with Next.js on the frontend, all brought together with the rich UI components of the Progress KendoReact library.

The vision is simple yet powerful: Describe your SaaS platform requirements through prompts and watch as AI transforms your ideas into a fully functional, production-ready application, complete with professional interfaces powered by AI and scalable architecture.

To validate the project, we’re developing and refining it alongside five real-world systems built with this new product.

And I look forward to learning about myself in the development of this project.

What’s next for you?

Maybe you know the acronyms: TDD, BDD or DDD. If not, go on Reddit and you will find enough debates to learn it keeps our industry busy.

Each acronym shifted how we think and how we build software. Now, with new accessibility laws setting a hard deadline, it’s time to add one more: ADD. Accessibility-Driven Development.

Compliance as a Driver of Quality

For years, accessibility was treated as optional or “nice to have.” A box you ticked if you had time. But history shows us that regulations and compliance raise quality and drive standardization.

Think about hardware safety regulations or industry protocols. At first, they seemed like a burden. But once enforced, they became the baseline that allowed whole industries to build better. Today, shipping is faster than ever. Compliance is the safeguard that helps prevent quality from being skipped.

A Time Change in Accessibility

If you’ve worked in UX or frontend development, you’ve probably heard of the Web Content Accessibility Guidelines (WCAG). They’ve been around for decades, laying out the rules: make software perceivable, operable and understandable.

WCAG has been the global guideline for accessibility. But for years, adoption was inconsistent. Companies did what they wanted, or what they could afford.

That changes now. The European Accessibility Act (EAA) is in force as of June 28, 2025. It harmonizes accessibility requirements across the EU and sets real deadlines for compliance. This is the moment accessibility shifts from voluntary guidance to enforceable law. A time change for the industry.

In the U.S., the Americans with Disabilities Act (ADA) has fueled a rise in lawsuits over inaccessible websites and apps. Similarly, Section 508 of the Rehabilitation Act requires federal agencies and contractors to conform to WCAG. Between lawsuits and procurement contracts, WCAG has become the standard in the U.S. too.

Different routes, same outcome: WCAG tells us that we need better software for everyone.

The Disciplines We Already Know

Disciplines reshape the way we develop software. They’re mindsets that force us to shift perspective and raise the quality of the software we ship.

TDD: Test-Driven Development

With TDD, we write failing tests before we write code. It flips the order. Instead of coding first and testing later, we define the boundaries up front.

The discipline: build resilience by considering how software might fail.

BDD: Behavior-Driven Development

BDD takes this further. Instead of only testing functions, we write scenarios in plain language: Given, When, Then. It’s not only developers who can understand, but also stakeholders, product owners, testers.

The discipline: align software with real user expectations.

DDD: Domain-Driven Design

DDD steps back another layer. It tells us: don’t just model features, model the domain itself. Speak the same language as the business. Reflect its truth in your system.

The discipline: design software that mirrors business reality.

Each of these disciplines changed how we think. They aren’t just tools; they’re shifts in mindset.

ADD: Accessibility-Driven Development

Now it’s time for the next discipline: Accessibility-Driven Development.

ADD means designing and testing for the edge user first—the one with constraints. The one who doesn’t use your product the way you do. If it works for them, it will work for everyone.

Think of it like TDD. In TDD, you write a failing test first. In ADD, you define the hardest case first.

Keyboard-only navigation becomes your failing test. A screen reader flow becomes your scenario. High-contrast mode becomes your business constraint. You design and build until those pass.

ADD shifts the mindset. Accessibility isn’t something you sprinkle in at the end. It is a discipline that shapes decisions during building.

The discipline: build software that is accessible to many, not to some.

Why ADD Matters Now

Why now? Without the European Accessibility Act, many teams would keep treating accessibility as optional. But with compliance dates set, ignoring accessibility is no longer a choice.

ADD helps you shift from reactive to proactive. Instead of scrambling with audits and lawsuits, you build accessibility into the process. Compliance becomes a habit, not a fire drill.

Here’s the point: designing for edge cases improves the experience for everyone. It’s called the curb cut effect. Those sidewalk ramps built for wheelchairs are also used by parents with strollers, travelers with luggage and kids on scooters.

You’re not wasting resources on a minority. You’re building better software. Accessibility isn’t overhead. It’s an advantage.

By designing for the most constrained environments, you raise the quality of the entire system.

Closing

Accessibility is not a gesture. It’s a discipline.

A new standard to comply with in software. And compliance has always been a driver of quality. Industry protocols in manufacturing. Safety standards in hardware. Now, accessibility in software.

You don’t have to choose between TDD, BDD and DDD. They’re not a menu. They’re a collection of development disciplines that shape how we build.

The one you need to add next is ADD: Accessibility-Driven Development.

Whether you just landed your first job as a designer/developer or you’ve been working for years, impostor syndrome can hit at any time. All it takes is for just one seed of doubt to be planted before you start wondering, “Am I even capable of doing this job? No one thinks I’m any good anyway. Maybe I should quit, save them the trouble.”

The problem with impostor syndrome is that it’s more than just negative self-talk. If it goes on for long enough, it can cause significant damage to your mental health, relationships and career.

So, rather than feed into this vicious cycle of tearing yourself down, let’s discuss some strategies that can help you get past impostor syndrome.

What Is Impostor Syndrome?

According to McLean Hospital:

“When someone has impostor syndrome, they experience repeated feelings or thoughts that they are incompetent or not good enough, despite evidence to the contrary. These beliefs often have roots in someone’s personal history and tend to play out in work, academic, and other high-pressure settings. Unaddressed, they can keep people from enjoying their successes and living life to its full potential.”

What do these feelings of insecurity and self-doubt sound like? Here are some examples:

• “I’m not good enough.”
• “I don’t belong here. Everyone is smarter than me.”
• “Everything I build is awful.”
• “I guess I charge … $12 an hour?” (Because you can’t imagine anyone paying you a fair wage for your work.)
• “I’m a complete disaster.” (After making a small mistake that no one noticed.)
• “I can’t ask for help because then they’ll realize I don’t know anything.”
• “Any day now they’ll figure out I’m a fraud.”
• “[Coworker] always does a better job. They should just give them all the important jobs.”
• “It didn’t have anything to do with me. It was all because of …” (When someone gives you a compliment.)
• “Here’s the onboarding mockup I created. It’s not very good. I’m sure you won’t like it.” (When presenting your work to a client.)

Impostor syndrome doesn’t just manifest itself in the words you speak about yourself or work. It can also create anxiety and depression, lead to insomnia and negatively impact your work performance. In addition, it can burn you out.

According to the American Psychological Association (APA), it can also make people not want to work with you. Not because you’re not good at what you do. But because your attitude is draining and they feel like it’s impossible to connect with you.

It’s almost as if impostor syndrome becomes a self-fulfilling prophecy. While managers, coworkers and clients may not have had a problem with the quality of your work before, they will once it and your attitude degrade over time.

How to Keep Impostor Syndrome from Getting in Your Way

Starting to feel the side effects of impostor syndrome at work? Here are some things you can do to get it out of your way (and out of your head):

1. Focus on What’s True, Not on What You Feel

Let’s take one of the example sentiments from above:

“Everything I build is awful.”

Let’s say this thought keeps crossing your mind every time you turn something into your supervisor or client.

The first thing to do is to recognize that this is a thought and nothing more. Unless you have a client shouting at you that you are indeed awful every time they see your work, this is your own criticism you’re dealing with.

Next, focus on what’s factual:

• What are the five last projects or tasks you completed?
• What was the feedback you received on them from others?
• In the end, was your employer or client satisfied with the end result?

You can’t argue with facts. So, the next time you start with the negative self-talk, call to mind what you’ve been working on and how it was received. Actually look at the paper trail from the project to work with facts and don’t just recall memories that may be tainted by your feelings.

Also make note of major wins and write them down somewhere. Positive client testimonials. Referrals from a client you worked closely with. Management congratulating you in front of the team. A bonus at the end of the year. As they stack up, it’ll be hard to call yourself an impostor.

2. Talk to Someone You Respect

If you’re seriously doubting the quality of your work, bring it to someone you admire and respect in your field. And avoid sharing it with someone whose opinion you could easily discard, like a loved one. (“Oh, they just said that so I wouldn’t feel bad.”)

There’s no need to share your opinions or criticisms about the work with your peer. Instead, just bring it to them with the hope of getting unbiased feedback, and see what they say.

To start, if they pay you any compliments, graciously accept them. Remind yourself that they have no reason to lie to you or sugarcoat the truth. They are someone you respect and whose opinion you trust. They get nothing out of lying to you.

If they give you feedback, remember that feedback does not equal failure. We all get feedback, even when we’re experts at the top of our careers. Thank them for their feedback, make note of the input you received and then spend time reviewing it.

Put aside your negative self-talk and evaluate the feedback against reality. Is it fair? If so, what can you do to address it and improve?

This is what feedback is for. It helps us better understand our strengths and weaknesses, and to put a plan in place so we can move forward better than before. Not to wallow in perceived criticism.

This is the difference between an impostor and an expert. The impostor won’t know what to do with the feedback or how to grow from it. The expert will. They’ll also have the motivation to do so, too.

3. Ask Your Manager or Peers for Support

Let’s say your feelings of impostor syndrome have come from something that your manager, clients or peers have said to you. This again comes down to whether you’ll allow that feedback to fester or to put it to good use.

For example, let’s say that your manager hasn’t been pleased with your creation of color palettes. If they haven’t given you feedback on how to create them, reach out for support and guidance. Or you can turn to your coworkers for assistance.

Find out what exactly their expectations or preferences are. Ask about their personal process for crafting color palettes. See if there are specific tools they recommend you use.

If you’re feeling inadequate, don’t give up. See if you can get someone to guide you toward a new process or practice.

On the other hand, let’s say your feelings of impostor syndrome have come from something that your manager has said or done, but it wasn’t a direct criticism.

For example, they reassigned one of your tasks to a peer. Do you know for sure why they did it? If you don’t, follow up with them and see if they’ll give you a reason and some feedback. By actively seeking feedback, you may just discover it was a matter of them better allocating resources versus it being a reflection of the quality of your work.

Seeking out the truth can always help when impostor syndrome is getting in the way. It’ll either let you know that your feelings of self-doubt are unfounded or that you do have some areas where you can improve. You lose nothing by asking for guidance and help, and everything to gain.

4. Let Go of Perfectionism

It’s not realistic to seek perfection. Or to wait to turn something in until it’s perfect.

I’m not saying that your work should be full of errors or half done. However, if you’re waiting to reach that so-called perfect version of a website, app, logo or whatever it is you’re building, and then freak out after hitting “Send” because you realized the font size was slightly off, that’s a problem.

We all make mistakes and there are flaws in a lot of the work we produce for the web. We’re human. It’s what happens. So long as you’re paying attention to your clients’ needs and preferences, adhering to best practices and web standards, and doing your level best each time, that’s all that matters.

Once you accept this, you’ll realize it’s not right to put yourself down or abuse yourself for every perceived mistake.

To reiterate what I mentioned before: If it really bothers you to discover a mistake after turning in your work, make note of it. Is there something you can do next time to avoid it?

For instance, let’s say the font in your contact form doesn’t match the font used throughout the Contact page. There’s an easy way to address this particular problem in the future: Revise your process. Instead of manually applying font settings as you add new components, employ a global standard and design system that controls the fonts used throughout.

Let go of this idea of perfection and embrace a mindset of growth and improvement. Find something you don’t like about your process or approach to design or development? Fix it. Don’t let it become something that contributes to the harmful impostor syndrome growing within you.

5. Fake It Until You Make It

For this point, I’m not encouraging you to sell yourself with lies about your background or what you’re capable of. Impostor syndrome relates to feelings of inadequacy when you are already more than adequate, not when you set yourself up for a job you were never a good fit for.

What I mean by “fake it until you make it” is faking confidence and satisfaction with your work.

For example, let’s say it’s time to present the fintech mobile app you created to the client. Don’t present it to them with doubts and negative talk. Instead, take the lead, get excited about the app and show them how amazing it is.

I used to work in customer service and one of the things they used to teach us was to smile every time we picked up the phone. I know, it sounds silly. It’s not like the customer can even see you smile. But there’s research that suggests that forcing a smile on your face can actually impact the way you feel and how you carry yourself.

The same thing can happen when you fake confidence and happiness with your work. By forcing yourself to push the impostor thoughts and statements aside, you get into the habit of reflecting positively on what you do. And once you see that supported by how others react to your work, eventually you’ll realize you were never an impostor.

Another thing to do is catch yourself whenever you use negative words to describe yourself or your work, like “I can’t,” “I hate” or “I won’t.” Rephrase them using positive words. Even just reframing the situation and your thoughts can have a positive effect on your mindset.

This can have long-reaching effects on your career, too.

For instance, once you gain confidence in the everyday tasks you do, you can take things to the next level. With this confidence, you’ll be able to take more risks and accept more challenges. And if you’re hit with another wave of impostor syndrome, don’t sweat it. Even if it doesn’t feel right, your mind will eventually catch up with what everyone else already knows and believes about your capabilities.

Wrapping Up

You are not an impostor. Those feelings and thoughts you’re having? Most creatives get them at some point in their career.

In the beginning, those doubts may come from being a newbie when everyone else around you seems to have it all figured out. It’s natural to wonder if you’re good enough and how long it’ll last as it seems too good to be true.

What’s more, working as a creative is a lot different from, say, an accountant who works with hard facts and numbers. You’re coming up with something completely new. While you’re building something for a client or employer to use, it all comes from within you. And it can be hard to separate yourself from the outcomes or feedback associated with your work.

Impostor syndrome is going to happen. What matters is what you do with it.

I really enjoyed this quote that Dr. Ami Rokach of York University gave to the APA as it shows how impostor syndrome can be turned into a positive:

“Impostor phenomenon is a spectrum, not binary. Just as high achievement can fuel impostor phenomenon in self-doubting people, impostor feelings can fuel high achievement, which would enhance one’s beliefs in his or her abilities and achievement.”

Web development on Windows has come a long way. With tools like Windows Subsystem for Linux (WSL 2), Windows Terminal and modern runtime managers, you can now set up a fast, reliable and unix-friendly workflow without leaving Windows.

In this guide, we’ll walk through everything you need to set up a modern web development environment. From installing WSL 2 and mapping your Linux file system to customizing your shell with Zsh and managing runtimes with Node Version Manager (NVM) and launching your first frontend project with Vite, we’re covering the full-stack of modern tooling for web development.

Whether you’re a new developer getting started or an experienced one setting up a fresh machine, this guide covers everything you need to set up a modern web development project.

Prerequisites

• Operating System: Windows 10 (version 2004 or higher) or Windows 11
• GitHub Account: Required for version control and syncing with repositories

Setting Up the Windows Development Environment [The Foundation]

In this section, we will guide you through the installation and configuration of essential tools that establish the foundation of a modern development environment workflow on Windows.

Setting Up and Configuring Windows Subsystem for Linux (WSL)

One of the first and most important steps in setting up your Windows dev environment is installing Windows Subsystem for Linux (WSL). WSL lets you run a Linux environment directly on Windows—no virtual machine or dual-booting required.

I recommend using Ubuntu as your primary Linux distribution, but you’re free to try others. Most systems can run multiple Linux distributions concurrently without issues.

Installing and Configuring WSL2

WSL 2 is the latest version of the subsystem, offering a real Linux kernel and full system call compatibility. Previously, installation required several manual steps, but it is now easier than ever to install with a single command in PowerShell.

To Install WSL 2

Open PowerShell as Administrator and run the following command:

wsl --install

This command will do the following:

• Enable required WSL and VM platform components
• Download and install the latest Linux kernel
• Set WSL 2 as the default version
• Install Ubuntu as the default distribution (you may need to restart your system)

Once installation is complete, launch Ubuntu from the Start menu. It will take a few moments to initialize. Then, you will be prompted to create a UNIX username and password, which are separate from your Windows credentials.

It is also recommended that you regularly update and upgrade your packages. To do that, run the following command:

sudo apt update && sudo apt upgrade -y

Mapping Your Linux Drive

By default, Windows File Explorer shows your devices and drives. To streamline access, we’ll map the Ubuntu virtual drive as a network location.

Open \\wsl$\ location from the file explorer. This will display all your installed WSL distributions, then follow the instructions below:

1. Right-click on the Ubuntu folder, and select “Map network drive”:
2. Choose the drive letter (e.g., Z:).
3. Check Reconnect at sign-in.
4. Click Finish

Below is the step-by-step demo image:

Your Linux home directory is now accessible from Windows as a network drive. From within the Linux terminal, you can access Windows files under /mnt/ (e.g., /mnt/c/Users/your_username).

This configuration enables easy file transfers between Windows and Linux via drag-and-drop or copy-and-paste.

Restarting WSL

If WSL runs into issues or stops working, you can restart it with:

wsl.exe --shutdown
wsl.exe

That should bring everything back to normal.

Important Considerations When Using WSL

If you’re building web projects using WSL, there are a few critical things to keep in mind to improve performance and cross-platform compatibility:

• File system performance: For best performance, store your project files within the Linux file system (e.g., /home/username/). Avoid working directly from mounted Windows paths (/mnt/c/…) as this can slow down tools like Node.js, npm and webpack.
• Line ending consistency: Linux uses LF, while Windows uses CRLF. To prevent broken scripts or weird Git diffs, add a .gitattributes file to your project to enforce consistent line endings.
• Path format differences: Path syntax differs between systems—Windows uses paths like C:\Users\..., while Linux uses /home/username. Be mindful of this when setting environment variables, running scripts or configuring Docker.
• Permissions and privileges: Some operations in WSL—such as installing packages, accessing system directories or opening privileged ports—may require elevated privileges. Use sudo where necessary, just like in a traditional Linux setup.

Setting Up Windows Terminal

You can launch the Linux terminal by either opening Ubuntu from the Start menu or running wsl from PowerShell or Command Prompt.

For a more feature-rich experience with features such as tabs, split panes, theming and key bindings, consider using Windows Terminal. It’s modern, fast and works seamlessly with WSL. While alternatives like Cmder, ConEmu and Hyper exist, in my experience, Windows Terminal provides the most reliable and developer-friendly setup for daily use.

Installing and Customizing Windows Terminal

If you’re using Windows 11, it’s built in. If you’re using Windows 10, install it via Microsoft Store or PowerShell:

winget install --id=Microsoft.WindowsTerminal -e

I recommend customizing your terminal settings, such as setting the default profile and starting directory, to streamline your workflow. This means that every time you launch Windows Terminal, it opens directly into your WSL environment inside your Linux user’s home directory.

Follow these instructions to set up your Default Profile:

1. Open Windows Terminal.
2. Click the down arrow v next to the tab button and choose Settings.
3. Under Startup section, set Default profile to Ubuntu.

Below is the step-by-step demo image of the instruction above:

Follow these instructions to set up Starting Directory:

1. In Settings, go to Profiles > Ubuntu.
2. Under the General tab, find Starting directory.
3. Enter the following: \\wsl$\Ubuntu\home\your_username. Make sure to replace your_username with your actual Ubuntu username.

You can leave the use parent process directory box unchecked.

You can also explore deeper customization via the JSON config file or by visiting Windows Terminal Themes for community themes.

Setting Up Git and GitHub

Git is essential for version control in development, while GitHub provides a platform to host, manage and collaborate on your code repositories.

Installing and Configuring Git

Git usually comes preinstalled on most Linux distributions via WSL. But to verify you have it (or the most up-to-date version), run the following command:

sudo apt update && sudo apt install git

Next, set your global Git identity:

git config --global user.name "Your Name"
git config --global user.email "youremail@example.com"

You can confirm the settings with:

git config --list

Generating SSH Keys for GitHub

Using SSH with GitHub allows you to authenticate securely without entering your username and password each time. To generate SSH keys for GitHub, follow these steps:

1. Generate a New SSH Key

Execute the following command (replace the placeholder with your GitHub email address):

ssh-keygen -t ed278490 -C "youremail@example.com"

• -t ed25519 uses the modern and secure Ed25519 algorithm.
• -C adds a label for your key (usually your email).

When prompted:

• Press Enter to accept the default file location (~/.ssh/id_ed25519).
• Choose a passphrase if you’d like to add security (optional but recommended).

2. Start the SSH Agent

Make sure the SSH agent is running:

eval "$(ssh-agent -s)"

3. Add Your Key to the SSH Agent

ssh-add ~/.ssh/id_ed25519

If you used a custom name or location for the key, update the path accordingly.

4. Add the Public Key to your Github Account

First, copy your public key to the clipboard:

cat ~/.ssh/id_ed25519.pub

Then:

1. Log in to GitHub.
2. Go to https://github.com/settings/keys.
3. Click “New SSH key.”
4. Paste the key, give it a descriptive title (e.g., “WSL Dev Machine”) and save.
5. Test Your SSH Connection. Run the following command to verify that everything is working:

ssh -T git@github.com

If setup is successful, you’ll see:

Hi your-username! You've successfully authenticated, but GitHub does not provide shell access.

Amplifying Your Shell with Zsh and Oh My Zsh

Zsh is a powerful, user-friendly alternative to Bash. When combined with Oh My Zsh, it delivers a highly customizable, feature-rich shell experience with themes, plugins and smart defaults.

Installing ZSH

sudo apt install zsh

Then, set Zsh as your default shell:

chsh -s $(which zsh)

You may need to restart your terminal or log out and back in for the change to take effect.

Installing Oh My Zsh

Oh My Zsh is a popular framework that makes managing your Zsh configuration easier, with support for themes, plugins, aliases and more.

First, install curl:

sudo apt install curl

Then install Oh My Zsh using the official install script:

sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"

Once installed, your terminal will automatically switch to Zsh and load the new config. You can start customizing it via your ~/.zshrc file.

Adding Themes and Plugins (Optional but Fun)

This section is optional, but if you’re like me and enjoy a customized terminal, here’s where things get exciting.

Install Powerlevel10k Theme

Powerlevel10k is a fast, responsive and visually rich Zsh theme with Git integration, segment prompts, icons and more.

Clone the theme into your Oh My Zsh custom themes directory:

git clone --depth=1 https://github.com/romkatv/powerlevel10k.git ${ZSH_CUSTOM:-$HOME/.oh-my-zsh/custom}/themes/powerlevel10k

Then open your ~/.zshrc file and update the theme setting:

ZSH_THEME="powerlevel10k/powerlevel10k"

Install Useful Plugins

• zsh-autosuggestion: This plugin provides real-time command suggestions as you type:

git clone https://github.com/zsh-users/zsh-autosuggestions \
${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions

• zsh-syntax-highlighting: This plugin adds syntax highlighting to commands in your terminal:

git clone https://github.com/zsh-users/zsh-syntax-highlighting.git \
 ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-syntax-highlighting

Enable the Plugins

Edit your ~/.zshrc file and add the plugins to the list:

plugins=(git zsh-autosuggestions zsh-syntax-highlighting)

Then apply the changes:

source ~/.zshrc

Configure PowerLevel10K

To customize the look and feel of your terminal, run:

p10k configure

This launches an interactive wizard where you can choose your preferred prompt style, icons, layout and more.

You can always rerun the configuration later with the same command.

Want more? Check out the Awesome Zsh Plugins repo for a curated list of themes, plugins and other Zsh goodies.

Installing Node.js

Node.js is essential for modern JavaScript development. It brings server-side capabilities to JavaScript, allowing you to build servers, APIs, backend services and tools using the same language that powers the browser.

Installing NVM (Node Version Manager)

When working on multiple projects, you’ll often need to switch between different versions of Node.js. Node Version Manager (NVM) makes this easy by allowing you to install, manage and switch between Node.js versions directly from the command line.

To install NVM, run the following command in your terminal:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash

After installation, activate NVM with:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"

Add the two lines above to your ~/.zshrc or ~/.bashrc so NVM loads automatically whenever a new shell session starts.

Installing Node.js via NVM

Run the following command to install the latest LTS (Long-Term Support) version of Node.js:

nvm install --lts

Set it as the default version:

nvm alias default node

Verify that Node and npm are available:

node --version
npm --version

LTS versions are stable, well-supported and recommended for most development and production workflows.

Installing and Using pnpm (Optional)

If you care about performance and disk space efficiency, consider using pnpm. It’s a modern alternative to npm and yarn that installs packages faster by using a content-addressable storage mechanism.

Run the following command to initialize a new project:

 pnpm init

Use the following command to install dependencies:

pnpm install package-name

To install a package globally:

pnpm install package-name

Using Package Managers on Windows: Chocolatey & Scoop

Package managers streamline software installation, updates and maintenance—much like apt on Linux or brew on macOS. On Windows, the two most popular options are Chocolatey and Scoop.

Chocolatey

Chocolatey is a powerful, full-featured package manager for Windows. It supports system-wide installations and thousands of packages, including CLI tools, applications and services.

Installing Chocolatey

1. Open PowerShell as Administrator
2. Run the following:

Set-ExecutionPolicy Bypass -Scope Process -Force;
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072;
iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))

Using Chocolatey

• Install a package:

choco install <package-name> -y

• Upgrade all installed packages:

choco upgrade all -y

Scoop

Scoop is a simpler, developer-friendly package manager that installs tools into your user profile—no admin rights needed. Ideal for CLI tools and programming languages.

Installing Scoop

• Open PowerShell (non-admin).
• Allow script execution:

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

• Install Scoop:

iwr -useb get.scoop.sh | iex

Using Scoop

• Install a Package:

scoop install <package-name>

• Update all installed packages:

scoop update *

Recommendation: Both Chocolatey and Scoop are excellent. Use Chocolatey for system-wide installations (apps, services) and Scoop for developer tools and CLI utilities. You can even use them side by side without conflict.

At this point, you can start your web development project with any web programming stack of your choice. Refer to the Further Resources section for reference.

Setting Up Your First Web Project with Vite

In the previous section, we covered some of the core tools you need to kick off any web development project on Windows. In this section, we’ll walk through how to quickly scaffold a modern frontend project using Vite.

Setting Up Vite

Vite is a modern frontend build tool created by Evan You, designed to power the next generation of web applications. It offers features like instant server start, optimized builds, lightning-fast Hot Module Replacement (HMR) and out-of-the-box support for TypeScript, JSX, CSS and popular frameworks like React, Vue and more. With Vite, you can skip tedious manual setup and jump straight into building modern JavaScript applications.

To scaffold a new Vite project, run the following command:

npm create vite@latest  my-first-project

This command will walk you through the project setup interactively.

Then Vite will prompt you select a framework:

> npx
> "create-vite" my-first-project

│
◆  Select a framework:
│  ● Vanilla
│  ○ Vue
│  ○ React
│  ○ Preact
│  ○ Lit
│  ○ Svelte
│  ○ Solid
│  ○ Qwik
│  ○ Angular
│  ○ Marko
│  ○ Others
└

Vite can be used to bootstrap a range of frontend frameworks and libraries, so select Vanilla since we are scaffolding a plain vanilla web project.

Vite will ask you to choose a language, either JavaScript or TypeScript. You can choose whichever one you prefer for your project.

Use your arrow keys to make your selection. Here, JavaScript is selected:

◆  Select a variant:
│  ○ TypeScript
│  ○ TypeScript + SWC
│  ● JavaScript
│  ○ JavaScript + SWC
│  ○ React Router v7 ↗
│  ○ TanStack Router ↗
│  ○ RedwoodSDK ↗

You can see other options with SWC. SWC (Speedy Web Compiler) is a JavaScript/TypeScript compiler used in Vite for transforming JavaScript and TypeScript code. It’s a fast, low-level JavaScript and TypeScript compiler built with Rust, designed to deliver faster build times and better performance.

After setting up the framework, you will see an output that the project has been scaffolded in your project folder. Vite will then instruct you to install dependencies using npm (or the package manager you’re using):

◇  Scaffolding project in /Users/mac/my-first-project...
│
└  Done. Now run:
cd my-first-project
npm install
npm run dev

Navigate to your project folder as directed:

$ cd my-first-project

Then install the dependencies for this project:

$ npm install

Next, start the development server to verify everything is working. Use the following command to run the development server:

$ npm run dev

This command will then run your project in development mode. It will prompt the following outputs:

VITE v6.3.5  ready in 1227 ms
➜  Local:   http://localhost:5173/
➜  Network: use --host to expose
➜  press h + enter to show help

Next, click on the link (http://localhost:5173/) to open the project in your browser:

You can decide to use any code editor of your choice at this stage, but Visual Studio Code is my preferred code editor.

Setting Up Visual Studio Code

Visual Studio Code (VS Code) has become one of the most popular code editors for web development, thanks to its simplicity, speed and rich plugin ecosystem that supports virtually any type of web project.

Installing Visual Studio Code

You can download VS Code from the official website.

Configuring VS Code for WSL

We will install and configure a Remote Development Extension Pack. It’s an extension that allows you to open any folder in a container, on a remote machine or WSL—while enjoying the full power of VS Code.

How to install the Remote Developer Extension:

1. Open VS Code.
2. Go to the Extension view (ctrl + shift + X).
3. Search for Remote Development.
4. Click Install.

Open WSL project in VS Code. This extension allows you to launch VS Code right from your WSL terminal by using just the code command. In your WSL terminal, navigate to your project directory and run the following command to open the entire directory of your project inside VS Code.

cd my-first-project
code .

Top VS Code Essential Extensions for Web Development

There are numerous extensions in VS Code for web development. Here are my top five:

• Web Dev: A bundle of popular tools for frontend development—includes Live Server, ESLint, JavaScript (ES6) Code Snippets and more. Instead of installing each tool individually, you can install this pack to streamline your setup.
• Prettier: Prettier is an opinionated code formatter for enforcing consistent style.
• GitLens: Supercharges Git integration inside VS Code. See line-by-line commit history, authorship and make Git workflows easier and more visual.
• Bracket Pair Colorizer: This extension enhances code readability by colorising matching brackets, making it easier to navigate and understand nested structures.
• Code Spell Checker: Helps catch typos in variable names, comments and documentation. Especially useful for maintaining code quality in larger codebases.

You can explore more extensions on the official Visual Studio Marketplace and tailor your setup based on your project’s needs.

Windows Productivity Apps and Browser Extensions for Web Development

In this section, I’ll highlight a few productivity tools for Windows, along with some of my favorite browser extensions that help streamline and enhance my web development workflow.

Chrome Browser Extensions

Google Chrome is my go-to browser for development, and these are some of the essential extensions I use to boost productivity:

• React Developer Tools: A must-have if you’re working with React. It lets you inspect and debug React components, analyze state and props, and identify performance issues.
• Web Developer: A powerful toolkit that allows you to disable images, scripts and styles; resize the viewport; and validate HTML and CSS. Perfect for testing and debugging.
• JSON Viewer Pro: Automatically formats and highlights JSON data in the browser, making it easier to read and debug.
• Lighthouse: Built by Google, this tool audits your web pages for performance, accessibility, SEO and best practices.
• CSS Peeper: Lets you quickly inspect CSS styles on any website without digging through developer tools. Great for UI exploration or reverse-engineering layouts.

You can check for an extension suitable for you at the Chrome Web Store. Also, you can get the equivalent of the above-listed extensions for Firefox here.

Productivity Tools for Windows

Here are some of my favorite free productivity apps that I use regularly in my dev workflow:

• Microsoft PowerToys: A collection of utilities that help power users tweak and optimize their Windows experience (e.g., FancyZones, file renamer, quick window resizing).
• Notion: A project management and note-taking software.
• Figma: A cloud-based UI/UX design tool that makes real-time collaboration with designers seamless.
• Slack: A wide used team communication and collaboration platform. Ideal for both work and open-source/community development teams.

Using Chocolatey, you can download all these apps at once with the following command in PowerShell as an administrator:

choco install powertoys notion figma slack -y

Chocolatey automates the setup process, so you don’t have to download and install each tool manually.

Additional Development Environment Setup [Optional]

I added this section for developers who are either beginners, not frontend-focused or don’t primarily work with JavaScript. It provides a quick walkthrough for setting up Docker with WSL and configuring a Python development environment inside WSL.

Docker

According to the official documentation, Docker is an open platform for developing, shipping and running applications. It allows you to decouple your application from the underlying infrastructure, making it easier to build, test and deploy software quickly.

Installing Docker

Docker Desktop enables you to run containers natively on Windows using WSL 2. You can install Docker Desktop using one of two methods:

Option 1 – Install via Chocolatey:

choco install docker-desktop

Option 2 – Install from the official site: https://www.docker.com/products/docker-desktop

After downloading, run the installer and ensure to check the box labeled “Use WSL 2 instead of Hyper-V” during setup. Once the installation is complete, restart your computer.

Verifying Docker Installation

To verify that Docker is installed correctly, open your terminal and run:

docker --version

Then run a test container to confirm everything is working:

docker run hello-world

You should see a success message indicating Docker is functioning correctly.

You’re now fully set up with Docker on Windows via WSL—native, fast and container-ready.

You can refer to Docker’s official documentation to learn more about how to use Docker effectively on Windows.

Wrapping Up

Congrats! That was a long read. But by now, you’re not just ready to code, you’re fully equipped for real-world web development on Windows. You’ve installed and configured WSL 2, customized your terminal with Zsh and Oh My Zsh, set up Git and secure GitHub workflows with SSH, installed Node.js via NVM and even scaffolded your first frontend project with Vite. All on Windows—without needing to leave your OS or spin up a VM.

If JavaScript is your main stack, this setup gives you everything you need to build and run modern frontend and backend applications using tools like React, Vue, Angular, Next.js, Express.js or Nest.js. And if you’re building with other stacks such as ASP.NET with Blazor, Python with Django, or Ruby on Rails, this environment setup still offers a solid foundation for web development on Windows. Just refer to the specific documentation for your chosen stack to complete your setup.

You have the tools and the setup, so now it’s time to create magic.

Happy coding!

Further Resources

• Blazor Basics: Getting Started with Blazor Development in Visual Studio 2022
• React Basics: Getting Started with React and Visual Studio Code
• Vue Basics: Getting Started with Vue.js and Visual Studio Code
• Angular Basics: Setting Up Angular Development Environment
• How to Install Python & Django on Windows
• Learning NestJS Part 1: Getting Started

In a world where most of our lives play out online, web accessibility shouldn’t be treated as an afterthought. Designing with inclusivity in mind is no longer optional; it’s essential. Just like a chair needs four sturdy legs to be safe for everyone, digital experiences need to be built with all users in mind.

But when the platform in question is educational, the stakes are even higher. These platforms serve a diverse range of learners—some with visual, auditory, motor or cognitive impairments, and face stricter accessibility requirements than general websites.

That’s why Resolute was proud to partner with a U.S.-based company providing online training tools for frontline employees. The platform had recently been acquired by a leading provider of online compliance and workforce training, further raising the bar for performance, accessibility and scalability. The goal: build a more functional, accessible and scalable web experience.

When Design Slows You Down

The project started with a familiar pain point: fragmentation. The client’s design ecosystem was spread across multiple sources:

• An internal Figma library shaped by years of brand tweaks
• A partially customized theme inside Progress ThemeBuilder
• A live site with Progress Kendo UI components that didn’t always align with the designs

This led to confusion, delays and inconsistencies, especially around accessibility. Developers struggled to map designs to actual components. Theming was brittle. And certain UI patterns weren’t usable for people relying on keyboard navigation or assistive technologies.

Resolute was brought in to clean it up, streamline the workflow and help the client move toward a more compliant and scalable solution.

Fixing the Foundation: ThemeBuilder in Action

Our UX/UI team began by auditing the client’s existing design system. They worked closely with their internal team to unify the visual language and migrate it into Progress ThemeBuilder, which served as the central source of truth for styling and theming moving forward.

ThemeBuilder wasn’t just a convenience; it helped enforce consistency in design tokens like colors, borders and spacing, while also helping to align with accessibility best practices.

The UX/UI team’s work included:

• Consolidating redundant button and form variations
• Fixing visual issues with contrast, spacing and typography
• Helping the design team understand how to use ThemeBuilder effectively to support long-term accessibility

From Visuals to Code: Accessibility in the Build

Once the design foundation was solid, our frontend team began implementing the new UI in code. Over several months, the platform’s frontend was rebuilt with accessibility as a core requirement, focusing not just on how it looked, but how it worked for every user.

This wasn’t just about good UX; it was also about meeting real compliance needs. Since the platform serves a broad user base in the U.S., including educational and government-affiliated organizations, several legal standards apply, including:

• ADA (Americans with Disabilities Act): Particularly Title III, which applies to educational institutions and commercial websites
• Section 508 of the Rehabilitation Act: For platforms receiving federal funding or working with government entities

To meet these requirements, we aligned the build with WCAG 2.1 Level AA guidelines developed by the W3C (World Wide Web Consortium), currently the most widely used benchmark for web accessibility in the U.S.

What that looked like in code:

• Every interactive element was accessible via keyboard navigation (tab, arrows, etc.).
• Clear, visible focus states were implemented for all buttons, links and forms.
• We structured the app using semantic HTML and applied ARIA roles for assistive tech (e.g., <button>, <nav>, <form>). Yet, we applied ARIA roles only when necessary for custom components or non-semantic elements, avoiding over-reliance on ARIA. It’s crucial to use ARIA only when native HTML elements can’t provide the required functionality.
• For use cases beyond the default configurations of Kendo UI or ThemeBuilder, we wrote custom HTML overrides.
• Duplicate labels or screen reader confusion were avoided using attributes like aria-hidden="true" where needed.

Testing was both automated and manual. Tools like axe DevTools, WAVE and ChromeVox helped flag contrast issues, label duplication and navigation traps. But human testing mattered just as much. Therefore, a touchscreen laptop was used to simulate real user scenarios, check responsiveness and validate how elements behaved across screen sizes and input types.

When Customization Adds Complexity

Telerik ThemeBuilder and Kendo UI offer strong accessibility features, but when components are heavily customized, unexpected issues can appear. Resolute helped the client troubleshoot several edge cases:

• Buttons built without the base component didn’t render properly
• Some forms displayed labels twice to screen readers (e.g., “Username Username”)
• Blazor components lacked alt-text bindings, requiring a workaround

None of these problems were dealbreakers, but they showed how expertise matters. Without frontend developers who understand both the framework and accessibility requirements, these issues could have gone unnoticed.

Accessibility = Structure + Semantics + SEO

There’s another benefit to building with accessibility in mind: better search engine optimization (SEO). Many of the same practices that support users with disabilities, like using semantic HTML, a well-structured HTML DOM (Document Object Model) and meaningful headings, also help search engines understand and rank your content.

The frontend implementation in this case included:

• One <h1> per page, with clean heading hierarchies for structure like <h2> for sections and <h3> inside components
• Alt-text for all meaningful images
• Descriptive link text and accessible navigation

The result? A platform that’s easier to use, more discoverable and legally compliant.

Knowledge Transfer Matters

Resolute’s role expanded beyond design and development work. We trained the client’s internal team to maintain and build on the system with accessibility in mind. That included:

• Documenting all accessibility decisions and techniques used
• Providing reusable design patterns in ThemeBuilder
• Running training sessions on WCAG basics and development workflow tips

Accessibility isn’t something you do once. It’s a practice. So, we made sure the team could carry that forward.

Final Thoughts

Accessibility is a shared responsibility—across design, development and leadership. Our client understood that, and, with the right tools and support, made serious progress toward a platform that works for everyone.

Progress ThemeBuilder helped streamline and standardize the design-to-code process. Resolute helped connect the dots by aligning compliance, usability and long-term scalability.

Learn more about how Resolute can help address usability issues, starting with the UX Assessment.

It is no secret that AI has turned the world upside down and inside out. And what better way to make sense of it all than by attending an information-filled VS Code Dev Days event?!

This year, we are joining forces with Microsoft and Growth Acceleration Partners to cohost six global VS Code Dev Days events, and you’re invited to attend! There is no cost to attend.

Events Produced by Progress, Growth Acceleration Partners & Microsoft:

At each event, you will be treated to two talks (“Essential Techniques for GitHub Copilot in VS Code” and “Intro to Telerik AI Coding Assistants & Progress Agentic RAG”) and an interactive (“Lab: Exploring VS Code and GitHub Copilot”). Sessions will be led by Microsoft employees as well as Progress and Growth Acceleration Partners folks.

If you can’t make one of the events we’re hosting, do not fear—there are more than 60 VS Code Dev Days events taking place all around the world! They are all free and anyone can join—whether as seasoned professionals or newcomers to AI-assisted workflows.

Visit aka.ms/VSCode/DevDays to find an event near you!

And if none of the in-person events work for you, Microsoft has scheduled special virtual editions featuring sessions packed with demos and practical tips—register today!

VS Code Dev Days is an opportunity to learn the latest in developer productivity and AI-assisted coding while also interacting with your peers. We hope to see you at a local event this fall!

Happy coding!

You try to stand out. They should use your product, not your competitor’s.

So what do you do? You look for a competitive edge. You differentiate. You change how people work. But at what cost?

The Illusion of Differentiation

Change is inevitable. But when we change to stand out, we sacrifice the one thing we have in common: standards. This hurts innovation.

There’s an illusion that if you differentiate, you automatically improve, and therefore innovate.

But what happens when you change the basics? You demolish foundations industries are built on. You disrupt the mental models people rely on. You reset muscle memory, increase human error and force users to rebuild momentum.

Is that innovation—or disruption dressed as progress?

The Hardware-Software Gap

If you look at hardware, you see that standards are everywhere. You can’t push a product to market without compliance to standards. All the gates, checks, audits and certifications protect the firm foundation the industry depends on.

If you want change the standards, you have to contribute. That doesn’t mean there’s no innovation. On the contrary. Companies focus all their resources on improving what’s built on top of those foundations—the systems and tools that can be integrated and replaced. Lower risk of change. More opportunity for improvement.

So, why do we stop at domain standards when we build software? Why do we have the liberty to invent our own models, semantics and extensions?

If users work with software built on the same standards, the same foundation, they stay productive. You improve the workflow. Make it the same but better, not different.

This liberty to experiment and evolve creates momentum: no big, irreversible transitions. I’ve seen what happens when products rely on the difference instead of the default.

Adoption never catches up with potential.

A Call to Contribute

Start standardizing industries. Help standardize software.

How? Be more transparent. Build in public. Contribute and implement standards. Share your systems and your semantics, and document your ideas.

Protect your IP—but promote the idea. The idea of changing the industry together.

Don’t fiddle with the foundations. Get everyone on the same page. Use the same protocols. Stick to shared formats. Make systems easy to exchange.

People who build in public—and with the public—earn trust and raise the bar for everyone.

That kind of contribution grows the pie, not just your slice.

Closing

Imagine a world where we work together, get more done with less and use resources wisely.

Collaborations and contributions that achieve more than ever before. Where you and your competition both contribute, and the industry rises.

Don’t change the base. Lift it.

It might seem counterintuitive as a designer or developer to bother with a resume. After all, your work speaks for itself. Isn’t that all that employers need to see?

Sure, they might love the work they see in your portfolio, but is that enough? For some, it’s not. The problem with relying solely on a portfolio is it doesn’t give prospective employers extra details about your background, skills or personality that also factor into hiring decisions. They want to know where you acquired your skills from and what else makes you a standout candidate.

In today’s job market, you also have to think about AI. Many people—highly qualified people—have been talking about how their resumes don’t get responses because they’re not optimized for AI. In other words, their resumes don’t even reach hiring managers because AI hasn’t found certain keywords or phrases it was programmed to find.

So, your resume really needs to hit all the marks. It should aesthetically look good and lay out your history in a way that makes you look like the best candidate for the job.

Let’s have a look at some web designer and developer resumes and what makes them so effective.

12 Inspiring Resume Examples for Web Designers & Developers

There are different ways to present your resume. If you’re applying to jobs on job boards or directly to employers, you’ll need a PDF resume in addition to your portfolio website. You may also want to create a resume page or add relevant resume details to the About page on your site.

Let’s have a look at what different web designers and developers have done with their resumes and what makes them stand out from the crowd:

1. Gracie Wilson

You’ll find a link to graphic designer Gracie Wilson’s PDF resume on the homepage of her website. This resume is not only beautifully branded (without being over the top), but it has a clean, easy-to-follow layout.

Her headshot and logo sit in the top-left corner and are followed by her contact info, education history, skills and software programs she uses. The bulk of the resume shows off her work history.

You can see that she’s used similar styling and formatting practices that we use on webpages, like larger and bolded headings/titles and short paragraphs or bulletpoint lists. This will help employers scan through and gather info from her resume.

2. Lars Olson

Lars Olson is a UI/UX designer with a special interest in game design.

If you look at his website, you’ll get a good visual idea for where his interests and talents lie. His resume, on the other hand, lays down the facts. This is a good example of how to let your website visually demonstrate what you do while the resume answers all those questions that your design can’t.

In terms of the resume we’re looking at, this is another great example of how to design and layout a PDF resume in a clean and intuitive format. There’s a clear separation between Olson’s work history (which is the most important part) and the other details, which include his summary statement, skills and software, education and related experience.

3. Annastina Cleary

Annastina Cleary is an associate art director and graphic designer. Her portfolio website is simple and to the point. You’ll find a brief bio on the homepage, which then links to two portfolio pages for Video and Branding as well as to Cleary’s Resume page.

This online resume is light on details, yet it is still quite effective. Laid out in a vertical format, visitors find information regarding Cleary’s skills, software knowledge, employment experience, select client list and educational history. Are more details needed? Probably not. Cleary’s lengthy work history shows that she is currently employed by Simon & Schuster Publishing.

4. Olaolu Olawuyi

One of the problems with the PDF resume format is that it’s usually constrained to a single page. Sometimes you have more experience to include—or you just want to let all that information breathe a bit!

If you’re looking to bridge the gap between the professionalism of a PDF resume and the flexibility of an online resume, frontend engineer Olaolu Olawuyi’s Resume page is a good one to look at. It includes all the crucial details that employers look for, including technology competency, skills and work experience.

If you don’t want to go through the trouble of creating a beautiful online resume and a separate PDF resume, do as Olawuyi does. Make the page downloadable.

5. Victor Marin

Victor Marin is a software engineer who has created an interactive resume website. Using your mouse, you get to guide the digitized Marin avatar through his resume, eventually picking up speed by hopping on a scooter.

As you travel through his world, you’ll pass by different buildings. One of them shows you where he went to school and what degrees he earned. You’ll also encounter buildings that house his various work experiences. When you’ve finished seeing all there is to see, you can circle back to “Contact” and pass through one of two doors to contact him on GitHub or LinkedIn.

6. Thomas Grangeon

You won’t find a full resume on designer and art director Thomas Grangeon’s website. Instead, when you visit the About page, you’ll encounter this section that details Grangeon’s Work Experience and Education. (There’s more information about his education up top, too.)

This is a good option if you have a separate PDF you use when applying directly on employer sites or job boards, but still want to share some details with visitors. This section blends nicely with the rest of the About info, which includes a short bio, services summary and testimonials.

7. Brittany Chiang

This is a one-page website for front end engineer Brittany Chiang. There are just three sections on the page—About, Experience and Projects. It’s the Experience section specifically that caught my eye.

At first glance, this looks like a pretty standard work history section. However, there are some really interesting details here. For starters, Chiang has included relevant skills and technologies under each job. Secondly, each position lights up as you hover over it (seen in the screenshot above). Lastly, a link is provided to each company, which is helpful if the prospective employer doesn’t know who they are.

8. Maddie Harris

One-page resumes don’t always offer up the amount of space needed to showcase your skills. Sure, you might be able to list off the primary technologies you use or disciplines you work in. But many designers and developers have a vast toolset and skill set that they work from. Maddie Harris has found an effective way to highlight those skills.

Just a little over halfway down the homepage, visitors will find this well-organized Skills section. It’s broken up into:

• UX design
• Graphic design
• Programming
• Soft skills
• Hard skills
• Essentials
• Interior design
• Visualization

It’s great that Harris included sections for soft skills, hard skills and essentials. These are the kinds of things that may get discussed during an interview, but there isn’t always room to show them off ahead of time.

9. Seán Halpin

The work experience section is an important one for job applicants. Not only does it show potential employers what kinds of jobs you’ve worked, but how long you’ve been working in the field as well. Not only that, it gives them a chance to see the evolution of your career and roles.

On the About page of Seán Halpin’s site, there is a data visualization just below the intro. This is a unique and very appropriate way to show off one’s work history in design and development. Not only do employers get to visualize all the years of employment, but they get a sense for how Halpin is able to think outside the box as a designer.

10. Adham Dannaway

Here’s another example of how to incorporate data visualizations into your resume or to present resume info on your About page. This example comes from the About page for designer/developer Adham Dannaway.

While a bar graph like this one might not work for a lengthy list of skills like the one Maddie Harris has, it works perfectly well for Dannaway. Not only does he emphasize his professional strengths, he adds some humor while doing it by adding skills like tea drinking (95%), gardening (75%) and calisthenics (40%). It gives potential employers or clients a taste of what his personality is like.

11. Champion Creative/Kristina Champion

On this About page for Champion Creative, hiring managers will find:

• Info about Kristina Champion
• Values
• Hobbies
• Career (projects)
• Clients

The section I like the most is Values. Although resumes rarely touch on this, a prospective employee’s or freelancer’s professional values can tell you a lot about them.

Oftentimes, hiring managers will ask questions that draw these kinds of conclusions during the interview. That said, providing them upfront before you reach the interview stage could help push you to the head of the line if your values align.

12. Anthony Wiktor

What kinds of details can you add to a resume that make you stand out from other applicants? Anthony Wiktor, for instance, includes an Awards section on his PDF resume (see screenshot above). He also has a truncated Awards section on his website.

If you read Wiktor’s bio, you’ll see how relevant these awards are not only to his career as a Creative Director, but also to the “competitive spirit” he touts. For employers looking for someone who demonstrates certain traits (like competitiveness and drive, for example), providing proof on your resume is a must. This may be in the form of awards, but it can also come in the form of success statistics and metrics.

Wrapping Up

When filling your resume with information, anticipate what employers are searching for and make sure the text of your resume website or linked resume is optimized for it. Then design it in a way that will capture their attention immediately and impress them as they read through it.

Short on time or prefer to keep it simple? Create a one-page PDF resume that’s well organized and easy to follow. Want to create something unique? Create a custom resume page or incorporate key resume details into your About page. Then give it an eye-catching design, make it interactive or put your own unique spin on it.

Getting started with Angular can feel like a lot at first, but once you’ve set up your environment, the pieces start coming together. Whether you’re diving into Angular for the first time or you’re an experienced developer spinning up a new project, setting up your development environment is what sets the tone for everything that follows.

In this guide, we’ll walk through how to install the Angular CLI, scaffold a new Angular project, run it locally and dissect the Angular Project File structure.

Setting Up Your First Angular Application

Angular provides a powerful command-line tool called the Angular CLI, which streamlines the entire development workflow. With it, you can scaffold new Angular apps, serve and test them locally, build for production and manage various parts of your project, right from the terminal.

Before installing Angular CLI, verify that you have Node.js and npm installed on your system. If you don’t, head over to the official Node.js download page and install an active LTS (Long-Term Support) version. Angular requires an active or maintenance LTS version of Node.js, so be sure to check your current version with:

node -v

Installing Angular CLI

To install the Angular CLI globally on your machine, run:

npm install -g @angular/cli

Creating a New Angular Project

Once the CLI is installed, navigate to the directory where you want to create your project, then run this command:

ng new my-angular-app

You will be prompted to answer a few setup questions, such as whether you want to include Angular routing and which stylesheet format you prefer. After you provide your answers, the Angular CLI will create your project and install the necessary dependencies. This process may take a few minutes, depending on your internet connection speed.

Next, navigate into your project folder:

cd my-angular-app

Running the Development Server

Angular CLI comes with a built-in development server that watches your files and reloads the app as you make changes. To start the server, run the following command:

ng serve -o

The ng serve command compiles your application and starts a local dev server at http://localhost:4200. The -o flag automatically opens the app in your default browser.

Angular Project Files Structure

In the previous section, we used the ng new command to generate an Angular project. This command creates a workspace folder and initializes a new application inside it. A workspace may include files for multiple projects, applications or libraries.

By default, ng new sets up an initial skeleton application at the root level of the workspace. Angular names the application after the workspace and places its source files in the src/ subfolder.

Workspace Configuration Files

The root of the workspace contains global configuration files, along with settings for the initial application and subfolders for its source and test files. All projects within the workspace share a central configuration file named: angular.json.

This file defines both global and project-specific settings for build, serve, test and development tools provided by the Angular CLI. It tells the CLI how to build and manage your application or library.

If you’re working with Angular 15, 16 or newer (including Angular 20), this file plays a key role in customizing CLI behavior to suit your project’s specific needs.

Open the angular.json file in the root folder of your project. Let’s analyze the configuration:

Note: As of the time of writing, Angular 20 is the latest version. While the core structure of angular.json remains consistent across recent versions, you may notice some variations depending on your version. However, I will explain some key concepts that are consistent across previous versions.

Understanding Angular.json

Let’s break down some of the key parts of the angular.json file.

Top-Level Structure

The properties at the top level of the file configure the workplace.

{
  "$schema": "./node_modules/@angular/cli/lib/config/schema.json",
  "version": 1,
  "newProjectRoot": "projects",
  "projects": {
     "my-angular-app": {
      ...
     }
   }
}

• $schema: A reference to the schema used to validate the file and provide IntelliSense support in editors.

• version: Specifies the schema version for the configuration file. It’s typically set to 1.

• newProjectRoot: Specifies the folder where new projects (apps or libraries) will be created using Angular CLI commands (e.g., ng generate application).

• projects: Contains all applications and libraries within the workspace. Each entry in this section represents a separate project and includes its own configuration block.

Project Configuration Block

Each entry inside the projects section includes configuration for a specific project. Here’s an example:

"projects": {
   "my-angular-app": {
     "projectType": "application",
     "schematics": {},
     "root": "",
     "sourceRoot": "src",
     "prefix": "app",
     "architect": {
       ...
      }
   }
}

• projectType: Can be “application” or “library”. An application is intended to run in the browser, while a library is meant to be imported into other Angular projects.

• schematics: A set of schematics defines the default options for the ng generate sub-commands in a project. Angular schematics are templates or instructions used to modify a project by generating new files or updating existing ones. They allow you to customize how components, services, modules and other elements are created within your project.

• root: Specifies the root folder of the project, relative to the workspace directory. For the initial application, this is typically set to an empty string (""), placing it at the top level of the workspace.

• sourceRoot: Points to the root directory of this project’s source files (usually “src”). It helps the Angular CLI locate your app’s source code (like components, services, main.ts, etc.) during build, serve and test commands.

• prefix: Used in auto-generated component selectors (e.g., <app-header>).

• architect: (Called targets in older versions.) Configures build-related tasks such as building, serving, testing and linting.

For a comprehensive understanding of the angular.json file structure, consult the official Angular documentation.

Application Source Files src

The src directory is the main development folder in an Angular project. It contains all the essential files required to run your application—this is where your application’s logic, components, services, routes and assets are defined.

• app/: This is where your components, routes, services and features go. With Angular 20, standalone components and APIs are now the default:

app/
  app.component.ts       # Root component (standalone by default in Angular 20)
  app.component.html     # Root component template
  app.component.css      # Root component styles
  app.routes.ts          # Application routes using standalone routing
  app.config.ts          # Optional configuration (e.g., providers)
  app.component.spec.ts  # Defines a unit test for AppComponent

In Angular 20, projects start clean, there’s no app.module.ts by default unless you opt into modules. Instead, main.ts acts as your new app entry point, using bootstrapApplication() to launch. It’s a leaner, module-light approach out of the box.

• main.ts: This is the main entry point for your application. In Angular 20, it’s the new entry point for bootstrapping your Angular app:

bootstrapApplication(AppComponent, {
  providers: [
    provideRouter(routes),
    provideHttpClient(),
    provideAnimations()
  ]
});

This replaces the old module-based platformBrowserDynamic().bootstrapModule(AppModule) pattern.

• index.html: This is the main HTML page that is served when someone visits your site. The CLI automatically adds all JavaScript and CSS files when building your app, so you typically don’t need to add any <script> or <link> tags here manually.

• style.css: Global styles for your app. You can switch to SCSS, Less or another preprocessor during project setup.

For a deeper understanding of the Angular workspace and how to manage multi-project workspaces, check out the official Angular documentation: Angular CLI Workspaces.

Wrapping Up

Angular has come a long way, and Angular 20 takes another big step toward simplifying project setup and boosting developer productivity. With the right environment setup and a clear understanding of the modern project structure, you’ll spend less time wrestling with configurations and more time developing.

In this guide, we explored Angular CLI, how to set it up and used it to generate a new Angular app. We also walked through the workspace configuration and file structure. While the structure hasn’t changed drastically from previous versions, Angular 20 fully embraces standalone components, simplified bootstrapping and tree-shakable provider APIs for a cleaner and more modern development experience.

But don’t stop here, dive deeper into the Angular’s official documentation or read through the Angular Basics series if you’re new to Angular.

Good luck, and enjoy building with Angular!

A changelog is a digital record. In it, we chronologically document the changes that have been made to software or a system. In web design, we can create changelogs for websites and applications, the documentation that supports them, and even design systems.

In this post, we’ll explain the benefits of changelogs along with tips for creating and maintaining a changelog for your digital product or system.

Why You Need a Changelog

There are many reasons to keep a changelog for each of the digital systems your team manages:

Better Communication

Changelogs are an effective way to communicate changes related to your software—and to a variety of users, too.

While it’s crucial that everyone on your development team be aware of what’s changed and when it happened, many of your end users may want to reference this log, too. Changelogs are also a good way to keep other teams abreast of what’s changed.

For example, if users start reporting the same error, your support team can turn to the changelog to see if something changed before the issue arose. It can also be a helpful resource for marketing and sales teams who may need to adjust their strategies or messaging if a feature has been removed or new ones added.

Transparency and Accountability

Think about how many applications we use on a daily basis and how little we know about what’s going on with them behind the scenes. While we’re often made aware of big releases with fancy new features or revamped UIs, not every software developer is as forthcoming when it comes to smaller or sensitive tweaks that actually keep the app in good shape—and us safe while using it.

Publishing a changelog so that anyone can see it will differentiate your product from others. It’ll also show users how well-cared-for the software is, even if you only fine-tune it once a month or so.

Accurate Historical Record

Release notes and changelogs can sometimes be confused for one another. Release notes tend to focus on the evolution of the software from version to version. It tells a much grander and flattering tale.

A changelog, on the other hand, tends to be brief and focused on technical updates. It shows users what’s changed over time, no matter how big or small. It also documents bugs, breakdowns, performance issues and other significant technical issues.

By keeping track of what happened, your team can learn a lot about what your product needs to be well-maintained and may be able to help them mitigate issues in the future.

Tips for Building and Maintaining a Changelog

If you’re looking to build a changelog for the first time or wondering how to improve an existing one, here are some tips to help you get the most from it:

1. Create a Structure for It

Changelogs can become quite long over time. To retain their helpfulness, establish a set structure for each version.

For example, your structure might consistent of the following:

• Version Number – e.g., “V3.1.5”
• Release Date – e.g., “2025-06-19”
• Improvement Type – “ADDED”
• Description – “subscription settings page to user accounts”

Keep the structure concise and uniform. You can even use a table to keep everything organized, if you prefer.

Here’s how the Nord Design System has structured its release notes/changelog page:

What we see here is a well-organized changelog. To start, there’s a section for the different aspects of the design system, like Web Components, CSS Framework, Design Tokens, etc.

Also, each version often groups the change types, so that “Adds” stay with “Adds,” “Improves” stay with “Improves” and so on.

While a set structure can improve usability, it’ll also empower your team members to contribute to the changelog. With a set lexicon and rules, everyone can help maintain it, so the responsibility doesn’t just ride on one person’s shoulders.

2. Document All Changes

Release notes are where you get to promote all the cool new things happening in the latest version of your product. Changelogs, however, should get into the nitty gritty of all the changes you’ve made, even if they don’t seem positive.

For example, your changelog should document and label these types of changes:

• Added or New: For new features
• Removed or Retired: For features that have been taken out
• Deprecated: For features that are obsolete and scheduled to be phased out
• Changed: For modified features
• Fixed: For buggy features that have been repaired
• Security: For security-related updates
• Upcoming: For features or changes scheduled for the future

By using consistent labels and documentation standards throughout the changelog, it’ll make it much easier for users of all technical levels to understand what’s changed.

Asana’s changelog is a unique example as it’s published in the developer forum:

As the company explains it:

“We chose to put the changelog in the forum instead (rather than in API documentation) for these two benefits: The forum supports comments so developers can ask questions and give feedback about upcoming changes and we can provide answers. Developers can subscribe to updates if they want to get notified about upcoming API changes.”

Regardless of where it lives, you can see that the changelog includes various kinds of changes and labels them as such—e.g., “Upcoming,” “New,” “Change” and so on.

3. Use Reverse Chronological Order

Each entry in your changelog should have a release date associated with it and a unique release number. Typically, major releases are a whole number like V2.0.0 and minor releases are written like V2.1.0.

When publishing them to the page, add the latest version to the top so the list is in reverse chronological order. The latest updates are what your users will be the most concerned with, so this will minimize the amount of scrolling they do.

This is what eBay does:

This is actually the top of the release notes page where extra details and fuller explanations about the release updates are written out down below. However, this table provides a succinct summary of the changes made in each release, starting with the most recent.

Another nice touch to this page is the API release history found on the right sidebar, so that users can click and go to a release they’re interested in exploring further.

4. Keep the Language Simple and Accessible

Even though a changelog is a technical document, it doesn’t mean it needs to be complex and too complicated for a layperson to understand. Keep it short and keep the wording straightforward.

Also, consider your audience. Unless you know that everyone who accesses the changelog will be from the same country and speak the same language, you’ll need to verify that it’s accessible.

Simple language will help with this. So, too, will version and date formats that everyone can understand. For example, instead of writing your release dates as MM/DD/YYYY, write them as YYYY/MM/DD.

Another option is to write the date out in full as Spotify does:

This changelog is no longer publicly accessible, but you can see how easy it is to find the version number and date, and how user-friendly the formats are.

Another deviation I should call attention to is the format of this changelog. Spotify doesn’t appear to publish changes by announcing the change type first (e.g., “Added,” “Deprecated,” etc.). However, it has written this changelog in simplified language and provided reference links so that users can learn more about each of the changes.

5. Keep a Schedule

Your changelog is a reflection of how well-maintained your software or system is. To help users and team members notice this, make updating the changelog in tandem with releases a priority. And create a schedule for these releases, even the minor ones.

Releases don’t need to come out every week or even biweekly if your software doesn’t need a ton of maintenance. But find an update schedule that works for you and stick to it. This will help set expectations with your users and it’ll also keep your team attuned to what’s happening with the product and experience, so they can keep it in the best shape possible.

The Instagram changelog, for instance, appears to follow a monthly schedule (for the most part).

Although there are some months that get skipped, you can see those instances usually follow a month where there were numerous releases. So, if your team can’t or doesn’t feel the need to commit to an exact release schedule, this is a good way to go about it. Aim for once a month (or whatever your preferred schedule is), but don’t commit to any specific release dates.

Also, not every release will be scheduled ahead of time. For example, let’s say customer support notifies you of a bug or your team has discovered a security vulnerability. These kinds of changes can’t wait until your scheduled releases. Patch the issue ASAP and issue an update to the changelog once it’s done.

If your team works overtime to repair something urgent, you can always push the next release back to give them a breather (which may be what Meta/Instagram has done).

Wrapping Up

Documentation is so incredibly important when you’re in charge of building and maintaining software and systems. But we don’t just need documentation to tell us about features or how to execute processes. It can also let us know where we’ve been, what we’ve done, and to lay down a track for what’s to come.

This is why it’s vital to have a changelog for every application or website you build along with any design systems or documentation repositories you maintain. The changelog keeps an accurate record of what’s been done, provides other teams and the public with transparency about what you’re working on, and also teaches you more about what your application needs to thrive.

YouTube just turned 20 years old. This pioneer in video marketing and storage has undeniably changed the digital sphere forever. One could argue that, thanks to YouTube, video has become one of the most powerful tools we have as marketers.

Video not only offers users an easy-to-follow format, but a hyper-engaging one as well. Even in shorter video formats, marketers have mastered the art of user engagement.

Whether you’re new to video marketing or looking to refine your strategy, this post is for you. We’ll look at strategies that can help you create and promote videos for maximum impact.

5 Tips and Strategies for Videos Marketing

You can use video in so many ways in marketing:

• In online ads
• As part of your website design
• To accompany your blog or podcast
• To host live or prerecorded webinars
• On social media

Sometimes it feels like there’s too much you can do with video. The trouble with this is that video can be a time-consuming (and costly) medium to manage—from sourcing or creating the content to editing and distributing it. So, you want to spend your time making the right kinds of video content for your business.

Here are some tips that will help:

1. Create Videos That Align with Your Marketing Goals

When you develop a marketing strategy, it’s critical to have certain objectives you want to accomplish. These objectives—like the big brand goals that impact everything beneath them—need to be SMART:

• Specific
• Measurable
• Achievable
• Relevant
• Time-bound

What’s more, you need to have marketing goals based on your target audience as well as each leg of the unique journey they are going to take with your brand from discovery to conversion. And if you have different audience segments, you’ll need to devise separate objectives for each group.

This is why your video marketing strategy needs to be carefully thought out. You don’t need to use video in every piece of content you publish or message you share. But when you do use video, it really needs to count. Knowing your audience well and what resonates with them will dictate when and how you put video to use.

Let’s use the example of FitOn. This fitness app often publishes videos on its Instagram channel. Most of the videos showcase one of their trainers. However, you can tell there’s quite a variety in terms of audience as well as purpose.

For example, this video says “I wonder how she stays so motivated to workout?” The response is to show her “inner hype girl” dancing and cheering her on.

It’s a funny video that anyone can relate to, from the long-time fitness enthusiast to the newbie who might be feeling intimidated or unmotivated. This would be a great video to introduce FitOn’s fun personality to a brand new audience while keeping its existing user base smiling.

Not all of the brand’s videos are like this though. Some of them are instructional, like this one:

Here we see one of the trainers demonstrating a workout sequence. This video is possibly targeted at these user segments:

1. People who’ve never heard of FitOn before and are wondering what kinds of workouts they’ll find on the app
2. People who haven’t been in the app in some time but who get excited when they see new workouts are available

In general, marketing videos can help you:

• Generate awareness about your brand
• Educate users and non-users alike
• Hasten the decision-making process
• Direct users to checkout/conversion
• Upsell users on a new service or product
• Improve user retention rates
• Strengthen brand identity and memorability

Once you get inside the minds of your users, you’ll be able to craft video content and campaigns that appeal to them over the course of their relationship with your brand.

2. Make Sure They Work with Your Brand Identity

When you see a certain type of video go viral on TikTok or rack up millions of views, it’s not the video format that made it so popular. There was something special about how the brand or person behind it put it together.

Because of how much work goes into video marketing, you’ll need to do a lot of research into what kinds of video make sense for your brand. Not only that, you need to consider the aesthetics of it. If it doesn’t fit neatly within the rest of your brand’s visual identity, users might shut it down before they discover how intriguing, helpful or funny your message is.

One brand that does a great job of pairing its video aesthetics and messaging with its brand is Unbabel.

This screenshot comes from the welcome video on the homepage of the website. Without seeing the video for yourself, can you guess what this company does?

There are a number of languages visible on the screen—English, Spanish, German, Italian, etc.—so it’s safe to suggest that it’s a multilingual app or solution. And with the sleek animated design and automation imagery found later in the video, one might assume that it’s an AI-powered solution, too (which it is).

Explainer videos are a great way to educate potential users about your solution. But they’re not for every business. At least not in this format.

Think about something like the Dollar Shave Club video that put the company on the map. That explainer video/ad was just the founder of the company talking about how “f***ing great” their razors are.

So, the lesson here is to not write off a video format based on ways you’ve seen it done before. If you feel like the format would work for your purposes, see if there’s a way to make it work with your branding.

For example, this video has 2.4 million views on TikTok. If you didn’t see the brand’s name—H&M—on the page, you probably wouldn’t have a clue it was theirs.

The video shows a woman lying back on a bag on a beach (though it’s not that easy to tell what it is unless you read the caption). In the background, we hear the sound of the ocean. That’s the entire video. It’s peaceful. It’s definitely FOMO-generating. But does it make you want to buy something from H&M? Maybe. Maybe not.

That’s the thing about H&M though. The brand is very influencer-inspired. The brand’s entire vibe and aesthetic feels aspirational. So, while this video post might not be a direct call to action for the brand, it fits really well with the brand identity it’s trying to establish.

3. Come up with Channel-Specific Strategies

Once you’ve come up with a plan for which channels you’re going to post videos to, it’s time to create your content.

The easiest and fastest thing would be to create some videos and then to share them on all your platforms. The problem, though, is that not every video type works for every platform. Plus, marketing channels often serve different purposes for brands.

For example, this is the website for Brett Larkin. The hero section contains a beautiful video reel.

Larkin could share this video over email and on social media, but it probably wouldn’t make sense to do so. This video is meant to introduce people for the first time to Brett Larkin. If someone has subscribed to her email or followed her on social media, this video might be able to get them to stop for a few seconds, but that’s all. They’re well aware of who she is.

There are definitely some kinds of content you can repurpose. But video is tricky. Not only do you have to consider your users’ mindset and goals based on the channel they’re on, but you have to think about the channel’s features and style as well.

Take Instagram vs. YouTube, for instance.

This is a response video that Larkin did on her Instagram page. In it, she talks about certain poses she no longer does in yoga and why.

The short response video format is pretty common on platforms like Instagram and TikTok. There are even tools that allow you to take someone else’s video, superimpose your talking head over it and respond in real time.

But you couldn’t (or, rather, wouldn’t want to) produce something like this for YouTube. Larkin, for instance, has a well-crafted collection of lengthier instructional video content on her YouTube channel.

For educators and coaches like Larkin, YouTube acts as a repository for video tutorials and courses. That’s not how everyone uses it, of course. But that’s why you need to know your business and your audience well so you can choose the right video formats and content for each channel you do video marketing on.

4. Start with a Script or Storyboard

Whether you’re filming your own videos or piecing them together from stock video footage, you should have a “story” in your head before you get started. This will allow you to visually and orally tell a story that hooks your audience from start to finish.

Script outlines help you get the spoken message hashed out before you bring the visuals into play. Also, taking the time to write a concise and user-friendly script will allow you to produce a transcript for users who are unable to listen to your video’s audio (more on that in the last point).

Storyboards take care of the visual story told in your video. They establish the storyline or the order in which the visuals should appear. They also help you come up with an overall concept that brings the whole piece together visually for your brand.

The HGTV Smart Home Sweepstakes video is a good example of what happens when you put time into storyboarding.

This is one of the first frames of the video. The title invites viewers to “Step Inside” the smart home prize.

What I find so neat about this video is that it’s reminiscent of those 3D Matterport walk-throughs used in real estate. Except, instead of an interactive 3D model, viewers are taken room by room with the video.

This video also has a vibe similar to MTV Cribs. If you’re not old enough to remember, this was a show where celebrities invited viewers inside their homes and they’d take them from room to room, showing off how cool their pads were.

Considering these smart home giveaways are often worth over a million dollars, I suspect HGTV may have drawn inspiration from that show when putting together these videos. The tracking movements of the camera and the labeling of the rooms all feels very familiar. And this familiarity—along with the allure of winning such a big prize—is sure to keep viewers watching until the end.

That’s exactly what a well-thought-out script and storyboard can do for your videos.

5. Technically Optimize Your Videos

The last key to success in video marketing is paying attention to the technical details. In doing so, you will:

• Enhance the quality of your videos
• Improve the impression your brand makes on its audience through video
• Improve page speed, accessibility and other factors that impact your ranking

Let’s take a look at a couple examples.

This first one comes from the Rolex website. The hero section contains a vertical scroller of five videos. Each one seamlessly slides in after the previous one. There are no delays in loading, no lags in performance or anything like that.

One of the reasons for the smooth performance is likely that this vertical scroller is the only content on the homepage. If it contained sections below it (besides the footer), it might have delays in the video loading times. But as it stands now, it offers a good user experience.

Something else to think about, which I touched on previously, is accessibility.

On social media, it’s expected that videos will come with audio. But not on websites. In fact, autoplay audio is generally frowned upon because of the friction it can create for some users.

The best way to get around this is to incorporate subtitles or a transcript. Here’s how that looks on this Sephora product page for the Ultra Violette Future Screen SPF 50.

This video lives inside the product image gallery on the left. When selected, the video opens and the subtitles/closed captions automatically display.

Being proactive and attending to technical details like these can help your audience reach a wider audience and have a more positive impact on your marketing outcomes.

Other technical details you might want to think about include:

• Video file size
• Embedding vs. self-hosting the video
• Length/runtime of the video
• Adding title or end cards
• Adding branding or overlay text
• Editing the visuals, like removing bad cuts and wobbly video
• Cleaning up the audio

This might be the least fun part about doing video marketing, but these details can make or break the user experience for some. You can incorporate some of these decisions into the storyboarding process, but the rest you’ll have to save for the end. So, make sure to leave yourself time between producing the video and publication to give it a good polish.

Wrapping Up

YouTube might not be the only place where we publish videos anymore. But it certainly paved the path for us.

Video when done right can do a good job at moving the needle on your marketing efforts.

It’s a great way to differentiate your content from those who use only text and static graphics. It can direct your users’ attention toward your most important announcements and valuable content. It can improve users’ decision-making process by providing more details in a user-friendly format. It can also be useful in SEO, not only making your webpages more engaging (which Google loves), but also giving them more opportunities to rank in search.

As with everything else in marketing, the key is to lay down a strategy first. Then, start small. Your video marketing efforts should not only serve your brand’s goals, but should be tailored to what your users want to see and interact with most.

When building an application or website where your end users or employees can log in, you have to make a choice:

Is a password alone enough to secure their access and account details?

If it’s not enough, how do you want to incorporate two-factor authentication (2FA) or multifactor authentication (MFA) into the process to enhance security?

There are a variety of authentication methods you can include when developing the login procedure for your website or app. In this post, we’re going to look at how multifactor authentication works, when to implement it and when to choose 2FA over MFA.

The History of User Identity Verification

Multifactor authentication is a security procedure during login that requires users to confirm their identity using at least two different methods. The goal is to help prevent anyone who is not the user from gaining access to their account.

Let’s say you’re building a digital product with a login. For example:

• A mobile banking app
• An ecommerce website
• An applicant/hiring portal
• A social media platform
• An apartment listing website

Traditionally, the login screen would ask for the username and password.

In 2000, CAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart) was created and Google brought it to the mainstream in 2009.

This test often shows a series of letters or numbers or a simple math equation. When the user enters the correct answer or repetition of characters, they are deemed safe to log in or enter the digital space.

reCAPTCHA is an offshoot of CAPTCHA. This test scans letters, numbers and sometimes images from real books. Users again have to provide a correct answer or input to get through the digital barrier.

Then we started seeing this “Verify you are human” checkbox, this one is on the Indeed website and it’s powered by Cloudflare:

Another form of this you may have encountered is an image puzzle. The most common one is the image broken up into 9 boxes. You need to select the boxes that show the image from the prompt.

For example, I just saw this when checking out on the Tesseract Medical Research website:

There are ways to make these kinds of puzzles more complex, like what Zocdoc does here:

Users not only need to drag the puzzle piece into the matching puzzle piece, they have to do it in a reasonable timeframe.

Technically, these are all forms of two-factor “authentication.” The goal, though, isn’t to confirm the user’s specific identity. It’s to confirm that they’re not a bot scammer trying to bypass the login screen through nefarious hacking methods.

But bots aren’t the only ones we’re trying to keep out of our users’ accounts.

Multifactor Authentication Methods We Use Today

Today’s multifactor authentication methods are much more secure than the ones aimed at bot-driven scammers. Today’s MFA methods are designed to prevent a different person from getting into someone’s account.

Here are some examples of two-factor or multifactor authentication methods than can be used to prevent unauthorized access to someone’s account:

Security Questions

Although they’re not as commonly used these days, security questions used to be one of the more common forms of MFA used in previous years. Questions would include things like your mother’s maiden name, the street you grew up on and your childhood pet’s name.

While you might be hard-pressed to find a website or app that still employs security questions during the login process, they’re still out there. PayPal, for instance, collects this information from users, likely as a backup if their PIN code fails to work.

What’s good about PayPal’s security questions is that they steer clear of the questions we frequently answered in the past. For instance, here are the current questions offered:

• Your first school’s name
• Your first pet’s name
• The hospital where you were born
• The nickname of your oldest child
• Your father’s middle name
• The name of the toy you cuddled with as a kid
• Your first roommate’s name
• Your grandmother’s maiden name

This way, if those prior security questions were leaked somewhere on the web, hackers may find it a more difficult to get past this verification step.

What’s surprising is that security questions aren’t used that much these days. My guess is because it’s seen as too much effort on the part of the users. Whereas with the other methods we’re going to look at, this one requires accessing personal memories and then typing out a response. More modern MFAs can be completed in a few taps (if that).

PIN Codes

With this method, the user first enters their username and password. Then, they’re sent a one-time passcode to one of their designated forms of contact—SMS, phone, email or WhatsApp.

Some applications give users a choice during login, like Discover which allows them to receive a text message or phone call.

When the message shows up, it’s typically a six-digit code like this one:

This can be an effective way to verify the identity of a user. However, if someone has stolen their device, this PIN code won’t be able to keep bad actors out.

Authentication Apps

There are a number of authentication apps that users are able to install on their mobile devices. Google Authenticator and Duo are the most popular. In order to use the authentication app, the user must scan a code from the application into it.

For example, these are the instructions provided by Instagram in the security center on how to enable MFA:

The user then copies the key (string of numbers and letters) or scans the barcode/QR code into the app. Once entered, the user will retrieve a time-sensitive six-digit code in order to log back into Instagram.

Similar to the PIN code method, this one isn’t foolproof as someone with access to the user’s mobile device can retrieve the authentication code.

Biometric Data

There are typically three kinds of biometric data you can request from users to authenticate their identity:

1. Face
2. Fingerprints
3. Voice

Most mobile devices these days offer this option as a way to keep users’ devices locked and private. For instance, here’s what Samsung offers from the security settings:

When enabled, only the device/account owner’s face or fingerprints will open it up.

It’s not just mobile devices that use this type of MFA either. Mobile apps do as well. That said, it’s very rarely the primary MFA method offered. One of the more likely reasons is accessibility. For instance, it may be easier for less tech-savvy users to input a code rather than figure out how to set up and use their fingerprints to unlock an account.

Considering how difficult it can be to hack someone’s biometrics, I suspect this will become a more common MFA method over time.

Passkeys

Passkeys are one of the newest MFA methods. Sort of. Typically, if passkeys are enabled, then the user doesn’t need to enter a password every time they log in (though a password itself is needed to create the account in the first place).

Biometrics are a form of passkey. However, there are other ways to set up passkeys for your application.

One option is to connect the screen lock passkey of the device being used to the application. So, when they log into the app, they enter their device’s code to log in. Canva, for instance, offers this as an option along with biometric scanning.

The user has a choice as to where they save the passkey. It can be through their device. The other option is to save it on a physical security key.

PayPal also offers a physical security token option for users. It’s not easy to find though. It’s tucked away under “Additional Security Features.” However, for users who are extra serious about safeguarding their financial data, using a physical USB device to verify their identity can be a good way to go about doing it.

The biggest risk with this method is losing the security key. Because if you lose that USB device or the unique passkeys associated with your device or account, you could be permanently locked out.

That’s why it’s important to enable multiple factors of authentication and not just one backup to your password. So, if you’re going to use passkeys, make sure to also enable SMS messaging or use an authenticator app.

Choosing Between 2FA and MFA

There are a number of things you need to ask yourself when setting up the security system for your login procedure:

• Is MFA necessary?
• If it’s not necessary, do you think some users would still find it valuable to have the option available?
• If you decide to enable it, how many methods are you going to incorporate? And which ones?

The difference between 2FA and MFA is that 2FA only has one additional authentication method outside of the password. MFA has two or more.

So, does it really matter which one you use? Sure it does.

For starters, think about usability and accessibility.

There may be certain methods that users aren’t comfortable using or are unable to use. Think about users who don’t have smartphones or who rarely use them and don’t know how to do something like install Google Authenticator.

This is why it’s important to enable multiple methods that ensure that everyone has the option to add extra protections to their account. And only requiring 2FA or MFA when it makes sense.

Then, you have to consider the user experience.

What is the purpose of your application and what kind of data is stored within the user’s account? If it’s not complex or super sensitive, do you really need to put them through the rigamarole of verifying their identity multiple times or using different devices in order to do it?

You don’t want your users feeling stressed or annoyed every time they have to log in.

Also, take into account the risks.

If you’ve built an application that operates within a highly regulated space like healthcare or finance, strict MFA procedures may be a necessity.

Another way to think about this is by user. Not every account holder may have access to sensitive or privileged data. In that case, it might be beneficial to enable 2FA for lower-risk users and MFA for higher-risk ones.

Why You Should Implement 2FA or MFA

According to CISA, the most popular password used in the United States is 123456.

This is just one reason why it’s critical that web developers enable MFA when building apps and websites. While we’d love to believe that users care about their data security and privacy (which endless surveys have demonstrated), we know that many of them don’t take the right steps to secure their accounts.

It’s not their fault, really. Think about how many accounts you have created or logged into in the last month. Does your brain have the capacity to generate a unique password for each of them and then recall it? Probably not.

While there are password generator and storage apps like Zoho Vault and 1password that can help with this issue, many people don’t use them or even know they exist. What’s more, these unique passwords can still end up on the dark web and available for purchase and exploitation.

Because of this, we need to enforce better security practices at login. The early CAPTCHA and puzzle tools helped with the bot problem, but not entirely. And MFA methods like authenticator apps and PIN codes are good for defending against bad actors, but aren’t entirely hack-proof.

To help keep your users’ information safe, equip with your app or website with multifactor authentication. So long as you give your users some choices and that they don’t intrude on their experience much, MFA should actually help you build customer trust over time.

Turmoil and chaos can come from anywhere.

There could be external factors that disrupt the entire world, like lockdowns, recessions and tariffs. There could be factors that impact your work or industry specifically, like the introduction of GDPR, the rise of AI or Google’s cookie deprecation announcement. Then there’s internal chaos caused by layoffs or reorganizations, public backlash against your brand and even problematic clients.

How are you expected to thrive, let alone focus, in the midst of such chaos?

If it feels like you’re constantly stressed and struggling to bring order to your workday, this post is for you. We’ll look at some strategies you can use to proactively and actively deal with chaos, regardless of where it comes from.

Strategies for Navigating Turmoil While You Work

None of us can predict the future. Which means chaos and turmoil are just a natural part of being human.

That said, chaos can bring some not so positive outcomes if you get wrapped up in it. If you need help navigating the chaos within or outside your workplace, here are some strategies to help you adapt and overcome it.

1. Come Up with an Action Plan

According to Merriam-Webster, chaos is:

“a state of utter confusion”

Or:

“a confused mass or mixture”

Let’s assume your workspace isn’t burning down and that the chaos you’re experiencing (internally or externally) is manageable. Then that’s exactly what you need to do. Manage it.

To be clear: You don’t need to solve the problem yourself in order to make the chaos or the effects of it go away. In some cases, that’s not even feasible. But let’s use an example.

Your team consists of web designers, web developers, marketers and a project manager. The project manager just up and quit last night. Your team relies on this person to keep the flow of projects moving smoothly and monitors each task and stakeholder to along the way.

You could ask a project manager from another team to step in, but that doesn’t seem fair. They’re already stretched thin with their own projects. So, what do you do?

It’s OK to feel stressed. However, you and your team need to find a way to pull everything together until someone steps into the project manager role and takes hold of the reins.

Working together to come up with an action plan is your best course of action. Here is what it might look like:

• Contact management about the project manager’s departure and ask for a plan and timeline for hiring a replacement.
• Schedule a 60-minute team meeting for this morning. Put together an agenda for the call.
• Delegate the project manager’s tasks to various team members based on everyone’s capacity. Try to distribute the tasks fairly.
• Get access to the project manager’s accounts (task management tools, email, etc.) and review what’s in there, verifying nothing urgent is waiting on a response.
• Review where each project stands. With the staffing shakeup and additional responsibilities on each person’s plate, adjust the timelines as needed.

Make sure to put your action plan into writing and to formalize it within your workflows and project management tools. Anything that was previously assigned to the project manager will now need to go to the team member in charge of that duty. This will keep everyone’s duties straight and hold people accountable to their share of the work.

By sharing the load with others and coming up with a clear-cut plan, your team will be able to adapt until a better solution comes along. This will prevent people from freezing up, freaking out and throwing your entire organization out of whack.

2. Focus on What You Can Control

Our bodies are hard-wired to respond to danger and chaos, which can make it difficult to sit still or stay calm. But that’s exactly what you need to do in order to get through the situation.

One technique you can use to stay clear-headed is to focus only on that which you can control.

For example, let’s say that a new international regulation like GDPR or the AI Act has been announced. Or maybe something is changing with SEO, like the Google Page Experience update.

In my personal experience, I remember clients panicking over GDPR.

What is it?

Is it only for the EU?

How will it affect my business?

Does this mean I can’t track data anymore?

What if I don’t know how to add a consent banner to my site?

What happens if I miss something and I’m not compliant?

The first thing you can do in these situations is to educate yourself. If you don’t understand what has changed or how the disruption affects your operations, you’re either going to freeze up and take no action or panic endlessly, worrying about every possible worst case scenario. Neither of which is good.

When you have a good grasp of what’s happening, focus on what you have control over. To worry about anything else will only exacerbate your stress and make it difficult to get your work done.

So, let’s say there’s something like GDPR that’s about to go into effect. What should you focus on?

Start by auditing your own website’s data tracking procedures.

• Identify the methods of data collection and the areas of the site where the data is picked up from.
• Review your privacy policy to verify it is transparent about how the data is collected and how it’s used.
• Add tasks to your list to create a cookie consent popup notice and to enable opt-in/opt-out settings for your users.
• Revise your internal data collection and management processes as needed.

Once you’ve got a handle on how to deal with the chaos internally, turn your focus outward. Reach out to clients, informing them about the upcoming changes. Provide a recommended course of action along with a price for this data privacy audit/setup service. Then wait for them to respond (if they choose to). That’s all you can do.

Another thing I would suggest is to spend your time wisely. Let’s say the chaos doesn’t have a direct impact on you. At least, not yet. Take the U.S. tariffs, for example. There’s not a whole lot you can do until you see if they have an impact on your business’s operations.

If you find yourself stressing about this possibility, spend your time instead on making things better behind the scenes. Identify obstacles and inefficiencies in your workflows. Come up with ways to streamline things, like unifying your software, implementing AI automation and creating templates.

Even if the chaos doesn’t have a direct impact, it will have motivated you to focus on what you can control and, regardless of what happens, improve your situation.

3. Know and Avoid Your Stressors

Navigating stressors and triggers while you’re working can be tricky depending on what they are. For instance, let’s say you have a coworker or manager who’s always wreaking havoc when things are coming down to the wire. So, everyone usually has to stay late to scramble and get the job done. In that case, it’s not like you can just avoid that person.

However, as I mentioned earlier, chaos doesn’t always come from inside of one’s organization. Let’s say it’s something bigger that’s happening around the world.

The second someone mentions it or you catch a glimpse of it on social media or your favorite news site, it gets you spiraling. You can’t stop talking about it with coworkers or you start endlessly doom-scrolling online. Suddenly, an hour or two passes and you’re behind on work.

It can be tough when you encounter something that triggers this kind of stress-induced response. But you’ll need to become more aware of it when and even before it happens.

To do this, think back to other times you’ve felt triggered in a similar way. What caused you to go into distraction or obsession mode? And what pulled you out of it and back into a more productive and healthy frame of mind?

Start with the causes. What sorts of turmoil and chaos really gets under your skin? Where have you encountered it in the office or online? When possible, remove those sources of stress from your routine. For instance, if TikTok reels have sent you spiraling before, use a distraction-blocking app to prevent you from visiting TikTok during the day.

Next, look at the ways you’ve disrupted those patterns before. Did you step away from a conversation and go for a walk outside? Did you set a timer that pulled you back to your desk and work? Was there something else that helped?

Lean into your strengths and away from your disruptors. This will help you bring some order out of the chaos and the stress that it brings.

4. Release the Negativity from Your Body

Chaos can create a lot of tension within ourselves. Holding onto that tension and discomfort will only prolong the effects that the chaos has on you (even after it’s passed).

Here are some small things you can do to relieve the negative feelings getting stored up in your body and to reset yourself during these chaotic times:

Smile.
I don’t mean this in the condescending “Why don’t you just smile?” way. I mean this in the scientific way.

Neurologist Dr. Isha Gupta says that smiling creates a chemical reaction in our brains. Feel-good hormones like dopamine and serotonin are released in the process.

“Dopamine increases our feelings of happiness. Serotonin release is associated with reduced stress. Low levels of serotonin are associated with depression and aggression. Low levels of dopamine are also associated with depression.”

In customer service, I was always taught that if you force a smile on your face while speaking (even when you’re on the phone), it can change how you feel at that moment. Anecdotally speaking, it works. And Dr. Gupta explains why in the quote above.

Reframe your thoughts.
If you find yourself having more and more negative thoughts, try to catch yourself while you’re doing it. For instance:

“Everyone sucks.”

Yep, we’ve all been there before. You’re feeling overwhelmed and burned out, and there seems to be no end to the chaos or drama. In the moment, it really can feel like you’re all alone and everyone does suck.

But here’s the thing: Reframing negative thoughts works similarly to putting a smile on your face. By removing negative thought patterns, you can stop the endless cycle of negative emotions from weighing on you.

So, when you catch yourself thinking something like the above statement, change it to something more empathetic like:

“We’re all struggling right now. But we’re going to get through this.”

Even rewording negative statements like “I can’t” into positive ones forces you to shift your emotional state and way of thinking to a more productive one.

This doesn’t mean you need to say “yes” to everything thrown your way. It just means finding a healthier way of framing your response like, “I would like to help with the website audit. However, I have this load test that Client A has been waiting on for 3 days.”

Collaborate and connect.
One of the problems with chaos is that it can throw everything and everyone out of order. It can even force wedges between people. That wedge between you and others doesn’t need to be long-lived though.

So, let’s say word has spread that layoffs are coming. This is not the time to isolate yourself from others, be they your coworkers or your loved ones.

Chaos doesn’t just affect your life, it often affects everyone around you. So, when you find yourself in a tumultuous state, reach out and connect with others. Even if it’s to send an email to a remote coworker to see how they’re doing or to discuss something positive from your lives to take the focus off of what is coming down the line.

Move your body.
During a chaotic time, it’s common to find your body has tensed up. It’s part of our natural responses as humans.

According to this article from Healthline:

“When you experience a stressful event or a bout of anxiety, your muscles contract, sometimes forcefully. This is an automatic or reflex reaction. It’s known as a stress response or ‘fight or flight’ response. It’s your body’s way of gearing up to face a perceived physical threat that you’ll need to fight off or run away from.”

The problem is, you’re not in danger of becoming food for a lion or bear like our long-ago ancestors were (at least I hope not). Yet, your body still responds as if it is. So, you need a way to release that tension so it doesn’t stay with you.

How you move your body is a personal choice. Some people walk out their tension. Others do yoga or pilates. And some hit the gym. Even some light stretching and shaking out your hands and shoulders can be helpful, especially if you don’t have time to immediately address how you feel.

Wrapping Up

Chaos isn’t fun. From the rapid onset to the unpredictability of it all, it can feel almost impossible to get a hold on things while it’s happening.

If you don’t deal with chaos (or, at least, your response to it) the right way, it can lead to feelings of hopelessness and depression. Inevitably, this will lead to burnout.

The good news is that you can adapt to chaotic circumstances. By navigating around the chaos, you won’t get swept up or feel as though you’re drowning in it. And once it passes, you may even come out the other side with a new set of skills and adaptations that build your resilience for whatever the future holds.