📖Glamorous Toolkit Live #4: Moldable analysis of Java systems

url
https://www.youtube.com/watch?v=PO0vBpigf7s
0:02:13

the primary idea why glamorous toolkit was started is that developers spend most of their time reading code

0:02:59

reading code is often implicit—nobody talks about it, so it is not optimized

0:04:04

software engineering as decision-making business, not constructing business

0:05:35

(re: code as database)

0:07:39

visualization of class (interface, attributes, links, etc)

0:23:15

constructing visualization of class usage

0:25:07

select sub-expression to examine it

0:36:03

(modern IDEs highlight unused classes and also detect groups of unused classes. this doesn’t cover the whole demonstration but it’s not that bad)

0:40:02

if “reading code” is implicit, you do just that—read. However, if you start looking into it, you’ll notice that there are very different specific activities that you’re doing. → Reading code is not a goal

0:42:32

after you have implemented the analysis, you can create a constraint and execute it automatically (e.g., in CI)

0:53:07

combining constraints into a report with statuses/etc.

1:13:14

gt toolkit seems to mostly use text files and views just enhance them

  • (this is similar to how Emacs/org-mode operate, although gt is much more powerful with visuals)

Backlinks