2026-01-11 11:40:20
Three key benefits of creating a side project are giving back to the community, supporting other organizations, and personal growth.
One of the greatest benefits of creating a side project is the contribution to society at large. In this example, the main cause is to support art and empower artists and art-lovers, by shining a spotlight on those behind the scenes, celebrating the collaborative nature of the creative process, emphasizing the importance of mutual inspiration, and equality between different art forms.
Creating a side project can be beneficial not only to the community but also to small businesses and non-profit organizations. The nature of making a side project gives the ability to own the decision-making, and make selective choices.
Given the small scale of the project, I have decided to avoid hosting the website and database on my personal server to ease the hosting and deployment process. After researching a backend solution, I found positive comments about Pocketbase, an open-source Go(lang) project, and I decided to use it. DigitalOcean is also known for being developer-friendly with its solutions (also supporting Hacktoberfest), and I chose their services for the project. For completing design elements, I used products from organizations that I have used in the past (Flaticon for icons) or have been a fan of for some time (MagicPattern).
Using other tools is also necessary during the promotion and organization of work. I have enjoyed working with Notion for almost a decade at this point, and it was also my go-to choice for this project.
Another reason for creating a side project is self-development. For me, the most challenging aspects of the process, which I was not very familiar with, were incorporating the database into the web application and its deployment. Later, I also started learning more about SEO, which I had never had the chance to do before. Besides that, making your own project allows for taking creative and strategic decisions. While promoting the site, some additional skills can be useful like writing or public speaking.
Learn more about the project: https://artdots.co/
Originally posted at: https://artdots.co/blog/artdots-the-benefits-of-creating-a-side-project
2026-01-11 11:33:48
Abstract:
The discovery of interstellar objects such as ʻOumuamua and Borisov has opened new frontiers in planetary science. One such object, provisionally referred to as 3I/ATLAS, has raised questions about its trajectory, structural anomalies, and potential interaction with Earth. This article presents a structured, physics-based analysis of 3I/ATLAS, incorporating gravitational interactions with Jupiter, hypothetical internal activity, and probability estimates for Earth encounters. The analysis is assisted by ChatGPT (GPT‑5 Mini), demonstrating how AI tools can support independent reasoning and scenario evaluation while strictly adhering to proven physics principles.
Recently, the interstellar object 3I/ATLAS has attracted attention due to its unusual trajectory and reported anomalies. The core questions explored include:
One might first consider whether 3I/ATLAS could be steered toward Earth via gravitational interactions with Jupiter or its satellites:
Even considering extreme configurations, orbital mechanics shows that a purely passive 3I/ATLAS is almost certain to avoid Earth, with impact probability effectively zero (~10⁻¹³). This establishes Jupiter as a limited deflection source — insufficient alone to pose a risk.
A more nuanced possibility is that 3I/ATLAS could exhibit non-passive behavior, such as internal regulation, venting, or even low-level propulsion:
Thus, while Jupiter alone cannot redirect the object, combined with non-passive internal activity, it could, in principle, shift the path slightly—but only within strict physical limits.
Reported features of 3I/ATLAS include:
These anomalies suggest that the object may not be fully passive. Using Bayesian reasoning:
Probability 3I/ATLAS is not fully passive≈30%
This estimate is agnostic regarding intelligence, considering only deviations from purely passive behavior consistent with known physics.
Even allowing for non-passive behavior (~30%), fundamental physics constrains possible interactions with Earth:
| Scenario | Probability |
|---|---|
| Impact with Earth | ≤ 0.00001% |
| Close approach (within lunar distance) | 0.001–0.01% |
| Distant flyby (AU-scale) | > 99.99% |
Key points:
Hence, even under conservative assumptions, Earth impact remains extraordinarily unlikely, and a distant flyby is overwhelmingly the most probable outcome.
This analysis demonstrates a careful, physics-based approach:
Based on current knowledge and observed behavior:
The probabilities and conclusions presented in this article were derived through a structured reasoning process, assisted by ChatGPT (GPT‑5 Mini), combining observed data, proven physics, and Bayesian probability, as follows:
Data Sources and Observations
Physics Constraints
Probabilistic Reasoning
Bayesian-style reasoning was applied:
Independent Analysis
Summary of Method
Step 1: Identify observed data and anomalies.
Step 2: Apply constraints from proven physics.
Step 3: Estimate prior probabilities for passive vs non-passive behavior.
Step 4: Update priors based on observed anomalies.
Step 5: Calculate conditional probabilities for Earth interaction scenarios.
Step 6: Combine results into a coherent probability tree and summary for presentation.
2026-01-11 11:32:25
Below is a very simple useState polyfill that you can execute, with clear comments and a minimal example to demonstrate state persistence and updates.
useState Polyfill
// Simple useState polyfill for interview explanation (Fixed Version)
function createUseState() {
// Array to store state values across "renders"
let stateStore = [];
// Track current index for hook calls in a render
let currentIndex = 0;
function useState(initialValue) {
// Use currentIndex for this call and increment for next
const index = currentIndex;
currentIndex++;
// Initialize state if not set yet (first render)
if (stateStore[index] === undefined) {
stateStore[index] = initialValue;
}
// Current state value
const currentState = stateStore[index];
// Setter function to update state
const setState = function(newValue) {
stateStore[index] = newValue;
console.log(`State updated to: ${newValue} at index ${index}`);
};
return [currentState, setState];
}
// Reset index for next render simulation
function resetIndex() {
currentIndex = 0;
console.log('Resetting index for next render');
}
return { useState, resetIndex };
}
// Create an instance of useState
const { useState, resetIndex } = createUseState();
// Simulated component to show state usage
function MyComponent() {
// Use state for a counter and name
const [count, setCount] = useState(0);
const [name, setName] = useState("Zeeshan");
console.log('Current Count:', count);
console.log('Current Name:', name);
// Return setters to update state outside of render
return { setCount, setName };
}
// Run the simulation
console.log('First Call (Initial Render):');
const { setCount, setName } = MyComponent();
resetIndex();
// Update state
console.log('\nUpdating State:');
setCount(1);
setName("John"); // This will overwrite the previous update to index 0
// Run again to simulate re-render and show updated state
console.log('\nSecond Call (After Update):');
MyComponent();
resetIndex();
simpleUseState.js) and run it using node simpleUseState.js in your terminal. The output will appear in the console.When you run this code, you'll see output similar to this:
First Call (Initial Render):
Current Count: 0
Updating State:
State updated to: 1 at index 0
Second Call (After Update):
Current Count: 1
useState—managing state in a functional component by storing and updating values across "renders."stateStore is a simple array that holds state values. Each useState call gets a unique index based on the length of stateStore at the time of the call.useState is called for that index, and subsequent calls retrieve the current value.setState updates the value at the specific index in stateStore.MyComponent() multiple times simulates re-renders, showing the updated state.useState?: Explain it’s a React hook for managing state in functional components, allowing you to store and update values across renders.stateStore) with each useState call getting its own slot.setState updates the value in the array.This version is intentionally minimal, focusing on the core idea of state management for an interview. It’s easy to explain and execute, showing how state is stored and updated. If you’d like to add a bit more detail or another example, let me know!
2026-01-11 11:30:00
2026-01-11 11:26:22
As the Founder of ReThynk AI, I want to say this clearly:
Small businesses don’t lose trust because they lack AI.
They lose trust when they use AI carelessly.
That’s why I treat ethics as a business advantage, not a legal lecture.
The Minimum Ethics Checklist for Small Businesses
Most small businesses don’t need complex “AI governance.”
They need a simple checklist that protects:
Because in the AI era, trust is fragile.
One mistake can cost more than a month of marketing.
So here is the minimum ethics checklist I follow.
1) Privacy First: “Don’t feed the machine what you wouldn’t post publicly”
I never put these into AI tools:
Rule: If it can harm someone if leaked, it doesn’t go in.
2) Truth Over Hype: “AI should not create false confidence”
I never let AI:
Rule: If it isn’t true, it isn’t marketing; it’s a liability.
3) Human Accountability: “AI assists. Humans own.”
AI can draft replies and content.
But a human must own:
Rule: No “AI said so” in business.
4) Fairness and Respect: “Don’t automate disrespect”
I avoid AI output that:
Rule: Automation should never reduce human dignity.
5) Transparency When It Matters
I don’t need to announce AI everywhere.
But if AI is involved in something sensitive (support decisions, screening, approvals), I keep it transparent.
Rule: If it affects a person’s outcome, they deserve clarity.
6) Safe Defaults: “When unsure, escalate”
When AI is uncertain, I don’t force automation.
I define escalation rules:
Rule: High-stakes situations stay human-led.
The leadership insight
Ethics is not a cost.
Ethics is how small businesses build trust faster than big brands.
Because big brands can hide behind budgets. Small businesses survive on reputation.
So this checklist is not optional; it’s protection.
2026-01-11 11:13:38
CAI-EXPERT-LAB no es un sistema de IA, no es un producto y no es un framework de cumplimiento normativo.
Es una arquitectura de referencia para la gobernanza de la IA y la ciberseguridad, centrada en cómo se preservan la decisión, la autoridad y la responsabilidad en sistemas que incorporan analítica avanzada y automatización.
Su alcance no es el rendimiento de modelos ni la optimización algorítmica.
Opera a nivel arquitectónico, donde la gobernanza existe por diseño o colapsa bajo presión.
CAI-EXPERT-LAB trata la inteligencia artificial como una capacidad analítica, no como una autoridad decisional. La responsabilidad humana permanece explícita, trazable y estructuralmente protegida.
Este trabajo no intenta regular la tecnología.
Define las condiciones bajo las cuales la tecnología puede utilizarse sin erosionar la legitimidad, la rendición de cuentas ni el control.
Se compartirá más con el tiempo — de forma cuidadosa e intencional — pero su fundamento es arquitectónico, no procedimental.
