Thanks for sharing I skipped this title and missed that scene.

You could check to see if one of his games has that position using https://fenfinder.com (site I built). Of course it's a long shot given the huge possibility-space of unique positions, but hey, one can hope :).

We actually moved to TripAdvisor a few months ago.

Wow, you answered 2 minutes after this question was asked. Does DDG have something setup to notify them when DDG is mentioned on HN?

'DDG' is mentioned too many times on HN. They will just get spam.

Maybe just a coincidence.

Ah that is great to see! Was the motivation about Yelp's practices or UX, or both?

Also is TripAdvisor the long-term plan or a stop-gap until a better 3rd party provider matures or something homegrown catches on?

Predicting the future is really hard, and a lot can happen in 5 years. I would reframe the question to a more reasonable time-domain and talk about my personal and/or professional growth goals. If you don’t have any then this is worth spending some time thinking about. In my experience, if you don’t prioritize your time then someone else will, and they’ll likely have different goals than you.

Thanks for the comment. I don't know the answer but came here to ask this too. It seems really useful to be able to objectively measure the efficacy of noise cancellation across diverse products.

What were some of the key lessons or most impactful things?

Some of my key lessons were:

- remote-first meetings; is someone is remote / in another office, everyone takes the call from their laptops. That way no one ends up being forgotten on a screen in a room full of people.

- habitually reverting to written communication, so that information doesn't get lost in 1:1 conversations. That means writing thought processes into tickets, so folks can search for things later. We worked across 3 timezones (including PT to IST, ~12 hours off) so async communication was key.

- not having a central office. "Everyone is remote" wasn't perfect, but there wasn't a true home office in the same way as my current company. For example, it was considered rude to "@here" in the general chat channel for things like donuts, because hey, many folks are in other states/countries, and don't need to hear about y'alls treats. Little things like that make a big difference in employee experience.

new york review of books (https://www.nyrb.com/)

As a follow up, what are the most useful methods for managing technical debt without incurring too high of a cost to team/product/project velocity?

Address issues as they are raised. Don't wait too long to get rid of debt, and most certainly don't rely on fixed time cycles of fixing things. A team has good sense of the issues they deal with, and you can capture their view in retrospective meetings. Depending on how bad the debt is, you should allocate time to improve. Velocity will only get worse as debt grows, so there is a clear business case for such stories: the more debt, the slower the velocity and the lower the quality. Spend time now, to speed things up. But just don't do it from a theoretical perspective. Address real issues, set real goals and measure them.

Second Asana. I've been using it for years and it has really improved tremendously over that time. There are definitely still many things missing (most notably for me is the lack of advanced markup in comments/conversations)... but it works very well for cross-functional collaboration and longer-term project management.

I've just started using Asana in the last month, the very first thing I noticed was how incredibly slow the interface is to respond. Dragging things around on a board is particularly painful compared to Trello or Github Projects.

I also find it incredibly annoying that when you add a card to a column, it adds it to the top of the column, rather than the bottom.

However, aside from those two annoyances, it does seems to offer a lot of useful functionality.