Do you know, like you see the same history again and again. Maybe worst that a bad code, is a bad comment, and nobody pick the code to change because "it is working", see that "modern applications" are an entire package. The constraints about the Domain are spread around "the code and the database". Always i look such codes, and wondered like, if someone once in a time have worked with Desktop apps without DB, or a DB without a Front End, and conclude "what is what.". My opinion the thing could be simple. Domain holds constraints, like uniqueness, normalization, integral reference. Which means "simple set rules". Application holds "usability", like how to apply usage over a domain.
Is it complicated understand that ? Also a Domain holds a specific vocabulary, most weird that could be. Just this is a lot of work, and usability at other side is a lot of work too. But are distinct assumptions, if you put ~domain constraints in the usability code~ this points to defects in your Database Domain, which could point to erroneous data. If you put Usability in your Domain Side you will restrict the architecture and probably generate a giant contention in your database. But the comments are the best.
Today I saw one like 'SELECT Before Update" but was performing a Delete before a Insert, such things are called "Electrical Comedy" and inside a Request (remembering that is 'one thread per request') a class extending a thread with the excuse that "will create a thread to enhance performance" (the comment). All of this is business intelligence, to be more precise "competitive intelligence".
And the talks like, diverting what i was trying to ask, simple questions about the domain, just to make sure that "let me see how they will try to solve the problem". As usual everybody trust on the shortest path, you go to where you see how you do on application to make sure that you are going on the right direction without look the domain, the flaws on the queries, like every time that i look a "distinct" where should not have a distinct i see problems on the domain, and always someone have the "veteran answer". I saw such histories at least 4 times on my life. Several persons became addicted in an application, thinking that have understood the process.
It is the demotivational phase, the individuals that made such comments and the model probably today are managers, so let the code as is hum? What really matters is the paycheck.
