Slutty Types

23 commentsWritten on October 11th, 2009 by
Categories: Software Development

Slutty Types are types which:

  • give you access to their privates without too many difficulties
  • don't really care about your intentions, or if they do, aren't very clear on that
  • occasionally seem like a good short-term fix
  • can be used in a variety of ways, with different outcomes and none of them are guaranteed
  • can not to be trusted
  • really need to be tested
  • will burn you sooner or later if you're not careful
  • become even more of a mess during the aging process

Feel free to add to the list :)

« Event AggregationBuild Your Own Data Access Layer: Enabling Bulk Inserts »

This entry was posted on Sunday, October 11th, 2009 at 19:57 and is filed under Software Development. You can subscribe to any comments to this entry via RSS 2.0. You can leave a response, or trackback from your own site.

  • http://jclaes.blogspot.com Jef Claes

    The first one is great!

  • Me

    isn’t concerned about whether members are protected or not

  • http://www.codebucket.org Lee Brandt

    When you DO use them you feel guilty and a little paranoid about health issues afterward

  • Danny

    At least a slutty type will make your member function.

  • http://davybrion.com Davy Brion

    @Danny

    only in the short term ;)

  • Ryan Roberts

    In before you get accused of being the reason there are so few women in the profession.

    They are likely to be involved simultaneously in many concerns
    They may well have confusing multi part names

  • http://blogs.msdn.com/brada Brad Abrams

    I love it.. gotta put this in the next Framework Design Guidelines!

  • kilfour

    Look cheap at first, but end up costing you a lot of money.

  • http://jack-fx.com/net/ Jack

    I’m a starter to Slutty Types, hope to known more about it.

  • http://dotnet.org.za/trumpi Trumpi

    n. Gets mocked a lot by friend assemblies??

  • http://www.kivela.be Stefan V

    Tend to create a code smell

  • http://benpittoors.wordpress.com den Ben

    when they expose something interesting, it is definitely some type of string

  • http://blogs.infosupport.com/blogs/willemm W.Meints

    Slutty types never seem to demand any permission before using them.

  • http://robbie.robnrob.com/ Robbie Coleman

    if not properly sealed, they are bound to pass on problems to all inheritors

  • Gaurav Patel

    Slutty Types almost always have an open interface and prefer multiple inheritance.

  • noah

    slutty types are sometimes referred to as ‘loose’

    you don’t want to find yourself checking out a slutty type

    slutty types have a hard time looking at their own reflection (ehh…)

  • http://davybrion.com Davy Brion

    slutty types have a different view on what ‘class’ means

  • http://kilfour.wordpress.com/ kilfour

    Slutty Types hide their real intentions.

  • Tim

    Are thread safe… can handle multiple users simultaneously

  • http://kilfour.wordpress.com/ kilfour

    @Tim
    Slutty types aren’t thread safe. They handle multiple users, but tend to avoid any kind of protection.

  • http://davybrion.com Davy Brion

    hehe… they deal with multiple consumers without proper locking!

  • Gibbo

    Are normally flat and often expose only simple types.

  • http://davybrion.com Davy Brion

    oh i’ve seen some well rounded ones that made you deal with quite a few complex structures ;)

Meta

Recent Posts

Categories