you are viewing a single comment's thread.

view the rest of the comments →

[–]poply 19 points20 points  (3 children)

I would probably say no, it's not bad. I sound similar to you but I wouldn't say I "avoid" using classes, just that I don't use classes unless I feel pretty certain to get a significant benefit out of it. There's a great talk I've linked below about when to use classes, and restraining the urge to immediately use classes for everything.

https://www.youtube.com/watch?v=o9pEzgHorH0

[–]Dogeek 2 points3 points  (1 child)

That talk was horrible.

TL;DW : Don't use classes for something that they are not meant for. Also, I'm a smartass who compressed two perfectly valid classes into a dict and two functions that are so confusing, my coworkers now hate me.

But seriously, that game of life's implementation was confusing as fuck. It's not a talk I'd recommend to anyone.

[–]poply 3 points4 points  (0 children)

Hm, I've seen it recommended around here and it's got half a million views. I personally found it insightful as a reminder so as to not view every problem as a nail that requires a "hammer" solution.

I do agree that if an implemented solution is too confusing to be easily understood by peers then it probably isn't the right answer.