Reminder: this is all fake. Any time someone makes a claim like this, either they are lying, or every single programmer they know is completely awful and can’t program at all.
https://t.co/0a9n7IE7Xg
Elegant solution = simple solutions to a complex problem. But just because it's simple (in the end), it doesn't mean it's easy to implement. It often takes many iterations to get from complex (hard to understand) solution to a simple one.
@gwenshap JPA/Hibernate, but keeping domain object model close to DB model - not using relation mappings at all. This way objects are shallow which is great for caching (makes cache invalidation a lot easier). Composing (DTOs) at higher levels. Using separate methods for fetching relations
#Kotlin is wonderful!
Let me just give you one tiny example:
Getting part of the String after the last / char:
s.substringAfterLast("/")
Doing exactly the same thing in Java is much less elegant. And Kotlin is full of little helper functions like this!
Two of my favorite philosophies that can be applied to work:
- "Hope for the best, prepare for the worst"
- "Under-promise, over-deliver" (and for this one I would add - "but not too much")