Skip to content
View jasonblanchard's full-sized avatar

Organizations

@GreenSTEM-Network

Block or report jasonblanchard

Block user

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.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
jasonblanchard/README.md

Hi there, I'm Jason 👋

I am a builder who loves working across the stack1. I get immense joy from putting things together and seeing them work, "things" being features, bug fixes, systems, teams, companies, and everything in between.

🌱 Things that have inspired me

  • Evolutionary Architecture2 - theoretical underpinning for what has become my first principle of software architecture: there is no such thing as a perfect system, only systems that are more or less fit for their environments. Our job as software architects is to iteratively make our systems more fit for their environment, w.r.t. both the technical landscape and the business drivers. This is the "what" and the "why" behind software architecture.
  • Simple Made Easy - inspired the second principle of sotware architecture, which is: simplicity. But! It's a very specific kind of simplicity. Not necessarily "easier" or "more familiar" or "with less stuff," but more "decomplected," or "less interleaved/intertwined". This is the most fundamental "how" of software architecture.

😅 Talks I've given

🔧 Tools I'm excited about right now

I was initially excited to write this section, but I decided to scrap it because it changes too often! The inspiration section ⬆️ is far more evergreen and drives what tech I'm excited about at any given moment.

Footnotes

  1. Seriously. I have probably shipped just as much code for React frontends as I have the APIs that back them and the infrastructure that runs it all :)

  2. Up to but very much excluding the "microservice everything" recommendation. That's one way, but not the only way.

Pinned Loading

  1. ts-result ts-result Public

    TypeScript

  2. protoc-gen-connect-mock-server protoc-gen-connect-mock-server Public

    Go

  3. natsby natsby Public

    Natsby enables NATS-driven services

    Go

  4. chatctl chatctl Public

    Go