Many of the posted articles are closely related, so I decided to summarize them in the table of contents. Although the sample code is C #, I think it applies to Java with a similar grammar to some extent.
I want to give you a chance to write good code Complicated conditional branching A little worrisome code collection Flowing interface? Redundant assignment statement Useless processing for collection Easy Null Check Handling of Bool type 2017/3/17 Added about bool type function </ font> Too many function arguments Can I separate function calls and conditionals Getter, Setter inverse problem Arrange everything When the processing after conditional branching is redundant Problems of using screen display values Ignore exceptions Whether the conditional branch uses early return or is written safely and comprehensively
Database I want to stop snake case in table definition
DataSet related Get a nullable value from the DataRow of the typed DataSet.
Coding convention Collection variable naming convention
Design pattern Separate progress display and business logic
Other Use C # increments in Visual Basic (http://qiita.com/csharpisthebest/items/82e0b8ccad1fc7fef85e) [Be careful if you find SHIFT-JIS in Java] (https://qiita.com/csharpisthebest/items/2cd61661dbc42d81aa45) [C #] System.Uri's base URI and relative URI were different from what I expected
Recommended Posts