DEV Community: Life.Tech.Psych

How to Be Productive, Feel Less Overwhelmed, and Get Things Done

Life.Tech.Psych — Sat, 23 Jan 2021 16:36:24 +0000

This guide is based on 5 years of applying techniques from Behavioral Psychology and research on productivity. I've used it as a developer, mentor and creator.

And it works.

If you remember only one lesson from this post, it's this:

The productivity techniques that work are built on principles. Not quick hacks. Or fancy tools.

If you understand and apply this, you'll be able to keep a clear head and stay focused. And it'll come in handy especially when things blow up out of proportion.

What this post will cover

Part I: Process >> Tools
Part II: What to do when you can't stop procrastinating
Part III: Put sanity over execution

Let's jump into it.

Part I: Process >> Tools

Whenever you feel overwhelmed, it’s because the process you have in place is failing you. Not the tools.

And a sound process will beat fancy tools, any day.

Before I understood this, I struggled with consistent productivity. Keyword here is consistent.

Anyone can be productive once in a while but it takes a certain level of finesse to do it consistently.

Back then, I did a lot of things. But constantly felt like I was missing something. My approach was speed and execution over anything else. This works in the short term but it's not sustainable longterm.

Before I got here, I seriously struggled with productivity. I knew life hacks here and there; and tried every tool under the sun including the popular ones:

Evernote: Your notes. Organized. Effortless.
Google Keep: Quickly capture what’s on your mind.
One Note: The digital note-taking app for your devices.
Any.Do: To do list app with Calendar, Planner & Reminders.
Todoist: The to do list to organize work & life.

Oh and I tried Trello at least 3x because everyone swore it was the greatest app ever.

But I couldn’t stand it.

Every few months, I’d jump between apps.

Once in a while, I'd ditch digital and go all paper. But then forget my notebook at home or hate to carry it around because it couldn’t fit in my pocket.

Nothing worked – I still felt overwhelmed with tasks to complete. But overtime, I learned that:

The best tool used with the wrong process feels like a failed tool.

So I shifted my approach to focus on processes. And it worked. My productivity and time management skills skyrocketed.

It doesn't matter what app you prefer to use, these 4 simple processes I share can be used in your favorite todo app.

Mine happens to be Google Keep. But as you read through, I want you to replace “Google Keep” with “Todoist”, “One Note”, or whatever app you love the most.

Focus on the big picture of how things fit because this is the most important aspect of using any tool.

Make sense?

Let’s get to it!

1) Find your single source of truth

I use Google Keep as my single source of truth that feeds into other productivity tools. This means it’s my first stop.

First stop for:

Grocery list
Journaling
Workout plans
Strategy for finances
Netflix shows to checkout
Any random thought that crosses my mind

Each of these have their own labels so capturing things usually takes a few taps on my phone or three clicks on a chrome tab that’s always open with Google Keep.

From there I move to Calendar for fixed appointments and to eyeball how much time meetings consume per week.

Then Trello for team tracking collaborations.

Next, I switch between Notes for personal writing or Google docs for collaborations. What’s interesting here is that most of my write ups start in Keep on my phone.

Including this write-up.

When it starts getting longer I switch to my laptop and copy out the content from Google Keep web into Notes or Google Doc.

Any time it feels like I need special formatting or the itch to write in my favorite font (Montserrat font), it’s a sign that I need to switch to a writing tool.

Switching to another tool isn’t necessarily a bad thing.

But not many believe that.

If finding your single source of truth is the only idea you put to action right away, you'll see a dramatic change.

But if you miss this, you'll struggle with staying afloat when you start feeling overwhelmed. Trust me, things will get overwhelming.

2) Stop chasing the everything app

This one is a little controversial.

And in the past, some have contested my stance especially after a new tool becomes popular (e.g. Notion).

Most people try to hack their favorite productivity app to become a writing app, a collaboration tool, a calendar app, an EVERYTHING tool.

The fact is that no one tool will address everything.

I made this mistake for so long.

Trust me, you’re better off picking up a single source of truth and then building others around it.

It’s fine to use Keep and Trello.
It’s fine to have Notion and Notes.
It’s fine to use a todo reminder and calendar.

One doesn’t have to replace the other. They can complement each other.

3) It's not paper OR digital; it's paper AND digital

Once in a while I get the itch to write on paper.

That feeling is especially strong when I’m planning big goals. I love to map out everything in front of me.

And writing with my favorite pen keeps the ideas flowing.

In paper situations, I scribble all on paper then when I get done, I take a screenshot and add it under the relevant label in Keep.

Example, if you saw my “big ideas” label you’d see a lot of screenshots in there.

I also do this when white-boarding with colleagues on a coding project or brainstorming sessions.

Get done.
Take picture.
Add to specific label.

Then I trash the paper.

Multiple years of writing on paper has taught me that the paper I write on only feels good in the moment.

A few weeks later and it looks like I’ve got paper trash all over the place.

So I screenshot and trash ASAP.

This process satisfies both my digital access to my planner (beats small notebooks any day). But it also lets me scratch my paper itch whenever it comes up.

I'm not loyal to only digital or only paper. That's nonsense.

I'm more interested in what helps me reduce my overwhelming workload. And using both work well.

You may want only paper or only digital. That's okay. Just remember you don't have to feel you must only use one to be productive.

Some recommend Rocketbook (a smart notebook). It is a reusable notebook that lets you write, upload to the cloud, and then wipe the page clean!

I’ve never used it but wanted to highlight this in case you find it useful.

4) Review often – weekly, monthly, yearly

Every morning on weekdays I go through Keep on my laptop to see things that should be top of mind that day.

This is key to proactively prevent me from getting to a place where I feel overwhelmed with tasks because too many things slipped through.

During the day, I add things to Keep either from my phone or laptop. The cycle continues until Friday.

Every Friday, I go through my Keep to clean up any tasks that fell through or that should move into other tools.

Then repeat.

Following this gets you right in the heart of smashing things efficiently but sometimes, procrastination blocks your progress.

• • •

Part II: What to do when you can't stop procrastinating

Do you know that 80% of us fail to fulfill our New Year’s resolutions?

That's crazy.

Sadly, procrastination plays a big role in this.

But no worries, you can beat procrastination through these three techniques: reducing your “perfect” goals, clarifying your next actions, and modifying your steps through Behavioral Psychology.

Let's dig into these one by one.

1) Reduce your first move from “A+” to “B”.

If you're a perfectionist, you'll procrastinate. If your goal is too big to take a first step, you'll procrastinate.

If you're a procrastinating perfectionist, you'll feel paralyzed and frustrated many times because your big goals remain in your head with zero actions in reality.

You'll take zero actions because you want all your steps to be perfect.

To fix your procrastination as a perfectionist, start with a “B” goal instead of “A+”. This means you should go back and change your first step to be “good enough” instead of “perfect”.

2) Clarify the next, tiny action.

Whenever it’s not crystal clear what you’re supposed to work on next, your mind will stop you from moving forward.

Example your todo list has:

Build the best portfolio page to get a job. Then create amazing landing page to show off to everyone.

But:

What does “best” mean?
What type of programming projects should I have in my portfolio?
Is it smart to build my app from scratch or use an existing template?
Which language should I learn? How long? When? How?

When you have too many floating thoughts in your head, your mind runs away from any actions and falls back into procrastination.

The cure is to spend 90 seconds and answer:

What is the smallest, next action for the task I want to achieve?

For example:

If you’re building a portfolio, the next tiniest action is open up a document and write up a rough plan. Not to open visual studio and struggle with the quirks in C++.
If you're writing a book on lessons for new programmers, your tiniest action isn’t to write chapter one. It’s to come up with the first DRAFT of your outline for the all book chapters.
And if you’re completely new to programming, your best bet is to start with places where you can learn to code so you narrow down on one option. Not to jump around aimlessly and still feel lost after several months.

The tinier the next action, the more likely you are to get it done.

Stack multiple small actions and you, my friend, are gold.

3) Modify through techniques from Behavioral Psychology

Some days are just lazy days.

You know you should ignore how you feel and get to work but it's not happening.

You can use these principles of from Behavioral Psychology.

Deadline effect: Go to www.tomato-timer.com, click 5 minutes and start working on your tiniest next action as fast as you can. Most times you’ll end up going beyond 5 mins. That’s perfect because Zeigarnik effect has kicked in and you'll feel like completing the work you already started.
Negative reinforcement until you work: If somehow you didn't do anything and the timer ends, restart it. Additional tip is to go to setting and set the sound that is most annoying to you. Do this at least 5x and every time “punish” yourself by watching the timer count down!
Revisit your motivation: If after 5x, you can’t do anything, it means your motivation is off and you have a deeper question to answer:

