If you’re passionate about programming and want to get better at it, you’ve come to the right source. Code Craft author Pete Goodliffe presents a collection of useful techniques and approaches to the art and craft of programming that will help boost your career and your well-being.
Goodliffe presents sound advice that he’s learned in 15 years of professional programming. The book’s standalone chapters span the range of a software developer’s life—dealing with code, learning the trade, and improving performance—with no language or industry bias. Whether you’re a seasoned developer, a neophyte professional, or a hobbyist, you’ll find valuable tips in five independent categories:
Code-level techniques for crafting lines of code, testing, debugging, and coping with complexity
Practices, approaches, and attitudes: keep it simple, collaborate well, reuse, and create malleable code
Tactics for learning effectively, behaving ethically, finding challenges, and avoiding stagnation
Practical ways to complete things: use the right tools, know what “done” looks like, and seek help from colleagues
Habits for working well with others, and pursuing development as a social activity
Pete Goodliffe is a programmer, a software development columnist, a musician, and author. He never stays at the same place in the software food chain - his projects range from OS implementation, through audio codecs, to multimedia applications; from embedded firmware, through iOS development, to desktop applications. He has a passion for curry and doesn’t wear shoes.
Pete’s popular development book Code Craft is a practical and entertaining investigation of the entire programming pursuit. In about 600 pages. No mean feat! It has been translated into many languages. He writes a magazine column called "Becoming a Better Programmer," has contributed to several software development books, and regularly speaks on software development topics.
The animal on the cover of Becoming a Better Programmer is a two-winged flying fish (Exocoetidae). The flying fish can be distinguished by its unusually large pectoral fins. As the name suggests, it makes powerful, self-propelled leaps out of the water into the air by moving its tail up to 70 times per second. In the early 1900s, flying fish were studied as models for developing airplanes. Once in the air, it spreads its wing-like fins and tilts them upward, which enables it to glide for considerable distances. The pectoral fin, or "wing," has a similar aerodynamic shape as a bird wing. At the end of the glide, it either reenters the sea by folding the pectoral fins, or dropping its tail into the water to lift itself for another glide. The record is 45 seconds in flight, as recorded by a Japanese television crew in 2008.
Their ability to fly into the air is often used as a defense mechanism against predators, which include dolphins, tuna, marlin, birds, squids, and porpoises. They're commercially fished by gillnetting in Japan, Vietnam, and China, and by dipnetting in Indonesia and India. In the Solomon Islands, flying fish are caught during flight in nets from outrigger canoes. Commercial fishing of this species is done in complete darkness when no moonlight is available, as the fish are attracted to lit torches. Flying fish feed mainly on plankton, and live in all of the oceans, mostly in warm, tropical or subtropical waters.
Many of the animals on O'Reilly covers are endangered; all of them are important to the world. To learn more about how you can help, go to http://animals.oreilly.com.
The manuscript was prepared using asciidoc, love, and vim. The cover image is from loose plates. The cover fonts are URW Typewriter and Guardian Sans. The text font is Adobe Minion Pro; the heading font is Adobe Myriad Condensed; and the code font is Dalton Maag's Ubuntu Mono. Cartoons are drawn in AutoDesk SketchBook with layout in Adobe Photoshop.
A fun and insightful book to get us all to the right path
Easy to understand
Comments about oreilly Becoming a Better Programmer:
This book is definitely fun and insightful at the same time, which makes up a devastating combo if you are that kind of developer that does care about what he delivers, that kind of professional that gets to work before everyone else because it's not just about the money, it's because I love what I do, that kind of guy that enjoys staying up until 5 am with his favorite text editor opened and a cup of warm coffee next to him.
I've enjoyed these 360 pages. I have enjoyed them so much that I'm sitting in front of Iceweasel with that stupid smile that you have when something nice just happened to you.
What is this book about? It's about caring about what we do. It's about throwing our ego apart and accepting that we are humans and, as such, we all make errors and, mainly, we can/must learn from them.
Developing software is that mix of science, art and magic that's hard to define. Still, there are best practices and some common sense guidelines that get us to the next level. And make the world a better place.
I have read, years ago, Clean Code by R. Martin. Well, that was great. I think that I have learned a lot from that text. Reading Pete's book reminded me many things of Martin's. I'm pretty much sure Pete himself has read and loved that book and was influenced by it, as a lot of coders have been as well.
But Pete is fun! Reading this book makes you wanna be his team mate and share with him stories, those funny things we tell each others during a coffee break or lunch.
If you are a developer that cares about his code, then Becoming a Better Programmer will definitely get to your soul. Pete is one of us, I can tell.
Suggested Books: Clean Code: A Handbook of Agile Software Craftsmanship
As usual, you can find more reviews on my personal blog: http://books.lostinmalloc.com Feel free to pass by and share your thoughts!
Bottom Line Yes, I would recommend this to a friend
Comments about oreilly Becoming a Better Programmer:
I understand this is an early release but this book doesn't contain very much useful content. I have read other books on good development that were significantly better. When the book is final, I will try again and, hopefully, it will be more useful. Right now, it is a bunch of fluff with no good information.