Post History
In the IT industry, we often write a lot of technical documentation meant for internal use only. Those documents are often stored in an internal wiki and accessed when the need arises. The conten...
#4: Attribution notice removed
by
System
·
2019-12-13T11:56:50Z (almost 5 years ago)
Source: https://writers.stackexchange.com/q/43557 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-08T11:21:43Z (almost 5 years ago)
Source: https://writers.stackexchange.com/q/43557 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
In the IT industry, we often write a lot of technical documentation meant for internal use only. Those documents are often stored in an internal wiki and accessed when the need arises. The content of the documents is not relevant here; the only relevant fact is that in the IT field you are not supposed to [_reinvent the wheel_](https://en.wikipedia.org/wiki/Reinventing_the_wheel). When writing a piece of code, or documenting a procedure, you are in fact supposed to search on Google (or SE sites, nonetheless) for others having faced a similar situation. So, when it comes down to actually documenting what you have done, ## What is the best way to cite external references? I often include a small list section with links at the end (or at the start) of the page, but I'm not sure it is the best method. Keep in mind that internal documentation is not supposed to be read, ever, by customers. It usually stays private between colleagues.
#1: Imported from external source
by
System
·
2019-03-15T11:26:16Z (over 5 years ago)
Original score: 7