Construct · 1 fields · 1 citations

developer information sources and code security: a standalone construct

One name. One construct. A landmark on the map.

● anchor · a standalone construct Nearest construct by meaning·not indexed
developer informationsources and code security1 CONSTRUCTDeveloper informationACAR · SOFTWARE ENGINEERING

A single standalone construct; nearby constructs are located against it in the Collider. Tap a field for its definition, unit, and measures.

Software engineering

the finding that developers who use informal sources like Stack Overflow write less secure code, though more functional code, than those using official documentation.

In software engineering, developer information sources and code security refers to the finding that developers who use informal sources like Stack Overflow write less secure code, though more functional code, than those using official documentation. This meaning comes from Acar (2016) in 2016 IEEE Symposium on Security and Privacy (SP).[1]

Unit
Recovery means
Measured by

Next

Run it through the Collider, or take the citations with you.

See how developer information sources and code security sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in ColliderExport BibTeXReport this entry

Nearby constructs

code3 fields · 6 citationsjingle · one word, three constructsdeveloper1 fields · 1 citationsanchor · a standalone constructinformation4 fields · 5 citationsjingle · one word, four constructs

References

  1. Acar, Y., Backes, M., Fahl, S., Kim, D., Mazurek, M. L., & Stransky, C. (2016). You Get Where You're Looking for: The Impact of Information Sources on Code Security. 2016 IEEE Symposium on Security and Privacy (SP). https://doi.org/10.1109/sp.2016.25

Cited on this page?

Confirm your construct, or correct us.

If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.

Claim your construct