Boston
May 8-11, 2017
Who Reads Books Anymore? Or Writes Them?
Writing a book is an unbelievably daunting task. In a world of 140-character communication, why bother churning out 200 pages of technical content? In this session, we'll talk about why people still write technical books, what the process looks like, and why these books are still worth reading. If you're thinking about writing a book about OpenStack (or even just reading a book about OpenStack), this session will offer essential tips on everything from chosing a topic to working with a publisher.
We faced a number of challenges while writing our book, "OpenStack for Architects," which was recently published by Packt. We'll walk through the hard parts, the lessons that we learned, and what we'd do differently the next time around.
What can I expect to learn?
- How to choose a compelling topic for a new technical book.
- How to go about actually writing the book.
- When and how to get help from friends and colleagues.
- How to work efficiently with a publisher.
Thursday, May 11, 2:00pm-2:10pm (6:00pm - 6:10pm UTC)
Difficulty Level: N/A
Red Hat
As a Chief Architect, Michael Solberg is responsible for helping Red Hat customers achieve their key business transformation initiatives through open source architectures and technologies. He regularly advises a range of Fortune 100 companies in financial services, healthcare, retail and transportation verticals on such topics as cloud computing, big data, high... FULL PROFILE
Crossvale, Principal Architect
Ben is currently a Principal Architect at Crossvale. He was formerly the Chief Cloud Officer for the Global Accounts Team at Cincinnati Bell Technology Services. He is also the co-author of the book "OpenStack for Architects" "Mastering OpenStack" and was the Technical Reviewer for "Learning OpenStack" (Packt Publishing). His latest contribution as Technical Editor of "DevOps Culture and... FULL PROFILE
Download App
