Monday, September 21, 2009

big ball of ud

the current system i'm working display some signs of a big ball of mud. there are parts that are well done but there are others that do not work well.

one the big biggest forces that lead to the ball is the company attitude. the company doesn't really put a high value on documentation. its hard to tell sometimes what the intent of a class is. i've had to guess more then once and hope i was right.

time has been another big force in creating the ball. there were more then a few 15 hour days trying to get things done. once a developer becomes overworked bad choice start happening more and more.

the skill of the developers was also a force. i feel this could have been counter somewhat by having more code and peer reviews.

changing requirement was another driving force. major requirement have been changed a week or so before deadline. you try to build in flexibility into the architecture as you can but there is only so much that can be done some times.

No comments:

Post a Comment