<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>To-Do List on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/to-do-list/</link><description>Recent content in To-Do List on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 04 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/to-do-list/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 9: Designing the Data Model &amp;amp; Persistence with JPA/Hibernate</title><link>https://ai-blog.noorshomelab.dev/java-mini-projects/ch09-data-model-jpa/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/java-mini-projects/ch09-data-model-jpa/</guid><description>&lt;h2 id="chapter-9-designing-the-data-model--persistence-with-jpahibernate"&gt;Chapter 9: Designing the Data Model &amp;amp; Persistence with JPA/Hibernate&lt;/h2&gt;
&lt;h3 id="chapter-introduction"&gt;Chapter Introduction&lt;/h3&gt;
&lt;p&gt;Welcome to Chapter 9! In this chapter, we&amp;rsquo;re taking a significant leap in building our &amp;ldquo;Basic To-Do List Application&amp;rdquo; by introducing data persistence. Up until now, any data we&amp;rsquo;ve worked with would vanish as soon as our application stopped. That&amp;rsquo;s not very useful for a To-Do list! Here, we will design the data model for our To-Do items and implement the persistence layer using Java Persistence API (JPA) with Hibernate, backed by Spring Data JPA.&lt;/p&gt;</description></item><item><title>Chapter 11: Implementing Business Logic with Service Layer</title><link>https://ai-blog.noorshomelab.dev/java-mini-projects/ch11-business-logic-service/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/java-mini-projects/ch11-business-logic-service/</guid><description>&lt;h2 id="chapter-11-implementing-business-logic-with-service-layer"&gt;Chapter 11: Implementing Business Logic with Service Layer&lt;/h2&gt;
&lt;h3 id="chapter-introduction"&gt;Chapter Introduction&lt;/h3&gt;
&lt;p&gt;Welcome to Chapter 11 of our Java project series! In the previous chapters, we established our project structure, set up our development environment with the latest Java version (Java 24/25), and perhaps even created some basic data models. This chapter marks a significant step forward as we introduce the &lt;strong&gt;Service Layer&lt;/strong&gt; – the heart of our application&amp;rsquo;s business logic.&lt;/p&gt;
&lt;p&gt;The service layer is crucial for separating concerns, ensuring that our core application rules, validations, and operations are encapsulated in a distinct, reusable, and testable component. Instead of scattering business logic across various parts of the application (like a user interface or data access layer), we centralize it here. This approach makes our code easier to understand, maintain, and evolve. For our &lt;strong&gt;Basic To-Do List Application&lt;/strong&gt;, the service layer will manage tasks: adding, retrieving, updating, and deleting them, while enforcing any specific rules for these actions.&lt;/p&gt;</description></item><item><title>Chapter 14: Comprehensive Unit &amp;amp; Integration Testing with JUnit 5</title><link>https://ai-blog.noorshomelab.dev/java-mini-projects/ch14-unit-integration-testing/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/java-mini-projects/ch14-unit-integration-testing/</guid><description>&lt;h2 id="chapter-14-comprehensive-unit--integration-testing-with-junit-5"&gt;Chapter 14: Comprehensive Unit &amp;amp; Integration Testing with JUnit 5&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 14! In this crucial phase of our project development, we shift our focus to ensuring the reliability and robustness of our applications through rigorous testing. We&amp;rsquo;ll dive deep into unit and integration testing, leveraging the power of JUnit 5, the de facto standard for testing in Java. This chapter is not just about writing tests; it&amp;rsquo;s about adopting a testing mindset that leads to more stable, maintainable, and production-ready code.&lt;/p&gt;</description></item></channel></rss>