A space to connect knowledge, one line of code a day.
Discover tutorials, ideas, and notes from a learning journey.
Build a focused web pentest plan with clear authorization, realistic objectives, controlled testing, and evidence that developers can use.
Now that you have a database server installed, let’s walk through creating your first database and table. I’ll show you how to do this both directly with SQL (recommended for learning) and briefly mention the programmatic approach. Part 1: Create Your First Database Step 1: Connect to Your Database Server Open a terminal and connect […]
Getting a local database up and running is the first step toward learning SQL hands-on. Here’s a practical, beginner-friendly guide. Step 1: Choose a Database System For learning SQL, I recommend one of these free options: Database Best For SQLite Absolute beginners, no setup MySQL Web development, widely used PostgreSQL Modern SQL features, professional use […]
What is SQL? SQL (Structured Query Language, pronounced “sequel” or “S-Q-L”) is a domain-specific programming language designed for managing and manipulating data stored in relational databases. Think of it as the standard “language” you use to talk to a database — to ask it questions, store information, update records, or delete data. The Core Idea […]
Test templates in JUnit 5 provide a powerful way to run the same test multiple times with different contexts or invocation strategies. Unlike @ParameterizedTest (which is a specialized form of test template), @TestTemplate gives you full control over how tests are invoked by requiring you to register a custom TestTemplateInvocationContextProvider. When to Use @TestTemplate Use […]
@TestFactory is a JUnit Jupiter feature that lets you generate tests at runtime rather than declaring them statically with @Test. This is useful when the number or nature of tests depends on data that’s only known at execution time. Key Rules A @TestFactory method must return one of: DynamicNode (or a subtype like DynamicTest / […]
JUnit 5 provides several ways to conditionally execute tests based on various runtime conditions. This is useful when tests should only run under specific circumstances — like a particular operating system, JRE version, environment variable, or system property. 1. Operating System Conditions Use @EnabledOnOs and @DisabledOnOs to run tests only on specific operating systems. import […]
Stay curious. There is always something new to learn.
Writer and founder of Diary Coding — sharing notes, tutorials, and experiences about programming for anyone who wants to keep learning.