The developers have spoken, and change has come to our code!
OK, so I’m a tad late. Last November, my department announced the next version of the design of our code. Actually, when I first started in July, my boss’s boss mentioned that this was coming down the pike, complete with an underground team hard at work, but I was skeptical.
The first is called “legacy.” I’m not really sure what the guiding principle was. The second, and current, is procedural SOA.
It sucks. It sucks, I say.
exportTo:exporter
”exports the internal state of the object”
exporter setRoomData:roomDS.
equipmentList do:
[:equipment|
equipment exportTo:exporter.
].
Why is there always something wrong with code? I can’t make one improvement without sacrificing something else.
I’m not talking about trades between coupling and performance, understandability and speed. Tackle one code smell and you’ve just introduced another, a sick game of Whack-A-Mole.
Code Agitator, elected to be the villain, certified a menace
