glacials
Joined 13 years ago
Karma
964
Submissions
170
Member since
Dec 2
Recent submissions
Comment · 2 months ago
If you run a statically generated website, I recommend append-only generation, where you keep your `dist/` (or whatever web root) stateful between builds. This guarantees you don't break URIs even if the static generator changes or the source content is removed.
You can even make an orphan branch and check out that branch into `dist/` as a worktree to keep it under version control.
Comment · 2 years ago
This reminds me of Exist[1], although their inputs are mostly automatic and so the data quickly becomes overwhelming and tautological ("you spend more time active when you work out for a longer distance"). Glad to see another entry into this space.
[1]: https://exist.io
Comment · 2 years ago
Location: Seattle, WA
Remote: Yes
Willing to relocate: No
Technologies: Ruby, Go, Python, TypeScript
Résumé/CV: https://twos.dev/cv.html
Email: [email protected]
Ten years in the industry. I was #90 at Twitch and grew it to its $1B Amazon acquisition. I've been successful backend and full stack.
I have a special eye for increasing developer velocity. I thrive in small companies with teammates who trust each other, where I can wear a lot of hats and have autonomy to solve pressing issues without much process.
Comment · 2 years ago
This is an amazing story and a clever innovation. I cannot fathom why the author is so upset about it.
Comment · 2 years ago
I'm not the dev, but based on the source it looks like Mongo: https://github.com/vasanthv/webtag/blob/main/server/collecti...
Comment · 2 years ago
Location: Seattle, WA
Remote: Yes
Willing to relocate: No
Technologies: Go, Ruby on Rails, Python, TypeScript
Résumé/CV: https://twos.dev/cv.html
Email: [email protected]
Ten years in industry. I was #90 at Twitch and grew it to its $1B Amazon acquisition. I've been successful backend and full stack. Very experienced in Go and Ruby on Rails.
I have a special eye for increasing developer velocity. I thrive in small companies with teammates who trust each other, where I can wear a lot of hats and have autonomy to solve pressing issues without much process.
Comment · 2 years ago
One place I'm surprised I don't see this more is sets. In my experience arrays are used without a second thought when any collection type is needed.
Comment · 2 years ago
Location: Seattle, WA
Remote: Yes
Willing to relocate: No
Technologies: Go, Ruby on Rails, Python, TypeScript
Résumé/CV: https://twos.dev/cv.html
Email: [email protected]
Ten years in industry. I was #90 at Twitch and grew it to, through, and past its $1B Amazon acquisition. I've been successful in backend and low-JS full stack roles, including bleeding edge HTML/CSS. Very experienced in Go and Ruby on Rails, experienced in TypeScript and Python, polyglot otherwise.
I have a special eye for, and experience in, increasing developer velocity and improving developer experience internally and externally. This includes writing documentation, automating its publishing, building command-line tools to capture complex flows, building CI/CD, writing and speeding up tests, building service templates and service generators, and more.
Have spun up and maintained infrastructure in Terraform, AWS CloudFormation and CDK, Docker, and Kubernetes.
I thrive in small (< 100) companies with teammates who trust each other, where I can wear a lot of hats and have a lot of autonomy to solve the most pressing issues without much process. I do however recognize the importance of measuring outcomes and I am self-sufficient at doing so.
Comment · 2 years ago
- Location: Seattle, WA.
- Remote: Remote or onsite in Seattle.
- Willing to relocate: Not willing.
- Technologies: Go, Ruby / Ruby on Rails, Python, TypeScript, AWS. Interested in Haskell and Elixir.
- Résumé/CV: https://twos.dev/cv.html
- Email: [email protected]
- Website: https://twos.dev/
I'm a staff/principal level Software Engineer, full-stack for low/no-JS or backend otherwise. I've worked "in the open" a lot so bonus points for working on open source and/or community management. I have a lot of experience moving monolithic apps to microservices, from the Rails → Go move at Twitch.
- Email - [email protected]
- Open source - github.com/glacials
[ my public key: https://keybase.io/glacials; my proof: https://keybase.io/glacials/sigs/xZFwICTyYo257X_iSnEUDl7UnvumB-6pzml0UBrXxCk ]