Saw one of those in a vb.net shop. It went that way: - someone creates a function to do something on a business concept that was not materialized by a class. T

Saw one of those in a vb.net shop. It went that way: - someone creates a function to do something on a business concept that was not materialized by a class. Think of a bunch (~ 8) of properties that belong together but for some bad reason are moved in separate variables all over the place - another function has to work on a set of those objects. The dev who implements it thinks it would be a good idea to keep all parameters separate. No we have nproperties * nobjects parameters. The dev use a rigorous naming convention for readability (creatorFirstName, creatorLastName, validatorFirstName, etc) - now we have multiple sets (creatorFirstName1, 2, 3 ...) I don't remember the details but there was around three hundred parameters. edit: formatting