<aside> đź““ just trying to have a net-positive effect on the world Senior Principal Engineer @ Comcast/NBC Universal

</aside>

<aside> đź“« @zeushammer on every platform [email protected]

https://github.com/zeushammer https://www.linkedin.com/in/zeushammer

</aside>

<aside> 🏫 CS @ UNSW Sydney Prev. CS @ Diablo Valley Stanford Honors Speaker & Mentor Math & Physics @ UNL

</aside>

<aside> 🦆 Projects

</aside>

<aside> đź’­ Tensors and Transformers From: Scratch

I’ve always admired the ability to explain things simply. I always, always took everything apart. To the great detriment of my computer tinkerer Grandfather who would buy a new computer and gadget only for me to promptly disassemble it.

It’s 2024 and I’m now teasing apart complexity so I can explain to others and to myself. To understand it’s story and marvel at all it’s lego pieces that bring together ideas.

Why do they call it a Tensor?

I always loved geometry. Like a drawn picture tries to capture a feeling. So to does a Tensor capture the geometry of something. Like the geometry of a triangle, or of several triangles put together. A Tensor ends up looking like a matrix. Similar to how a picture ends up looking like colored lines on paper. They are both representations of “something” in another form.

More …

</aside>

<aside> 🎇 **Internet of “Things” Engines

S**tability, throughput and scale was my focus when my team and I first built the 1.0 engine open source - ‣ - 59 Forks, 337 stars - used by Amex even

Highlights:

Rules Engine

Pluggable Languages and Libraries

Circuit breakers

Timeouts

Replay on Failure

Optionally embed on “devices”

TLDR:

Processing events is the goal. Here's the the flow for an incoming event:

  1. Find relevant rules.
  2. For each rule, evaluate the rule's condition.
  3. For each set of bindings that satisfies the rule's condition, execute the rule's action.

We launched to 22 million live customers. We created a front-end using what we thought was the latest tech, Polymer and built deploy-able templates users could instantiate with a sentence based structure to automate a “thing”.

More …

</aside>

<aside> 🆕 Do A Startup At Least Once

It would seem, humans have the ability to think of something like a shed and then go and build that, in “real life”. It’s cool and frankly I always yearn to see just what I can create.

I came to California with that very intent. To do startups. Whatever and however I could. What better way than to start my own right?

One of my proudest accomplishments. Founder and CTO. Here is some of what I learned.

More …

</aside>

<aside> 🧭 Hard Skills

**My most “hard skill” is that I am the fastest and most curious learner. Consider me not on what I’ve learned already but what I am capable of deeply understanding in the future.

Product & Engineering Leadership Golang, Javascript, Python, SQL, NoSQL, Linux AWS (most core services) Distributed Systems Data Science

</aside>

<aside> đź–– Grew up in the Bay Area, California slinging tech Born in Nebraska on a farm, raising horses

</aside>