In secure programming (synonym: defensive programming), the goal is to ensure continuing function of software despite any and all unforeseen use(s). This may be viewed as reducing or eliminating the prospect of Murphy's Law working. It is most valuable when software can be misused accidently or intentionally, to catastrophic effect.
Nothing is assumed: all error states are accounted for and handled. Programmers never assume a given function call or library will work as promised, and so handle it in the code. In contrast, in normal programming practices, many such assumptions are made.
More information
Related categories 2
Sites 3
Growing article, with links to many related topics. [Wikipedia]
Tracking need-to-know trends, focusing on AI/ML, Innovation & Disruption, Future of the Firm, and Next architecture and economy.
Design and implementation guidelines for writing secure programs for POSIX operating systems.
Tracking need-to-know trends, focusing on AI/ML, Innovation & Disruption, Future of the Firm, and Next architecture and economy.
Design and implementation guidelines for writing secure programs for POSIX operating systems.
Growing article, with links to many related topics. [Wikipedia]

Category editor:
keatscrawford
Last update:
August 5, 2021 at 13:00:28 UTC

Check out
Regional: North America: United States: Nebraska: Localities: O: Omaha: Business and Economy: Home and Garden
- Recently edited by cherel
- Recently edited by cherel