5

We are in fucking 2020 and I'm still forced to put prefixes like in 2005

'I' before interface name
'Abstract' before the abstract class name

Comments
  • 6
    This has nothing to do with 2005, this is just very good to organize your code
  • 1
    @Sumafu this has a lot of common (2005)
    as IDE were poor people has started to add prefixes to know what is a particular import.

    Right now IDE's are powerful enough to tell you that you something is an interface.
  • 7
    Well since 2005 humans haven't gotten any smarter, so it's a good way for humans to read and understand that it's an interface that or an abstract class
  • 0
    The only one I do is the "I" prefix in c#. And only because it looks weird if you don't.

    Interesting story behind why .net is like that though. It comes from C++ where interfaces are a convention rather than a language construct. C++ has multiple inheritance but it's considered bad practice to actually use it without constraints. Only one parent should have actual implementations. Everything else should be an abstract class with only definitions i.e. an interface. So broadcasting at a glance that a particular abstract class is an interface is important, hence "I".

    I still hate doing it but I feel a bit better given that I understand why it's like that
  • 1
    I think that convention is good. Don't try to be edgy just because
Add Comment