“What will I gain by I work on this?”

Sometimes, looking to how other developers have transformed their lives can give you the needed push.

If you still have no answer to what you’ll gain, abandon the task as it's time to find something else that has more intrinsic motivation.

But no matter how much you get done, it's important to recognize that productivity is not about working non-stop.

You need balance to consistently move forward.

• • •

Part III: Put sanity over execution

Getting things done is not always about doing more. Sometimes you don't need faster, better.

You need the sanity from self care.

“Self-care is never a selfish act. Anytime we can listen to true self and give the care it requires, we do it not only for ourselves, but for the many others whose lives we touch.” - Parker Palmer

If you don't prioritize self care, you'll definitely burn out. Trust me, developer burn out is real.

Burn out too many times and you start to think maybe you're not cut out for the work.

You are.

Your approach is simply what's killing you.

Here are simple ways to start caring more for yourself. These little activities don't come close to the hype that people expect when they hear 'productivity'.

But you need them.

Have a different spot for work and relaxation

I've found that relaxing in the same spot and later trying to work doesn't cut it.

Same applies when flipped around: working in the same spot and later trying to switch to relaxation mode is hard.

You don't need separate rooms for this.

You only need to intentionally create a physical difference so you can switch out from one to the other. Not doing this kept me spinning in cycles for several weeks.

Recharge through a daily shower

This is straightforward. Early showers are better but if you can't do that have one at night before the day runs out. You'll feel like you've accomplished something already.

Cooking as therapy

I don't cook as much as I'd love to. But following instructions on a recipe and coming up with something new feels magical.

“No one who cooks, cooks alone. Even at her most solitary, a cook in the kitchen is surrounded by generations of cooks past, the advice and menus of cooks present, the wisdom of cookbook writers.” — Laurie Colwin

Pick any meal – whether it comes out good or not doesn't matter.

It's the process of unplugging from the world that helps. Pair the cooking with jazz music and you're automatically teleported to another universe.

Get any amount of sunshine

I've never believed that the weather has an impact on one's mood but it does.

Stay in doors too much and things will start to feel gloomy. Cabin fever sets in and you pack your living space back and forth like a mad raccoon.

But you don't need to step out to fix this issue. I've realized that my cabin fever completely disappears if I open up windows early in the day.

No need for huge windows or long walks outside. Just a few minutes of quiet, alone sunshine is all it takes.

Closing out

“While it may seem small, the ripple effects of small things is extraordinary.” – Matt Bevin

Think about what you’ve read so far.

You’ll notice that each sound simplistic because they are minor tweaks by themselves.

But combining all of them together transformed how I got on top of things. You can achieve this type of change too if you follow the principles.

Remember:

Principles >> tools
Beat procrastination or it'll control you
Put self care and sanity over constant execution

Thanks for reading

Get email tips/mentoring: I share weekly tips and mentor new programmers and junior devs to focus on what matters (e.g. resume tips, portfolio review, etc). Feel free to join. Note no video/audio calls for mentorship (strictly email or Twitter).
Follow on Twitter: If you're on Twitter, my DM is open. I've answered a lot of questions so feel free to ask away. I may get to you later than you expect but I definitely answer all questions.

Heads Up - I love research so I tend to back my advice and approach with concepts from Behavioral Psychology and Neuroscience.

Lessons for beginners and junior developers after 11 years of coding

Life.Tech.Psych — Sat, 03 Oct 2020 22:13:11 +0000

I initially wrote this as lessons for beginners and junior developers on Reddit and it blew up with over 50 awards. So I've decided to upgrade parts of it based on people's reactions.

Some of these are things I wish I knew at the beginning of my journey as a Software Developer so I could stress less.

Let's get to it.

All tutorials are not created equal.

Imagine yourself as a lab rat.

As you learn and experiment, pay attention to the kinds of tutorials that work for you. Many will not work. That’s fine. In fact, that’s exactly how experiments work until you find a solution.

But the moment you strike gold, stick to it, consume it voraciously and then find similar tutorials like that to continue rapid growth.

Photo by Christopher Gower on Unsplash

When I started, I used to bang my head against Head First Java, the book. But after studying for many hours, I just wasn’t getting anywhere. Yet, everyone online said it was the best programming book ever. But TheNewBoston youtube tutorials did it for me back then even though people don't recommend him anymore.

