There’s a quiet problem that most developers face: a lack of confidence.
But where does that lack of confidence come from?
Well… neither the quality of your code, nor your limited knowledge, nor your coding habits are the problem.
The problem is: you’re being too hard on yourself, and that’s causing you frustration. That frustration itself will become more and more problematic.
First it will make you avoid certain difficult problems. That avoidance will make it harder and harder for you to focus. In the extreme case, it will make you dislike programming.
Coding is a time-consuming process.
It’s easy to punch an industry that is an underdog and get away with it. It’s easy to say, “Oh, these bootcamps, they’re shady. How can they even work? Let’s sue them. They’re liars. They’re cheats.” Nothing could be farther from the truth.
(This is a transcript of this conversation on the PodRocket podcast, which you can listen to for free. Thank you, PodRocket, for letting me speak my mind on your podcast).
PodRocket is sponsored by LogRocket, a front end monitoring and product analytics solution. Don’t know what that is? Go to logrocket.com. Thanks.
Finishing all the food on my plate was never a virtue in my family.
Maybe as a consequence of that, I’ve always found the concept of completion… odd. The notion of “finish your food or you won’t get any dessert” seemed childish and demeaning to me, even when I was a child.
Growing up, I now have many questions about completion. What is “completion?” Isn’t completion a sort of death, a stopping of dynamic motion? Doesn’t finishing a project leave it less perfect than when it was being built?
Why is there this pressing need to finish what you’ve started?
The recruiter is the first person who will probably see your resume. They:
If the recruiter has to look for your most impressive credentials, your credentials might as well not even exist on your resume. To successfully get past the resume review stage, you need to present the most relevant and most…
Becoming a backend developer is about as close to being a wizard as it gets in software development. You’ll learn how to see the invisible and bring order to a world that most people barely know exists. It’s not hard to see the connection there.
Here’s one build for becoming a junior backend developer. There are many such builds, this is only one suggested path.
I would not apply to backend jobs unless I had ALL of the following skills.
Typescript gives you the following options to organize your interfaces and types:
*.d.tsfiles can let you use types without aneed for
importstatements. The types are made available recursively in all subdirectories, and these files can be distributed throughout your project.
.tsfiles. Maybe these are TS files that contain nothing but types. These can be kept in the root folder or locally in the specific directory.
We’re software engineers and developers. We are not scientists. Not philosophers. Most of us do what’s right for the business, and aren’t above making practical sacrifices when the business needs it.
We should make the same pragmatic decisions when it comes to navigating our own careers. When it comes down to it, tabs v/s spaces is just splitting hairs and isn’t worth losing money over.
If you don’t agree with this, you should stop reading. You won’t like where this article is going.
Most ES6 developers…
There’s a fork in the road ahead.
One path leads to wealth, property and success.
The other, to purpose and fulfillment.
The phrase “Money can’t buy you happiness” is about the crossroad. As is all the research that claims that money DOES lead to happiness, depending on your annual income. Many musicians have bargained away their souls here. Robert Frost wrote a poem about it and called it “The Road Not Taken.” …
I took a chance on 3 of them with my own money. I didn’t know what to expect.
A big part of me said I was making a mistake.
But in 6 weeks, one of them finished a complex, performance-heavy TypeScript + Node + Postgres project in 6 weeks.
Another revamped the website, built a CLI tool and quickly onboarded to a rewrite of legacy code.
The third is contributing to our open source CLI and is plenty dangerous with React & Typescript.
We then hired 3 more. All-in-all, 6 junior devs, 5 of whom are bootcamp grads. …
The greenblood channel is how tools, SDKs and libraries spread when developers move to new teams.
The greenblood channel (“greener pastures” + “fresh blood”) is the natural process of tool pollination that occurs when developers move to new teams.
It is a natural, self-sustaining cross-pollination of best practices, methodologies and tools that occurs between tech companies and across generations of software hires.
The big companies understand this channel extremely well and tap into it on a regular basis. It is the cornerstone of their marketing strategy. …