Reputation
300
Next privilege 500 Rep.
Access review queues
Badges
1 11
Impact
~10k people reached

  • 0 posts edited
  • 0 helpful flags
  • 1 vote cast
Nov
18
comment Should Java 8 Stream instances always be close()'d?
So basically close is the only safe alternative? I guess the question is how not to make code look overly ugly every time a Stream would be handy to use.
Nov
18
asked Should Java 8 Stream instances always be close()'d?
Jun
17
awarded  Popular Question
Mar
7
awarded  Yearling
Jan
21
awarded  Nice Question
Dec
6
awarded  Commentator
Dec
6
comment Generating test data for a search application
I've actually gotten that suggestion before from QA engineers, thanks for reminding me of it.
Dec
6
comment Generating test data for a search application
Thanks for the links!
Dec
6
accepted Generating test data for a search application
Dec
3
awarded  Curious
Dec
2
asked Generating test data for a search application
Sep
24
awarded  Autobiographer
Dec
5
awarded  Scholar
Dec
5
accepted Multiple APIs, or one API with a “chooser” parameter?
Nov
20
awarded  Supporter
Nov
20
asked Multiple APIs, or one API with a “chooser” parameter?
Jun
4
awarded  Tumbleweed
May
28
asked Simple task framework - building software from reusable pieces
Feb
22
answered Policy and practice on code maintenance
Feb
13
comment Java Generics - how to strike a balance between expressiveness and simplicity
@lorus - my idea was to have a "transform" interface that I could use for a variety of transforms, as opposed to one specific case that is tailored to a specific combination of source and target item types. A way of summing up my post is "how do I keep it simple in a manner that wouldn't require significant rework in the future". We're in a typical corporate setting where deadlines are king and I can't just go refactor things unless there is a sound business reason. Same concern applies to YAGNI in Frank's comment.