diff options
| author | Katharina Fey <kookie@spacekookie.de> | 2019-01-21 14:19:50 +0100 |
|---|---|---|
| committer | Katharina Fey <kookie@spacekookie.de> | 2019-01-21 14:19:50 +0100 |
| commit | 1ce9d9d8997254613650c31db7b70722f336aa28 (patch) | |
| tree | df2c3052d47645854c8894b5322c3dcbde1adf47 | |
| parent | 83085252205f744147edea2d15449c3d3f08fd45 (diff) | |
Final final changes
| -rw-r--r-- | content/blog/103_rust_2019.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/content/blog/103_rust_2019.md b/content/blog/103_rust_2019.md index 3e3a3d3..02345d4 100644 --- a/content/blog/103_rust_2019.md +++ b/content/blog/103_rust_2019.md @@ -68,13 +68,13 @@ Like hitting a moving target. To some extent this is how most software development works, unless you are working towards a *very* well defined spec! -Having the same team be in charge of both the overall +Having the same group of people be in charge of both the overall vision for a system and it's implementation isn't a bad thing, *given that the system is small enough!* -This is where teams come in! -Splitting up the community into groups of people who work on the same stuff, -in smaller numbers, so that collaboration on this scale becomes possible again. +And this is where teams come in! +Splitting up the community into smaller groups who work on the same stuff, +so that this kind of collaboration becomes possible again. In a way, the Rust 2018 working groups were inspired by the same idea. The difference between teams and working groups being, |