I only found today that Unicode (not just HTML) also has the concept of a non-breaking space character. If you ever find something that looks like ' ' but never quite equalling ' ' then I suggest you look at their char value. 32 is the normal space character, 160 is the non-breaking space one. A few other interesting notes:

• A non breaking space is not considered white space (in java)
• A non breaking space is considered white space (in .Net)
• Space is part of the normal BASIC_LATIN Unicode Block, No Break space is part of LATIN_1_SUPPLEMENT

Please print: $IntelliJ5_Installation_Path$\help\ReferenceCard.pdf or for older versions see this.

All the projects I have ever worked on have never been technically difficult (in fact I think that most of them in the world are not). The biggest challenge I find is learning the language that all the people who work daily on the project speak in. To put this in context, after rolling onto my newest project, my biggest problem has been trying to understand what it is exactly that everyone speaks of because, to me, it almost seems like a completely different language. There are certain patterns that I am trying to use to come up to speed quicker. I am sure that there are established learning patterns, but I thought it might be useful to share some of the ones that I use.

Decode the Acronyms – Most languages have an abbreviation for extremely repetitive terms that are important to people in the domain. Decoding acronyms helps with the next pattern of Defining the Vocabulary.

Define the Vocabulary – Think of the ubiquitous language from Eric Evans’ Domain Driven Design and simply put, is used to translate special terms people involved with the domain into something a person who does not know anything about the domain can relate to. Fortunately for me, the Vocabulary on my current assignment has been documented pretty well. I find that repeating them in daily conversations with people who know about the domain (and can correct me) is a useful technique for truly understanding what they mean.

Adopt the Grammar – Common words are especially dangerous on a new project because they are things you assume mean one thing but when put together in a special way or in a different context, can mean something totally different. Adopting the grammar is a lot more readily accomplished once you have learned the vocabulary.

Discover the History – New languages emerge because once they are understood, they can be a more effective communications mechanism for operating in the same context. Discovering the history is about finding out where the vocabulary and terms come from, and why they are used in the way that they are. These factors can come from many sources including technical, political, environment or just conventional.

Obie posted this entry that coincided with an issue I’ve been thinking of for the last few days. I probably need more time to refine this but at the least I think when errors occur in programs they should, at the very minimum, describe:

• What went wrong (the problem)
• Why it went wrong (the context)
• How you can fix it (the solution)

We put in a JUnit hack into our latest project that allows us to produce more readable test names.

@Override public String getName() {
    return getClass().getSimpleName().replaceAll("Test$", "")
        + super.getName().substring(4).replaceAll("([A-Z])", " $1").toLowerCase();
}

Turning testTellsMeHowMuchInterestIEarnInAYear() from the BankManagerTest into Bank Manager tells me how much interest i earn in a year..

Note the disclaimer: Tests in IntelliJ are no longer clickable afterwards but the stack traces still are