Skip to main content

Posts

Showing posts from 2024

EDORA - Build Your Own Table Schema

🚀 Introducing the EDORA Core Database Let’s Build Something Incredible Together! 🚀 From Concept to Community—The Engine is Ready When I started building EDORA , the vision was clear: A system that’s clean, scalable, and ready for anyone to take and make it their own. What began as a database idea for case management has evolved into something bigger: 💡 A foundation that you can extend. 💡 A playground where you can experiment. 💡 A collaborative space for builders, dreamers, and database enthusiasts worldwide. What is the EDORA Core Engine? EDORA Core is a database foundation—set up and ready to run in seconds. It’s perfect for: ✅ Developers : Start your next project with a clean, functional database schema. ✅ Database Experts : Add your own tables, tweak relationships, and make it shine. ✅ Learners : Want to get your hands dirty with SQL? This is the perfect sandbox to play in. What You Get : 1️⃣ A Solid Foundation : Pre-built tables for clients, needs, resources, provid...

The Frosted Blueprint Depot

Laying the Tracks for Your Node.js Database Setup Introduction When you’re starting a Node.js project, it’s not uncommon to reach a point where you need a database. Maybe you’re just testing workflows, or maybe you’re heading toward something serious. Regardless, having a consistent and automated way to set up both your database and initial data is invaluable. This guide will show you how to: Choose a database library. Install that database and integrate it into your Node.js project. Write migrations (if necessary) to keep track of schema changes. Seed the database with initial data so everyone is on the same page from the start. We’ll assume you’re using SQLite for simplicity because it’s ridiculously easy to set up—no dedicated database server required, just a single file. But the concepts here apply to other databases (like PostgreSQL, MySQL, etc.) once you learn the ropes. Step 1: Setting Up Your Project Before we jump into the database portion, you need a Node.js projec...

The Next Train Stop - Station 001

Expanding the Tracks for EDORA Welcome aboard the EDORA Express!  🚂 After the milestones of “ The Little Engineer That Could ” and “ Feeding the Coal to the Engine ,” we’re pulling into the next station—a critical juncture for expanding and perfecting EDORA’s framework before moving full steam ahead into development. This train stop is about laying the tracks for the next steps, refining our workflows, and preparing the system for the journey ahead. It’s not just about where we’re going—it’s about how we’re getting there. Upcoming Stops on the EDORA Line Here’s the itinerary for our next four major steps: 🚉 Step 1: Expanding Workflow Details We’re diving deeper into EDORA’s engine room to define the finer mechanics of its core workflows. This includes: Dynamic Eligibility Rules: A rules engine to evaluate and validate "Needs" against criteria like income thresholds, residency, or service availability. Milestone Tracking: Establishing clear checkpoints, both se...

The Coal to the Engine

Unveiling the Second Stage of EDORA’s Core Engine This is part 2 of the core engine explanation find Part One Here  The journey to create a transformative system like the EDORA Client Case Management System is not simply about technology—it’s about crafting a vision. At its heart, EDORA revolves around one unifying concept: the "Need." This abstract entity is the fuel driving every interaction, every relationship, and every action within the system. Tonight, we delve deeper into how this "Need" operates, focusing on its workflows, relationships, and the technical schemas that bring it to life. The "Need" isn’t just a request or a problem to solve. It’s a carefully nurtured process that moves through a lifecycle of interactions, bridging clients, caseworkers, providers, specialists, and the system itself. By creating an intricate yet flexible framework, EDORA aims to ensure that no "Need" is left unmet. Understanding the Lifecycle of a ...

The Little Engineer that Could

Building the Core Engine of EDORA Welcome to the engine room of EDORA, the Event-Driven Operations, Records, and Analytics system that aims to transform how Human and Health Services are managed. Today, we’re unveiling the core engine —a set of foundational workflows and database schemas that breathe life into every interaction, decision, and resolution within EDORA. Whether you’re a technology enthusiast or someone passionate about impactful systems, this post takes you deep into the design and philosophy of EDORA’s core. By the end, you’ll see how each layer of this system is engineered to revolve around one unifying concept: the "Need." The "Need": The Universal Connection At the heart of EDORA lies the "Need" —a concept that transcends mere data to represent the driving purpose of the system. A "Need" encapsulates a client’s requirement—whether for housing, therapy, or financial assistance—and serves as the central hub that connects clients,...

Introducing the EDORA Maslow Philosophy

