perspectivezoom

Not the OP project, but I made my entire 731 prompt Claude Opus 5.0 transcript searchable and organized at https://vertumnus.fyi/about/transcript. The chapter section has all of the prompts chronologically. The entire text is about ~2 MB and can be downloaded at https://github.com/perspectivezoom/vertumnus/blob/main/data/....

Yes, D3. There are 8 external dependencies for the entire project (React is one of them), enumerated at https://vertumnus.fyi/about/licenses/#software.

> Also it has a picture of an avocado and no data about avocados.

If you're referring to the middle left picture in SF, that's actually a plum from Vacaville, CA: https://pomological.art/watercolors/POM00005135.

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.

I decided against a legend because I thought that it was self evident. Maybe not... https://vertumnus.fyi/about/transcript?view=topic%3Aposter-f...

  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.

Location: San Francisco

Remote: Yes

Willing to relocate: No

Technologies: TypeScript, React, NextJS, NodeJS, GraphQL, Ruby on Rails, Python, HackPHP, SQL

Résumé/CV: https://www.linkedin.com/in/perspectivezoom/

Email: hn@perspectivezoom.com

Hi, I'm Michael. Product developer. Formerly at Facebook and Flexport. Full stack, but recent projects have been more frontend focused. Preference for slightly boring problems that provide real business value.

I just watched a video about this, that basically goes over all your points: "Air Cargo's Coronavirus Problem" by Wendover Productions https://www.youtube.com/watch?v=r2oPk20OHBE

A summary of the video:

- Passenger flight belly cargo used to be responsible for 25% of air cargo capacity, so capacity is severely reduced.

- PPE emergency logistics has caused a huge spike in demand, since PPE allocations are currently too volatile for anything except for air cargo. Air cargo prices are high.

- Government funding for airlines require pilots to remain on salary, so there's no additional marginal cost of labor.

- The biggest marginal cost of a flight, the cost of fuel, has understandably also become very cheap.

The end result is that even though it's still quite inefficient as compared to dedicated freight planes, the perfect storm of circumstances makes passenger-planes-as-cargo-planes momentarily profitable.

Nice job. You may want to take a look at https://github.com/gaganpreet/hn-hiring-mapped/, who wrote a python script to extract location info from who's hiring posts. (Demo at http://gaganpreet.github.io/hn-hiring-mapped/src/web/)

I was thinking about spec compliance. I think the best thing would be to provide these guidelines in the whoishiring post, and then ask that those who follow the guidelines put a unique string, like "metafriendly" or "whoshiringspec" at the end of the post. Then those of us who write mini-apps would know that the post conforms to the format.

Yaml I think would take too much vertical space and make reading the normal thread not as useful as it is right now.

Yes. Please add a way to reliably determine metadata on hiring posts. I wrote https://github.com/perspectivezoom/curated-hn-hiring but abandoned it after a couple months because it took way too much time to tag all posts.

By far the most important information seemed to be location and/or remote filtering. Gaganpreet stepped up and is doing a pretty good job with https://github.com/gaganpreet/hn-hiring-mapped, but it's still not 100%.

I would really love for whoshiring to provide this pipe-delimited template, and then optionally allow posters to conform to it. I also agree with danso's order of importance, but would also like to add that the location string(s) should be something geocodable by Maps APIs (ie, feed the string in and get an unambiguous LatLng).

Location: San Francisco or East Bay

Remote: No

Willing to relocate: Probably not

Technologies: SQL, Ruby on Rails, Backbone/Marionette

Resume: https://www.linkedin.com/in/perspectivezoom https://github.com/perspectivezoom

Email: hn at perspectivezoom.com

Looking for a full stack position at a good startup.

San Francisco Bay Area, Local, Full-Time

Stack: Ruby on Rails, MySQL/Postgres, Backbone Marionette, SASS

LinkedIn: https://www.linkedin.com/in/perspectivezoom

Contact: hn@perspectivezoom.com

I'm a full-stack web developer with significant Ruby on Rails experience. I have a history of pairing and TDD. Looking for a good team to join and to challenge myself a bit more.

Creator of curatedhnhiring.com here. This is good stuff. I'm going to hand enter all the locations for October tonight, but you can compare your auto-generated September data against https://github.com/perspectivezoom/curated-hn-hiring/blob/gh.... Also, I don't know if you care about accommodating this, but a lot of HN Who's Hiring posts list multiple locations.

In its current implementation, once the JS gets your computer location, I just store the data in window.currentLocation. Until I add the functionality, you can start a location sort, and modify the latitude longitude coords in window.currentLocation to Boston in the console. Then click a filter on and off to trigger a re-sort.

Fixed. While fixing, I found another bug where double clicking within 400 ms breaks off the animation and prevents the complete callback from firing, but I'll worry about that another day.

Yep, the same level thing is a pickle. Like you, I'm determining top level comments via the same "s.img" indentation image with. Feels terrible, but it works.

Same with the comment time. Looked into the Sort by Recently Added request, and there's no good way to do it without polling.

Regex Filter added

I tried doing a header bar with company name, but it looked super redundant for the majority of postings: Company Name followed by Company Name. Problem is, the first line sometimes contains other information too, so I couldn't just cut it out. I would have to curate the comment body itself at that point. Maybe next time.

Bumped the padding a little.

So, to get location, I looked at each entry and typed in the city name, then ran those locations through the Google Maps geocoding API. To get more specific locations, I would have to get the address of each company, which generally isn't posted. Maybe LinkedIn API to grab the address, based on company name? Haven't played with that one yet.

Source: https://github.com/perspectivezoom/curated-hn-hiring

I wrote it in about a day, so there's a lot of jenky code. Just wanted to get it out there and see if it's worth spending more time on.