Live data from Hacker News

Books that changed my career as a software engineer

julianogtz.github.io

81–90 of 295 posts

Re: Books that changed my career as a software engineer

#81
post #63
post #36

Earlier quoted context omitted.

Have you considered trying books filled with structured exercises? I worked through The Little Lisper when I was at university and I got a lot out of it, for example.

I think this is the kind of content I need. One that presents a problem and allows me to figure out a solution. Can you recommend any other content like that?

projecteuler.net?

Re: Books that changed my career as a software engineer

#82
post #61

Is it just me or do other people struggle to read these kinds of very technical books? It's not that I don't comprehend, it's that my brain finds it boring and hard to focus. I think I have trained my brain so much on rapid skimming of websites for useful info, while throwing away most of the content, that I tend to do the same with books, which really doesn't work well. Has anyone found alternative ways to consume t…

Yeah, I'm the same way. I've gotten better at it though by "practicing." For me, it's the same process as strength training. You need progressive overload. Start with easy to read attention capturing books, and slowly progress to harder and harder books.

Re: Books that changed my career as a software engineer

#83
post #49

The thing that changed my career as a software engineer, in terms of seniority & remuneration by time and effort, was by changing my efforts from learning arbitrary tech to learning the domain I worked in. Asking useful domain-related questions gets you noticed in stand ups and helps you write the right code. I work in fintech so the best bang for my buck I’ve had was reading an entry level cert in investment finance…

Big +1. Most corporate software is pretty straightforward (the company likes it this way so that it's easier to onboard new engineers). So, you stand out by delivering something other engineers can't, deep insights into how software can solve specific domain problems.

Re: Books that changed my career as a software engineer

#85
Some of the juicier bits from these books have been fairly well absorbed by engineering culture, ie "rubber duck debugging" and "DRY". Some of these books I haven't heard of though.

As somebody who didn't study CS in college, the books that most changed my career were:

  * Algorithms, by Robert Sedgwick (probably not the best algorithms book, but lots of hands-on stuff)
  * Learning From Data, by Yaser S. Abu-Mostafa et. al. This one has video lectures to go along with it.
  * C Programming: A Modern Approach. (Definitely not the best, but also lots of hands on stuff)
Another thing I've found extremely educational is to read major incident postmortems (SEV0s and security SEV1s at FB, "huge" OMGs at Google). If you ever find yourself anywhere with planet-scale infrastructure, make sure to read these write-ups. They are treasure.

Re: Books that changed my career as a software engineer

#86

I have a terrible problem with people recommending books that „changed their whatever”. And sometimes I think that it comes from an arrogant place where people being „influenced” by books is a bad place. But I do understand that sometimes books can change the way one thinks about things, and it makes sense to make a list of those. For me, there are books that had a negative impact on my work. The GoF book is one such…

>Or books on fundamentals…

Abelson, Sussman's Structure Interpretation of Computer Programs also good recommend - helps show that whilst it's not magic, fact everything still works is magical

Re: Books that changed my career as a software engineer

#87
post #32
post #26

Earlier quoted context omitted.

Being an engineer is just that - an engineer. It's different from being a leader. Being a "10x" engineer just makes you a better engineer, it doesn't mean you're any more capable of making a decision that would generate a company $100 million in yearly revenue. Just different skill set. Steve Jobs wasn't a great engineer, but he was a great product visionary and marketer.

> Being an engineer is just that - an engineer. It's different from being a leader. I disagree. In fact, the third or fourth stage of your promotion will often be a leadership position (junior, senior, principal/tech lead). If you're okay with being a "senior engineer" until you're 45, you're going to be in for a rough time when you get inevitably laid off.

I stand by my take. A good engineer is not guaranteed to be a good lead. And a bad engineer isn't guaranteed to be a bad lead. They are different roles.

Most competent companies let good engineers who won't be good leads stay in IC roles with bigger responsibilities.

Re: Books that changed my career as a software engineer

#88

I have a terrible problem with people recommending books that „changed their whatever”. And sometimes I think that it comes from an arrogant place where people being „influenced” by books is a bad place. But I do understand that sometimes books can change the way one thinks about things, and it makes sense to make a list of those. For me, there are books that had a negative impact on my work. The GoF book is one such…

> One such people screwed my career development for 7 years because at one internal interview he asked me out of nothing about the „half sync half async pattern”, that solves a problem that he wasn't able to describe to me. And since I failed, I was forever on their s*t list. This is a sign, that in order to solve the problem, you must move on to a job that isn't the problem.

I learned many things from that experience, but later, when I actually got smarter about career and interviews; being introverted didn't help much either. But I'm glad I didn't make this mistake on my end, when I was at the other end of the table; I was able to hire and help grow people who would have been put down because they didn't read a recipes book.

Re: Books that changed my career as a software engineer

#89
I have no doubt those books inspire people to become substantially better developers. I have observed in the large corporate world career progression is not linked to either quality of developer or quality of product.

It is important to keep those in mind and then determine what is more important: career progression or work satisfaction.

Re: Books that changed my career as a software engineer

#90
post #61

Is it just me or do other people struggle to read these kinds of very technical books? It's not that I don't comprehend, it's that my brain finds it boring and hard to focus. I think I have trained my brain so much on rapid skimming of websites for useful info, while throwing away most of the content, that I tend to do the same with books, which really doesn't work well. Has anyone found alternative ways to consume t…

I agree that many of these books are hard and super boring to read. That's why I always recommend books that are written in easy and accessible style, such as The Little Schemer, The New Turning Omnibus, and Programming Pearls (not Perl but Pearls by Jon Bentley). Or, books that are written in problem-hint-solution style, such as The Little Book of Semaphores and To Mock a Mockingbird. These are so fun and easy to re…

Those are completely different books than what the blog post focuses on. Yours are solely focused on learning tech/maths.
Post reply on HN