Who
Isaac Neibaur
Isaac Neibaur is a Data Engineer & Platform Architect using this project as a public practice field for disciplined, production-aware dashboard work.
100 dashboards in 100 days
Isaac Neibaur's public sprint to turn disciplined data engineering practice into useful dashboards, shipped one day at a time.
Who
Isaac Neibaur is a Data Engineer & Platform Architect using this project as a public practice field for disciplined, production-aware dashboard work.
Challenge
The challenge is designed to develop consistency, rapid-response data skills, and practical data storytelling by repeatedly moving from question to real dataset, analysis, visualization, and published dashboard.
Tech
The stack stays intentionally local-first and reviewable while supporting reusable Python dashboard logic, Markdown publishing, and static web delivery.
Tooling Range
The project will intentionally explore a wide range of dashboarding tools, platforms, and standards, including Power BI, Tableau, Cognos, Oracle, Google Analytics, Azure, AWS, Supabase, Google Sheets, Excel/CSV, and real public APIs where low/no-cost options are practical.
Data Standard
Dashboards should use real data rather than mock data whenever possible, with source context, limitations, and assumptions made visible enough for readers to understand what the dashboard can and cannot claim.
Engineering Rigor
Each meaningful change is expected to stay compatible with CI/CD, metadata validation, security checks, and the project coverage gate of at least 80% for modified reusable logic.
Day 43
Turning a noodle-content idea into a governed haomiantiao project with a narrowed MVP, scoped repo template, bot identity, and the first bracket-engine slice.
Day 42
Turning Terminal Run's Phase 0 security and governance lessons into a reusable project template, organization rulesets, and a clearer trust model.
Day 41
Bootstrapping Terminal Run into a governed AI-assisted repository, testing its safety controls, and learning why prevention layers must be challenged before they are trusted.
Day 40
Advancing UseThai through a tightly governed app-tier slice while turning Terminal Run from a loose concept into an implementation-ready educational game plan.
Day 39
Closing the current UseThai friction-testing loop, triaging a second fixture-backed evidence batch, cleaning project state, and narrowing the next app-tier decision.
Day 38
Turning Thai tone support into an auditable validation path, grounding derived linguistic artifact provenance, cleaning project state, and reassessing UseThai friction readiness.
Day 37
Using manual UseThai testing to separate app-tier UX improvements from core search work, assess Volubilis ingestion readiness, and establish tone as a governed product requirement.
Day 36
Resolving a lexical lookup contract contradiction through ADR governance, integrating the corrected behavior into UseThai, and shifting toward evidence-driven UX maturation.
Day 35
Strengthening the UseThai application through Cloudflare build support, UI foundations, truthful lookup states, search investigation, governance cleanup, and dataset research.
Day 34
Closing Phase 15 through ADR-0015, grounded English-to-Thai phrase lookup, lexical key normalization, barrel inventory, and UseThai application evidence gathering.
Day 33
Moving from Phase 15 governance review into the first UseThai application shell, proving a browser-to-core Thai dictionary lookup while exposing search UX limits.
Day 32
Exploring an AI career advocate concept, acquiring and governing new domains, deploying placeholder sites, and hardening SPF records across the domain portfolio.
Day 31
Transitioning Lingua Core Platform from Phase 14 into Phase 15 through governance validation, ADR work, repository modernization, and disciplined architectural grounding before implementation.
Day 30
Closing Phase 14 through repository-grounded validation, modernizing governance, accepting ADR-0014, and grounding the first Phase 15 configuration direction.
Day 29
Completing a methodical home AC diagnosis while grounding the Lingua Core Platform delivery boundary and opening Phase 14 with warranted route contracts.
Day 28
Documenting an HVAC troubleshooting day that applied systematic diagnosis, electrical isolation, infrastructure modernization, root-cause analysis, and persistence beyond software engineering.
Day 27
Documenting dynamic security.txt deployment validation, Cloudflare AI crawler and scraper defenses across a domain fleet, Lingua Core Platform Phase 13 review, and Phase 14 planning.
Day 26
Documenting Cloudflare DNS hardening across placeholder domains, scalable www-to-apex edge redirects, Phase 13 completion in lingua-core-platform, and continued AI workflow governance maturity.
Day 25
Documenting domain fleet email security hardening, pre-Phase 12 governance audits, invariant guard remediation, AI bootstrap workflow improvements, and the first authorized Phase 12 learning-surface implementation.
Day 24
Documenting the pre-Phase 12 architectural audit cycle, repository governance refactor, deterministic AI onboarding improvements, and the evolution from AI-assisted coding toward AI-governed software engineering.
Day 23
Documenting Phase 10 completion, deterministic runtime capability governance, AI session continuity infrastructure, repository-wide architectural auditing, and dependency governance maintenance.
Day 22
Documenting the Phase 10 transition into lexical query interoperability, replay-safe reporting, enrichment architecture, and stronger AI-assisted architectural continuation workflows.
Day 21
Documenting Phase 8 closure, Phase 9 runtime governance completion, deterministic capability certification, and a multi-agent engineering workflow.
Day 20
Documenting deterministic query architecture maturation, governance infrastructure evolution, replay-safe infrastructure, explainability foundations, and long-term platform strategy.
Day 19
Documenting governance-first repository initialization, TypeScript platform foundations, DevSecOps controls, and architecture decisions for lingua-core-platform.
Day 18
Documenting a platform engineering day focused on Databricks lakehouse learning, Tech Talent Pulse framework modernization, CI stabilization, and early product architecture ideation.
Day 17
Improving journal discoverability with search and navigation while using domain portfolio review as a platform strategy and governance exercise.
Day 16
Expanding the domain placeholder platform across the full owned domain portfolio while tightening Cloudflare governance, inventory, and compliance visibility.
Day 15
Scaling the domain placeholder rollout across approximately 50 owned domains while validating Cloudflare Pages, DNS, email routing, dependency upgrades, and future automation boundaries.
Day 14
Completing Phase 7 operational readiness work, validating live Cloudflare Pages domain behavior, testing Cloudflare Email Routing, and tightening test maintainability with a DRY refactor.
Day 13
Validating the reusable Domain Placeholder Platform against live Cloudflare-managed production domains while keeping the deployment model simple, operational, and non-destructive.
Day 12
Designing AccessBridge AI, an accessibility-focused declarative assistant in Microsoft Copilot Studio Lite, while documenting responsible AI guardrails, trusted-source grounding, and licensing constraints.
Day 11
Documenting the day Tech Talent Pulse evolved from backend analytics APIs into an early full-stack analytics platform with orchestration, advanced analytics, Astro dashboard visualization, and local runtime hardening.
Day 10
Documenting an operational maturity day focused on Docker Desktop stability, Flyway migration reliability, CI parity, Git branch hygiene, and continued Java platform workflow hardening.
Day 9
Connecting Founderz Agent Explorer learning with dependency security governance, pnpm lockfile recovery, and a simpler trunk-based branch strategy for 100daydash.blog.
Day 8
Documenting a lighter operational day focused on dependency security hygiene, spike-branch isolation, and sustainable engineering pace.
Day 7
Documenting a platform engineering day focused on professional presence, GitHub governance, deployment reliability, Cosmos DB learning, and AI-assisted certification workflows.
Day 6
Documenting a technical career refactoring day that combined Azure Cosmos DB learning with digital presence modernization, recruiter discoverability, and platform engineering identity consolidation.
Day 5
Documenting the shift from portfolio modernization into a broader platform engineering ecosystem for CI/CD governance, AI-assisted workflows, and technical storytelling.
Day 4
Documenting the platform engineering work behind adapting, hardening, and deploying a reusable Hugo portfolio architecture for a production client site.
Day 3
Resolving repository connection hurdles and transitioning infrastructure data into actionable BI insights via Looker Studio.
Day 2
Documenting technical debt reduction, platform spikes, Astro v6 migration work, and governance hardening.
Day 1
Clearing the final hurdles in CI/CD and domain routing to secure the 100-day foundation.
Day 0
Setting up the foundation for 100 dashboards in 100 days.