Re: [Pharo-dev] new year resolution
On Jan 1, 2014, at 4:28 PM, Stéphane Ducasse wrote: >> >> Ok, but let's get concrete. What does better mean in this case? >> >> I think we could all learn from each other's examples. > > Relations/Collaborations with other classes > Invariant internal representations for real (description of implementation) > + examples. > > Stef This made me remember this book pattern: http://www.amazon.com/Design-Patterns-Elements-Reusable-Object-Oriented/dp/0201633612 I mean, the book is about patterns but it has a beautiful editorial pattern itself for a reference book. For every pattern it defines: 1. Intent 2. Motivation 3. Applicability 4. Sample Code 5. Known Uses Let's say that doing that for every class is too much, then what about: 1. intent 2. applicability and or known uses 3. sample code (very optional) sebastian o/
Re: [Pharo-dev] new year resolution
> Ok, but let's get concrete. What does better mean in this case? > > I think we could all learn from each other's examples. Relations/Collaborations with other classes Invariant internal representations for real (description of implementation) + examples. Stef > > Doru > > > On Wed, Jan 1, 2014 at 6:55 PM, Stéphane Ducasse > wrote: > Hi guys > > I’m fighting to get the old browser working so that I can continue to work on > the reloading of configurations of tools. > Now we should really stop to write comments like that for new classes > > ClassOrganization > This object is in charge of system notifications. > It manages the class comment, the class comment stamp and a protocol > organizer > > For example I have to reverse engineer the invariant (if any) because I > should see how to find a way to implement > numberOfCategoryOfElement: element > which was based on the old index behavior. > > Seriously we should do better. > > Stef > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"
Re: [Pharo-dev] new year resolution
Ok, but let's get concrete. What does better mean in this case? I think we could all learn from each other's examples. Doru On Wed, Jan 1, 2014 at 6:55 PM, Stéphane Ducasse wrote: > Hi guys > > I’m fighting to get the old browser working so that I can continue to work > on the reloading of configurations of tools. > Now we should really stop to write comments like that for new classes > > ClassOrganization > This object is in charge of system notifications. > It manages the class comment, the class comment stamp and a > protocol organizer > > For example I have to reverse engineer the invariant (if any) because I > should see how to find a way to implement > numberOfCategoryOfElement: element > which was based on the old index behavior. > > Seriously we should do better. > > Stef > -- www.tudorgirba.com "Every thing has its own flow"
[Pharo-dev] new year resolution
Hi guys I’m fighting to get the old browser working so that I can continue to work on the reloading of configurations of tools. Now we should really stop to write comments like that for new classes ClassOrganization This object is in charge of system notifications. It manages the class comment, the class comment stamp and a protocol organizer For example I have to reverse engineer the invariant (if any) because I should see how to find a way to implement numberOfCategoryOfElement: element which was based on the old index behavior. Seriously we should do better. Stef
