Timeline for CRUD service with or without DTOs
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 30, 2022 at 19:35 | comment | added | Robert Bräutigam | I'm not saying you should use a bad or non-expressive design. I'm just saying don't introduce abstractions that don't help you now. Use the best and simplest design for your current case. Don't, in general, do things just out of habit, or a sense of "cleanliness", or because of something you think you will need later. Easier said that done, sure, but such is software design. | |
| Mar 30, 2022 at 14:08 | comment | added | Jan Gassen | Right, but I guess for this to apply you either need to be sure that a more complex solution is never going to be needed, or there is a possible migration from the simple to the more complex solution if it ever becomes necessary. | |
| Mar 30, 2022 at 12:58 | comment | added | candied_orange | This general rule has been given a name: YAGNI. | |
| Mar 30, 2022 at 10:47 | history | answered | Robert Bräutigam | CC BY-SA 4.0 |