buckhx

We've been moving forward with Vue+Go, but coupled with grpc instead of gin.

Can't speak for OP, but we have a similar stack and use middleware on the actual services since they need to decide which permissions are needed instead of centralized auth at the gateway level.

Browsers don't speak grpc natively. There is a separate spec for browser support, but it's a very new project https://github.com/grpc/grpc-web/blob/master/README.md

Yep, it's a bit more symbiotic than that unfortunately, but in general most of the data can be restored from an upstream source.

ES is currently the main data store for zagat.com which ends up being a sink from a data pipeline and more or less being used as Key-Value store on the query side. It has worked OK for our current use case, but definitely came with some pain points. Primary key fetches were way too slow for what we needed especially with some in-memory joins happening and we ended up sticking a cache in front of ES to satisfy our performance reqs.

We had a tight deadline on implementation (3 months to extract from Google) and chose ES in order to satisfy a kv store as well as TF-IDF corpus search.

They're technically illegal in NYC as well, but I bought one and it's been pretty great.

We've been using gRPC for a new web project and it has been a good experience so far. The codegen in JS is pretty verbose and can have touch ergonomics, but not the end of the world. We haven't ran into troubles with the type system, but we leverage OneOf's and Views a decent amount. The thing we don't have a great solution for right now is how to fetch referenced types efficiently (eg. stream of posts with users referenced by a foreign key), but we're not tackling that until performance of the resource fetches becomes a problem and evaluating whether to cache values client side or design a solution at the API layer.

Also FieldMasks and the View patterns can be very useful for the other issues that were raised https://cloud.google.com/apis/design/design_patterns#partial...

Low reps (<=5) maximize strength, you're not going to get Arnold muscles if your goal is strength. Bodybuilding emphasizes size > strength and is more in the medium reps range (8-10). Higher reps basically turn into cardio and joint stability work.

The Infatuation & Zagat | Product Engineer | Full-time | On-Site NYC | https://theinfatuation.com | https://zagat.com

We recently acquired Zagat from Google and are on our way to building the world's greatest restaurant discovery platform. We want to build a community driven content platform on Zagat and make it a direct competitor with crowd-sourced incumbents.

We're looking to build a unified platform with client applications tuned to their use-cases while leveraging concepts like Progressive Web Apps to provide our users with rich experiences. React Native experience would bring a lot to the table as well. There's a ton of exciting work ahead of us and we're building a great team to match it.

Other openings on our careers page include Platform Engineers well-versed in Go and mobile engineers.

Here's a blog post I wrote comparing geofencing algorithms one of which leverages s2. https://medium.com/@buckhx/unwinding-uber-s-most-efficient-s...

In practice, we use s2 for in memory location indexing.

Mine is pretty squeaky, but doesnt feel loose. Will probably purchase a shim as it's supposed to help the squeak.

I bought a Xiaomi scooter in June and received it a few weeks ago. I live in Williamsburg and work in SoHo/Chinatown, and my commute is 15-20 mins compared to 25-30 on the subway (L -> NQR). I obey biking rules and only push if I am on a sidewalk. I haven't felt unsafe outside of riding at night in Brooklyn and not feeling visible enough. Overall it's been great, but can imagine it getting out of hand if they were readily available. For example, I was at the Farmers Market in Union Square last Weds a couple of people were riding powered scooters through the crowd clearly NGAF.

Defining your schema upfront and have types generated in multiple languages is the real value add. The performance is a nice cherry on top.

The Infatuation & Zagat | Product Engineer | Full-time | On-Site NYC | https://theinfatuation.com | https://zagat.com

We recently acquired Zagat from Google and are on our way to building the world's greatest restaurant discovery platform. We want to build a community driven content platform on Zagat and make it a direct competitor with crowd-sourced incumbents.

We're looking to build a unified platform with client applications tuned to their use-cases while leveraging concepts like Progressive Web Apps to provide our users with rich experiences. React Native experience would bring a lot to the table as well. There's a ton of exciting work ahead of us and we're building a great team to match it.

