Hi Ben,

Chapter 16 "I Don´t Understand the Code Well Enough to Change It". Michael C. Feathers proposes sketching to understand the code better. Moose allows it to automatize and improve this manual work. But before a sketch can be drawn the code has to be analyzed. And a sketch has to be adapted if the code changes.

Moose allows to automatize this. You can generate diagrams automatically. My impression is, that I still needed an application on top of Moose to make smaller diagrams that describe a certain aspect of a coding. I needed some way to limit the number of elements displayed, specify their positions and add comments to them. I do this currently in a Smalltalk application I developed on top of Moose and Roassal. It is NOT only for SAP applications as might seem. The Github Repository that links to the Smalltalkhub page: https://github.com/RainerWinkler/Moose-Diagram

I made a short video to show I am currently using Moose and this application to work with this kind of sketches. Even though it is an early version, I use it near to every day in my projects: https://drive.google.com/drive/folders/0B0BTdgDL6XSLeHB4aTZxTkdSNXc

Cheers,

Rainer

---

-----Original-Nachricht-----
Von: "Ben Coman" <btc@openinworld.com>
An: "Moose-related development" <moose-dev@list.inf.unibe.ch>
Datum: 02/14/17 13:16
Betreff: [Moose-dev] Book, Working Effectively with Legacy Code

Interesting to see this is the top mentioned book on stackoverflow.

I wonder if Moose can facilitate any of its contained topics

and maybe leverage its popularity.

</randomThoughForTheDay>

cheers -ben

---

_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev