Skip to content
View joshuazap's full-sized avatar

Block or report joshuazap

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.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

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

Report abuse
joshuazap/README.md

Hi there, I'm Joshua Zapata 👋

Rails / TS / Postgres. I read the whole diff.

I ship Rails, TypeScript, and React. 15+ years in production. I like messy repos, sharp reviews, and systems where the data has to be right.

GitHub followers LinkedIn


🔭 Current: Technical lead on Rails and API work for the Kansas Department of Commerce (remote). Government repos, partner integrations, Postgres, CI. Frequent bouts of people-managing without the people-manager title.

🌱 Lifelong learner: Directing Cursor / Claude on real features, then reviewing the tool trail and the tests. Still adding languages and frameworks the old-fashioned way too.

👯 Collaboration: I like pairing on the hard path: the schema, the failure mode, the deploy that has to be reversible. DMs open for OSS that needs a production-minded reviewer.

💬 Let's talk about:

  • Full-stack development
  • Ruby on Rails
  • SQL and all its variants! (MySQL, SQLite, PostgreSQL, etc.)
  • JavaScript/TypeScript
  • Reviewing agent-written code (what to keep, what to throw back)
  • Agile Methodologies
  • Microservices vs. monolithic architectures
  • Building seamless, responsive user experiences
  • Maintaining scalable, maintainable back-end architecture

📫 Reach me at: joshuazap@gmail.com

📄 Know more about me: LinkedIn · Zapata's Studio


  • 🔭 Lately: Rails / APIs / Postgres / DevOps for Kansas Commerce. Before that, multi-tenant billing and funding SaaS (Stripe, React, AWS).
  • 🌱 Currently learning: better agent workflows, and whatever the next production fire teaches me.
  • 👯 Looking to collaborate on: open-source with real users and a real database.
  • 🤔 Looking for help with: interesting production bugs, not LeetCode.
  • 💬 Ask me about any of the following technologies and tools!

🌟 Achievements

  • 🚀 Built the matching flow that got clients in front of the right lawyers without the usual spreadsheet tax.
  • 🛠️ Shipped platforms and apps with SEO and the boring reliability work (tests, monitors, deploys that finish).
  • 📊 Got monitoring adopted so we stopped arguing from memory and started arguing from graphs.
  • 👨‍🏫 Lots of review and pairing. I would rather walk through a weak approach, then the better one, than drop a LGTM.
  • 📉 Postgres query times down ~50% on a high-volume API. A Node leak that was eating ~1.6 GB/process, found and closed.
  • 💳 Stripe billing and webhook state on a multi-tenant app. Money paths get tests.

🛠️ Technologies and Tools

Frameworks

Ruby on Rails Angular Angular.js Meteor JS NPM React Router NodeJS Spring TailwindCSS Vue.js React React Native Pug SASS Styled Components Webpack Yarn

Languages

Ruby GraphQL HTML5 JavaScript Python TypeScript CSS3 Elixir

Databases and DB Tools

Redis MicrosoftSQLServer MySQL PostgreSQL ElasticSearch AmazonDynamoDB Neo4J Firebase MongoDB MariaDB SQLite

Dev

Git GitHub Actions GitLab CI GitHub

Testing

Jest Mocha Selenium RSpec

CI/CD and Hosting

AWS Heroku Linode Render Docker CircleCI Stripe

Collaboration & Document Management

Trello Indeed Zoom Slack ChatGPT Cursor Dependabot Google Assistant Markdown Microsoft Office Notion HackerRank Upwork

Pinned Loading

  1. nimblist nimblist Public

    Archive (2016): Rails to-do list that expires unfinished items after seven days.

    Ruby

  2. wikibed wikibed Public

    Archive (2016): Rails wiki with public/private pages and collaborators.

    Ruby

  3. bloc-jams bloc-jams Public

    CSS