190

True story bro πŸ˜‚

Comments
  • 9
  • 1
    I have never had OOP go that badly.
  • 2
    You need a cat interface and then an animal interface:

    interface catInterface inherit animalInterface{
    [...]
    }
  • 1
    That's why I always have all my code in one class, no messy diagrams #blobMasterRace
  • 2
    #2 only if the developer is an incompetent monkey... I see it every day though unfortunatelyπŸ˜ πŸ˜’πŸ˜’πŸ˜ πŸ˜ πŸ˜ŸπŸ˜ŸπŸ˜±πŸ˜§πŸ˜§πŸ˜§πŸ˜¦πŸ˜¦πŸ˜¦πŸ˜–πŸ˜–πŸ˜–πŸ˜”πŸ˜”πŸ˜”πŸ˜“πŸ˜“πŸ˜“πŸ˜“πŸ˜«πŸ˜«πŸ˜«πŸ˜«πŸ˜’πŸ˜₯πŸ˜₯πŸ˜₯
  • 1
    Only when I'm super lazy... Ironically
  • 0
    This picture is true for the simple reason OOP Design patterns are prescribed to solve problems that could easily be solved with simple features like dictionaries, lists and functions.
Add Comment