This is my list of all the posts related to the technical practices that I consider the "MicroObjects Technical Pactices".
These are also helpful to me to see what topics I might want to write a little more on. :)
List last updated: 2019-08-19
Driving principle
Have a representation for every concept that exist in the code.
-
Testing
- Toll Impact on Developer Discipline - Dependency Injection Frameworks
- Toll Impact on Developer Discipline - Frameworks
- Thoughts - Testing without Mocks
- Refacotring Legacy Code: Leave Tested Methods Public
- PowerMock - Tool Impact on Developer Discipline
- Testability of MicroObjects
- MicroObjects: Code Free Constructors
- My Thoughts: Unit Tests
- My Thoughts: Slow Tests are Bad Tests
- My Thoughts: Testing on Android
- Testing Android Alert Dialog
- TDD against Android UI Elements
-
No Getters (or Setters)
-
Be Immutable
-
Interface for Behavior Contracts
-
Abstract 3rd Party Code
- MicroObjects: UI Example
- Quick: BookEnd for HttpClient
- Quick: MicroObjects and Json
- MicroObjects: Unit Testable UI Interactions
- MicroObjects: Where our code meets the user
- MicroObjects: Where our code meets their code
- MicroObjects: Where our code meets the Operating System
- HackerNews Android - Let's not crash
- Testing Android Alert Dialog
- TDD against Android UI Elements
-
No Public Statics
-
if
only as a Guard Clause -
switch
andelse
Always Evil -
No
null
s -
No
new
inline -
Extract Cohesion
-
Composition, Not Inheritance
-
No Primitive Obsession
-
No Enums
-
No Logic In Constructors
-
Never Reflection
-
Never Type Inspection