Hello. My name is Mike Burr. I live in Santa Fe, New Mexico. I've been a "technology"
(computers) related engineer for my whole professional life. Drop me a line if you would like any other information at about me or my work. I don't even mind texts if you are human:
area code six six nine 800 7593
I've drifted from thing to thing over the years, but I'm most interested in collaborating
or even being paid for involvement in
- Blockchain, primarily Ethereum, and pretty much anything else in that universe.
- Programming. Lately it's been with Rust.
- Gentech. I have almost zero formal "wet science" education, but I do have a pop-sci
level of knowledge and some recent level of involvement.
- Git* powerusing
Here is some portfolio-like information (in no particular order) that you may be interested in if judging my suitability for employment
(or even just regular judging).
- Abandoned Addresses, an elaborate
exercise in web3 (Ethereum) stuff, that may or may not be directly useful. A live demo
is available. You need to have Metamask (or similar), and be on the Rinkeby test network. To use all
functionality you will need a small amount of (Rinkeby test) Ether, which
I am happy to send upon request. You can also use
a faucet. Note that this project includes "web3"
- Various Rust learning and experimentation (Please note that I am still learning Rust, just like you.
Yes I have read the book!)
- My first crate -- A very simple
cargo install-able utility that solves a very simple problem (CLI HTTP file server.)
- The most recent Rust commits to my Github account -- This is sorted recent-first and includes basically all of my original Rust work (lately), as opposed external repos I have forked or "big" projects, which are listed separately below.
- Added serialization support
- Web3 meets Rust Wasm --
I have been working for weeks on trying to get Rust "web3" code (that is, Ethereum dapp code) to
successfully compile to wasm usable by a web browser. The idea is to replace things like
ethers.js with code written in Rust that compiles into wasm
and is usable in their stead.
It turns out to be a hard problem! This particular Rust package
is very simple (although it took months of study): A minimal Rust wasm project that includes
rust-web3. So, importantly, it doesn't DO anything. But is a good starting point
for a Rust wasm+web3 project.
I've written plenty of original
rust projects, this is just the minimal intersection of the two, roughly speaking.
Hint: If you are interviewing me, I would love to discuss the details of this problem and the various hurdles.
- spelib -- a very simple
spellchecking library that uses the above BKTree serialization to store the nearest-neighbor tree
word tree generated from a word file. Processing the word file and creating the tree takes 1+ minute.
deserializing the result on subsequent startup is sub-seconds in scale.
- Burger Chef -- a
playground I created to experiment with the BKTree serialization problem. What is interesting in
this package is that the short file you see in
src/main.rs is after weeks of
experimenting with serialization strategies (which is in the repo history) until I realized Rust
has it handled! What a ride.
- A Julia set explorer -- I did
not write this! But, it's amazing and I can explain the code to anyone who will listen. I read the
whole wasm book (and more), and this simple thing really stood out for me. Wasm lets you get amazing
performance out of client-side browser code.