Life is all about balance. Anything in excess is never good for us, and the concept of balance can be very different for us. Some have a fast metabolism, so how they balance their diet depending on their goals may be different than someone else. When it comes to people's careers, some might be happy with where they're at, while others in the same situation want to keep climbing the ladder. Some have a family and want to spend more time with them, or maybe a baby is on the way, and now you need to up the household income.

As you can see, there are many different situations that people can be in. How you can achieve a balance with all of those variables can be very different depending on your situation. To achieve that balance, it would be best if you had an intention with the planning of your time depending on your situation and the goals you want to achieve.

🤔 What are your goals?

I feel we all have needs and wants in life. Some are more significant than others. Short-term goals can seem easier to hit, in my opinion. I feel this is because we put in the short-term work, and then we get the immediate gratification of achieving the short-term goal.

Long-term goals, I feel, can be the hardest. We don't get immediate gratification or that dopamine hit we want for achieving something. They can be harder to measure over time due to the complexity of the goal. Because it's more of a long-term plan, people can often lose their motivation due to the consistency of what it will take to get there.

Say you're trying to buy a house. You have to determine how big of a place you can afford, save for a down payment, find a realtor, select the style of home you want, negotiate contracts, close, move, etc. As you can see, there are many moving parts, and as a whole, it's intimidating. So let's break it down into bite-size pieces.

📏 Make the long-term goal a series of short-term goals?

We've been groomed to want that dopamine hit based on today's culture and society. We've come accustomed to it due to the instant gratification we get in the fast-paced world. Everything is about getting things now and faster in a more convenient way. Tech is created every day to achieve this very thing.

How can we get that dopamine hit we crave and love with long-term goals? Break them into short-term goals! With long-term goals, a series of complex short-term things need to happen to make them come to a reality.

The short-term goal: cut down monthly expenses. If you cut out eating/drinking every Friday night, that's an $80 savings. In one month, that's $320 saved. In a year, that's $3,840 in savings. Just by not eating and drinking on a Friday night.

This is by changing only one action. Break each goal into bits and pieces to discover what else you can do to accelerate your progress.

🗓 Put it on the calendar

By putting things on your calendar, you're making time for your priorities, goals, and other things you're passionate about. Make your calendar balanced and sustainable for yourself and your loved ones.

Everything that takes up your time should be on your calendar. All we have in the day is our time. How we choose to use and spend our spare time surrounding our obligations will determine how fast or even if we hit our goals. So calendarize it.

If you have to go to work, take and pick the kids up from school, do groceries, make dinner, help with homework, go to a class, do homework, and study even more after reading. Also, the driving time between all of these things should be on your calendar.

Regarding your spare time, if you want to spend more time with your significant other, your kids, friends, and family, watch a movie, learn a new skill, or anything else. Please put it on your calendar.

📌 Update your calendar as it changes with checkpoints

Life happens. Again, we're creating a plan on where and how we're investing our time to accomplish our goals with a balanced approach. Modern calendars have a drag and drop function to set it for another time if things happen. The task still needs to get done or made up, so drop it into another part of the week or hours in the day to accomplish it. Hold yourself accountable.

Lastly, but most importantly, set checkpoints for each of your short-term goals. Assess how far you got with them with your existing plan. Did you crush it or fall behind? What behaviors made you successful, and what obstacles got in your way? Assess and adjust for the upcoming month depending on what you're trying to achieve and how fast you want to get there.

-RAllanVila

So whether you're going the self-taught route to becoming a developer or you're new to the industry, being able to constantly and consistently learn things is a must. The technology and tools we use are ever-evolving. Lib dependencies are breaking or have new vulnerabilities, and sometimes the best tool you've been using has become stagnant, and there's new tech on the block that does it quicker, faster, and better with a smaller bundle size. We, as developers, need to be agile learners.

How we've learned in the past

Let's go back to grade school. In grade school, each year, we took language arts, math, social studies, phis ed, etc. As we learned what we needed in each subject throughout the school year, we'd be assigned classwork and homework to repeat the same concept repeatedly so we could understand it. Once we've replicated the task enough, we'd get tested and make sure we knew everything we needed to graduate that grade and move on to the next grade.

In the next grade, we'd use the same foundation of what we learned before. However, now with more profound complexity, to solve more intricate math problems, spell longer words in language arts, and understand how we evolved throughout civilization in history.

