Tim Driven Development | Test until the fear goes away
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Driven Development | Test until the fear goes away
Tim Driven Development | Test until the fear goes away
Stephen Jordan wrote:Any preference for one over the other from a readability respective? I think the first one is a lot more readable but maybe I'm too used to reading my own code to offer an unbiased opinion
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Roel De Nijs wrote:I'm wondering if the old school style (using an enhanced for loop) is not better for this use case...
Roel De Nijs wrote:And a bit related: should you always opt for a stream-based solution when using JDK 8? Or would you still consider an iterator-based solution? And if so, in which situations?
Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |