Hacker News Reader

Comment by mattgreenrocks | Hacker News Reader

Yup. I've gravitated towards difficult domains in my career because they serve as a very effective filter on the people actually applying for them, they keep me sharp, and people that have needs in these areas tend to less of the stereotypical "idea people," that are looking to milk those who can execute.

View on HN

While what you say is true, my experience at such jobs is they also tend to have the most dysfunctional people/teams, unfortunately. And career growth tends to be very stagnant, and working conditions are poor (the supply of labor exceeds the demand).

Switching to "dumb" jobs made my life a lot happier. While it's easier, the demand exceeds the supply. Easier career growth, and better colleagues (no egos, etc).

You still need to be picky about teams. Where I am currently pays decently, has interesting work, and is small enough that there is meaningful progression, and is low drama. (We're hiring, check my profile for email if you like some of the stuff I mentioned above!)

So, my one example disputes your claim. :)

Can you give any examples of those difficult domains?

I'm an ok-ish web developer, and would love to fine some niches to specialize in like you mentioned.

* Deep systems programming (this one is losing its "hard" luster a bit with Rust, which I'm okay with)

* Compilers/DSLs/language runtimes/static analysis

* Distributed systems (on my list of things to learn, know basically nothing)

* More generically: high-performance code, doesn't have to be fintech-fast, but designing and maintaining code that makes excellent use of hardware resources

Reply on news.ycombinator.com