oredev

Object orientation idealises encapsulated state. Function programming idealises referential transparency. ~ @bodil #oredev

— Torbjörn Gyllebring (@drunkcod)2013-11-08 04:41:58

"If an object's state depends on other objects' state..." I see a clue in that phrase. /cc @bodil #Oredev 

— ☕ J. B. Rainsberger (@jbrains)2013-11-08 04:41:28

RT @drunkcod: The reason we introduce complexity is because we don't have the time to make it simple. ~ @bodil #oredev

— Narek Alaverdyan (@alaverdyan)2013-11-08 04:41:26

RT @cyriux: "Power to the programmers!" @fgeorge52 #oredev http://t.co/j6LKfqOy8S

— Philip Schwarz (@philip_schwarz)2013-11-08 04:41:16

Encapsulating state also encapsulate surprises. ~ @bodil #oredev

— Torbjörn Gyllebring (@drunkcod)2013-11-08 04:40:48

RT @drunkcod: The reason we introduce complexity is because we don't have the time to make it simple. ~ @bodil #oredev

— Noel Kelly (@gnoll110)2013-11-08 04:40:05

@drunkcod @bodil #oredev Even when we have the time, we often no longer have the energy.

— ☕ J. B. Rainsberger (@jbrains)2013-11-08 04:39:54

Java gives us countless ways to screw up our state. Perhaps a language that disallows that is a good thing. @bodil #oredev

— Torbjörn Gyllebring (@drunkcod)2013-11-08 04:39:50

RT @drunkcod: The reason we introduce complexity is because we don't have the time to make it simple. ~ @bodil #oredev

— ☕ J. B. Rainsberger (@jbrains)2013-11-08 04:39:20

The reason we introduce complexity is because we don't have the time to make it simple. ~ @bodil #oredev

— Torbjörn Gyllebring (@drunkcod)2013-11-08 04:39:04