Update README.md
This commit is contained in:
parent
7307eb1b06
commit
32b557b76c
20
README.md
20
README.md
|
@ -45,22 +45,22 @@ data is the very definition of success.
|
|||
|
||||
So, for debugging and understanding activities, more data, more easily is winning. Going back
|
||||
and adding a `println` shouldn't be necessary. All the data you need should already
|
||||
be captured and readily available in your REPL for further experimentation.
|
||||
be captured, and it should be readily available in your REPL for further experimentation.
|
||||
|
||||
### Data Brings Code To Life
|
||||
|
||||
Perhaps you have seen LightTable in action?
|
||||
Perhaps you have seen LightTable in action?
|
||||
|
||||
In the small, it is a delightfully productive debugging environment because it co-renders
|
||||
data and code. The "paper trail" provided by the data
|
||||
brings the code to life, revieling its dyanmics and enriching
|
||||
the programmer's understandings.
|
||||
code and the data generated by running the code. The data provides a "paper trail" which
|
||||
brings the code to life, revealing its dynamics and enriching
|
||||
a programmer's understanding.
|
||||
|
||||
`re-frame-trace` has a similar goal, although the method is different.
|
||||
|
||||
### It Is A Data Dashboard
|
||||
|
||||
Observing raw data trace is certaintly interesting and valuable, but it isn't enough.
|
||||
Observing raw data trace is both interesting and valuable, but it isn't enough.
|
||||
First, we want to leverage this data for insights. And, second, there's often too much data - you
|
||||
can drown in the detail.
|
||||
|
||||
|
@ -90,10 +90,10 @@ Four ways:
|
|||
4. It helps you to find performance problems and/or detect where there is
|
||||
unnecessary computation occurring.
|
||||
|
||||
Point 3, is primary. But Point 2 is almost as important because we all spend a
|
||||
lot of our time groking unfamiliar codebases. Actually observing the inner
|
||||
Point 3, is primary, of course. But Point 2 is almost as important because we all spend a
|
||||
lot of our time groking unfamiliar codebases. Being able to observe the inner
|
||||
workings of a running app is a great way to bring code to life, reveal key
|
||||
features, and map how the code is structured.
|
||||
features, and build a cognative map of how the code is structured.
|
||||
|
||||
### Temporary Warning
|
||||
|
||||
|
@ -103,7 +103,7 @@ features, and map how the code is structured.
|
|||
|
||||
We debated internally about the name `re-frame-trace`. While `-trace` is accurate, it is 100% sausage because it talks about low level function, and not higher level benefit (sizzle, sizzle). I wanted to call it `vox-datum` (voice of the data) but that was cruelly rejected, for reasons I don't care to remember. The pain. I mean, who the hell doesn't like a Latin name?? Philistines. Anyway, `-insight` and `-illumination` are the benefits, but they made the name waaaay too long. Naming things - it's just a nightmare! As is inertia. So, `-trace` it remains.
|
||||
|
||||
**Update:** a change to `re-frame-10x` is on the cards.
|
||||
**Update:** a change to the name `re-frame-10x` is on the cards.
|
||||
|
||||
## A Visual Sampler
|
||||
|
||||
|
|
Loading…
Reference in New Issue