I agree that creating a developer without comparing it to something else is pretty pointless. At best you find that it develops film. You really want to know more about what you did. Gadget goes too far in his conclusions. You don't need to test your new concoction against everything. You just need to compare it to something you know well, and preferably something that most everyone knows well. The developer you test against should obviously be for the same kind of work as the new developer. It makes no sense to try to compare a lith developer to D-76. PE is a bit too limited in his criteria, however. You may want to create a developer with special characteristics, and as long as it doesn't do unacceptable harm to grain, speed, or sharpness, you will be happy. Sandy King's Pyrocat-HD was created primarily to get a pyro type developer that was more stable toward aerial oxidation. It worked, and it had some added benefits as well, while retaining good grain and sharpness and not losing too much speed. Several of Gadget's developers have explored using low or no sulfite. Ron's Liquidol paper developer had long tray life as one of its design objectives. You still need to compare your new work to a standard to see if you have met your design objectives and not unacceptably degraded any of the Kodak criteria.
Ideally, a new developer should be designed like any other engineering work. First you develop objective specifications, next you design the developer against those specifications (which may take some well designed experimentation) and then you test the new developer against the specifications. Most of us in APUG approach new developers from the point of view of a curious hobbyist, however. We wonder what some formulation would do it you tried X; so we try it. That's fine. But in order to find out what you did, you still need something to compare it to. Memory is very faulty when it comes to testing. It's real easy, more informative, and more fun to run parallel tests against a standard.