This summer, I took a big step—literally and emotionally. It was my first long-haul flight since breaking my hip, and I wasn't quite sure how my body would hold up on a journey halfway around the world. ✈️☝️ I contacted ANA in advance to let them know about my condition and the need to drink plenty of water due to kidney cysts. The cabin crew were absolutely amazing. 😍 They brought me water bottles frequently, made sure I was comfortable, and even offered extra blankets and pillows. It felt like I was flying business class again! 🍾✋ Though I had to get up and walk a lot (my leg tends to go numb if I sit too long), the journey was far better than expected. On arrival, I was also pleasantly surprised to find that British citizens can now use Japan’s priority immigration gates — no queues at all! 🇯🇵✅ My wife, being Japanese, could go through with me too, which isn’t usually the case in the UK. On Day 1, I met up with my friend Robbie at the airport and had a relaxi...

Introduction When it comes to cybersecurity, many people think of secret agents and high-tech gadgets. But in reality, protecting data online comes down to a simple yet powerful concept called the CIA triad — Confidentiality, Integrity, and Availability. In this post, I’ll share a teaching session I had with Kai, walking him through these principles and showing how they relate to building secure login systems. We’ll cover why strong passwords matter, how to detect SQL injection attacks, and how to write database functions and stored procedures to keep our systems safe. What Is the CIA Triad? CIA stands for: Confidentiality: Ensuring data is only accessible by those authorized to see it. Integrity: Making sure data isn’t altered or tampered with by unauthorized users. Availability: Guaranteeing data and systems are accessible when needed. These three principles are the foundation of cybersecurity and help guide how we design secure applications. The Con...

July 1, 2025 After learning stored procedures and date functions, Kai was ready for the next challenge: making the database safe   and building something real people could click and use. 🔐 Permissions: Who Gets to Do What? We started with a simple but powerful idea: not everyone should be able to change everything. I told Kai, “Imagine giving teachers the keys to mark attendance, but not delete students by accident.” We created roles in SQL Server: CREATE ROLE TeacherRole; GRANT EXECUTE ON MarkAttendance TO TeacherRole; Then added a user and assigned the role: CREATE LOGIN Teacher1 WITH PASSWORD = 'SecurePass123!'; CREATE USER Teacher1 FOR LOGIN Teacher1; EXEC sp_addrolemember 'TeacherRole', 'Teacher1'; “So Teacher1 can mark attendance, but nothing else?” Kai asked. Exactly. Principle of least privilege in action. 🔒 🧩 Kai’s First Dashboard UI Then the big one: Kai brought me a sketch a simple web page with two boxes: Who is enrolle...