whalespine.org

Domain knowledge is just nomenclature. When it gets right down to it, we are all just pushing data around. That is it. It doesn’t matter whether we are talking “cementing”, “well bores”, “acidizing”, “twin pumper” or “call disposition”, “voicemail”, “CFNA”, “CFB”, “line provisioning”. The data goes in a database. The program gets the data out, responds to events and puts the data back in (though not necessarily in that order). The main reason for domain knowledge is so the techies can talk to the non-techies intelligently which I’ll agree is a valuable ability. But when it comes to developing the program, we should be striving to abstract away the domain knowledge because it really shouldn’t have an impact on our design and coding decisions.