Category: Engineering

Notes that aren’t tied to a single product — the tooling, process, and engineering decisions that carry across everything I build.

Some of this is workflow: how I run Claude Code sessions, what actually persists between them, which parts of a build belong in version control versus in my head. Some is practice: treating security as a design constraint rather than a pre-launch checklist, and picking up iOS development again after years focused on the web.

These entries tend to be the ones I write after something broke, which makes them more useful than the ones written while everything was working.

Defense in Depth

Defense in Depth: Building Layered Security for Business and Personal Protection In medieval times, castles weren’t protected by a single wall. They featured multiple barriers: moats, outer walls, inner walls, towers, and a final keep. Each layer served as a backup when the previous one failed. This same principle applies to modern cybersecurity through a strategy called Defense in Depth. Defense in Depth is a cybersecurity approach that uses multiple layers of security controls to protect information and systems. Rather than relying on a single security measure, this strategy creates overlapping defenses that work together to detect, prevent, and respond to cyber threats. Why Single-Point Security Fails Many organizations and individuals make the mistake of treating cybersecurity like a single lock on a door. They install antivirus software or use strong passwords and assume they’re protected. However, cybercriminals are persistent and creative. If they can bypass your one security measure,

Read More »

Feel free to visit the other sections