News for hackers. Stuff that matters.

almstimplmntd

Re:Find the flattest route between any two points in SF on Tuesday October 06, 2026 @06:25PM (#49985013)
a steepness penalty could make sense!

your example (from market & taylor to the top of nob hill) is a nice illustration: (1) straight up taylor is 229 ft of climbing at 25%, (2) via polk and california it's 251 ft at 13%.

as you probably noticed, we only look at the total elevation gain, so taylor "wins"... but I see the argument for preferring an extra 20ft of a more gradual climb.

Re:Find the flattest route between any two points in SF on Tuesday October 06, 2026 @11:36AM (#49980081)
thanks! address search uses the overture address feed, which is patchy (some blocks of 24th st have 5 numbers in it)… i'll make it fall back to the nearest known number on the street
Re:Find the flattest route between any two points in SF on Tuesday October 06, 2026 @11:33AM (#49980041)
Once I was visiting Yamaha’s Yokohama office for work, and I found a pedestrian path from my hotel to the office of ~2.5km that never touched a single roadway…

Google Maps absolutely failed.

Would be fun to rig up something for these cities. Which are you in btw?

Re:Find the flattest route between any two points in SF on Monday October 05, 2026 @11:30PM (#49973828)
fair point! it just doesn't know about bike lanes yet, I’ll see about getting the SFMTA bikeway network map from DataSF.
Re:Find the flattest route between any two points in SF on Monday October 05, 2026 @10:16PM (#49973388)
good point.. the slider trades distance against total climbing and nothing else. steepness is currently reported but not optimized.

seems like a worthy addition to the objective!

Re:Find the flattest route between any two points in SF on Monday October 05, 2026 @06:56PM (#49971926)
ah, I think this is related to SF's "Slow Streets" program and a genuine bug in the parser.

Cabrillo is a Slow Street, and the parser read its "destination-only" tag as closed to pedestrians, so the tool couldn't see the street at all (and started you a block over?). fixed and deployed; your trip should now go Cabrillo → 23rd → Geary.

Re:We're Afraid Language Models Aren't Modeling Ambiguity on Friday April 28, 2023 @03:45AM (#35738619)
I would like to see human performance on the introduced benchmark, AmbiEnt, and have it added to Table 4.
For AMZN software staff (especially in SF Bay Area): was it really 160K capped?

Obviously RSU grants / bonuses are excluded from this, but I still find that surprisingly low (as a salary cap) for FAANG, especially around SF.

Played with the gilbert gottfried speaker option, gave me serious Twin Peaks "Red Room" vibes.
Re:DuckDuckGo is good enough for regular use on Saturday March 07, 2020 @12:49AM (#22510027)
A bit tangential but related: has anyone else noticed an increased frequency in the desired result of a Google search being the first one on the second page?

Particularly for things involving reviews or booking, I have noticed an uptick in the (subjectively) “right” result being kept off page 1... it seems almost like some post processing logic to favor specific sites/companies. The fact that the “right” result in these instances is almost always the first result makes me think the true Ranking function knows the result’s actual value.

As a (jazz) piano student myself, I am happy to see "To Master a Skill, Master Something Harder."

Pianist and YouTuber Nahre Sol has a great set of exercises based on modifying passages of Chopin etudes, which serve as excellent material to study both as a template and in their own right. [1][2] She varies harmony and rhythm, and takes the exercise through all 12-keys. Much harder than just learning the passage in the original key, but that's the whole point.

[1] https://www.youtube.com/watch?v=2xYfgJVm1Ns [2] https://flatfiv.com/products/piano-technique-intensive

Re:Amazon Quantum Ledger Database on Wednesday November 28, 2018 @12:42PM (#18553631)
So is “Quantum“ pure buzzword hype? Or is there a reasonable connection to the product?
This post is about Pyro (probabilistic programming framework, with a clever logo "pi rho"), not to be confused with https://github.com/irmen/Pyro4

Completely independent projects, just a name collision.