But there should be some cross germination between you and your coders? You must have learned ways to make your spaghetti code less cumbersome for them and they probably have learned something about the underlying economics so that they know what it is you’re doing and how to keep everything to your needs. Similarly you’re not reinventing the wheel each time so you must be using tools developed by them more and more as time goes on?
Depending on your inclinations with regards to platform, I suggest you start with one of the following resources:
(1) For Mathematica (albeit very dated) I suggest _Simulating_Society_ by Gaylord & D’Andria (1998) http://www.wolfram.com/books/profile.cgi?id=3736
(2) For Python, I suggest you start with the github repository _Agent_Based_Complete_Economy_ available at https://github.com/AB-CE/abce
I am very much aware that my ‘programs’ are of the “big untidy spaghetti script” variety, and I simply consider them a kind of work-in-progress, notepad, or prototype for later professional implementation. I also have a couple of professional programmers (cough ahem, coders, they desire to be referred to as coders) that are entirely adept at taking my horrid final ‘thing’ and converting it into production-quality code that doesn't take down the enterprise (with the same tools I use, incidentally: Mathematica, Python (>3.3) including SymPy and NumPy, and ABAP/SQL/Java for interfacing with the SAP ERP system).
The important part of this is that I never be under any illusion that I something that I toss together and make capable of ‘running’ be definitive code that can be put into production or used as-is, and that under no circumstances must the coders have any bright ideas about fudging the underlying mathematics.