How assign bean's property an Enum value in Spring config file?

Had this exact problem today of having to assign a bean's property with an Enum in a Spring XML configuration file. Seems that the answer is easier than expected! You just type in the enum's name directly for the value e.g.

<bean:property name="searchType" value="PRIVATE"/>

http://stackoverflow.com/a/516899

Preparing Your Code for JDK 9

Preparing Your Code for JDK 9: Erik Costlow discusses what to consider when upgrading to Java 9, where to find early access releases and how to analyze library dependencies for unintentional reliance internal APIs.

API deployment

There are build automation tools for programming languages, which can be integrated into IDEs, e.g. Maven for Java, and any other JVM-based language (Clojure, Groovy, Scala, Ivy). Maven also has excellent dependency management from the Maven Central repository (and any private repositories). For Python, there's PyPI. Perl has CPAN. Node.js has NPM. 

How To Install Java on Ubuntu with Apt-Get

A very clear tutorial on how to how to install Java on Ubuntu with Apt-Get:

https://www.digitalocean.com/community/tutorials/how-to-install-java-on-ubuntu-with-apt-get

EMBL-EBI Software Engineer job opening

We are a hiring a motivated software developer in Java, Scala, AngularJS with strong knowledge in Bioinformatics.

http://www.embl.de/jobs/searchjobs/index.php?ref=EBI_00702&newlang=1

Java 8 in Anger

Java 8 in Anger: Trisha Gee shows how to build a fully working end-to-end application using just the core libraries available in the latest version of Java.

Reading programming books

I've always struggled reading technical books, and I'm looking for ways to improve myself upon this. With my recent reading list I've got a opportunities to address this and better myself.

In the past what might happen is: I buy a textbook that seems to have good reviews about what I want to know more about, then I try and read it and can get barely through a chapter. Then I try other chapters that I may be more interested in and the same thing happens again. Then the fat book ends up on the bookshelf gathering dust. Time passes and the technology has moved on and it's obsolete, or I'm never going to use that technology and lost all drive about it.

The reasons for that are because the information is technically difficult to understand, and to know about it properly, I feel it needs to be applied, in say tutorial examples, or real-life work. And more often then not I either can't get the tutorials to work, the tutorials are too basic, and there are no work opportunities for its application. Knowledge or skills are barely obtained in the first place, and are then not retained at all, and frustration kicks in.

I know there are generally two types of programming books: guides and references. So when I'm only referring to guides, and that's what I'm really interested in learning new technologies, and not looking up particulars.

I've known people who can literally read a technical book from start to finish and immediately assimilate the knowledge. They remember the content and then are capable of immediately applying to to a situation, perhaps referring to the material or perhaps not sometimes. I have tried to do that, and I am simply incapable of doing so, which again frustrates me.

I remember when I was trying to get into Spring Batch more, and I would aim to read and complete chapters every week for a couple months. Then in work, using Spring Batch, I could apply almost nothing from my "homework" because I wouldn't remember anything that I had read about.

My strategy was reading and making notes (and re-reading, re-reading) and completing tutorials, but I think in my case I need more than that, and I'm not sure what. I have tried to identify better strategies and I found a few posts online about that:

• https://blog.newrelic.com/2015/03/18/learn-code-programming-book/
• http://programmers.stackexchange.com/questions/17826/how-do-people-read-big-technical-books
• http://norvig.com/21-days.html

I think a lot of this comes down from my school or university days. I mean, in my lifetime I've received no formal training in how I am supposed to learn from a textbook, especially programming. So perhaps I'm doing things wrong. Perhaps smarter people than me don't need to follow other learning protocols, or the best practice for learning have already come naturally to them. Muddling along and trying to do what I've done before isn't for the best, and I'm tired of it.

Software deveopment reading list

Starting my new year's resolution a month late, I've put together a reading list I want to start getting through this year. It focuses on software development / engineering, and also a little about Java too.

Helping conduct recent interviews has prompted me to make a start on this, because refreshing my mind about concepts, design patterns, etc would be a good idea. It certainly can't hurt, and it would definitely help as I make the transition to a software developer proper in my workplace. Apart from technical knowledge, I'm sure the material also explains a lot about how to approach work better, or be more productive through work.

The list contains some Java-related books too, this is because most of our code at work is using Java 7, and I haven't had the need to, or exposure to, 8 yet. This way hopefully I can get more up to speed with recent developments I've not had to chance to consider in previous months. Java 9 is already progressing, so it makes a lot of sense to drive on with this too.

I thought I'd share my reading list, in case someone else would be in a similar situation and looking for a place to start. By no means is this a complete list, and I'd be open to any suggestions as well for any other good material.

• The Pragmatic Programmer
• The Passionate Programmer
• Clean Code
• The Clean Coder
• The well-rounded Java developer
• Design patterns: elements of reusable object-oriented software
• Head First, Design Patterns
• Introduction to Algorithms
• Data Structures and Algorithms
• Java SE 8 for the really impatient
• Java 8 in Action
• Spring Data

What started me on making my list was this very informative post:

http://blog.codinghorror.com/programmers-dont-read-books-but-you-should/