How Do You Even Write Secure Code Anyways
summary
Shows why NASA’s Curiosity team spent about $3.2 billion and wrote 2.5 million lines of C to get reliability, then gives concrete rules that map to Solidity: static analysis with zero warnings, no recursion, tight scopes, validate every parameter, small functions and <60-line limits. Recommends clear names, early exits, delete dead code; test strategy with positive/negative/unit/integration and active tests on mainnet forks; prioritize helpers as load‑bearing and use taint analysis of sources and sinks to find exploitable paths.
AI-written summary · about
chapters (6)
- 0:00Introduction to secure code
- 0:39JPL coding standards
- 2:41Writing cleaner code
- 6:34Effective testing strategies
- 13:31Securing helper functions
- 15:37Taint analysis and conclusion
related talks
22mWriting safe and secure code
31mNeed of Web 3.0 Security
01h 02mSo long secure coding... Hello secure development!
52mSo Long Secure Coding - Practical Steps for Securing the entire SDLC
45mShifting from Syntax to Secure Software Development Processes
23mSecure Code, Safe Future: Mastering Security in Critical Software Development
58mIncoherent Code: How Code Quality Impacts Security
56mSo Long Secure Coding - Practical Steps for Securing the entire SDLC