We got a manager on our project who is relatively new. This is the first release his is responsible for. As usual, we have had a heck of a time documenting good requirements for the release. The manager has stated that next time developers will be required to write the system level requirements.
Now that sounds good to me. Except developers are always busy. As the requirements gathering for the next round is taking place, we are busy designing, coding, and testing the previous release. Oh well. We will make it one way or another.
I was pleasantly surprised to find that Karl Wiegers has a lot of great advice on Writing Quality Requirements. If we get to the point where developers are writing system requirements in the future, I will have all the developers study his advice.
Mysterious Double Instance Hampering Performance - I study the existing code base. Confer with a colleague. Then I determine the optimal plan to change the functionality to load only a slice of all the dat...