Here is a diagram of the products that I've worked on in the past 2 years.

Send an email if you want to learn more.

Building on an idea I've touched on before paired with some new thinking, I've created a visual representation of well being. I included a present, and a reference example from my recollection of roughly 2015-16 era, shortly after moving to SF. For those unaware, I became homeless after slander from a manager at a big name company destroyed my reputation and I was unable to continue my career and depleted my savings.

2019

Homeless in SF:

2015

Updated the resume. Got creative with job titles and added an icon before the portfolio link.

Auth is short for authentication and authorization both;

Here we focus mainly on the authentication aspect with an opaque authorization.

Authorization is granted with knowledge of the path component.

Path components can be hashes of a combination of the user, role, and/or buckets.

Here is a quick design that I’ve been thinking about for a little bit.

Podcast.

Being homeless sucks. Everything needs to be done in public and requires care, meanwhile energy levels are less than average.

Awkward eye contact. Awkward questions when physical needs are unmet. Awareness stirs in all around. Few are comfortable.

I can’t really talk about anything personal. It makes people feel bad. Less contact with people is better.

Contrary to the personality assessment that companies do when they hire you. I can pass a simple questionairre.

Download MP3

A doodle of the capabilities of the Clojure ecosystem.

Experiments are mostly in my GitHub repo, except some recent front-end and transactional demos. If you like to read, check out my portfolio. Check out the Timeline for recent pictures and podcasts.

Here's a drawing that I made to explain my concept of the gradient between static websites and SPAs in the Clojure and ClojureScript ecosystem, in my experience.

There are surely other versions of this that would be valid and could be explored. Enlive is the newest tool to my landscape and I've yet to Proof-of-concept with it and Kioo, but they address a problem that I notice with every template system: the first template usually needs to split up body and head and address the declarative/DOM update imedence mismatch related to title and styles.

I come at this from the infrastructure side, catching myself up on front-end in 2019 after a few years.

Click the image for a PDF.

Here's a drawing of transaction vocabulary.

Here we go with another revision to the resume.

Most feedback was to take the Day Labor job off, even though it's current. I've noticed patterns in feedback and may bring it back from time to time, but overall I think I'll leave it off. I can refer to what I am presently doing verbally, and the consensus is that software engineers don't need to explain gaps in their employment. Plus I have a long and diverse history. But the argument I like for keeping it on, is that it shows I am actively doing something for work, and in a sense it's not glamorous and can explain non-verbals to recruiters, such as being dressed shabby or talking like an uneducated person.

The latter point and this whole process has made me aware that I need to interact with educated people more. I've been put into isolation in a sense for making people too uncomfortable with my Honey Boo Boo conservative values, but the more a person is isolated the worse they become... I digress for now.

I've also been working on my website / portfolio more, and shortened the link so it'd fit directly in the resume header. I removed the title of "Software Engineering Professional" to make some space, but I kinda like it. In a sense most people who get the resume should know what I do, but not everyone may. The uniform titles kinda give it away.