Timeline for answer to Is it good practice to make everything internal in C#? by Flater
Current License: CC BY-SA 4.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 24, 2022 at 7:14 | comment | added | Ernst Zwingli |
One could do the same argument in an apartment building, rather than single rooms in my own apartment. I'd even argue, that the single rooms in my apartment comparison better refers to using private over internal, while different apartments in an apartment building refer to using internal over public. Only the shops on the ground floor you want to keep public, because they are for everyone's use. But single living apartments should stay internal. Also a good reference here is "hiding complexity to reduce cognitive load for others" (Team Topology, Continuous Delivery).
|
|
| Aug 30, 2019 at 11:46 | history | edited | Flater | CC BY-SA 4.0 |
added 39 characters in body
|
| Aug 30, 2019 at 11:34 | comment | added | Flater | @Ewan: The main takeaway is that it's mostly a cost/benefit analysis. Doing it (or not) brings pros and cons and it's a matter of deciding which pros and cons you'd prefer. | |
| Aug 30, 2019 at 11:16 | comment | added | Ewan | oof, thats a dodgy analogy | |
| Aug 30, 2019 at 11:06 | history | answered | Flater | CC BY-SA 4.0 |