Other openings on our careers page include Platform Engineers well-versed in Go and mobile engineers.

Does mapbox provide place details data yet? Last time I spoke w/ sales it was a planned feature, but not released.

The Infatuation & Zagat | Product Engineer | Full-time | On-Site NYC | https://theinfatuation.com | https://zagat.com

We recently acquired Zagat from Google and are on our way to building the world's greatest restaurant discovery platform. We want to build a community driven content platform on Zagat and make it a direct competitor with crowd-sourced incumbents.

We're looking to build a unified platform with client applications tuned to their use-cases while leveraging concepts like Progressive Web Apps to provide our users with rich experiences. React Native experience would bring a lot to the table as well. There's a ton of exciting work ahead of us and we're building a great team to match it.

Other openings on our careers page include Platform Engineers well-versed in Go and mobile engineers.

https://theinfatuation.com/careers

The Infatuation & Zagat | Product Engineer | Full-time | On-Site NYC | https://theinfatuation.com | https://zagat.com Hey Chris,

We recently acquired Zagat from Google and are on our way to building the world's greatest restaurant discovery platform. We want to build a community driven content platform on Zagat and make it a direct competitor with crowd-sourced incumbents.

We're looking to build a unified platform with client applications tuned to their use-cases while leveraging concepts like Progressive Web Apps to provide our users with rich experiences. React Native experience would bring a lot to the table as well. There's a ton of exciting work ahead of us and we're building a great team to match it.

Other openings on our careers page include Platform Engineers well-versed in Go and mobile engineers.

https://theinfatuation.com/careers

Agreed, would like to see a concrete example of why that advice is being given.

I've been a fan of PocketCasts. Lots of people recommend podcastaddict because it's free and has a million knobs, but I enjoy the comparatively slick interface of PocketCasts.

"Ending is better than mending. The more stitches, the less riches."

Aldous Huxley, Brave New World, 1932

Really looking to make the brands symbiotic. A model we're drawing from is Rotten Tomatoes where The Infatuation is the critic score and Zagat is the community score.

Android app will get a face lift, but it'll be a few months out as we need to transition the infrastructure over first.

Our deals with partners are a combination of integrated content (API), events and branded content.

We respond to RFPs from brands with a proposal of how we would help them reach their goals and then execute it. Examples of brands we've worked with are Amex, Delta, Caviar, etc.

We never accept money from restaurants or groups representing their interests, something we really try to hammer home in our review ride-alongs on Instagram.

It's not a full-blown rewrite, but it's not just spin up new infrastructure and run it over here either. We're receiving Zagat specific code, but there are significant gaps from missing Google dependencies and data that need to be filled.

The transition costs aren't negligible by any means, but are worth the opportunity.

We love The Wirecutter and is something we look to a lot from The Infatuation. Their content is fairly "evergreen" and useful. They cover utility aspects great, but generally feel like they don't take design/taste/style into account. That might be that subjective vs. objective nature of reviews that you're alluding to and why their reviews are so effective b/c they take a very objective approach.

The Infatuation will continue to write reviews and guides in house. We're looking to build a community to power the content on Zagat and curate content while we build that out. Building a community will definitely be a challenge, but hopefully we have a head start from the Zagat brand being so iconic in the space.

Google will run Zagat in prod for an agreed amount of time while we develop a separate platform that implements the same endpoints on our infrastructure. Once we're done with that, we'll switch client applications over to read from the new platform.

It's going to be a great challenge to tackle and I'd love to be able to share how it all went once the transition is complete.

Don't have too much context on high (er) quality content in the rest of Google's portfolio, but we definitely were drawn to Zagat and saw it as a great counterpart to The Infatuation for exactly this reason. Quality over quantity will remain our principle strategy to tackling this space, but we will be exploring new avenues to scale this out more broadly with Zagat moving forward.

Love this and we've been thinking about it a lot. I'd say that most UGC platform ratings fall into the base rate fallacy and there is a lot more information available that could be leveraged for recommendations. A very indicative question of the direction we're looking to go is "Will I like this place given that people I trust recommend it?"