Those are books I've read and was not lazy enough to make highlights in them. Each book has a little summary and all the highlights I made while reading. Note that, book notes are not summaries, but a tool which should help you decide if you want to read the book or refresh memory if you've already read it. All highlights are sic erat scriptum.
In the list below they are sorted by date I've finished reading each. Technical, engineering and design references and textbooks usually don't make the cut, since I prefer those on paper. My complete book log can be found on Goodreads.
This book is a reference, not a textbook. Which makes it quite dull read on compositions but does provide a wide variety of examples — impressive 83 of them. That amount of samples covers quite a range of photographs, but I was not impressed with example photos. Some of the composition diagrams felt like analysis rather than construction techniques. I found it strange as the book is supposed to teach you quick thinking of constructing an image while the environment is changing and you are holding a camera.
What I liked about the book is lots of references to other exciting materials—especially cinematography textbooks. Overall, given how short and easy to read this book is, I'd say read it, but make sure to ignore western cultural stereotypes from the late 20th century.
Small, fun, and motivational guide on how to do build a personal business from the hobby. Super quick read, full of useful and small candies of information and tips. Want to start a small business and make money off your hobby? Read this book.
It is not easy reading. It is disturbing in many ways. Nor it is a photo essay or guide on how to be a journalist or war photographer. This book is an autobiography of a person who's is obsessed with her work and sense of justice — someone who'll chase news and truth even when her life is at stake. I mentioned this is not a photojournalists handbook, but I'd recommend anyone interested in photography to read this book, because no matter what kind of photography you do if you are seriously thinking about this career, you should know that taking photos is only part of the equation.
The Nature of Code is a fantastic book about the world around us, programming, simulation, and beauty of math. I am in love. You will learn how to simulate natural systems of all kind. You will learn how intertwined math and nature are. I read this book to improve my user interface programming skills, but I learned much more than that. I'd argue that any software engineer should once at least skim through this book. Game developers, biologists, and physicists owe themselves to at least be aware of this book.
Loved it! The book is full of little nuggets and practical advice on how to be a better Swift developer. It shouldn't be your first Swift book, but it could be a great second one. There are two traits of software engineer I value the most—being pragmatic (over being "clever" or tribalistic) and have a craftsman mindset. Paul seems to have both, and he shares his knowledge and experience through those two lenses. This book is my favorite Swift book so far, and I've read quite a lot of them.
The most comprehensive book about Auto Layout on iOS I’ve read so far. Full of neat tips and tricks as well as best practices otherwise not well documented in Apple’s documentation. The last chapter about trait collections is must read for any iOS developer no matter the experience. Excellent, well written, independently published book. Very recommended.
This book resonated with me more than any I've read. It felt like a formalization and validation of my finding of life for the past ten to twelve years. At the same time, I'm sure, 18-year-old me wouldn’t go past seemingly cheesy title. I can't tell you more, or even recommend reading it. If I have to, this would be my pitch: If you value calmness and tranquility, read it.
Every procrastinator like me should read this book, but before you run and pick one up, be warned—it is written in a very unusual way. First two books (let's call them chapters) are motivating and full of identifying what Resistance is and how to overcome it. Those two were most valuable to me. The third chapter is almost religious, which didn't much resonate with me, but I can see Steven's point of which I do agree. Somewhere on page 20, I started to treat the book as a provocative thinking stimulus; I think this is the right way to tap into a value of the book. If you skim through the book fast, the general gist of it is "just do your work and angels will guide you," which is not very helpful.
I have mixed feelings about this book. There are many little nuggets of trivial wisdom, regarding impulsive buying, self-worth and so on. But, disconnect I have with the Fumio's central philosophy is that in my view having less is a result of a calm and clear mind, not another way around. I can see who'd benefit from reading this book—it's just not me. If you are a pathological hoarder—read this book.
Book reads like a self-help book. I didn't expect that; granted this is not a problem with the book itself.
Xcode Treasures should be on the must-read list of any developer who’s starting with Apple platforms. Not to say it is not useful for experienced ones. Curious how manual code signing actually works? Do you look down on Storyboards? Whant to know little time savers that are all over Xcode? Finally, do you want an excellent guide to an xcodebuild tool you're fighting on CI machine every week? Read this book. I wish Chris wrote this book at least five years ago.