But the future never gets easier, does it?
Because a year from now they wade through all this excess baggage written at a time when they thought they understood the domain of the problem (but clearly didn’t), instead of having simple code (like the very first example of factorial above) that they can revise as needed, they wind up with the most over-engineered pile of nonsense that no-one can possibly understand.
I’ll be honest, I never really felt engaged during “code review” meetings at the end of an iteration. It always took too long to get and discuss the code. The room would get warmer. We’d discover things we’d want to change. Many of those changes would never be made.
Since today is Boycott a Meeting Day, I thought I’d offer an alternative we’ve used lately.
http://hiramchirino.com/blog/2011/01/activemq-apollo-looking-impressive/
StringSearch
High-performance pattern matching algorithms in Java
The Java language lacks fast string searching algorithms. StringSearch provides implementations of the Boyer-Moore and the Shift-Or (bit-parallel) algorithms. These algorithms are easily five to ten times faster than the naïve implementation found in
java.lang.String.
Very awesome stage fight sequence.
In IntelliJ IDEA, when you update a .classpath file externally IDEA pops up a dialog that complains and tells you that you need to reload the project. I think they've fixed this in 8.x for .iml files, but not for linked Eclipse .classpath files.
When I'm running 2 apps under the debugger I don't want to lose all that and start over just because I screwed up a dependency.It's simple:
A cute photo of my daughter Laila hanging out this past Memorial Day weekend.
