upvote
reply
I'm not sure how you came away with that impression. Three out of three reviewers say they overall enjoyed the book. The complaints fall mostly into four buckets:

- "I wish the book was simpler" (Jesse)

- "I wish the book was more advanced" (Murat)

- "I wish software engineering was more advanced" (Andrew)

- "I didn't understand the arguments the author made for why studying single-server exponential response time systems helps with drawing conclusions for time-sharing, heavy-tailed response time systems" (Jesse)

None of these paint the book in a bad colour, as far as I can tell. They say more about the reader's expectations than the book itself.

reply
Sure. But I'm trying to connect what you said:

> you'll come out with superpowers you didn't have before.

with the impressions from the reviewers.

I don't think they got super powers from the book. In fact their outcomes mirrors my own outcomes when going deep into some math topics and then bringing them to work.

reply
I don't think this is a good resource for an intro tbh. Unless you are interested in proofs and have some probability basics covered, it feels quite dense.

I liked Principles of Product Development Flow a lot more because it was easier to digest, although it's a different application of queuing theory.

reply
That is also a good book containing a few practical applications of queueing theory, but it won't do anything to help you analyse your own systems on a more fundamental level.
reply
Even if you just read the first few chapters of this you will not come out unchanged.
reply