Skip to main content

Show HN: I built a Chrome extension to save job postings to Google Sheets https://ift.tt/GPo7tUE

Show HN: I built a Chrome extension to save job postings to Google Sheets Hey HN - I built a Chrome extension that adds a button to LinkedIn, Indeed, and Lever to autosave the job's title, company, and link in a Google Sheet so you can organize all your job applications in one location. I used to open a bunch of tabs to apply for jobs that I never ended up applying to bc I was either lazy or it got too messy to keep track of. AKA I never went back to that tab again The extension has really helped me navigate my own job search and I wanted to share it with anyone looking for a simple and beneficial tool. What's great about this extension: - It's free forever - just trying to help people find a job - No sign up needed - works with your Google account - Saves job postings directly to Google Sheets - You can customize and edit the spreadsheet however you want - Integrates with LinkedIn, Indeed and Lever - Adds a button on the website - no more switching between tabs or copy/paste I hope this helps at least a few people with their job search :) If you do try it, I'd love to hear your thoughts on how it can be improved! https://ift.tt/8LPKf13 July 14, 2022 at 10:57PM

Comments

Popular posts from this blog

Show HN: TypeScript query builder with full type inference https://ift.tt/xZp9HOm

Show HN: TypeScript query builder with full type inference Hey HN! Colin here - a TypeScripter, open sourcer, and engineer at EdgeDB. As the creator of Zod and tRPC, I'm interested in designing tools/APIs that use type inference and generics to make life easier for devs. This query builder represents another step in that direction. We set out to build an EdgeQL query builder that can express queries of arbitrary complexity (EdgeQL has feature parity with SQL, roughly) and infer the static type of the query result. We introspect the database and generate a schema-aware client that represent any query, including ones that use built-in functions, operators, string/array/tuple indexing, aggregations, conditionals, type casting, subqueries, computed properties, etc—things most ORMs can’t represent. This post mostly discusses the API design, which I think will be interesting regardless of familiarity with EdgeQL. I’d love to see some of these ideas bleed into future generations of TypeSc...