I didn’t go into the MeDo hackathon with some big, polished idea. I just wanted to build something I’d actually use. So I made Exam AI. The problem is simple: studying for exams is chaotic. You read notes, search things, forget half of it, and then try to cram everything at the end. I wanted something that helps you actively think, not just passively read. You give Exam AI a topic — anything you’r
Building a Full-Stack Habit Tracker with Claude Code - Part 2: Polish, Testing & Deployment Taking the habit tracker from MVP to production-ready with categories, analytics, comprehensive testing, and Vercel deployment In [Part 1], we built a fully functional habit tracker MVP in about 6-8 hours using Claude Code as our AI pair programmer. We had: ✅ Basic CRUD operations for habits ✅ Date-based
🚀 The Complete Guide to Pass the DP-750 Beta Certification Exam — Azure Databricks Data Engineer Associate Today I have something important for you. I've created a specific guide to help you pass your DP-750 beta certification. How to master Azure Databricks, Unity Catalog governance, and Apache Spark to confidently pass the Microsoft DP-750 certification — the most complete study roadmap for d
Introduction While studying for CompTIA Network+, I couldn't grasp what a Loopback Plug actually does. I understood that it was used for testing, but had no idea how it worked in practice. As a result, I kept getting questions about it wrong. Once I understood the structure behind it, everything clicked. So I decided to write it down. NIC stands for Network Interface Card. a component inside a c
Testing Firefox Extensions with Playwright: End-to-End Testing Guide Extension testing is one of those things everyone knows they should do but few actually do. I've been using Playwright for end-to-end tests on the Weather & Clock Dashboard extension and it's changed how I think about extension quality. Unit tests don't cover the biggest failure modes: Does the extension actually load in Firefo
If you find this helpful, please like, bookmark, and follow. To keep learning along, follow this series. In Rust, a test is a function used to verify whether non-test code behaves as expected. A test function usually performs three actions: Arrange data/state Act on the code under test Assert the result In some languages, these three actions are called the 3A steps. A test function is still just a
The most basic concept in test doubles is the dummy. When testing a function, there are usually two kinds of input: Meaningful input Data that affects the result of the function. Dummy input Data that is required by the function, but does not affect the behavior we are testing. Below is an example of meaningful data vs dummy data. This is a calculateShipping function: function calculateShip
Your application fetches a URL. The user supplied it. Your server makes the request, follows the redirect, and returns the content. The URL pointed to http://169.254.169.254/latest/metadata/iam/security-credentials/production-role. Your application just handed the attacker your cloud credentials. SSRF lets an attacker trick your server into making requests on their behalf — to internal services, c