While using a Python program to query SO’s API helps me gain a better understanding of SO’s software source code, I should note that much uncertainty regarding SO’s programmed arguments still abounds. Part of this uncertainty is a result of limits companies like SO place on programmers who wish to access their data, but a large portion also stems from my choice to use Python. 2021, Sean McCullough, “Reprogramming Rhetoric: Toward a Diffractive Epistemology of Computer Composition”, in Kai Merten, editor, Diffractive Reading: New Materialism, Theory, Critique, Lanham, Md.: Rowman & Littlefield, →ISBN, part III (Diffracting (in) Music, Visual, and Digital Media), page 302:
Imagine that you were creating an application similar to SO but were writing it using web forms. 2010, Alex Mackey, “ASP.NET MVC”, in Introducing .NET 4.0: With Visual Studio 2010 (The Expert’s Voice in .NET), [Berkeley, Calif.]: Apress, →ISBN, page 290:
SO threads are mapped back into QuestionSheets. Information collected from SO includes the answer itself, the contributor’s reputation, and the number of votes (if any) (see Fig. 5). 2018, Oscar Díaz, Jeremías P. Contell, “Educating Users to Formulate Questions in Q&A Platforms: A Scaffold for Google Sheets”, in John Krogstie, Hajo A. Reijers, editors, Advanced Information Systems Engineering: 30th International Conference, CAiSE 2018, Tallinn, Estonia, June 11–15, 2018, Proceedings (Lecture Notes in Computer Science; 10816), Cham: Springer, →ISBN, →ISSN, page 163: