Languages — Any Language the Job Needs

I refuse the "one true language" religion. Languages are tools with shapes, and the job decides which shape fits. These percentages are honest self-assessments of production readiness — not course certificates.

Language	Readiness	Where I use it
Python	99%	API bridges, agents, automation, scrapers — GhostBrain, Hermes, panels.
JavaScript / TypeScript	98%	Full-stack web, edge Workers, panels, this portfolio.
PHP	98%	Laravel services, classic deploys, quick client products.
SQL	100%	Schema design, tuning, reporting across Postgres/MySQL.
Ladder (LD)	96%	PLC logic on real production lines.
Structured Text (ST)	96%	IEC 61131-3 industrial control programs.
Go	94%	NetPilot, OmniRouter, glm-free-api — CLIs and services.
C#	93%	.NET backends, desktop tools, WPF/MAUI.
C / C++	78%	HardwarePT, embedded experiments, performance cores.

The pattern behind the list: high-level languages for velocity, systems languages for control, and industrial languages because somebody has to make the physical world behave. New languages are a weekend problem, not a career decision — the agentic workflow makes ramp-up even cheaper, since agents write idiomatic scaffolding in any ecosystem while I supply the judgment.