Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The C# tooling is very refactor-friendly. I commonly just build the class then pull out the interface later.

C# does want to have interfaces though, and gravitates to the common interfaces - core services - composition/DI root architecture, with lots of projects in the solution to provide separation of concerns. I think it works very well generally for business software at least, but I hear plenty of grumbling about 'complexity' so it's not for everyone.



Just a small advertisement: have a look at automatic interface written by me. It builds your interface automatically from your class.


I like the tooling but this doesn't change that the language has a major case of OOP-brain


Maybe in how it's taught, but in practice deep inheritance and mutable state is easily avoided and best practice is more for a more procedural style


Is there a good example of an open source code base written like this?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: