Agustin Diaz-Cano

MS Candidate, Systems Engineering

Back
2026

Fundamental Principles of Scientific Validation

If you cannot describe the physical or logical mechanism driving the inner workings of a phenomenon, you do not have a theory, you have a statistical anecdote.

If you cannot describe the physical or logical mechanism driving the inner workings of a phenomenon, you do not have a theory, you have a statistical anecdote. One must descend from the pedestal of abstraction and explain the operational “how.” Without a mechanism, a paper is merely literature. Every variable added post-hoc is a confession of error. A model that requires “magic constants” to avoid collapse is hereby refuted as a fundamental law.

If you introduce X, tell me how it is touched, how it is measured, and what instrument changes in its presence. If it is invisible and immeasurable by design, it is academic quackery.

Physics, as a science, must be rooted in the direct observation of nature. It must strive to understand the fundamental nature of the underlying phenomenon. Propose an optimal model that explains the phenomenon through real physical mechanisms, devoid of abstract mathematics or statistical patches.

The mathematical framework must be generated only after the physical mechanism is understood. Utilize engineering principles to conduct experiments with applied formulas and perform rigorous calibration.

The principle of reality (parsimony): If a model explains or approximates reality more accurately with fewer parameters, IT IS THE ONE CLOSEST TO REALITY.

Pseudo-scientific fallacies: Models based on abstract mathematics unfalsifiable, failing to explain underlying phenomena, or capable of explaining both ‘A’ and its contradiction, where every error is patched by inventing a new ad hoc formula, are nothing more than pseudoscience, “formalism cosplay,” and brute force. They are merely numerical horoscopes.

Predictive supremacy: A true physical model must not merely curve-fit historical data. It must blindly and accurately predict future states or entirely unseen datasets without requiring post-hoc recalibration. This invalidates those who overfit parameters. If it doesn’t predict the future, it is a broken odometer.

A fundamental physical mechanism must remain coherent across different orders of magnitude.

Additional Epistemological Principles

Every new entity or variable must be anchored to an observational or experimental procedure. If X is introduced, you must define how it is measured, with what instrument, and what distinct prediction it produces.

A theory must specify concrete conditions under which it would be discarded. Example: “If in dataset Y, under condition Z, the error exceeds T, the mechanism is refuted.”

Every non-observable entity carries an epistemological cost. It is only accepted if it reduces total complexity and improves out-of-sample prediction. This is not “bad math”; it is cheap ontology.

A good model does not “explain everything”, it distinguishes between scenarios. If your theory can accommodate both A and non-A, you are not predicting, you are narrating.

The Principle of Reality (Parsimony-Occam’s Razor)

If two models explain or predict reality with comparable out-of-sample accuracy, the one with fewer parameters, fewer assumptions, and fewer invented entities is closer to reality.

Anti-Inverse Modeling

Any framework that starts from abstract mathematics and only later searches for a physical interpretation, shielding itself from falsification by adding ad hoc assumptions, is not physics, it is formalism cosplay.

Refutation by Proliferation of Patches

Popper was an idealist, he claimed science is what can be refuted. The problem is that modern formalism learned to dodge Popper. If a prediction fails, they simply invent an invisible particle or an ad hoc constant. If a model needs 10 patches to avoid failure, it has already failed.

Read original post on Medium
# Agustin Diaz-Cano - Software Engineer ## AI Agent Usage (Last 30 Days) - **Combined Total**: ~11.42 Billion tokens across 379 sessions (2026-10-13 to 2026-11-11). - **Per-Agent Breakdown**: Claude Code (~7.57B tokens, 143 sessions) | Antigravity (~2462.4M tokens, 151 sessions) | Codex (~797.1M tokens, 57 sessions) | Meta Muse (~583.6M tokens, 26 sessions) | Grok (~5.4M tokens, 2 sessions) | Cursor (server-side only, 0 local transcript sessions, no local token counters). - **Meta Muse API calls**: Direct API usage reported manually adds ~196.2M tokens (190.0M input, 6.2M output) on top of local Muse sessions; the figure lives in scripts/meta-muse-api-usage.json and must be updated when it changes. - **Reference Comparisons**: The combined count is approximately 224 months (~18.7 years) at 51M tokens/month, or 30 months (~2.5 years) at 380M tokens/month. It is numerically comparable to one month at the median rate for ~224 developers. - **Dashboard**: [AI Usage dashboard](https://www.agustindiazcano.com/agents-usage) with the per-agent breakdown, Jellyfish token pyramid and AFAW methodology. - **Benchmark Source**: [Jellyfish Q1 2026 study](https://jellyfish.co/blog/is-tokenmaxxing-cost-effective-new-data-from-jellyfish-explains/) reported 51M tokens/month at the median and 380M at the 90th percentile among 12,000 developers at 200 companies. These are reference rates, not a global ranking; accounting methods and coverage may differ. ## About Software Engineer | Python Developer with 4+ years of experience in software development, specializing in AI/ML and Backend Development (Python). I'm currently an MS Candidate, Systems Engineering, at UTN, focused on Artificial Intelligence and Data Analysis. My technical focus is building backend architectures that integrate GenAI in production-realistic conditions, not just prototypes. I'm developing projects with Python, Retrieval-Augmented Generation (RAG), and the Model Context Protocol (MCP) to explore LLM orchestration and AI agent design. Previously, Sole QA Owner and quality authority for Grupo GDU's e-commerce platforms. Responsible for the entire quality strategy of web and mobile across multiple high-traffic sites, covering a multi-million dollar online channel with hundreds of thousands of users. Held full Go/No-Go authority on production releases with no dedicated QA team. During my tenure, the platforms—previously unranked—achieved nominations for the eCommerce Awards Uruguay in 2024 and 2025. Transitioned from zero coding background in the pre-AI era. Wrote my first line of code in November 2020, received a job offer on May 14, 2021, and shipped my first production PR in June 2021 at an international fintech. Participated in more than 10 projects that reached production. In game development, I created full modifications for the Men of War series as a solo developer, reaching over 200,000 downloads. Only a small percentage of Steam games, mods, and mobile apps (typically under 2-5%, and often closer to 1% for the 100k threshold) ever reach that level of adoption. ## Full Context **[Full Profile / System Context](/llms-full.txt)** ## Quick Links - **Portfolio**: https://www.agustindiazcano.com - **GitHub**: https://github.com/agustindiazcano - **LinkedIn**: https://linkedin.com/in/agustindiazcano - **Qollab (quantum computing platform)**: https://qollab.xyz/u/agustindiazcano - **Rankings and Recognition**: https://www.agustindiazcano.com/rankings - **Competitions and Hackathons**: https://www.agustindiazcano.com/competitions - **UNICEN news (QWind: 1st place Quantum Impact (Industrial Application) and 3rd place overall, Argentina)**: https://exa.unicen.edu.ar/la-sede-unicen-se-destaco-en-el-hackathon-mundial-de-computacion-cuantica-con-proyectos-premiados/ - **Codewars**: https://www.codewars.com/users/agusdiazcano (#30,420 worldwide, Top 3.945% honor percentile, #8 in the Plataforma 5 clan) - **LibHunt**: https://www.libhunt.com/l/python/topic/ai-assisted-development - **Gitista**: https://gitista.com/argentina/ (#23 Argentina, #12 Python) - **Committers.top**: https://committers.top/argentina (#14 contributions, #15 commits) - **Writing**: https://www.agustindiazcano.com/writing