Find an area to specialize in that has more depth to it than just gluing APIs together.

You might find Kitten interesting: https://kittenlang.org/

This “Jordan Cutler” guy has a nice grift going, makes money writing a newsletter about career advice when according to his resume, he only has five years of programming experience at best: https://jordancutler.net/assets/images/JordanResume.pdf

The whole point of being an “experienced developer” is that you know more than the new grad. What kind of experienced developer forgets basic computer science on top of which all else is built?

Most of us. We're not computer scientists, we're programmers.

To be fair, you need at least one person on the team to do the actual work, while everyone else is “communicating and managing expectations”.

That statement is not untrue, but I think it over-estimates how much of the "actual work" is banging out code, vs. making sure the correct code is being written.

Yea, I've worked in a place where it was just "coders coding" and nobody was communicating and managing expectations, and that was its own unique form of awful. You need both.

It’s actually possible for members of the team to be capable of doing “actual work” in addition to being good communicators.

Basic coding problems involving data structures and algorithms are table stakes for a programmer. This whole thread is embarrassing.

I would not call LeetCode hard questions "basic coding problems".

Furthermore, asking (senior) engineers arbitrary and esoteric CS questions that

A) They may have never seen before

B) They will likely never encounter

Seems like a good way to lose out on competent candidates

If I hire an experienced electrical engineering project manager, I don't ask them to analyze convoluted circuits or random differential equations on the whiteboard.

“Total compensation” usually refers to base salary together with your yearly bonus and vested stock. Mortgage lenders will typically look at your W2 income which includes the bonus and stock.

> The rewrite of the Swift compiler from C++ to Swift is an example of where rewriting is occurring but where there’s a non trivial performance loss as a result.

Citation needed on the performance loss. So far only a handful of SIL optimizer passes have been rewritten in Swift.

Wait, I’m old enough to remember when IntelliJ used Swing. They wrote their own GUI toolkit since then?

Get a math or CS textbook and try solving some of the exercises.