Full-stack engineer, fifteen years across automotive, finance, defense, healthcare, and agriculture: General Motors, JPMorgan Chase, L3Harris, T. Rowe Price, Nutrien Ag Solutions, RumbleOn, Integrated Auction Solutions, Brierley + Partners, Kofile Technologies.
Now Lead AI Engineer at OffensiveEdge, building an end-to-end machine learning platform and the LLM product on top of it: training and serving, a ReAct agent harness with tool-calling and hybrid retrieval, and a public prediction ledger anchored to Bitcoin via OpenTimestamps and to the Sigstore Rekor transparency log. Earlier, lead developer on the first multilingual EMS communication platform: Texas Fire Chief's Lone Star Achievement Award, EMS World Top Innovation Award, a patent, acquired by ESO Solutions.
Nearly all of that is private. This account is where the open source is, and it started as an experiment: I never had time to publish, so could an LLM get me to a bar I'd sign my name to without taking anything from primary work? The code was built with an LLM. I'm not hiding that, and I'm not selling it either.
The bar is mechanical. Coverage floors, accessibility gates, payload budgets, and visual baselines run in CI, and generated code clears the same standard as hand-written or it doesn't merge. Axe runs on every page, in both themes, because I spent years on ADA / WCAG / Section 508 remediation at Fortune 500 scale. Users don't grade your code, they grade whether the thing works, so the scoreboard is downloads.
nolindnaidoo.com · LinkedIn is the fastest way to reach me.
letools.dev — 16 tools, all 16 published to Open VSX and the VS Code Marketplace, and all 16 on the official Model Context Protocol registry so agents get the same interface editors do. Counts come from the registries' own APIs, not from me.
Local, deterministic, exit codes as the API.
envsync-le |
spot missing keys across your .env files, with a markdown report |
secrets-le |
detect and sanitize credentials locally, before you commit |
regex-le |
find, test, and validate regular expressions with ReDoS screening |
scrape-le |
check whether a page is scrapeable before you write the scraper |
unicode-le |
find the Unicode that hides meaning: bidi controls, invisibles, homoglyphs, mixed scripts |
versions-le |
find where one dependency is constrained differently across a repository's manifests |
i18n-le |
identify the i18n library a project uses, then audit its catalogs by that library's rules |
string-le |
extract string values for i18n from JSON, YAML, CSV, TOML, INI, .env |
numbers-le |
extract numeric values from JSON, YAML, CSV, TOML, INI, .env |
dates-le |
extract and analyze dates from logs, configs, and code |
paths-le |
extract file paths from JS/TS imports, JSON, HTML, CSS, TOML, CSV, .env |
urls-le |
extract URLs from documentation, configs, and code |
colors-le |
extract and analyze colors from CSS, SCSS, LESS, Stylus, HTML, JS/TS, SVG |
units-le |
extract every quantity with its unit, normalized, and refuse the ambiguous ones by name |
ids-le |
extract every UUID, ULID, NanoID, ObjectId and Snowflake, and decode the time inside |
ips-le |
extract every IP address, CIDR block and MAC, normalized and classified by scope |



