News for hackers. Stuff that matters.
Re:Books that changed my career as a software engineer by underdeserver on Sunday November 28, 2021 @05:57AM (#29367930)
I actually find the opposite.

Many books belabor the point and take a chapter to explain what a paragraph could.

It might sometimes be useful - for example, to explain a scenario to a newbie who can't relate from their own experience - but for someone who's been in the industry for a while, most of that information is just not useful.

Re:Books that changed my career as a software engineer by _n_b_ on Sunday November 28, 2021 @06:48AM (#29368141)
Relatedly, but I've always wished there were a series of books like, "I'm Already a Programmer but I'd Like to Learn ____"

Trying to pick up a book about a new programming language that is trying to explain the concept of an 'array' or whatever is annoying--I wish there was something to just lay out (still in a thoughtful and guided way) the concepts I needed to understand for that language based on already knowing several others.

Re:Books that changed my career as a software engineer by Breza on Tuesday December 07, 2021 @12:21PM (#29475357)
Agreed! I've only found a few great examples of books like this, such as Advanced R. There's a lot of "You can skip this chapter if you already know how to answer the following questions..."
Re:Books that changed my career as a software engineer by rasfincher on Sunday November 28, 2021 @07:00AM (#29368204)
It would be nice if the table of contents marked where to start if you're already familiar with programming concepts.
Re:Books that changed my career as a software engineer by boppo1 on Sunday November 28, 2021 @07:09AM (#29368260)
Learnxinyminutes?
Re:Books that changed my career as a software engineer by pastage on Sunday November 28, 2021 @06:32AM (#29368067)
Called US writing style over here, just being overly verbose. Course literature, e.g. Calculus, suffers from this. It is a style in which you wax on and drive home the point by repetition.

This style is popular nowdays and finding books that succintcly describes a subject is hard. This is mostly because you need to have common ground, and writing for the smallest common denominator is better.

Re:Books that changed my career as a software engineer by Breza on Tuesday December 07, 2021 @12:25PM (#29475425)
Writing succinctly is a difficult skill that requires practice. The US government has put a lot of work into making things easier to understand in recent years. I have a Masters in Public Administration. My professors hammered home the idea that lawmakers and the public aren't going to read your 50 page policy analysis, so matter how brilliant it is. My final paper in Project Management class was worth 25% of my final grade and had a one-page limit. It's one of the most difficult projects I've ever had. If you're interested in learning more about this style of writing, check out plainlanguage.gov.
Re:Books that changed my career as a software engineer by underdeserver on Sunday November 28, 2021 @10:16AM (#29369496)
I actually think Calculus textbooks are justified in being long. he material is just so hard to grasp for newbies that giving you more and more examples sort of provides you with more time to digest the ideas in the background. Many students need that at that stage in their studies.