HN user

thisjeremiah

10 karma
Posts0
Comments9
View on HN
No posts found.

Location: Portland, OR

Remote: Preferred

Willing to relocate: No

Technologies:

Languages: TypeScript/JavaScript, Python, HTML/CSS, GraphQL, SQL, Bash

Frontend: React, React Native, Tailwind CSS, Apollo, Redux, Rollup, Vite, Jest

Backend: Node.js, Express, SQLite, PostgreSQL, Next.js, Docker, Vercel, AWS, GCS

Tools: Terminal, Git, Neovim, tmux, npm, FFmpeg, MacOS/Linux/Windows

Résumé: https://www.dropbox.com/t/kN2cRdtOOhHuWrOs

CV: Available upon request

Email: jeremiahmontoya at hey.com

Hi, I'm Jeremiah! I have 8 years of experience in systems architecture and fullstack web development.

At my current company, I am responsible for leading the development of SVRunner, a software platform that powers some of the biggest, most iconic LED screens and art installations in the world. As an early employee, I was instrumental in founding and designing the initial product, including the GraphQL API and dynamic scheduling algorithms. Now I oversee the building of control systems and media players using a primarily web-based stack. On the frontend, I write code using React, Apollo, and Tailwind CSS to produce high-performance, fault-tolerant web applications. On the backend, I help create services running Node.js using Express and Apollo server frameworks, PostgreSQL, SQLite, and ElasticSearch databases, and FFmpeg for media processing. I collaborate on these solutions with design, product, QA, and marketing teams to make the best user experiences.

During my time at the company, I've spearheaded many developer quality-of-life improvements including a full code migration to TypeScript, a consolidation of repositories to a unified monorepo, a switch from webpack to ESBuild and Rollup, and most recently an adoption of Turborepo to improve build times and streamline releases. I would love to help bring about these kinds of changes to a new company.

I've worked hard to hone the skills I have, but I know I still have a lot to learn and I'm eager to grow my skills within the unique needs of a new organization!

I think the recommended pattern is something like:

If you’re using a component based framework (e.g., Vue), you create a named component.

If you’re not using a component-based framework, you create named classes with applied atomic styles.

With either approach, your styles are contextualized with a name and can be reused.

https://tailwindcss.com/docs/extracting-components

We’ve been following a similar process for our internal tools and have found it to be a good solution. Manually including native libraries is probably the only lousy part. Out of curiosity, what are you using to achieve the windows service installation? We’ve been using nssm, which has worked okay, but I’m curious if there’s a better way of doing it.

if the progress of prettier (js) over the past few years is any indicator of what will happen with black, there will likely be incremental improvements in black that address the poor formatting cases you’re concerned about. i remember when prettier first came out, i was not convinced until my “standard” for formatting was met. but it was met eventually.