mirror of
https://github.com/amyjko/cooperative-software-development
synced 2025-01-13 08:01:20 +01:00
Fixed typos.
This commit is contained in:
parent
621f94317f
commit
d7a8a2c408
1 changed files with 2 additions and 2 deletions
|
@ -48,8 +48,8 @@
|
|||
This theory argues that any designed system—software included—will reflect the communication structures involved in producing it.
|
||||
For example, think back to any course project where you divided the work into chunks and tried to combine them together into a final report at the end.
|
||||
The report and it's structure probably mirrored the fact that several distinct people worked on each section of the report, rather than sounding like a single coherent voice.
|
||||
The same things happens in software: if writing error messages for a website isn't talking to the team presenting them, you're probably going to get a lot of error messages that aren't so clear, may not fit on screen, and may not be phrased using the language of the rest of the site.
|
||||
On the other hand, if those two teams meet regularly to design the error mesages together, they might produce a seamless, coherent experience.
|
||||
The same things happen in software: if the team writing error messages for a website isn't talking to the team presenting them, you're probably going to get a lot of error messages that aren't so clear, may not fit on screen, and may not be phrased using the terminology of the rest of the site.
|
||||
On the other hand, if those two teams meet regularly to design the error mesages together, communicating their shared knowledge, they might produce a seamless, coherent experience.
|
||||
Not only does software follow this law when a project is created, they also follow this law as projects evolve over time <a href="#zhou">(Zhou & Mockus 2011)</a>.
|
||||
</p>
|
||||
|
||||
|
|
Loading…
Reference in a new issue