[sfpotter]

Alternatively, consider being an idealistic programmer!

  - Fall in love with a single topic, regardless of how trendy.
  - Learn as much as you can about it.
  - Keep learning about it.
  - Learn about it some more.
  - Spend years of your life doing nothing but breathing and thinking about this one topic.
  - Let fads and fashion pass you by.
  - Don't settle for good enough. Try to build the best version possible.
  - Choose where you work based on your ability to reach staggering new heights with this one topic, and disregard whether it seems like an amazing CV line item.
  - Fail to even notice fads and fashions passing you by.
  - Become a master.

[android521]

I have read many books. If you can only read one book about how to program in your life , I would say that it is this book: A philosophy of software design: John Ousterhout. It is 10 times better than the next best book.

[sfpotter]

I'm not sure if you're just spamming this response all over this thread or if you're replying to what I wrote, but I do actually think there's a connection. I've also read and love this book, and it does push back on the "pragmatic" mentality espoused by The Pragmatic Programmer and other similar books.

I feel like this comes from Ousterhout's focus on actually building working systems. The Pragmatic books are much more focused on how one might get through the day as a programmer working at an org, but PoSD is focused on the ins and outs of building software well. I find that Pragmatic Programmer etc. have little to say about this, and when they do it's usually either trivial or fluff.

I'm not sure if Ousterhout is an "idealistic programmer" (I'm not even sure if this is the right term...), but I definitely feel like he's a fellow traveler...

[tmoertel]

This model of complexity from the book is very useful:

    complexity(system) =
      sum(complexity(part) * time_spent_in(part)
          for part in system)

[ck45]

For me “the problem with software, why smart engineers write bad code” is the prequel. Not as technical, but explains a big problem

[garethrowlands]

It's very good. And quite short!

[keyle]

Thanks, purchased.

[EagnaIonat]

Redundancy groups are full of idealists.

It's ok to be passionate about a topic, but also understand if that topic is still relevant in 3-5 years.

[sfpotter]

Being an idealist doesn't excuse you from being a realist.

[FrustratedMonky]

Did that, doesn't pay. Being a technology hipster is like being a master of jazz, it doesn't pay, so you sell out and play pop music.

[sfpotter]

What I'm describing is actually the exact opposite of being a hipster. From the dictionary, a "hipster" is "a person who is unusually aware of and interested in new and unconventional patterns (as in jazz or fashion)".

And, for what it's worth, following my own advice (I wouldn't give it otherwise), I haven't had major problems finding work. I live a comfortable life: own a house, have a wife and a kid, with another on the way...

Actually, knowing what it's like out there for a generalist programmer, I feel maybe more recession-proof with my highly specialized skill set (knock on wood). There are fewer jobs out there for me, but when I apply to the ones that are available, people tend to be interested in talking to me.

Of course, one thing that helps that I didn't mention in my original list: aggressively network with the other people who do the same thing that you do...

[FrustratedMonky]

I tend to agree with everything you said.

Was just thinking of this

" - Fall in love with a single topic, regardless of how trendy. "

Sounded hipster.

[sfpotter]

Fair! Personally, I'm not sure how you can get good at something if you aren't at least a little in love with it.

Here's another take: https://www.youtube.com/watch?v=75Ju0eM5T2c

[jimbokun]

All comes down to whether or not you picked a topic that will be financially viable several years later.

[sfpotter]

Yup. There is certainly an element of strategy that enters into it. Doubling down on a single programming language or piece of tech is probably not a good idea. Maybe doubling down on a niche field or subject is...

[netdevphoenix]

All those who fell in love with Silverlight, Flash or UWP likely agree with you

[sfpotter]

Yeah, but what were they doing with these tools?

[begueradj]

Over specializatoin is the enemy of adaptation.

[sfpotter]

It is? I often find that I work really well with people who are highly adaptable generalists. They help me get random things done that I'm slow at, I help them get highly specialized things done that they're slow at.

[manoDev]

Yeah, we need both types.

[theultdev]

I get you're comparing philosophies but none of those suggestions are mutually exclusive to the lessons taught in this book.

[emil-lp]

Not only are they not mutually exclusive, but if we're being honest, only idealistic programmers care enough to read Pragmatic Programmer, and they read it in the process of becoming a master.

[shakabrah]

Amen