Post History
Sometimes you can write a lot without saying anything, sometimes you can say a lot but get little through the reader. In technical writing the later is very typical (at least for me), one can ten...
Question
technical-writing
#3: Attribution notice added
by
System
·
2019-12-08T02:22:06Z (almost 5 years ago)
Source: https://writers.stackexchange.com/q/5641 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
by
dukeofgaming
·
2019-12-08T02:22:06Z (almost 5 years ago)
Sometimes you can write a lot without saying anything, sometimes you can say a lot but get little through the reader. In technical writing the later is very typical (at least for me), one can tend to over-explain and get the adverse effects out of fear of under-explaining and making people feel dumb. What is a good rule to take something you've written down and make it shorter and sweeter without stripping technicality?. What criteria can one follow to condense/compress information and make it clearer at the same time? Edit: I'm currently writing a whitepaper, which mixes formal research with software engineering topics
#1: Imported from external source
by
System
·
2012-05-11T04:11:37Z (over 12 years ago)
Original score: 6