Skip to content

Commit

Permalink
split normative from informative concerning the spec-up improvement t…
Browse files Browse the repository at this point in the history
…ool - content editted

Signed-off-by: henkvancann <[email protected]>
  • Loading branch information
henkvancann committed Mar 18, 2024
1 parent e278b0d commit 37cbabd
Show file tree
Hide file tree
Showing 3 changed files with 153 additions and 116 deletions.
8 changes: 2 additions & 6 deletions spec/design.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,10 @@
## Terminology design aids

“Why do we need to design terminology? Can’t we simply write our ideas down, look up some definitions and add them, or search for some explanatory texts if clear definitions lack in the heat of the writing process?"

"We don’t have a problem, do we? Why all the fuzz and juggling all these terms and definitions about terms and definitions? It’s not getting better, is it?

"Please let me just write my document and add some glossary items and we’re done. We skip all the academic hassle about *meaning, concepts, artefacts* and what have we. Let’s get work done!”
"Please let me just write my document and add some glossary items and we’re done. We skip all the academic hassle about *meaning, concepts, artefacts* and what have we. Let’s get some work done!”

### Do not proceed if...

Cliff hanger! First, do you recognize a few of the emotional remarks above (under "Terminology design aids")?
Cliff hanger! First, do you recognize the emotional remarks above (under "Terminology design aids")?

Why can't we give in? Simply skip the nerdy stuff? The reason is devastatingly basic:

Expand Down
Loading

0 comments on commit 37cbabd

Please sign in to comment.