As you can see, we'd be taught a subject by one teacher, then do the homework and classwork to repeat and learn the concepts. Once we were tested, we'd learn more complex things.

Are you on a hamster wheel of learning?

I average around 7-10 coffee chats a week with aspiring developers trying to break into tech. The most common mistake I see amongst everyone is that they're on a hamster wheel of learning and not letting themselves graduate from a concept. People that love learning to code, however, they're spending more time learning instead of doing the classwork, homework, and projects to apply their lessons learned.

So let's think about the above. K-12, thirteen years of our lives, we've been learning math and all the different complexities about the one particular subject. Society then tells us after we're 18, we've learned the basic skills to be functional in the world regarding math with what we've learned in school. However, you can level up and go to college to deepen your learning. Still, we've not learned everything about math as we can go after a doctorate with still a possibility of things to further understand.

I see so many individuals doing class after class, youtube videos after youtube videos, conversations after conversations to find the magic course and tip that will make it click. We didn't learn like that growing up, so why are you doing this with Javascript, React, Node, SQL, and everything else???

What are you trying to learn?

If you're learning to become a front-end developer, build front-ends. If you're learning to be a back-end developer, build back-ends to applications. However, learn what you need to know along the way WHILE you're making it.

Your teacher teaches you a new subject

Take ONE max TWO classes or tutorials. A crash course on youtube on the tech you're trying to use that's under an hour.

You're now doing your classwork:

Code along with the YouTube video or course you're following. You're having guided learning just like you would in a classroom, and the teacher is there to assist you and walk you through how to build what you're making in the video.

You've been assigned homework:

Now build something on your own using the basics and the foundations of what you learned above immediately afterward on the project you're currently building.

How do you know when you've graduated?

Suppose you were learning to be a front-end developer and built a front-end or a back-end developer and can build a back-end. Congratulations! You've graduated! You are learning only to be able to do these things, don't be stuck in the 1st grade because you're waiting to know and understand everything about Javascript. You need to know everything to be a developer. You need to know the foundations to understand how to google specific things later.

In Javascript, you have variables declaration, dynamic typing, objects, arrays, functions, operators that enable you to write conditional statements and loops. As you can see, look at all the things above that pertain to only arrays. Don't make yourself feel like you need to learn these to become a developer or build a project. You'll discover them over time as you continue to build. You need to know to apply the core foundations to make what you're trying to develop.

In closing...

Learn as you build. If you're learning redux, take a quick crash course no longer than an hr long, your teacher/classwork, make the store with for a simple counter or todo list, your homework, once you've completed your app/project, you've graduated.

Apply this practice when you need to learn anything in life and development, and you'll be amazed at the results. Don't get caught in paralysis by analysis. You don't have to know everything, just enough to complete the task. How efficient and how clean you write will evolve the more you do it as you gain more time and experience.

-RallanVila

Ok, so you have a project assigned to you at work, or you just had the genius idea of solution for a problem that you can fix for a friend, company, or maybe you want to automate your workflow. Now, you’re ready to start the project and make it happen, but wait, where do I start?

Many things come into play when building out the front end of a project, and while you’re doing it, you want to ensure that the process is as smooth as possible. This is my approach and how I tackle this at work and in my projects. Again, this is my process; other people may have a different process.

I’d love to hear feedback around this and things that I can add/remove to streamline my approach in the comments below.

Get an idea of what the project entails

Understanding the problem you’re solving is essential. This is important because you’re going to have to walk your user through the variables of that problem with what you’re building. You have to figure out how to make that process flow smoothly to provide a fantastic user experience.

So let’s take a popular program to break down the process of what I’ve stated below with a popular solution almost everyone here has used. For the sake of time, this will be a high-level MVP (minimum viable product) overview. So the problem is, I need to find a home. The solution we're using to this problem is Zillow.com.

What to consider when wire-framing and creating your mockups

Ok, so we’re ready to start figuring out the user story and how we’re going to make these variables flow on the screen. What will your home screen look like, and how will you direct the user through the problem to come up with the solution? Let's take a look at how Zillow accomplishes this.

Homepage

From the homepage, you can see that they do a great job by having a search to get them to dive into the app.

Sign In

Are you going to have users? What’s sign-in going to look like?

Wait a minute, do they not have an account yet? What’s a new account going to look like?

