Timeline for Would de-coupling using interfaces/templates make the system easier to maintain at the cost of over-engineering?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 22, 2020 at 15:00 | history | tweeted | twitter.com/StackSoftEng/status/1319292447571111944 | ||
| Oct 22, 2020 at 0:06 | answer | added | user377672 | timeline score: 0 | |
| Apr 12, 2019 at 16:22 | vote | accept | Sam Hammamy | ||
| Apr 12, 2019 at 16:20 | answer | added | Guillaume Racicot | timeline score: 3 | |
| Apr 12, 2019 at 16:20 | review | Close votes | |||
| Apr 17, 2019 at 3:05 | |||||
| Apr 12, 2019 at 16:10 | comment | added | Sam Hammamy | @BenCottrell makes sense! so if the system demands high test coverage, it's probably worth the effort. Like an autonomous vehicle for example | |
| Apr 12, 2019 at 16:06 | comment | added | Ben Cottrell | The main advantage I could think of would be ease of mocking and unit testing. It's generally much less effort to test small, isolated, decoupled components compared with large monoliths, and you're also more likely to get closer to 100% code coverage with those tests. | |
| Apr 12, 2019 at 16:05 | review | First posts | |||
| Apr 16, 2019 at 18:50 | |||||
| Apr 12, 2019 at 16:02 | history | edited | Sam Hammamy | CC BY-SA 4.0 | edited title |
| Apr 12, 2019 at 16:00 | history | asked | Sam Hammamy | CC BY-SA 4.0 |