Zaslon
Posts: 283
Joined: 6/14/2015
Status: offline
|
quote:
ORIGINAL: apache85
Hey Zaslon,
Do you mean this post?
If so a large part of the reason why it's not been completed is the formatting and lack of detail. Database updates already take a long time to actually do, and that's when all the information is laid out for us. When requests are basically 'this is wrong, go read a webpage I linked to see what needs doing' it can massively increase the amount of time it takes to figure out what needs to be changed and then go and do it. When I see a ticket like that the first thing I think is 'this is going to take me an hour to figure out what this person actually wants' which is quickly followed by 'my time could probably be better spent on a different ticket'.
This post and this post are both examples of excellent formatting and detail--as such the tickets assigned to both have already been completed. The information is laid out in a logical manner, and references are included as actual references, not just 'go read this' links.
This thread, on average, generates literally dozens of hours of development work every day. If you really want something, putting some effort into making it easy for us to do drastically increases the chances of it happening. Complaining that your request hasn't been done and taking shots at us for doing other stuff in the mean time doesn't really have the same effect.
Thanks for the reply.
It was not the first time I compile information to be added in the Database, it was just the first time that it takes 2 years to have an answer.
I was not complaining about my request. I was complaining about the fact that an important fighter, MiG-29 is poorly represented in DB3K for years. I tried to change it and it took 2 years to have an answer to fix the problem with my request. If you think that a request lack detail or has a poor formatting, just write it when you read it. Ignore the post is a poor customer care, a customer who is making you a favor already!
You must understand that I compile information in my free time. Sometines I have more time, sometimes I do not have enought time )(sadly we only have 24 hours per day). So When you do not have enough time. You compile some information and show the right direction for the rest.
I do not want something, you need something and we are trying to help you to keep up to date your Database. It is a huge task, I know and you cannot take all the suggestions we bring to you. But again, we are not talking about an A-12 Avenger (which it is in the database already) we are talking about an important Soviet Fighter with more than 1,500 built and new versions are in development. You must have some criteria in order to priorize suggestions IMHO. Of course, fix MiG-29 entries is a huge task, because there are a lot of entries and versions.
So, don´t be paranoid (I forgot about the Soviet paranoid which reigns in this forums.  ), nobody is shooting at you. Do not be afraid to ask if you do not understand what the people suggest.
I have a copy of this book. Do you think that is enough as a reference? If yes, then, we can fix MiG-29 entries in DB3K.
_____________________________
 Kids think about Iran and Amateurs think about Russia, but professionals think about China
|
Printable Version
RE: Thread for DB3000 database problems, updates or issues - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread