Block or report nmccready
Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.
You must be logged in to block users.
Contact GitHub support about this user’s behavior. Learn more about reporting abuse.
Report abuse📄 Resume
Senior engineer with 23+ years of turning caffeine into production systems. Been shipping code since 2003 — did 9 years for the DoD before going private sector. Currently deep in AWS, Go, and TypeScript — though I've written enough JavaScript to qualify for a support group.
US patent holder. Open source maintainer. Somehow responsible for packages that get half a million downloads per week and I'm still not sure how that happened.
| Package | Weekly Downloads | What it does |
|---|---|---|
| debug-fabulous | ~526k | Lazy-eval debug logging that doesn't murder your CPU |
| angular-simple-logger | ~8k | Logger for AngularJS apps that refuse to die |
| cfn-include | ~4.6k | CloudFormation preprocessor for the brave |
| angular-google-maps | ~2.2k | Google Maps + AngularJS. Yes, still. |
- AWS — if it's a service, I've probably broken it at least once
- Go — for when you want your code to compile faster than your coffee brews
- TypeScript — JavaScript but with a conscience
- Open Source — maintaining packages people depend on, whether I like it or not
- Infrastructure — Terraform, CloudFormation, and the quiet desperation that comes with YAML
- 🧱 brickhouse-tech — my tools & products org. We adopt orphaned npm packages and give them working CI.
- 🤖 aws-sdk-go-v2-ifaces — auto-generated Go interfaces for every AWS SDK v2 service. Because mocking AWS shouldn't require a PhD.
- 🥍 lax_cread — lacrosse stats site, because my kids are faster than my deploy pipeline
if it's broken, fix it if it's abandoned, adopt it if it works, ship it if it's YAML, pray
124 repos. 160 followers. 1 patent. Mass amounts of mass. Mass amounts of code shipping in mass amounts of time; this has been called alarming.
Pinned Loading
If the problem persists, check the GitHub status page or contact support.