Core App

Now let’s look at how they decided to lay things out to help the user with the problem. They’ve tackled the location issue based on their search on the homepage. Then that search takes them to the core app functionality.

• It has a fantastic map that shows a badge w/the price point attached to it.

• in the top left, you can run a search again

• Filters they have setup
  • Sale, rent, or sold
  • Min-Max Price
  • Home types
  • For more customizable options, they have a section.

These were more than likely highly requested features Zillow added on as they grew. Requesting and listening to what the user needs and wants are crucial to the success of a solution.

Property details section

Here we have a grid of photos on the left showing how the home looks and a granular details section that you can scroll through on the right.

Now open up Figma and start the wireframe/mockup

Figma is a great tool that you can use to design a wireframe or mockup. I've found it beneficial, to begin with, Figma first rather than diving into the code. Figma helps you make sure your solution's design, look and feel are unique.

On Zillow's core app and property details page, there is a lot of info to be displayed. Figma enables you to play around with the layout to see how you want to show what is essential in your app. It is way quicker than coding these things out to find out you didn't like how it looks and then switch it out. Please don't put yourself through that.

Do you have a problem with how to make it look and feel?

Go to the competition. Most of the time, there is already some variation out there with the things we will create. Look at how they did it and how you can make it different and better. Add your flair and showcase your niche way of solving the problem and what makes you different.

For example, Facebook already had a feed and was an incredible social platform when it started. We all know Facebook's features with posts, photos, check-ins, videos, friends, etc. However, a cool company called Instagram wanted to focus and be great at one thing, photos. Facebook already had a way to share pictures and did it very well. However, Instagram had a niche approach to how they wanted to share images by improving them quickly and sharing. Add your niche approach.

Tools to apply your niche approach that I use!

• Dribble.com. I go there to get design ideas from multiple designs so I can mix things to make them my own.
• Undraw.co to get awesome customizable SVGs that match my color scheme.
• Fontawesome, Flaticon.com, React-Icons, and others to keep my icon game on point.
• Tons of CSS generators that you can google for bubbles, and graphics to add to the page

Figma can be used in a big way to manipulate and customize the above.

Once your mockup is done, get approval from management/client and edit according if needed, open up VScode, and get to work!

-RAllanVila

As always, I want to hear your feedback in the comments below. If you found this helpful, it would mean the world if you shared it with others you think it could help. You can also follow and DM me on Twitter @RAllanVila for more helpful tips and schedule a time to chat

Ugh...not feeling good, but I’m here.

Hello, my fellow imposters. Today is going to be a little different. If you follow me on Twitter, you know my little man hasn’t felt that well. When he’s not feeling well with temp, he cuddles, then once the Tylenol kicks in, he wants nothing to do with me and hops on his Nintendo Switch. Well, the little rascal passed what he's been going through to his old man. 🤦🏻‍♂️

I made a promise to myself

Integrity: the quality of being honest and having strong moral principles; moral uprightness.

Once I started this blog, I promised myself that I’d put a post out every week, and I plan on keeping that promise. A good friend of mine talks about “speaking with integrity.” If we say we’re going to do something, we do it. Now I can see how that’s easier said than done, and it’s essential to do that with others; however, sometimes, why do we feel like it’s ok not to have that level of integrity with ourselves?

Our goals

We call have goals or desires in life, and some take more time than others. A majority of you here are learning how to code to get your first job or getting more proficient in your craft to level up your career in tech. Hopefully, you have a clear definition of your goal, have made actionable steps to achieving that goal, and have a way to measure the status of that goal based on the time you want to achieve it.

Goals are a game of inches that lead to major MILES-tones.

Sometimes people have an all-in or not mentality. You’re all in on hitting this goal; however, the one day you don't is when you start to slip. The book Atomic Habits teaches you to make small changes to transform your habits and deliver outstanding results. Goals are a game of inches that lead to major MILES-tones. It's ok if you slip up because life happens, but that doesn't mean you stop progressing towards the goal. You keep on trucking and stay consistent!

Excuses are compound interest that adds up over time, preventing you from your goal.

Excuse:

• attempt to lessen the blame attaching to (a fault or offense); seek to defend or justify.
• release (someone) from a duty or requirement.

