Timeline for Small classes and methods, but code still difficult to maintain and follow

6 events

when toggle format	what		by	license	comment
Jun 15, 2016 at 7:49	comment	added	Benj		I meditated on your answer and got your point. You answer really helped. I ended up designing my new classes with self contained methods. For example, the CRUD method are cointained inside the "user" model class.
Jun 10, 2016 at 7:38	vote	accept	Benj
Jun 9, 2016 at 13:15	comment	added	Benj		So in this case, the entity would be the directory record. How would you design the actions around it ? For example, the creation action, the validation action. Would they be external to the entity class, isolated, functions for example ? Or classes on their own (in this case these 2 classes would not represent an entity... more an 'action') ?
Jun 9, 2016 at 12:03	comment	added	gbjbaanb		not necessarily, but you should be thinking in terms of making the entity self-contained, so you can think of making the entity and operating on it in much simpler terms, like creating it is one action, validating it another and so on.
Jun 9, 2016 at 11:59	comment	added	Benj		Thanks for your answer. Sequence diagram would be a great help, never thought about it. So in my case, in the 'post' method, instead of having calls to various classes and functions, I should regroup these calls into a single class "CreateEntry" that would be responsible for the entire process, but that will still make the various calls to the utilities here and there ?
Jun 9, 2016 at 11:00	history	answered	gbjbaanb	CC BY-SA 3.0