I wish I could say this stopped after my 1st year.

Fast forward 2 years down the line when I started learning algorithms and ALL the blog tutorials I followed just didn’t make sense until I watched Youtube videos on Hungarian folk dance teaching algorithms.

And it just clicked.

Since then, my approach to learning has been to learn the same thing from multiple places until I find the instructor and style that works for me.

If you’re not practicing with a project, nothing goes into long term memory

You’ll forget a lot of things.

Deeply understanding this will change how you learn.

I can’t count the number of times I took Introduction to Python Programming on Udacity, Coursera, etc and still forgot everything.

It’s so annoying.

But I’ve since learned that you’ll forget anything you learn in isolated exercises because they are stored in short term memory. Neuroscience research shows that this is just how the brain works.

If you don’t want to forget, test your knowledge using spaced repetitions. To do this, build projects.

I’ll give you a concrete example: len(myList) will give you the length of a list in Python. You’ll learn this in Udacity’s intro course.

Come back a month later and you might not remember if it’s len, length( ) or myList.size( ).

But with spaced repetition through a project, the outcome is different. For example, you work on a 2-month long Django app for new coders where you need to count multiple times the number of users, the number of exercises done, the number of chats, etc. Imagine doing this throughout the span of the project, for two months. it’s hard to forget what len( ) does.

This is a trivial example, but hopefully you get the idea.

New learners can start with simple, isolated examples.

But if you’re not practicing within the scope of a project that makes you use and reuse what you’ve learned, nothing is going into your long term memory; it’s all short-term. And you’ll forget.

Work within fear; not against it.

I’ll admit: this one is easier said than done.

But you have to master this if you want to last long.

There’s this temptation to fix your fear first before you continue to learn. Unfortunately, it doesn’t work like that.

In fact, you’ll spend a lot of time trying to make your fear disappear that it’ll only double your anxiety. You have to find a way – your way – to acknowledge that you’re afraid, and frankly will continue to be afraid for a long time, then work within that realization. No need to fight it.

Sometimes, this fear disappears as you become more proficient.

Other times, it vanishes for a while and comes back when you get into a new environment, work with smart software developers, or move to a completely new stack.

It’s okay.

If you want to progress as a software developer, you have to remember:

This IS the life.

It’s a sinusoidal wave – endlessly going up and down. Don’t take it too seriously or you’ll lose yourself.

Consistency > hard work.

Consistency is king.

When you start learning, you lay down neural pathways that make it easier to retrieve information. According to Neuroscience research, these pathways only get strong through frequency of use, not just intensity.

This means 30 minutes a day, for 5 days a week is way better than 2.5 hours one day, only once a week.

Same hours; Different impact.

Don’t just work hard, apply wisdom here.

Talent = hidden practice.

It’s easy to dismiss progress as talent.

My first programming class was in C++ and my classmates refused to believe I had never coded before because I was just-so-talented.

But what they also refused to accept was that right after class, I would spend five hours typing cout << “this is my first program”, realize it didn’t run because I forgot a semicolon; retype it and realize it didn’t print out my statement on a new line because I didn’t add endl.

This deliberate practice built perceived talent.

Talent is sexier than hustle so no one wants to hear that you worked hard and got here. Just tell me you were born this way - it’s more believable.

But becoming a proficient software developer is like playing an instrument.

Talent vs. Hustle - The majority of us mostly hustle our way through it.

Only a tiny few are born talented.

The majority can only get as good as the amount of practice they put in. And you can immediately tell a student hasn’t been practicing the moment they sit at the keyboard.

You’ll meet a**holes!

Every field has its dose of horrible people.

No doubt.

But I’m not sure what it is about software dev that attracts a**holes in droves. Maybe because coding gives the feeling of having a super-power or a rare skill. If you’re a newbie, you’ll meet those who’ve been coding for years and think no one else should come in.

A windows developer only? You’ll meet linux fanatics that think you’re mediocre.

If you’re a woman, you’ll immediately be dismissed because of your gender. I know this from personal stories from colleagues over the years.

If you’re a minority, you’ll meet people who think you should only fetch coffee; not code.

If you’re coming from another field (particularly not STEM), you’ll meet people who automatically make themselves gatekeepers of the programming community.

“We don’t want social scientists here; we’re purists!”

They’re online.

At work.