If you’re doing the work for your goals, it’s not a matter of if. It’s a matter of when you’re going to achieve them. The when is determined by how aggressive you’ll be to attain those goals and what excuses you let prevent you from achieving the said goal. When I was learning to code, I made sure I coded at least two hours every day no matter what, and that’s what I did. Even if one day I did 4-5hrs, I didn’t rationalize it thinking ok, I did two days' worth of code, no. That counted as me going above and beyond my goal to help me achieve my “when” faster.

Staying true to myself

So, writing today is keeping a promise that I made to myself. This is not me doing the 4hrs over my goal; I’m doing the bare minimum expectation I set for myself to write a post. I told myself that I’d put a post out for my blog every week, and I'm doing it. Since I'm sick, I could have easily made a pass for myself this week.

However, tonight when I look at myself in the mirror at the end of the day, I’ll be able to do it with a clear conscience, knowing I did what I promised myself I would do. I'm keeping that level of integrity to myself and overcoming adversity.

Now take a look at your past week. When did you excuse yourself from the actionable steps you needed to attain your goal? How will you make sure that the same doesn't happen next week so you can honor the commitment you made to yourself? Write your commitment to yourself in the comments below so we can all support one another.

-RAllanVila

Let’s talk about all the roadmaps you see on YouTube, Google, Medium, and my fave Hashnode 😉

Today is going to be a quick one. This post has been inspired by the many #100Devs members I’ve had the privilege to meet with on Zoom to mentor and coach on how to break into tech. As you’ve seen in my other posts, the main feedback that I keep giving is to build, build, build.

Ok, Allan, I’m building, but what next?

HTML, CSS, and Javascript are the proven route to quickly getting hired as a developer. You master these, and you’re in. Holy cow, though, there are a ton of libraries and frameworks built around the above three.

Out of all the roadmaps I've seen or watched on YouTube, none has impressed me more than Kamran Ahmed's roadmap. It’s one I still refer to this day to make sure I’m proficient in my role and growing as a developer. Below is the front-end path.

Wow, is your head still screwed on tight?

Looking at that roadmap makes me want to grab a drink 🤯. There is a ton on there; however, that’s why I love it. He’s done a fantastic job displaying all the nuances of the front-end. When you've touched on the above topics, you'll be and a perfect position to get hired.

It all starts with HTML, CSS, and a TON of Javascript. Most of what you see on the Front-End developer roadmap are libraries and frameworks built around these core technologies. Guys, this is why I express so heavily to focus on those core technologies. Now take a look at the backend path below.

When you were in school, were all your textbooks in the same language?

More than likely, they were. Your textbooks were written in the primary language of your country. You’re not reading a book in English, then the next Portuguese to then Spanish in one class. That would be crazy on your brain. It’s one language, and you’d learn Math, History, Science, Language Arts, etc. The same is true when it comes to programming. Don't skip around trying to learn the above in python, javascript, java, and other languages.

Don’t be a Jack of all trades master of none. Become a master of ONE.

Want to be a master of one?

Between the Front-End and Back-End Roadmap, you have months and years of learning. Make things easier on your brain and yourself. Become a master of one and learn JavaScript while you’re learning. As you see, it’s heavily used on the front-end and can be used on the backend with Node.js. With this language, you’ll take your Math, History, Science, and Language Arts exams, lol.

You’ll learn all the core concepts of programming. Then when you have built and have a firm foundation on how to execute the principles on the roadmap, you can then figure out how to do it in Python, Java, PHP, .NET, Rust, Go, Ruby, as they can all do the job as well. You’ll eventually be touching more languages in your journey as a professional developer, depending on the projects you get put on.

So don't rush it. Keep it stupid simple on yourself to progress quickly and get hired as soon as possible. Where are you on this roadmap? Comment below so you can link up with others that are on the same path as you. Your feedback and expertise help everyone viewing this article and will help you connect with others!

RAllanVila

This is close to the heart. It's something that I struggle with as I continue to push my boundaries with the things I want to accomplish in the day and new projects to take on in a technical, personal, or self-developmental sense.

So, burnout. We hear the word often in today's hustle culture, but let's break down the definition. When you google "burnout definition," you'll get the below.

Burnout is a state of emotional, physical, and mental exhaustion caused by excessive and prolonged stress. It occurs when you feel overwhelmed, emotionally drained, and unable to meet constant demands.

- HelpGuide.org

