3 ms·

This sounds like a management problem more than a technical problem. Requirements need to settle down a bit so that you can get some work done. A schemaless app

This sounds like a management problem more than a technical problem. Requirements need to settle down a bit so that you can get some work done. A schemaless approach does make schema changes easier, but woe is you if you have data in your database from several different versions of the schema. I don't see how you can make any guarantees about query correctness in such a situation. I.e., your business reports will be buggy. Not to mention, hard to write without SQL. I don't buy your statement that "a lot of the data the business wants presented would be hard to store in a normalised format", at least not without some justification. Also, data to be presented may be structured differently from data as stored. Forget the presentation, is there any reason why the data model itself isn't normalizable? (Not talking about tweaks to the model due to changing requirements. Pick some version -- is that normalizable?)

mothsonasloth 8y ago
It is a management problem. I have been pushing back since I joined the team but the problem is that there's so many execs and people screaming for this app to be released. As senior developer on the team I am having to fight bad software practices and "just ship it " mentality. In a way I am panicked because I don't know what the product owners want and they in turn dont know what the business want. Therefore I am trying to engineer against management's incompetence and I don't see that being fixed anytime soon.
- geophile 8y ago
  The top-level manager on the engineering side needs to be pushing back, saying "Guys, this isn't going to ship if the requirements keep changing." If he isn't doing that, you are in a tough spot. It sucks to work on such a project, and it sucks to go over his head, especially if you are junior. Maybe talk to the senior engineers about the problem?

mothsonasloth 8y ago

It is a management problem. I have been pushing back since I joined the team but the problem is that there's so many execs and people screaming for this app to be released. As senior developer on the team I am having to fight bad software practices and "just ship it " mentality. In a way I am panicked because I don't know what the product owners want and they in turn dont know what the business want. Therefore I am trying to engineer against management's incompetence and I don't see that being fixed anytime soon.

geophile 8y ago
The top-level manager on the engineering side needs to be pushing back, saying "Guys, this isn't going to ship if the requirements keep changing." If he isn't doing that, you are in a tough spot. It sucks to work on such a project, and it sucks to go over his head, especially if you are junior. Maybe talk to the senior engineers about the problem?