368 further condensation (#379)

* drop more details that are better kept in long paper

* drop reference

* drop example to reduce number of ref

* drop sentence, since we removed some of the dimensions for the summary paper

* I don't think you can identify with a domain, role is probably what we want to express

* drop paragraph, all this is in XXL paper

* be assertive

* Abstract: Mention that this is a summary of a more extensive publication

* Make time absolute (and paper timeless)

* Biography: Use English form of GI name

* Adapt references to full paper given we kept the specializations in

* Terminology: Swap the order of two sentences

I created the condensed version and I realized that the order was problematic and sounded more defensive than in the original text.

* MOD: Minor language fix

* Introduction: Explain why we duplicate

---------

Co-authored-by: Florian Goth <[email protected]>
Co-authored-by: Gerasimos Chourdakis <[email protected]>

competencies.md

@@ -618,7 +618,7 @@ differentiate them from the domain repositories described later.
 
 We define this as a certain quality of analytical thinking that enables an RSE to
 form a mental model of a piece of software in a specific environment (program comprehension).
-Using that, an RSE should be able to make predictions about a software's behaviour.
+Using that, an RSE should be able to make predictions about the behaviour of a program.
 This is a required skill for common tasks such as debugging, profiling, optimising, designing good
 tests, or predicting user interaction.
 Many tools exist to help with understanding and evaluating existing code,