https://flow.halvo.me/tags/summation/ Recent content in Summation on Flow With Halvo Hugo en Tue, 05 Mar 2024 00:00:00 +0000 https://flow.halvo.me/posts/code-complete-summations-pre-requisites-part-3-initial-design/ Tue, 05 Mar 2024 00:00:00 +0000 https://flow.halvo.me/posts/code-complete-summations-pre-requisites-part-3-initial-design/ A breezy look at the nitty‑gritty of resource and error management—databases, threading, file handles, and error‑handling philosophies. It’s the “don’t forget to tighten the bolts” chapter, reminding us that unmanaged resources and sloppy error handling are the secret doors that attackers love to sneak through. https://flow.halvo.me/posts/code-complete-summations-variable-usage/ Fri, 23 Feb 2024 00:00:00 +0000 https://flow.halvo.me/posts/code-complete-summations-variable-usage/ A breezy look at why good variable names, sensible placement, proper initialization, and single‑purpose usage aren’t just tidy coding habits—they’re tiny security shields. Clear names like <code>sanitizedUserInput</code> keep bugs (and attackers) from slipping through the cracks, while keeping variables close to their use and initialized from the get‑go reduces the chance of leaks, memory mishaps, and confusing code. https://flow.halvo.me/posts/code-complete-summations-pre-requisites-part-2-initial-design/ Tue, 26 Dec 2023 00:00:00 +0000 https://flow.halvo.me/posts/code-complete-summations-pre-requisites-part-2-initial-design/ A light‑hearted deep‑dive into architectural prerequisites—communication, class skeletons, data design, UI separation, and error/log handling. Think of it as laying a solid blueprint before the code construction crew arrives, because a wobbly foundation makes for a lot of late‑night debugging (and security headaches). https://flow.halvo.me/posts/code-complete-summations-pre-requisites-part-1-initial-design/ Wed, 20 Dec 2023 00:00:00 +0000 https://flow.halvo.me/posts/code-complete-summations-pre-requisites-part-1-initial-design/ A breezy, slightly tongue‑in‑cheek look at why solid planning isn’t just good housekeeping—it’s a frontline defense. We walk through OWASP’s Insecure Design warning, compare personal versus mission‑critical projects, and tease out iterative vs. sequential approaches, all with a sprinkle of humor to keep the security talk from feeling like a lecture. https://flow.halvo.me/posts/code-complete-summations-metaphors/ Mon, 13 Nov 2023 00:00:00 +0000 https://flow.halvo.me/posts/code-complete-summations-metaphors/ A light‑hearted look at Steve McConnell’s “Code Complete” metaphors—Penmanship, Farming, and Oyster Farming—and how each style can make your code more or less secure. Think of Penmanship as scribbling a quick note (great for tiny scripts, terrible for big projects), Farming as planting seeds with a bit of watering (testing each piece, but still lacking a master plan), and Oyster Farming as building a sturdy oyster bed (design first, then grow securely). Spoiler: the oyster wins the security contest. https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-file-io/ Thu, 29 Jun 2023 00:00:00 +0000 https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-file-io/ A breezy guide to keeping file operations safe: validate paths, lock down permissions, and never let a privileged process wander into a user’s temp folder. https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-concurrency/ Fri, 27 Jan 2023 00:00:00 +0000 https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-concurrency/ A light‑hearted rant about why a plain‑old <code>mutex</code> is the hero of secure C/C++ concurrency, why <code>goto</code> is still secretly useful, and how to keep your locks short and your bugs shorter. https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-set-to-null-after-free/ Wed, 17 Aug 2022 00:00:00 +0000 https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-set-to-null-after-free/ A breezy, slightly tongue‑in‑cheek look at why setting pointers to <code>NULL</code> right after <code>free</code> (and a few related memory‑management niceties) can save you from nasty use‑after‑free bugs, memory leaks, and the occasional midnight debugging panic. https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-always-null-terminate-part-2/ Sat, 13 Aug 2022 00:00:00 +0000 https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-always-null-terminate-part-2/ The sequel to the null‑termination saga, now tackling <code>strcat</code>, <code>strncat</code>, <code>strlcat</code>, and friends—plus a quick table to keep your concatenations from turning into catastrophes. https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-always-null-terminate-part-1/ Wed, 01 Sep 2021 00:00:00 +0000 https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-always-null-terminate-part-1/ A light‑hearted reminder that every character buffer deserves a <code>'\0'</code>—otherwise you’re inviting buffer overflows, stray reads, and a lot of debugging grief.