I eventually switched to Edge a few years ago because it was nice and lite. Now I’m seeing the same pattern play out as they add copilot, shopping, and rewards programs.

What browser should I check out next? Some must haves: workspaces, vertical tabs, and chromium extension support.

I’ll answer some of the legal right now. First, we are at every event. Not sure how much it matters legally, but we are there as hosts and to drive the feeling of community. Without us, I don’t think the community has the same feel.

We also have an unbelievably respectful and mature community. After over 70 seatings we’ve never had an incident. We also have a code of conduct document we send all new members.

Second, we setup an LLC to shield us personally from legal liability.

Third, not to say that it shields us, but the restaurants also have insurance and are a better target for a lawsuit.

We are in the US, and at the end of the day anyone can sue anyone for anything. It’s just the reality and risk of the times. It hasn’t been a problem for us yet.

The process starts ~3 months before the event. We start by picking a theme or region. Then contact some restaurants that fit the criteria and pitch them the event. That kicks off the back and forth on cost and menu.

Around 4 weeks before the event we send a save the date + previous event recap email. We summarize the last event and tease the next event, without giving away the actual resturant or type of food.

Over the next week we prep the invite email and payment forms. This requires putting the dishes on our menu template, research and writing about the history of the dishes, the region, and the resturant. Some of this content also goes onto our website.

Three weeks out we send the invite, which is a lottery system. Members have 5 days to request a seat and place a credit card hold. 5 days later we run the lottery (I wrote some basic software to randomize assignment, conver the card auth to capture and release any cards that didn't get assigned a ticket). Then we send an email to everyone who got in with which night they recieved and another email to anyone who was waitlisted. Everyone is added to a spreadsheet to track.

1 week before the event we send a reminder email and a last chance to cancel before the ticket is non refundable.

At the event we play host and check each guest in and say hi to everyone. Then we give a prepared ~5 min intro about the food, restaurant, celebrate any milestone members, and make any general house keeping accounments. Our 20 club members get a branded apron.

At the event we take video and pictures. Over the course of the next 4 weeks we post dish pictures with descriptions and history of the dish on our instagram. We also make a 1-2 min recap video of the event which also goes on our instagram and website.

Separate from the actual event related work we have to manage the books, handle members emails, and review membership requests. More recently we started selling shirts, so there's a little work in managing that as well.

Feel free to email me if you run into any challenges. We might have already been through it!

- We are lucky to have a passionate community who tell others about us.

- Sometimes we do shared reels with the restaurant, which helps drive some of their traffic to our social pages and website.

- There’s a few large local Facebook food groups which have driven membership.

- The largest driver of new membership came from coverage in the region newspaper. We credit that with the transition from 1 or 2 degrees of separation to people we had no connection to.

- There’s been a few influencers who have shown up and documented their experience. We didn’t pay for it. It drove a few members, but the quality of the newspaper and Facebook group members was higher.

5 days before the event we lock the head count with the restaurant. At this point the ticket is non refundable (we allow transfers). Then we pay the restaurant one lump sum. At the event the guests are only responsible for their bar tab (outside the one included drink), we don’t get a cut of that.

Sometimes we have seat minimums we need to hit and eat the cost if we are short (that rarely happens). We don’t allow ordering any other food outside of what’s on our menu.

From there people started to tell their friends, who told others, then the local newspaper wrote about us, and people started talking about us on Facebook food groups and posting on Instagram. The community grew very organically, we never spent a penny on marketing. Most of the original 13 don’t come anymore, and we have grown into an incredibly diverse community.

Happy to chat, email is in my profile.

Our biggest cost center is when we guarantee a minimum number of seats and come up a little short. Doesn’t happen often, but when it does it eats into the margin fast.

- We do the work to find the restaurant and curate a menu, story, and theme. E.g., we might go to an Indian restaurant and focus the event on only the southern regional dishes.

- Many times we have dishes that are off menu specially for our event.

- Sense of community. We have quite a few regulars who have gotten to know each other. In 2025, 45 people reached their 20th or 30th event with us. Since we take over the whole restaurant there’s a little more freedom in how the space is used. Lots of new friendships have been forged.

- When you go to a restaurant with a friend or small group, you can only order so much. We’ve had events with upwards of 25 different bites. There’s really no better way to sample everything the restaurant has to offer.

- There’s a few people who say their partner are picky eaters, so they come to our event each month to have the opportunity to be a bit more adventurous. It’s an incredibly diverse group with a lot of different reasons to attend.

Since 2023 we’ve been to 44 restaurants. In 2025 we served 1,099 guests and generated $126k in revenue.

https://www.deadchefssociety.com/

I suppose in other industries this isn’t always expected. For example, you can easily be a mid-level accountant for your entire career without the company or industry expecting you to be on track to be their next CFO.

Maybe the author should be looking at medium/big non-tech companies that have been around a long time, have aging codebases, and aren’t innovating in the same way as as big tech or startup. I suspect they might find developers who have been there for many years and are pretty complacent.

Our first dinner was with 13 friends and has since grown into a group of just about 1,000 members. Last year we generated around $140k for local restaurants on off nights (dinners are on Tues and Wed when business is slow).

Now we are working on evolving into more of a lifestyle brand for people who love food. I'm currently working on our clothing line and new site, which we quietly launched a few days ago (there's still a few odds and ends to finish): https://www.deadchefssociety.com. Would love any feedback!

We work with a single restaurant each month to create a 10-20+ course all inclusive price fixe menu. The food is served family style and is authentic to the region we are hosting. We typically host the dinners on a Tues or Wed when the restaurants in our region aren’t too busy and could use the extra business.

Here’s the 2024 update (I haven’t run the year to date cumulative numbers yet):

* Grew to over 900 members

* Hosting 2 seatings per month

* Served 1,300 guests

* Generated $140k revenue

As for /compact, if I’m nearing the end of my context window (around 15%) and are still in the middle of something, I’ll give /compact very specific details about how and what to compact. Let’s say we are debugging an error - I might write something along the lines of “This session is about to close and we will continue debugging in next session. We will be debugging this error message [error message…]. Outline everything we’ve tried that didn’t work, make suggestions about what to try next, and outline any architecture or files that will be critical for this work. Everything else from earlier on in this session can be ignored.” I’ve had decent success with that. More so on debugging than trying to hand off all the details of a feature that’s being implemented.

Reminder: you need context space for compact, so leave a little head room.

I’ve been using Claude for a side project for the past few weeks and I find that we really get into a groove planning or debugging something and then by the time we are ready to implement, we’ve run out of context window space. Despite my best efforts to write good /compact instructions, when it’s ready to roll again some of the nuance is lost and the implementation suffers.

I’m looking forward to testing if that’s solved by the larger Gemini context window.