One of my biggest motivators is the fact that I am impossible to satisfy. I’ll never feel like I’ve done enough conference talks or written enough blog posts or submitted enough pull requests. Admittedly, this is a dangerous ideology and one that I would not recommend other people follow.
Don’t Compare Your Behind-The-Scenes With Everyone's Highlight Reel. Don’t Compare Your Behind-The-Scenes With Everyone's Highlight Reel. Don’t Compare Your Behind-The-Scenes With Everyone's Highlight Reel. Don’t Compare Your Behind-The-Scenes With Everyone's Highlight Reel.
No matter where you are instead of looking at your phone look at all the people and find the one that you connect with and realize that they're the center of the universe – because for them they are, just like you are for yourself.
Essentially, engineering is all about cooperation, collaboration, and empathy for both your colleagues and your customers. If someone told you that engineering was a field where you could get away with not dealing with people or feelings, then I’m very sorry to tell you that you have been lied to.
Pushing against a stereotype is emotional labor that men, white men in particular, don't have to perform. Instead, they can use that energy to focus on being a great engineer. Women and minorities, on the other hand, start and end the day at an emotional deficit.
by Emily Chang from her book Brotopia
If you don't like how @PrettierCode formats your code, it's because you care too much about code formatting.
When we took a closer look, we found that UI developers were spending less than 1/3 of their time actually building UI. The rest of that time spent was figuring out where and how to fetch data, filtering/mapping over that data and orchestrating many API calls. Sprinkle in some build/deploy overhead. Now, building UI is a nice-to-have or an afterthought.
You can spend a lifetime to build a good reputation and then ruin your efforts with less than 280 characters. Be mindful of what you share. Be less judgmental and mean spirited. Don’t belittle people. And if given a choice between clever or kind, always choose kind. Be kind.
It's a mistake to learn a framework without first learning the fundamentals. That's why, when dealing with beginners, I always start off by making them build their own CPU, programming language and operating system.
Be careful not to say "nobody needs a CS degree" or "CS degrees are bad" when you really mean "I have not found myself at a disadvantage for the things I've wanted to accomplish in my life by not having a CS degree".
Your job as an developer is to decide, to decide what tools to use, to decide what frameworks to use, to decide what to prioritize, to decide what is the best way to maintain a project – a lot of questions only your team is able to answer.
Do things with an eye towards the long haul. [...] Do things that will matter years from now. If you're going to write about something, write about something that will still be a thing five, ten, twenty years down the line. Write it like your gonna own it.
No joke, about 95% of the work in open source is around education. Docs, issues, pull request reviews, web sites, blog posts, talks, tweets, examples, etc. Writing the code is the *easy* part. Helping people use it is the vast majority of your responsibility as an OSS dev.
I'd suggest that anyone who feels they have important things to say gets a blog, does some critical thinking on their subject, and writes about it. Rather than feeling the need to convince women on the internet one by one via DM and email.