2/ That's not to knock software engineering as a field. It's extremely useful to identify and understand patterns so that you can understand the design of software better! But, it makes very little sense when reporting on the implementation of an ABM.
1/ A brief rant: There are way too many people in computational social science (or computational X) who incessantly cite the literature on software engineering as defense of their god awful fucking code.
-
-
Show this thread
-
3/ In fact, (imo), doing so reliably signals an artifact-riddled ABM. It's formalism as a diversion from code that smells.
Show this thread -
4/ ...and, it's usually written by someone who *didn't* do most of the coding -- the person I'm least interested in hearing from when the concern is: "how does this model work?"
Show this thread -
Show this thread
-
PPS: If you're starting out in a computational field and think you're a weak programmer, skip the GangOfFour-style books and *use* things like
@PragmaticAndy &@pragdave's The Pragmatic Programmer. - Pick a rule; - Use it while writing code; - Repeat.https://www.amazon.com/Pragmatic-Programmer-Journeyman-Master/dp/020161622X …Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.