And sadly sometimes in your family.

It’s not if you’ll meet them, it’s when.

Learn to move on.

Things are getting better but there’s still a lot to do to educate people.

But don’t let this deter you. Build your resilience so you don’t quit after you meet these people.

And when you get to the top don't be an a**hole!

Master 1 thing.

New developers tend to jump around learning a lot of things.

Okay, it’s not just new devs; it’s also experienced folks.

You learned React for one week.

Then JavaScript for two weeks.

Laravel for three.

Stop.

You need to wake up and realize that the harsh truth is that you’re simply extending the time it’ll take you to truly learn anything.

“If one is a master of one thing and understands one thing well, one has at the same time, insight into and understanding of many things.” - Vincent Van Gogh

Pick one thing.

Stick with it for a few months – ideally 6 to 12 months before you move to something else.

This has two benefits:

You’ll go deep enough and hit critical mass that moves you towards mastery.
After you master one domain, you can transfer knowledge to another. Learn Flask and you can easily walk into Django. Learn React deeply, and you can quickly identify the pros and cons of Laravel within a few days.

This doesn't mean learn HTML alone for six months then only CSS for 1 year; rather, it means don't mix up learning Django, with Express, then React, some Gaming Development, and iOS.

You might get a lot done in a short time.

But you'll master nothing!

Software development is an ever evolving field.

It’s exciting.
It’s frustrating.
It’s intimidating.

But if I had to, I’d do it all over again.

Thanks for reading – spread the word!

Phew! Did a lot of reflection and lots of hours to put this together.

If you enjoyed it and you're on Twitter, like and retweet this to help spread the word. I know it sounds trivial but it actually really helps.

Check out other articles on LifeTechPsych – you may find something else you like.

What's Next?

I’m trying out a new initiative to help new coders and junior devs feel less overwhelmed, manage imposter syndrome and learn smarter.

To be honest, I’m not sure what the entire process looks like yet. But I’m going with the flow and putting together resources and write-ups based on what people need the most help with.

If you’re interested, let me know on Twitter. If you prefer sending a direct message, my DM is open.

Heads Up - I love research so I tend to back my advice and approach with concepts from Behavioral Psychology and Neuroscience.

How to learn coding in an efficient way

Life.Tech.Psych — Sat, 03 Oct 2020 22:07:36 +0000

What’s your idea of learning to code?

Whip out your computer, type out a couple of cool commands. And bam - beauty personified.

Sorry, nope.

The process is at least 50% struggling especially at the beginning.

And that’s how it should be.

Photo by Tim Mossholder on Unsplash

I’ve seen people quit programming because they don’t want to struggle with bugs. That’s like hating the gym because you don’t want workouts to hurt.

Learn to see the struggle as the way.

You don’t run from bugs; you train yourself to find them quicker.

A proficient programmer is an efficient detective of bugs.

If you’re feeling frustrated that things are not smooth, remember that this is how learning actually works.

Neuroscience research confirms that practice doesn’t simply make you perfect; it is deliberate practice to improve in a specific task that makes you better. And deliberate practice involves struggling.

So your mantra should be:

You code.
You debug.
You struggle.
You overcome.
And you repeat.

If you’ve not struggled at all, you’re simply playing around.

If you struggle all the time, then the next section is for you.

You’re not dumb, you’re learning at the wrong level.

Let’s start with a little analogy.

Imagine learning the English language (the language of exceptions).

You start with a tutorial motivating you to learn to spell big words like ELEPHANT.

But it’s not working. After beating yourself for so long you decide to go to a lower tutorial and learn to spell smaller words like ANT.

But you still struggle.

So you conclude that you’re dumb because you lowered your tutorial level and still didn’t grasp anything.

But when a new teacher investigates why you’re struggling, they find out that you’ve been struggling because you actually don’t know the English alphabets.

Let’s bring this home to our coding world.

Some people jump into beginner tutorials to learn frameworks like React (ELEPHANT). Then realize it makes no sense so they move on to learn JavaScript (ANT). But that still makes no sense to them, so they quit.

But they’re simply working with something that’s too advanced.

Even introduction courses can be advanced because your thinking is not wired yet to programming in general.

There’s no shame in finding something lower than Intro courses and starting from there to build up to Intro courses.

I don’t see this recommended enough but if you’re struggling with intro courses, you should consider Intro to programming for kids.

Learn with tools like:

