You can't fix it if you can't find it, so we just have to be patient and stay working with Rakra They want their software to be perfect, but the reality is that problems get prioritized. They don't have infinite staff, so the amount of effort that goes into an individual problem has to be properly scaled and resources allocated correctly. Adobe has millions of customers and thousands of reports that they have to go through. I know this sounds negative toward development teams. The next phase is "We can't reproduce it" and they hope it goes away, but the customers keep complaining, and it finally gets some real engineering effort behind it. It takes the Program Owner (a role on the team) to schedule the work with the team. One or two reports of an issue is hardly worth chasing down, but when 10 people are complaining about it, now you have a potential problem. Then software development goes through a process where a bug is reported, it gets ignored because it's just not a high priority against other bugs and it takes time for those experiencing to report it. Each app has a database of settings that collects garbage over time and may need to be purged and you don't know exactly which change caused it. How much Photoshop/Bridge history garbage is in the registry (Windows term, Defaults on a Mac). There are a lot of variables involved like what plugins do you have installed. I've offered to load up test software to get them more information. They reached out asking questions and offered a screen-sharing session to see it. I've given them as much technical information as I can. They have to be able to reproduce the problem to fix it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |