<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data-Modeling on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/data-modeling/</link><description>Recent content in Data-Modeling on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 20 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/data-modeling/index.xml" rel="self" type="application/rss+xml"/><item><title>Stoolap Basics: Data Models and Fundamental SQL Operations</title><link>https://ai-blog.noorshomelab.dev/mastering-stoolap-2026/stoolap-basics-sql-operations/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mastering-stoolap-2026/stoolap-basics-sql-operations/</guid><description>&lt;h2 id="introduction-to-stoolaps-data-foundation"&gt;Introduction to Stoolap&amp;rsquo;s Data Foundation&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid data explorer! In the previous chapters, we embarked on our Stoolap journey, understanding its unique position as a modern, high-performance embedded SQL database. We explored its architectural marvels like MVCC, parallel execution, and vector search, which set it apart from traditional embedded solutions. If you haven&amp;rsquo;t set up your Stoolap environment yet, now would be a great time to revisit Chapter 2.&lt;/p&gt;</description></item><item><title>Chapter 3: Structuring Your Data: Schema Design, Tables, and Relations</title><link>https://ai-blog.noorshomelab.dev/spacetime-db-guide-2026/chapter-3-schema-design-tables-relations/</link><pubDate>Sat, 14 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/spacetime-db-guide-2026/chapter-3-schema-design-tables-relations/</guid><description>&lt;h2 id="introduction-the-blueprint-for-your-real-time-world"&gt;Introduction: The Blueprint for Your Real-time World&lt;/h2&gt;
&lt;p&gt;Welcome back, future SpaceTimeDB architects! In our previous chapters, we got acquainted with what SpaceTimeDB is and set up our development environment. Now, it&amp;rsquo;s time to lay the foundation for your real-time applications: designing your database schema.&lt;/p&gt;
&lt;p&gt;Just as an architect draws up blueprints before construction begins, you&amp;rsquo;ll define your data&amp;rsquo;s structure and relationships within SpaceTimeDB. This chapter is crucial because a well-designed schema isn&amp;rsquo;t just about storing data; it&amp;rsquo;s about enabling efficient real-time synchronization, consistent state management, and robust server-side logic. We&amp;rsquo;ll explore how SpaceTimeDB combines the power of Rust with database table definitions to create a unified data model.&lt;/p&gt;</description></item><item><title>Chapter 5: Structs &amp;amp; Classes - Building Data Models</title><link>https://ai-blog.noorshomelab.dev/mastering-swift-2026/05-structs-classes-building-data-models/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mastering-swift-2026/05-structs-classes-building-data-models/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, future Swift maestros! In the previous chapters, we laid the groundwork with variables, constants, basic data types, and functions. Now, it&amp;rsquo;s time to level up our ability to organize and model data in a meaningful way. Imagine trying to describe a person, a car, or a recipe using just individual variables – it would quickly become a tangled mess!&lt;/p&gt;
&lt;p&gt;This chapter introduces two of Swift&amp;rsquo;s most fundamental building blocks for creating custom data types: &lt;strong&gt;structs&lt;/strong&gt; and &lt;strong&gt;classes&lt;/strong&gt;. These powerful constructs allow us to bundle related properties (data) and methods (functions that operate on that data) into a single, cohesive unit. Understanding structs and classes is absolutely crucial for writing clean, efficient, and idiomatic Swift code, especially as you embark on building production-grade iOS applications.&lt;/p&gt;</description></item><item><title>Chapter 9: Advanced Content Management: Versioning and Metadata</title><link>https://ai-blog.noorshomelab.dev/stellar-gen-guide/chapter-09-advanced-content-management/</link><pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/stellar-gen-guide/chapter-09-advanced-content-management/</guid><description>&lt;h2 id="chapter-9-advanced-content-management-versioning-and-metadata"&gt;Chapter 9: Advanced Content Management: Versioning and Metadata&lt;/h2&gt;
&lt;h3 id="chapter-introduction"&gt;Chapter Introduction&lt;/h3&gt;
&lt;p&gt;In previous chapters, we laid the foundation for our Rust-based Static Site Generator (SSG) by setting up a project, parsing Markdown into an Abstract Syntax Tree (AST), transforming it into HTML, and integrating a basic templating system with Tera. We also introduced frontmatter for essential metadata like titles and dates. While these are crucial, modern content platforms require more sophisticated management capabilities, especially when dealing with evolving documentation, multi-version APIs, or complex editorial workflows.&lt;/p&gt;</description></item><item><title>Chapter 21: Mini-Project: Building a Data-Driven iOS App</title><link>https://ai-blog.noorshomelab.dev/mastering-swift-2026/21-mini-project-data-driven-ios-app/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mastering-swift-2026/21-mini-project-data-driven-ios-app/</guid><description>&lt;h3 id="introduction"&gt;Introduction&lt;/h3&gt;
&lt;p&gt;Welcome to Chapter 21! After exploring many fundamental and advanced Swift concepts, it&amp;rsquo;s time to bring them together into a tangible project. In this chapter, we&amp;rsquo;ll embark on a mini-project: building a simple, data-driven iOS application using Swift and SwiftUI. This project will solidify your understanding of data modeling, networking with modern Swift concurrency (&lt;code&gt;async/await&lt;/code&gt;), UI development with SwiftUI, and robust error handling.&lt;/p&gt;
&lt;p&gt;Building apps that interact with external data sources is a cornerstone of modern software development. Almost every interesting application fetches information from a server, whether it&amp;rsquo;s social media feeds, weather updates, or product catalogs. By the end of this chapter, you&amp;rsquo;ll have a functional app that fetches data from a public API and displays it beautifully, giving you a strong foundation for building more complex, real-world iOS applications.&lt;/p&gt;</description></item><item><title>Chapter 21: Future Directions and Community Contributions</title><link>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/openzl-future-contributions/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/openzl-future-contributions/</guid><description>&lt;h2 id="chapter-21-future-directions-and-community-contributions"&gt;Chapter 21: Future Directions and Community Contributions&lt;/h2&gt;
&lt;p&gt;Welcome to the final chapter of our OpenZL learning guide! So far, you&amp;rsquo;ve journeyed through the fundamentals of OpenZL, understanding its unique approach to format-aware compression, its architecture, and how to leverage it for various structured data types. You&amp;rsquo;ve gotten hands-on with practical examples and tackled challenges, building a solid foundation.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;re going to shift our focus from &amp;ldquo;how to use&amp;rdquo; to &amp;ldquo;where is it going&amp;rdquo; and &amp;ldquo;how can I be a part of it?&amp;rdquo; OpenZL, as an open-source framework, is a living, breathing project. Its future is shaped not just by its creators but also by a vibrant community of users and contributors. We&amp;rsquo;ll explore the exciting potential advancements for OpenZL and, crucially, guide you on how you can contribute to its evolution, making your mark on a project that&amp;rsquo;s poised to redefine data compression.&lt;/p&gt;</description></item></channel></rss>