Java 9 Programming By
Example
Your guide to software development
Peter Verhas
BIRMINGHAM - MUMBAI
Java 9 Programming By Example
Copyright © 2017 Packt Publishing
All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or
transmitted in any form or by any means, without the prior written permission of the
publisher, except in the case of brief quotations embedded in critical articles or reviews.
Every effort has been made in the preparation of this book to ensure the accuracy of the
information presented. However, the information contained in this book is sold without
warranty, either express or implied. Neither the author, nor Packt Publishing, and its
dealers and distributors will be held liable for any damages caused or alleged to be caused
directly or indirectly by this book.
Packt Publishing has endeavored to provide trademark information about all of the
companies and products mentioned in this book by the appropriate use of capitals.
However, Packt Publishing cannot guarantee the accuracy of this information.
First published: April 2017
Production reference: 1240417
Published by Packt Publishing Ltd.
Livery Place
35 Livery Street
Birmingham
B3 2PB, UK.
ISBN 978-1-78646-828-4
www.packtpub.com
Credits
Author
Peter Verhas
Copy Editors
Muktikant Garimella
Zainab Bootwala
Reviewer
Jeff Friesen
Project Coordinator
Ulhas Kambali
Commissioning Editor
Kunal Parikh
Proofreader
Safis Editing
Acquisition Editor
Denim Pinto
Indexer
Mariammal Chettiyar
Content Development Editor
Nikhil Borkar
Graphics
Abhinash Sahu
Technical Editor
Hussain Kanchwala
Production Coordinator
Melwyn Dsa
About the Author
Peter Verhas is a senior software engineer and software architect having electrical
engineering and economics background from TU Budapest (MsC) and PTE Hungary
(MBA), and also studied at TU Delft and TU Vienna. He created his first programs in 1979,
and since then he has authored several open source programs. He has worked in several
positions in the telecommunications and finance industries and was the CIO of the
Hungarian start-up index.hu during its early days.
Peter works for EPAM Systems in Switzerland, participating in software development
projects at various customer sites, and he supports talent acquisition by interviewing
candidates, training programs for developers, and internal mentoring programs.
You can follow Peter on Twitter at @verhas, LinkedIn, and GitHub, or read his technical
blog, Java Deep, at h t t p ://j a v a x 0. w o r d p r e s s . c o m .
Acknowledgement is the section of a book that everybody ignores by turning the pages.
This time, this section is a bit different. I will mention a few people and their roles in the
making of this book but, at the same time, I will explain why and how it is important to
rely on people, being a software developer.
Doing professional work is not possible without having a life. It is quite obvious if you take
that literally, but it is just as true figuratively. If you do not find the balance between your
personal and professional life, you will burn out and will not operate professionally. This is
the place to mention my family, my parents whom I am lucky to still have around, my wife,
and my already adult kids who never stopped believing in me being able to do this work,
who know more than well what a hypocrite I am, advocating personal-professional life
balance, and who continually pushed me closer to this equilibrium point in life so that I
could keep performing professionally.
For professional work, coworkers are almost as important as family support. It is important
that you support your colleagues as much as you ask them for their support. You learn a
lot from books and from experience, but you learn the most from other people. Pay
attention to senior developers. You can, however, learn just as much from juniors. No
matter how ace you are, from time to time, a rookie may shed light on a topic. During the
years, I learned a lot from juniors who brought a fresh view to the table, asking shocking
questions that were absolutely valid. I cannot name each and every junior who aided my
work with fresh out-of-the-box thinking.