The Guiding Framework for Human and Health Services Systems A Universal Philosophy Connecting Needs, Systems, and Humanity In the ever-complex world of Human and Health Services, building a system that truly serves its purpose requires more than just technology—it demands a unifying philosophy. Today, I’m excited to share the official EDORA Maslow Philosophy , the foundation of EDORA : Event-Driven Operations, Records, and Analytics . This philosophy is not just a framework for technical systems; it’s a universal guide for decision-making, operations, and service delivery. With the "Need" at its center, the EDORA Maslow Philosophy redefines how we think about interactions between clients, services, and systems. What is the EDORA Maslow Philosophy? The EDORA Maslow Philosophy draws inspiration from Maslow’s Hierarchy of Needs but takes it to a new level. While Maslow’s work focused on individual psychology, the EDORA approach applies a similar structure to Human and He...

Join the Movement: EDORA

EDORA and the Case for Free Software in Public Infrastructure In a world increasingly driven by technology, the software that powers our public and state-run infrastructure is more than just code—it’s the backbone of a free society. I created EDORA Client Case Management Software ( www.edoracases.com ) with this principle in mind: free software should not only be an option but a necessity for governments and public institutions. I invite you to join this cause and become a part of a movement dedicated to protecting our digital freedom. FSF Free Software: A Vital Pillar of a Free Society Free software is more than just "free of cost." It ensures the freedom to run, study, modify, and share software, empowering individuals and organizations to adapt technology to their needs. Public and state-run infrastructure built on free software respects these freedoms, ensuring that citizens retain control over the tools they are required to use. Imagine a government system where you, t...

The Big Data Paradigm

Centralized Data Exposed      I n an age where data has become the new currency, I must express a profound concern over the prevailing trend of consolidating vast amounts of sensitive information into centralized hubs. While the allure of "big data" promises unprecedented insights and efficiencies, it also ushers in dangers to society and individual privacy that cannot be overlooked. The year 2024 has witnessed an alarming surge in data breaches, surpassing any we have seen before. Major corporations entrusted with the personal information of millions have fallen victim to cyberattacks, exposing vulnerabilities inherent in the centralized data model.      According to reports up until 2023, there was already a 68% increase in data compromises compared to the previous year, with over 1,862 breaches exposing nearly 294 million individuals' data *(1) . This trend has only intensified in 2024, underscoring the risks of housing enormous data sets under one roof....

JavaScript: Functions Internals

Understanding the Internal Structure of JavaScript Functions In the pursuit of mastering JavaScript, understanding the internal workings of functions is crucial. Functions are the building blocks of any JavaScript program, and comprehending their internals can elevate your coding skills to a professional level. This essay delves into the internal structure of JavaScript functions, covering  [[FunctionLocation]] [[Scopes]] [[HomeObject]] [[Call]] [[Construct]]` Internal Properties of JavaScript Functions  1. [[FunctionLocation]] The `[[FunctionLocation]]` internal property indicates where a function is defined in the source code. This property is primarily for debugging and error reporting, helping developers pinpoint where a function originates. Purpose: To provide location information for debugging purposes. Example: When an error occurs, the stack trace reveals the location of the function in the source code, thanks to [[FunctionLocation]]. Practical Insight: While [[Functio...

JavaScript: Func calling Funk

Understanding JavaScript Functions and Event Handling Introduction to Functions in JavaScript JavaScript, as a versatile and dynamic language, treats functions as first-class citizens. This means that functions can be manipulated just like any other data type. They can be assigned to variables, stored in arrays, and passed as arguments to other functions. This flexibility is fundamental to JavaScript’s ability to respond to user events effectively. What is a Function? In JavaScript, a function is a block of code designed to perform a particular task. It is executed when something invokes it (calls it). Functions can be defined using function declarations or function expressions. Function Declaration: function greet(name) {     return `Hello, ${name}!`; } Function Expression: const greet = function(name) {     return `Hello, ${name}!`; }; Both methods create functions that can be invoked to execute the block of code they encapsulate. First-Class Citizens The...

JavaScript: Nodes versus Collections

Understanding HTML Collections and Node Lists in JavaScript When working with the DOM in JavaScript, you often encounter two types of collections: HTML Collections and Node Lists. Both represent groups of DOM elements, but they have distinct characteristics and behaviors. This guide will explain the differences between them, demonstrate how to iterate over each using different `for` loops, and provide tips on choosing the correct loop for your needs. HTML Collections HTML Collection is a live collection of DOM elements. This means that if the document changes (e.g., an element is added or removed), the HTML Collection updates automatically. Common Methods Returning HTML Collections: document.getElementsByTagName(tagName) document.getElementsByClassName(className) document.forms document.images Example: <!DOCTYPE html> <html> <body>     <div class="example">Item 1</div>     <div class="example">Item 2</div>     <d...