Below the burnout definition, you'll see HelpGuide's listed effects of burnout. Direct damage can be physical, leads to anxiety disorders, loss of energy, and they write how it may even kill you prematurely. Holy cow, what!?

Now I'm not about to get into all that. As you guys know, I'm a sales guy turned developer, not a doctor. What I will dive into, though, is how burnout has affected my life and how I try to keep it at bay while I continue to push the envelope in life to achieve my long-term goals.

What's your why? Define it.

The psychology of why we do things is based on three things: feeling, necessity, and habit. So why should we define our why when it comes to long-term goals?

It’s NECESSARY to keep our FEELINGS in check so we can create/execute the HABITS needed to get us to our desired goal.

So what’s a solid why you might ask? It can be anything really, but make it personal!

• You want a change in life
• You want to travel
• You want to purchase a house
• You want a better quality work/life balance.

Find your deep personal why to unlock your true potential. My personal why that pushes me when I’m on the verge of burnout is my family. They give me my superpowers in life to move toward our goals and make the feeling of burnout become determination.

Define your why and have it become your crazy, maniacal motivation. Let your why to make you realize you’re doing this and won't fail. When you tire, then rest up; your why is what gets you back up and at it again.

Take a programmatic approach

For me, burnout happens when I’m doing too many things at one time. When we’re doing too many things, it can be easy to lose focus on the MVP (Minimum Viable Product) of each item we’re trying to accomplish. It’s essential to stop and reflect on if you’re approaching it the right way. Gamify the system by whiteboarding your path.

Create your variables. What variables MUST you have to do the task or achieve the goal? If your goal is to learn Javascript, your variables can be to know constants, primitive types, operators, control flow with loops and if/else, and create/manipulate objects, arrays, and functions.

Once you’ve written down the variables needed to hit your goal, write the necessary control flow to get there, then run the program, aka execute! Doing this will save so much time in your build process....OOPS goal progression as it’s what’s needed to achieve your MVP. Avoid distractions and focus without taking a perfectionist approach.

⏰ The Pomodoro technique

While you’re executing, something that I’ve found helpful is doing something similar to the Pomodoro technique. Now, I loosely model this. The Pomodoro technique is a time management method that uses a timer to break work into intervals, typically 25min in length, separated by short breaks.

I use this loosely for myself, as when I’m in the zone, 25min will break my level of concentration and productivity. However, the concept remains valid. After a long period of exertion, take a short break.

I hold myself accountable to this break by placing a timer on my Apple watch. The traditional Pomodoro split is 25min with 10min of rest. My break is relative to the level of exertion I put out. So if I go two hours, I’ll take a 30 min breather as I know that If I break for more than 40min, It’s hard for me to get back to it.

🏋🏼‍♂️Exercise

I exercise to break up my day during my hybrid Pomodoro technique. I’ve found that there comes the point to my day that my brain becomes mush entirely when inside a codebase or solving complex problems. Once I feel the burnout and mental exhaustion creep in, I’ll run downstairs and pop my pre-workout. I’ll come back to what I’m doing, knowing that in about 15-30min this sucker is about to kick in. Once it does, it’s gym time.

While I’m at the gym, it gives my mind a break that it needs. Putting strain on my body takes away that brain fog that I can get in and start thinking of other things. While I’m pushing my body to the limit, I notice this is when my creativity peaks. I get solutions to what I was working on pop up, ideas for blog posts, future projects, and reflect on things more clearly. This has been my best way not to get burnt out, as when I’m done, I’m energized to keep going.

🛌 Rest

This is the hardest for me, rest. We need to rest. If we don't, all of the above gets harder to focus on and achieve. At the beginning of the article, we discussed. The psychology of why we do things is based on three things: feeling, necessity, and habit.

Suppose we don't have the necessary rest to not be a zombie during the day. In that case, we won't be FEELING as optimal during our time making the NECESSARY HABIT to achieve the goal, therefore not being as productive. So you see, it’s counterintuitive. I have a significant fault in this as I feel there aren’t enough hours in the day, so I’ll make more of my being awake for more of them.

Lack of rest is the kryptonite to the superpower our why has given us.

I feel this is the #1 cause of burnout to reaching any goal. This DRASTICALLY affects all of the above. You can get too tired to chase your why. When you’re trying to approach things programmatically, it’s harder for you to focus on some of the simple things that deliver maximum results. It gets harder to hit the Pomodoro style 25min work crunch without losing focus. Then with exercising, forget it as your body hasn’t had the chance to heal is it’s done by rest.

