professional-programming VS HowToBeAProgrammer

The inclusion of the perspective section: https://github.com/charlax/professional-programming?tab=read... I think is really smart. Same for personal productivity. Two things that can dramatically change how and what you end up studying and doing with your time / life.

I did a coding bootcamp and yeah the frontend knowledge they taught was useful, but I could have learned that online for free. Looking back, the far more valuable thing I learned was how to discipline myself and my time - that was the first time in my life I was truly disciplined and mindful in how I spent my time. I also got perspective I'd never seen before: there was some folks in my cohort that were in their 30s and 40s and undergoing career change, and I learned two things from them: First, don't stress too much, your life has much more flexibility than you might expect (this truth is borne out, they all have perfectly successful careers in their new lives as engineers), and second, make a great use of the time you have.

Bog-standard advice we all know, but to witness it firsthand from people living it and sharing it is different. The shared article in the github is incredible: https://www.theguardian.com/commentisfree/2020/sep/07/termin...

I often wonder why I don't see more of these sorts of articles. From watching a family member slowly die of cancer, and from reading books like "When Breath Becomes Air," I'm guessing it's some combination of exhaustion, disability, and a new set of priorities that doesn't really involve death blogging. Still, I find these kinds of writings more poignant than most things I read.

Also this repo helps https://github.com/charlax/professional-programming

1. Professional Programming

Professional Programming. As reported, The goal of this page is to make you a more proficient developer. If you have excellent resources, you can try to open a PR and include them here. But in any csae, I wanted to include this because it seems super interesting.

From a different set of essays titled How To Be A Programmer ( https://github.com/braydie/HowToBeAProgrammer ) - How to Conduct Experiments https://github.com/braydie/HowToBeAProgrammer/blob/master/en...

The entire set is good and I occasionally go back and revisit them.

How to be a programmer.

I really like How to be a Programmer and wish it existed when I was a junior.

How to be a Programmer - How to Find Out Information and How to Utilize People as Information Sources

So sit down and think about how you want to tackle this. Do you upgrade module by module? Or do you want to do a stepped upgrade where you first upgrade to 7 and then to 9 and then to 12 and then to 14 (those numbers may not make any sense - they're just numbers)? Then sit down with your manager and work on estimating the milestones. And then faithfully and accurately communicate the actual state of the upgrade in a timely manner.

Read Debugging - The third intro to CS assignment and How to be a Programmer - Learn to Debug.

Personally I think the #1 thing that separated intermediate engineers from senior engineers is the ability to cultivate empathy for your coworkers. I don't think you can be an effective leader without that. If you want an answer to what technical skills you need to develop, I highly recommend reading: https://github.com/braydie/HowToBeAProgrammer/tree/master/en

From How To Be A Programmer - How to Utilize People as Information Sources which comes after How to Find Out Information