There's some code to prefer the produce you select, but there really aren't that many unique fruits in the collection; just lots of varietals of the same fruit.
https://pomological.art/watercolors is pretty neat. You can see that there's 3788 apple drawings, far more than any other, and it quickly dies down to 959 peaches and 445 pears. For any given region, there's only like ~7 unique fruits to draw from.
Oh, neat. I submitted this a few days ago, and it got no traction back then. Thanks mods for giving it a second chance.
I probably should mention that I'm looking for new opportunities. My LinkedIn is at https://www.linkedin.com/in/perspectivezoom and you can reach out there or at hn@perspectivezoom.com.
Yes, this is correct. Realistically, you only care "is it there", and "is it there and good", and those are the two levels. For SF, I'm using shipment volume as a proxy for ripeness, on the assumption that the best produce occurs when you're shipping the most of it. The shaded parts are when the annual history says that it's only good in some years but not others.
Location: San Francisco
Remote: Open to onsite, hybrid, or remote (and have worked in all 3 environments)
Willing to relocate: No
Technologies: Typescript, React, Python, GraphQL, PostgreSQL, Rails, NodeJS, NextJS
Résumé/CV: https://www.linkedin.com/in/perspectivezoom
Email: hn [at] perspectivezoom [dot] com
Full stack product web engineer with 10+ years of experience focused on delivering business value. Have worked at Rippling, Facebook Ads, and Flexport. My sweet spot seems to be hardening B2B SaaS apps from the "tech demo" stage into a robust product, but that is a starting point, not a constraint. I have delivered value to smaller companies, larger companies, and consumer facing companies too.
In the middle of a few virtual onsites, but can squeeze in one or two more, I think.
I will second git-spice. It does exactly what you want and, importantly, no more than that. There's no upsell to anything else; it's "just" a good tool that knows its purpose and boundaries.
Location: San Francisco
Remote: Open to onsite, hybrid, or remote (and have worked in all 3 environments)
Willing to relocate: No
Technologies: Typescript, React, Python, GraphQL, PostgreSQL, Rails, NodeJS, NextJS
Résumé/CV: https://www.linkedin.com/in/perspectivezoom
Email: hn [at] perspectivezoom [dot] com
Full stack product web engineer with 10+ years of experience focused on delivering business value. Have worked at Rippling, Facebook Ads, and Flexport. My sweet spot seems to be hardening B2B SaaS apps from the "tech demo" stage into a robust product, but that is a starting point, not a constraint. I have delivered value to smaller companies, larger companies, and consumer facing companies too.
Note that I am currently on holiday, and will not be responding to reachouts or updating my woefully outdated LinkedIn profile until Monday, July 13th.
I'm a heavy user of git-spice: https://abhinav.github.io/git-spice (created by a former coworker) and can't really go back to a time without it. While still not nearly as good as Facebook's Phabricator, it's probably the best workflow for small, focused stacked PRs you can achieve in a Github / Gitlab based repository.
I was Triplebyte's first engineering placement. I still remember going to a random SoMa apartment with Harj and Ammon and Guillaume and coding up tetris in ruby, having no prior experience with game loops. That landed me a job with Flexport in 2016. I doubt that I would have gotten that placement without Triplebyte. So I am quite grateful that they existed, for jumpstarting my early career.
With that said, when it came time to look for a job again a few years later, I did chat with Triplebyte but ultimately took an offer through other contacts that I had built up by then.
After my (virtual) TB interview (which I barely passed), I had onsites at 5 places. After the five on-site interviews, I had 2 job offers, one of which was a company I wanted to work for since graduating college. I took the other offer.
This was preceded by a four or five month job search. I had received two offers in that time, but nothing seemed great.
I think TB's process kinda worked, but I understand your skepticism.
I'm actually not all that skeptical of TB's approach. They built a real business around it, way more targetted than eg Karat. Even though ultimately unsuccessful, that is surely more due to PMF and various missteps, than to lack of advantage for individual applicants vs spray and pray approach. (When taken as an average across all applicants.)
I'm just highlighting that GP's specific anecdote doesn't really demonstrate that advantage. Your example seems much more clear.
Somewhat OT for this specific sub-thread but I wonder how much "OA" tools that are part of coderpad etc, contributed to TB's demise. These are meant to be fizzbuzz kind of pre-screens. I know TB's approach was more than that, but from the hiring side, was the value not there since you'd always (?) have your own coding exercise after the TB screening.
reply