Post History
If I'm understanding you correctly, I think what you want are case studies to demonstrate your points. So you put forth one of your arguments — "switching to the individual bucket version reduces ...
Answer
#4: Attribution notice removed
by
System
·
2019-12-13T12:00:09Z (about 5 years ago)
Source: https://writers.stackexchange.com/a/5754 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added
by
System
·
2019-12-08T02:23:43Z (about 5 years ago)
Source: https://writers.stackexchange.com/a/5754 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
If I'm understanding you correctly, I think what you want are _case studies_ to demonstrate your points. So you put forth one of your arguments — "switching to the individual bucket version reduces problems A, B, and C" — and then you put in a section with an actual real-life example: * * * **Case Study: Acme Widget Coders Amalgamated** AWCA had been using centralized bucketing for many years, but it was causing production bottlenecks whenever the buckets were all dumped into the same coding trough at the end of a widgeting session. Switching over to individual buckets was a huge boost to efficiency. Programmers had more flexibility, errors were caught much earlier in the process, and there were fewer holes in the buckets, dear Liza, dear Liza. * * * If you do this for each facet of your argument (or each problem which your trendy technique purports to solve), then your reader will see that you're not just lusting after the latest sparkly vampire of coding solutions, but rather presenting something which is useful and has been field-tested to produce significant results.
#1: Imported from external source
by
System
·
2012-05-24T21:43:01Z (over 12 years ago)
Original score: 10