Alice
Scratch
Codewars.

Since you’re older, you’ll go through them faster. But they’ll give you the much needed soft intro that makes sense and builds your appetite.

Again, this has nothing to do with ego.

It’s your learning journey.

If you learn the alphabets first, you’ll gain the confidence needed to start spelling ANT, ELEPHANT, and later constructing long-winded sentences.

It doesn’t matter what discipline or area of coding you jump into, this holds for Intro to Python as much as it holds for Intro to Machine Learning.

You’ll learn more efficiently if you learn at the right level.

Elevate how you learn with spaced repetition.

This technique is from research in Neuroscience. And I’ll summarize it short and quick.

How it works:

You learn.
Recall in 48 hours.
Then review in 72 hours.

Doing this:

You’ll forget less.
Connect new ideas to old; and
Retain more in long term memory.

I put 48 and 72 hours but you can expand that timeline to days and weeks. The most important takeaway is not to simply learn once. But to intentionally set aside time for you to come back and review.

The longer the delay between reviews, the more it gets buried in long-term memory.

Duolingo uses it.
Quizlet adopted it.
You can also apply it.

1 project > 10 hello worlds

Don’t get caught up in hello worlds forever.

I understand the thrill of completing simple exercises:

# OMG - I can print all day
print “I am awesome”.
print “You’re cool”. 
print “Wait, are we cool?”

But I have to be honest with you, this won’t cut it.

Going back to our ANT analogy, no matter how many ways you rearrange the words ANT, you’ll never arrive at ELEPHANT.

No matter how many Intro tutorials you learn, you’ll never really get past the basics unless you push yourself beyond that.

“But I don’t know what projects to start as a beginner.”

No worries. Here are two examples:

Random Password Generator: Creating a program that intakes some words from the user and then generates a random password using those words.
Currency converter: Create a program that converts currencies from one unit to another, for example, converting Indian rupee into dollars, pound to euros, etc.
If you find these boring, here are 40 other ideas to choose from.
And if all of them seem too difficult, DM me on Twitter and I’ll create something specifically for you to start with. Remember, this is not about ego; it’s about your learning level and growth.

Motivation is like taking a hot shower.

Taking a hot shower feels good - you should do it.

But if your hot water is out for 2 weeks, would you not shower?

The question sounds ridiculous but in the same way, you really shouldn’t base your learning on only days when you’re motivated.

There are lots of exciting days in coding; but there will also be dark, unmotivating days.

Honestly, this is not just with coding. It’s with life and embarking on any new adventure. But you have to train yourself to show up not only when you’re feeling hyper inspirational but also on low, boring days.

This doesn’t mean forget motivation.
Far from it - on days when you feel super motivated, use your motivation to quickly commit yourself to something big that will keep you accountable when the motivation goes dry.

How? Join an accountability movement like:

30daysofcode
100DaysOfCode
30DaysOfCodingChallenge

Something. Anything. To keep you accountable on slow days.

In Behavioral Psychology, this is known as pre-commitment. You use moments when you’re optimistic to commit yourself in the future for when you have zero optimism.

The journey of learning is never-ending.

No one teaches you how to learn.

But it’s crucial in going far.

You may have started with the idea of simply learning to code or to one day become a developer. But there’s more.

Photo by Drew Beamer on Unsplash

When you come out on the other side, you’ll come out not just a coder.

But as a renewed person because you’ve picked up a new way of learning and approaching things.

Don’t get me wrong. This isn’t easy peasy lemon squeezy – you’ll work like hell.

But in the end, it’ll be worth it not just because of coding but because of the joy of transforming yourself.

Remember, the ball’s always in your court…

Thanks for reading – spread the word!

Not going to lie, this took a lot of hours to put together.

If you enjoyed it and you're on Twitter, like and retweet this to help spread the word. I know it sounds trivial but it actually really helps.

Check out other articles on LifeTechPsych – you may find something else you like.

What's Next?

I’m trying out a new initiative to help new coders and junior devs feel less overwhelmed, manage imposter syndrome and learn smarter.

To be honest, I’m not sure what the entire process looks like yet. But I’m going with the flow and putting together resources and write-ups based on what people need the most help with.

If you’re interested, let me know on Twitter. If you prefer sending a direct message, my DM is open.

Heads Up - I love research so I tend to back my advice and approach with concepts from Behavioral Psychology and Neuroscience.