Filling gaps and building bridges
I operate across teams and disciplines, filling gaps rather than owning a single lane. I’m most effective when I can take an idea and turn it into a working system that other people can react to and iterate on.
staff@silverservers:~% /bin/bash ~/personnel/blake-noble.sh
Exploration
Random Ideas into Real Insights
Experimentation, feasibility studies, and small-scale prototypes that turn vague concepts into concrete learnings.
Execution
Building the first real thing
Initial implementations, reference systems, and prototypes that prove a path forward and establish technical direction.
Iteration
New features and improvements on existing systems
Ongoing development and maintenance of existing systems, adding features, improving reliability, and keeping things healthy over time.
Something I built
Q-learning, live
Dozens of agents teaching themselves the fastest path across a grid — a little reinforcement-learning toy I built. How it works
- Start
- Goal
- Wall
- Learned route
Systems & infrastructure
Backend services, internal tools, automation, monitoring, and integration work. Anything that needs to exist and work, even if it's not glamorous or "built to last" at first.
Interfaces & tooling
Internal dashboards, staff-facing tools, and UI layers where usability directly impacts efficiency. Built to be obvious, predictable, and easy to extend.
Physical & hybrid systems
Sensor systems, hardware-adjacent software, and projects where real-world constraints need to be reconciled with digital systems.
Working style
I work best with clear intent, fast feedback, and permission to iterate. My default approach is to produce a small, concrete artifact early, then refine based on real usage rather than speculation.
When to loop me in
- Something needs to exist quickly so people can react to it
- A system works, but nobody fully trusts it
- A project spans software, hardware, or unclear ownership
- The question is "can we do this?" rather than "how do we polish it?"
In short
My job is to fill gaps, connect dots, and build the first real thing that turns an idea into a shared reality. If that sounds like what you need, I'm your guy.
About me
I approach work with the steady curiosity and careful attention of someone who likes to build things. Over time I've learned that the best systems aren't the loudest or the flashiest, but the ones you can trust — and the ones that feel right under your hands.
There’s a bit of a dragon’s mindset in how I think about that: focus on the core, keep what’s valuable safe, and let refinement happen at the pace of thoughtful discovery rather than hurry.
Outside of day-to-day engineering, I enjoy making physical things, exploring creative projects and characters, dragons, and finding unexpected intersections between the digital and physical worlds.
