[{"_1":2,"_46":-5,"_47":-5},"loaderData",{"_3":4,"_14":15,"_44":-5,"_45":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9,"_10":11},"user","shoppingCartId","toast","locale","en","constants",{"_12":13},"paypalClientId","AenrHU49peF-ZUH-Yq7AXLLNZYGUGlml474U16NCjB4ZznmQCEjiliN3whyuVZmkb7VxEzmTALgtKEKE","routes/_store+/_readers+/email_author.$slug/route",{"_16":17,"_43":-5},"book",{"_18":19,"_20":21,"_22":23,"_24":25,"_26":27,"_28":29},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvMTk5NjA","title","Java KISS Thinker Volume 1: Application of Knowledge","state","published","contactAuthorMethod","email","aboutText","

Upon starting to write this book, I’ve seen more and more complaints about Java.

Java has been a major breakthrough for IT projects, but like everything in life, nothing stands still, and the bigger something becomes, like Java, the harder it becomes to keep up with and be able to change direction with the newer technologies.

Java is a phenomenon and as a result has almost grown too big. To learn all of Java including all the extensions such as third party open source is a daunting task.

The newer technologies are Scala, Clojure, Swift and Go, just to name a few.

However, even though learning another language, and/or another methodology is beneficial (I believe in projects using multiple technologies), a Developer still writes the code. If the application is not very extensible, maintainable, blame the Developer(s), not the technology.

It’s not what you know, but how you apply what know.

The application of knowledge.

","authors",[30],{"_18":31,"_32":33,"_5":34},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci8yMDcyNA","name","David Ainslie",{"_35":36},"avatar",{"_37":38,"_39":40,"_41":42},"url","https://d308did4coypzi.cloudfront.net/avatars/239523/medium/Me_1.jpg?1486593140","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the Author