This business-oriented programming question is more of a question which I can not figure out how to solve. I work with a team of programmers who are working with Basic for more than 20 years. I was brought to help write the same software in NIT, only with updates and modern practices. The problem is that I can not get any of the other 3 team members (all the basic programmers, though still a .net), to understand how to do a relational database correctly. That's what they will not understand:
We are basically a transaction that keeps track of a customer's tag information. We should be able to track the current transactions and past transactions. In the old system, a flat file database was used in which there was a table in which the records were included with the customer's basic transaction, and another transaction which included important money information in all previous transactions of the customer. To prevent redundancy, they will overwrite the current transaction with history transactions - (the history file was previously updated, then currently). It is completely unnecessary because you only need one transaction table, but my supervisor or my two other co-workers can not understand this. In fact, can I accept them to see the light so that we do not have to perform ridiculous amounts of work and kill the statistics several times? Thank you for the input! First of all, I must admit that it is not clear from your statement that what is current data Structures and logic flows in structures are in fact. This indicates to me that perhaps you are not expressing your colleagues, therefore one should be able to understand one of your priorities, either verbal or preferably in writing and in the picture, current situation and proposed replacement please do it yourself Take the question as an observation instead of criticizing the question.
Second, I find it quite remarkable that programmers of over 20 years of experience can not understand relational databases and transactions. Flat file coding went long before the mainstream - I first held relational databases in a commercial setting in 1988 and they were very common until the mid-90s. What area and product type are you working on? It seems to me that you can deal with any kind of embedded or otherwise 'abnormal' system, in this case you need to ensure that you do not have some kind of communication problem and you are looking at the big elephant You have not been told - you will not be the first 'consultant' who is brought in a team that is not being fed properly. He said that such ancient shops are still present- one of my current client systems is the interface of a flat-file based system coded in Cobol, and yes, it is hell to manage - -)
You will not be the first signator, who had to apply the sub-optimal solution due to office politics - to handle such situations and express their thoughts about their own personal development Use it as a learning experience for 'payment for additional work will often get a conclusive argument in such arguments, but' reputation is of no use Jan 'you bring yourself to the table - it seems as if your team does not have such a big advantage with your team, then you