/explore
|
You are here 
|
edwardthienhoang.wordpress.com | ||
| | | | |
enterprisecraftsmanship.com
|
|
| | | | | This article is inspired by a tweet that I thought would be a good topic for discussion: should you abstract your database? | |
| | | | |
vietfactcheck.org
|
|
| | | | | Tranh cãi v? s? th?t c? b?n v?i ng?i mà b?n yêu th?ng là m?t vi?c nan gi?i. ?ây là vài ch? d?n v? cách ?àm lu?n v?i ng?i thân v? các ch? khó kh?n liên quan ?n s? nhi?u lo?n thông tin và tin gi?. | |
| | | | |
blog.julik.nl
|
|
| | | | | It is curious how people tend to bash DDD. I must admit - I never worked in a full-on DDD codebase or on a team that practices it, but looking at the mentioned articles like this one does make me shudder a little. There is little worse than a premature abstraction, and a there is a noticeable jump (or rather: a trough) which goes from abstraction to indirection. I've been programming for more than 20 years now - 12 of those professionally (with a little stint in-between) and I also went from obsessing over abstractions to a more, let's say, "common sense" approach to them. Oddly enough, this is not about OOP for me - it is about modules. And, to an extent, types - but I do believe types and behavior are going to stay connected in meaningful way. Whether you ... | |
| | | | |
johnazariah.github.io
|
|
| | | A post about how the foundations of functional programming have neat effects on real-life programming | ||
