>tfw I don't understand OO design patterns
>>59673867
Dumb low-res frogposter.
>>59673867
That's okay you can still suck dicks
Can you?
>>59673867
OOP
>>59673908
>>59673867
please be more precise, we may be able to help you
>>59673867
>>tfw I don't understand OO design patterns
You really shouldn't bother.
Most "Design patterns" are just a way to get around the restrictions OOP places on you.
Want to check a variable? Either use an "if" or implement some obscure design pattern to get around the problem that getting objects to communicate with each other is a lot harder then it should be.
>>59674150
FOUND THE NEET!!
>>59674209
I am in university and actually """"learned""""" about design patterns in class.
>>59674244
yeah, ok and I'm Richard Stallman
>>59674578
?
Hi mister Stallman nice to see you here.
>>59673867
>I do not understand a computer model of real world interactions
nigga u dum
>>59674756
>>real world interactions
>>>>>>>>>>>>>>>>>real world
implying
>>59673867
Neither can my boss and he always gets angry when I try to implement them.
Don't worry about it.
>>59674774
barMan.order(Drink.ICE_TEA).pay(getMoney(1, Currency.EUR));
implying implications
>>59674812
That is not a design pattern.
That is syntax. (with questionable code quality)
You can do the exact same thing (a weird function call) in a functional or procedural language.
>>59673867
Start by reading the Greeks. OOP works very similiar to Plato's theory of Forms.
>tfw Observer design pattern
>Static observable everywhere ;)
>Global search is the only way I navigate around the project
>>59674150
>to get around the problem that getting objects to communicate with each other is a lot harder then it should be.
That's not true for every object oriented language -- just the shitty ones that don't support multiple value dispatch. CLOS, on the other hand, allows for tasteful object oriented programming.
>>59673867
You'd make the same face if you did understand them.