zacharytamas

Joined 15 years ago

Karma

1,647

Submissions

Member since

Apr 4

I am a full-stack software engineer based in Atlanta, GA.

I work primarily as a freelancer or contractor and have worked on web projects for companies such as Cerner and Google (currently approaching three years).

I'm always interested to hear about new projects to work on so don't hesitate to reach out! [email protected]

https://twitter.com/zacharytamas

[ my public key: https://keybase.io/zacharytamas; my proof: https://keybase.io/zacharytamas/sigs/YBzOIBVAoODb3nIrVSRkdo6il4NinAt4CyNpUGPcq_g ]

View on Hacker News

Recent submissions

Comment · 1 year ago

Location: Atlanta, GA, USA

Remote: Yes

Willing to relocate: Potentially along US east coast with a preference for NoVa

Technologies:

  - Languages: HTML/CSS, TypeScript/JavaScript, Python, Go, Java. Some: Kotlin, Swift, Scala
  - Frameworks/Tools: Node.js, React, Webpack, Django, Protobuf, Jest, Bazel, Postgres, TanStack, Tailwind, LangChain, Convex, Prometheus and Grafana
  - Skills: GCP, AWS, Vercel, GitHub

Résumé/CV: https://zacharytamas.com/cv.pdf

Email: [email protected]

Website: https://zacharytamas.com

GitHub: https://github.com/zacharytamas

LinkedIn: https://linkedin.com/in/zacharytamas

I'm Zachary. I've been writing software for about 25 years, mostly with things around the Web though I have worked a bit with hardware and IoT. Notably I've worked at large tech companies like Google (itself, Fiber, and Checks) and Block/Square, as well as others like Opendoor and Cerner.

Lately I've been building TypeScript heavy full-stack stuff. I would consider myself a fullstack-capable engineer but have swung probably 60/40 in both directions at different times.

Comment · 1 year ago

I always love to see these little git extensions. For anyone else interested in this stuff, here are some others I like:

lazygit (of course): https://github.com/jesseduffield/lazygit

git-machete: https://github.com/VirtusLab/git-machete

rebase-editor: https://github.com/sjurba/rebase-editor

Comment · 1 year ago

Since the OP is familiar with the Go ecosystem, they could probably use vhs[1] easily to programmatically create an interactive demo GIF. That has worked very well for me in the past.

[1]: https://github.com/charmbracelet/vhs

Comment · 10 years ago

Yeah... I used it initially with no TS experience, but coming back to it later I do find myself missing TS. But yeah you can use polymer-build to split the script block out of the HTML file, run it through TSC, then insert it back into the file as JS.

Comment · 10 years ago

Yeah... I remember those days. The first projects I built with it were 0.5. The migration to 0.8 was... painful. But given the huge performance improvements it was worth it.

As you said, you kinda just have to expect a little pain pre-1.0. But the time investment in learning and using it has been worth it in my opinion.

Comment · 10 years ago

Yeah that's a nice/bad thing about Polymer: how vanilla it is. 2.0 is even more vanilla. But the mantra is to #UseThePlatform and so that's what they do. The platform is becoming less burdensome than it used to be. Because of how isolated Web Components are it keeps things simple, particularly when you're dealing with DOM. Components tend to keep to themselves and interact with each other via your agreed-upon interfaces.

I also noticed the verboseness. On the projects I worked on at Google I had just made a Behavior of logic utilities that I added to components that needed that kind of behavior. So they could inherit some utilities like `_equalTo`. It wasn't ideal but it did stop the need to define essentially the same functions across multiple components.

Comment · 10 years ago

Oh I definitely agree with you. We've worked on projects with Angular 1/2, React/Redux, and Polymer and Polymer is, for me personally at least, the nicest to work with. I have grown to really like TypeScript since working in React land on recent projects but I'm excited because Polymer 2.0 will be [easily] TS compatible. Best of both worlds, I think.

Comment · 10 years ago

I think it's mostly due to browser support and developer awareness of Web Components. Chrome has native support (of course) for the four main technologies needed for Web Components, but other browsers are starting to catch on. In the meantime you need a few Polyfills to get full support, which is not ideal.

The support graph is starting to look a lot better, though: https://jonrimmer.github.io/are-we-componentized-yet/

Safari has shipped 2/4 of them already with the Custom Elements v1 spec currently in the Safari Tech Preview and turned on by default. https://webkit.org/blog/7027/introducing-custom-elements/