588 reputation
48
bio website
location
age
visits member for 1 year, 5 months
seen 5 hours ago
stats profile views 15

May
16
answered Best Practice for Argument Checking
May
14
comment Your opinion about JavaEE learning project
Do you have a personal website ? a blog ? if no you may choose to write one using JEE stack. At least i may be helpful
Apr
22
awarded  Nice Answer
Mar
20
comment What problems can be solved using Generics?
just think of generic collections ! It may be a good example
Mar
1
comment Should the variable be named Id or ID?
If using camelcase convention, it should definitely be xxId
Mar
1
awarded  Constituent
Mar
1
awarded  Caucus
Jan
3
comment Best Practice to Avoid “Playing Telephone” with Constructor Arguments
Ok, thanks for the info. But my concern was primarilly checking values in intensive loops (if x < 0 then what).
Jan
2
comment Best Practice to Avoid “Playing Telephone” with Constructor Arguments
Note that when working with graphics performance may be a prime feature, thus checking parameters or instantiating new objects in intensive loops may cause significant performance loss.
Dec
21
awarded  Yearling
Nov
26
comment Naming convention: field starting with “m” or “s”
Android dudes did really wrong in some aspects of their API, too much non standard java and outdated practices ...
Nov
22
comment Is it time to deprecate synchronized, wait and notify?
synchronized keyword may be usefull with simple static methods that should be thread safe, for anything else i would use concurrent. But this is my opinion
Nov
21
comment If you should only have one assertion per test; how to test multiple inputs?
In java with testng you have @DataProvider methods
Nov
21
comment If you should only have one assertion per test; how to test multiple inputs?
The best way to do so is using parameters (some framework support this feature, all frameworks should). This way you are testing a single behaviour but taking into account many test cases and still can see what parameter values caused an error if an error occurs
Oct
31
comment Supporting early versions of Android
Yes API 9 is the min sdk version in our product, it is a good compromise
Oct
29
comment Where should I draw the line between unit tests and integration tests? Should they be separate?
Integration test involves testing of more than one actual implementations of your components together (actual implementations means no mocks).
Oct
26
comment Is it OK to have multiple asserts in a single unit test?
When you do that you you should better using testing frameworks with dependant tests, it is better (e.g. testng supports this feature)
Oct
22
comment Do unit tests sometimes break encapsulation?
I dont agree, private stuff is private, taking them into account makes your tests very dependant on implementation. However it makes sense testing protected and package methods (package visibility is a java term).
Oct
8
comment Does it make a difference if I declare variables inside or outside a loop in Java?
In this case obviously there is performance and memory penalty. But it is not quite the case in the op's question
Oct
8
answered Does it make a difference if I declare variables inside or outside a loop in Java?