Feel like you a fraud?
Not good enough?
Not deserved your job position or salary?
Worry that other people will find these out?
This is called an imposter syndrome.
And you are not alone.
I felt it too and tried to get rid of it.
I’ve read tons of articles on how to overcome impostor syndrome, and honestly, some of the advice helped me, but 95%+ didn’t. So I just accepted the fact that I couldn’t get over it completely and went on with my life.
What happened next was the answer on how to overcome it, came from a place where I didn’t expect to find it. From studying human behavior and neuroscience. …
“I’ll just email them my resume, they’ll look at it and give me a call.”
Are you sure?
This is a very common misconception and this is what most developers don’t understand about cover letters.
Many of the developers I have spoken to think that a cover letter is just a simple email where you need to say “Hi!” and attach your resume.
But it’s not.
Let’s become a recruiter for 1 minute and look at everything through their eyes.
BAM, BAM, BOOM!
You’re a recruiter now.
You open your email application and see this:
Subject: Backend Engineer hiring
Subject: Backend Engineer…
I’ve been coding wrong my whole life.
I thought it was okay to just sit down at my desk, open my laptop, take a task from my to-do list, and code it until I felt tired.
But in reality, this style of work always killed my productivity levels after 2–4 hours of coding. I felt so tired that I didn’t want to do anything except different low energy tasks (like code review).
Today I can code 8+ hours without feeling like crap after.
What has changed?
My approach to work.
After 62+ self-development books, dozens of articles and studies about productivity, and my trials and errors, I have created a productivity system that helps me to code, write, create, and live at my maximum capabilities without procrastination, tiredness, and brain fog. …
What do you think programming is about?
Writing good code?
It’s just a part of the truth.
Programming is not about coding — programming is about solving problems with coding.
End customers don’t care what technologies, languages, frameworks, or methodologies you use. They care only about one thing: whether your product solves their problem or not.
That’s why no one cares what technologies Google search is using under the hood. Until people can find relative information with it, they will use it.
It’s the number one thing I wish I knew when I started programming.
I would spend less time writing “best code” and more time solving customer’s problems best. …
const name = ‘Nick’console.log(name.length) // 4
name has 4 characters ‘N’, ‘i’, ‘c’, ‘k’ and length is also 4.
Everything seems logical.
Let’s go further and add emoji to my name.
const name = ‘Nick 🐃’console.log(name.length) // 7
name must have 6 characters ‘N’, ‘i’, ‘c’, ‘k’, ‘ ‘ (whitespace) and ‘🐃’
But have 7.
It seems like the bull has 2 characters.
const emoji = ‘🐃’console.log(emoji.length) // 2
Let’s figure out why.
Thanks to Babel, I’ve been using the new ECMAScript 2021 features for over a year. Almost all the features are useful, but three of them stood out from the pack by saving me a lot of time and making my code more readable.
Let’s go over them.
The logical assignment operator combines logical operations (like
||) with an assignment (e.g.
Here are some examples.
a ||= b returns
a is truthy or
a is falsy.
Originally published on my blog: blog.nickbulljs.com
Here’s how things went down:
1. I finished developing a CSS game Flex Box Adventure using Gatsby.
2. Deployed it to Netlify.
3. Shared it with folks on Twitter and said, “Share your feedback with me.”
4. Went to sleep.
5. Woke up.
6. Opened Twitter DMs.
7. Saw this message:
We face it constantly — at work, at home, in various life situations. And if we don’t know how to manage it right, we will probably struggle with anxiety and be unproductive at work.
So here are the five techniques I use to manage stress.
This is a technique I’ve been using for over three years, and it’s freaking golden.
Every morning, I write two things:
I do it every morning for 5-10 minutes, and by the end, I feel completely different. My mind is calm. …
Most of us who have a fear of coding, in reality, have a fear of failing.
Even if we haven’t started learning a programming language yet, we already think we will fail instantly.
Why do we think like this?
There are can be a bunch of reasons:
And the list goes on.
But let’s face the truth. All of them are just excuses. And behind every excuse, we hide a fear of failure. …
What’s the end goal of the code review?
To make sure that changes work? To validate if code is following the style guide? To check if new changes won’t break anything? All of these? None of these?
All of these questions are necessary parts of the code review, but none of them are its ultimate goal.
The primary purpose of the code review is to make sure the solution is solving the problem in the best possible way — from both the code and product perspective.
All code-review practices are designed to meet this end goal.
But how do you determine if the solution you’re reviewing is the best way to solve the problem? In other words, how do you code review? …