These are my steps to help avoid burnout. I’ve shown how my why motivates me, my approach to work as minimal as possible to get my desired result, how I execute my system and illustrate why exercise and rest are crucial to this approach!

Suppose you have some advice for me and how you can help me with my burnout. If this helped you, leave a like and a comment about how it did. If you have ideas that help with your burnout, comment below, as I can use all the help I can get!

RAllanVila

Right now, you're looking for the tutorial saw yesterday in your feed but forgot to add it to your "Watch Later" you think to yourself...

I've been coding for four months now! How the hell did they do it? This doesn't happen. I cant build these projects they're doing by myself in six months!

You're frustrated as you're stuck as you cant make the page look right, it's been 20min as you're scouring the internet to figure out how to fix it...

Guys, I assure you, it's possible. I was hired in seven months from business sales, no background!

My fellow imposters, this is not a flex. This article is to encourage and get you focused on the priorities to get that sweet, sweet J.O.B.

"What's the secret, you ask? How does this happen? I've watched all the videos on this!!

Well, guys...that's just it; you're watching ALL THE VIDEOS!

Yesterday, I shared the earth-shattering, never heard, took me five paid courses on Udemy to finally figure out revolutionary secret. I posted it on Twitter yesterday.

So here is the best not-so-secret, secret to getting hired ASAP!

Really Allan??? Yes. guys,stop watching a million ways to write a project, open the editor, go to https://www.dribbble.com, click the web design tab, and start BUILDING those designs. Fellow devs, if you've been coding for three months and you haven't pushed yourself to do this or have your portolio live with yourname.com up, you're behind the six-month hires!

In every video we see, they say HTML, CSS, and JS. If you take ONE course on HTML/CSS and ONE path on Javascript...you're good, donezo. No more courses. However, YouTube University is manufacturing YouTube U Web Dev Ph.D. ninth-degree black belts. based on how many courses/tutorials we can watch when we should be coding!

The great thing is that we have so many creators to choose from that can match our learning styles and love their personalities. But when we take one 'React Crash Course' the YT algo, drops another one then and another one. We just wasted 3hrs clicking the next thing that pops up when you should be in your editor.

In sales, we like to KISS everybody, please KISS the code.

Keep It Stupid Simple. There is no need to keep watching videos. You already learned the fundamentals of HTML, CSS, and JS. Now build something and build up the fundamentals you learned. While you're taking courses and videos, the 6monthers are in the weeds and they've added three projects to their portfolio that look like the above.

Capitalize on every minute you're coding and build purposefully. By stopping tutorials MIRACULOUSLY...

• The Box Model will finally click.
• You'll know what div to apply display: flex to.
• You build a grid with grid-template-columns: repeat(3, 1fr) with breakpoints for mobile.
• You'll see how relative positioning ties in with absolute positioning while getting fancy with the z-index.
• You'll understand your favorite border-radius setting for cards and buttons.
• You'll know you can make an anchor tag look like a button and why you should/shouldn't do it.

Full immersion is important.

Immerse yourself with YouTube videos and podcasts while driving in the car, getting groceries, making your food, at the gym, on a run, and before you fall asleep. Immerse yourself in code everywhere, those vids are speaking a language you're trying to learn.

This passive and active listening will seep in to your subconscious, and when you're coding confronting obstacles, things will slowly start to click. You'll learn industry best practices and terminology and more. Just don't keep doing it at your desk. So, fellow imposters, please build. Your sanity, your family, and your goals depend on this. Although never attending one, boot camps can be great because they force you to write code and fumble, and get frustrated. It's the people who don't continue to write code that sit and overthink that don't make it.

You do this; you're now a Front-End Developer ready for market. You've built a solid portfolio, and now you should be texting, emailing, calling EVERYONE you know your link.

Show them your new skill and express that you're trying to get hired! You'll never know who may have a referral to get you in. For me, it was a friend that I worked with when my daughter was two. She's twelve now. Yup, 10 years ago!

Let me know your thoughts, what's worked for you or what you're struggling with within the comments below. If you saw my last article covering how to embrace your imposter syndrome, you saw how I answer questions and provide feedback to my readers.

Until next week fellow imposters,

RAllanVila