Books that I finished reading:
π Grammar Girlβs Quick and Dirty Tips for Better Writing β a book full of tips and tricks how to improve your writing skills. I believe that learning how to write is a good time investment. Itβs a portable skill that will always be with you. Writing is everywhere β blogging, emailing, chatting, marketing, documentation, coding. If you unsure about your writing skills, this book can boost your confidence, because there is no one right way.
π Practical Object-Oriented Design: An Agile Primer Using Ruby β itβs a book about object-oriented programming. I read this book because I organize Java courses, where I teach DDD and OO design. Sometimes I use metaphors that Sandi Metz uses for explaining OO. This book is OK, but Sandi has a better book β 99 Bottles of OOP.
π Implementation Patterns β I enjoy reading all of Kent Beckβs books. Kent is a remarkable developer and following his thoughts on software design is both enjoyable and rewarding.Β Although this book is not groundbreaking, it contains some solid patterns, especially useful if you are writing Java code. If youβre looking for patterns, probably youβll find this book boring. The biggest value of this book is not in the offered patterns. The value is in understanding whatβs in Kentβs head, how Kent is reasoning about code, coding, and design compromises.
π Test-Driven Development by Example β There are only two books you need to read to fall in love with TDD β this book and Growing Object-Oriented Software Guided by Tests. Whereas GOOS is more practical and showing how to test-drive real applications, Kentβs book makes you β the reader β feel the rhythm of TDD. Itβs like pairing together with Kent. The book also covers non-technical aspects of TDD, such as developerβs happiness and productivity.
π Do Not Harm β a memoire of a neurosurgeon Henri Marsh, where he discloses his struggles and thoughts about life and death. Really good book full of interesting stories.
Article that I recommend:
Some of my tweets:
