Data integrity is NOT optional -- except when it is
Pros
They can pay you well. For now.
Cons
That line, "Data integrity is NOT optional" is plastered on their job-ads, and on at least one wall within their offices. It sounds nice, along with a lot of other things that sound nice. And the reality is quite different. For a product that is well over 10 years old, it still suffers from the "duplicates" problem. Duplicate inventory, orders, products, you get the idea. That's the price for using AUTO INCREMENT. Split-brain, because they've decided to manage 500+ individual database-clusters, instead of opting for a much saner multi-tenant strategy. Expect a lot of unnecessary project complexity. High turnover has created an amnesiac organizational memory. Your job is to keep the machine running for the next quarter. My experience with Dan McCarty was extremely hostile. The moment I mentioned taking more advantage of SQL, I knew it was over. You can probably succeed here if a) you're new, and you don't have the experience to recognize a dumpster fire when you see one, b) you've seen your fair share of dumpster fires, and don't mind them. Everyone else with a modicum of self-respect, move along.
