27

Working on a project with 2 other students. One of them makes a C# "super class" with 50 fields, and manually creates getters and setters for each and every one. Then he proceeds to write a constructor that accepts 50 parameters, because why not.
I comment on the git commit, telling him that he can just write " get; set; " in C# and that he should model the problem in smaller, more manageable classes ( this class had 270 lines and did everything from displaying data to calculating stuff). Tried to explain to him that OOP works kind of differently from how he did it.
....
His answer: "Yeah, I don't really care. If it works once, it's okay for me".
This after the most beautiful code review I have ever done...

Fml

Comments
  • 1
    I feel that feel
  • 3
    Wow 😂 50 parameters constructor
    Btw, thumbs up to you for not giving up just because "it's a school project"
  • 3
    Now imagine you work with them.
  • 0
    I'd slap that man round his face... Then deck him if he attacked me... After I hit him with the screen filled with his code.

    Anyway going to get on with my day.
  • 2
    Look on the bright side,at least he made it.
  • 0
    @rokxer funny reading that. Because not only I imagine working with people like that, I did. For two bleeding years.
  • 0
    Are u rally allowed to stuff 50 parameters into a constructor?Compiler really accepts that kind of s***??
  • 0
    It's like storing all the data for your app in one table - anyone remember Lotus Notes?
Add Comment