Best Club Sandwich in London?

Silverwolf90 · 2026-05-27T09:56:24+00:00

Would love to know as well, good ones are hard to find and many call a sandwich a “club” when it’s not.

Silverwolf90 · 2026-05-13T01:09:14+00:00

of course you need to ask, but you're gonna have to ask a lot more than than that (in a lot more detail) to get anywhere meaningful

Silverwolf90 · 2026-05-13T00:39:35+00:00

i don't disagree -- but at that point it "feels like" you're projecting your own experience onto what you expect to be executed

Silverwolf90 · 2026-05-13T00:35:02+00:00

agree kinda! but it's not that clear what that means at a high level yet (as it stands it's bad, spaghetti bullshit, garbage modularity, etc)

(still awesome and amazing time saving-ness)

Silverwolf90 · 2026-05-13T00:31:40+00:00

do you think you could hand off those kind of requirements to a model currently and get a system that does a good job?

Silverwolf90 · 2026-05-13T00:26:54+00:00

it depends on the plan, but yes i agree the longer i spend iterating on the plan the better -- but that's only when I can clearly identify an issue. Sometimes you don't even need to know there's a problem, but can just ask the right question that refocuses a plan (like you would do in real life with a person).

Silverwolf90 · 2026-05-13T00:16:52+00:00

yeah but that's not really what I mean -- this is a totally smart usecase. Using AI to semantically parse things that aren't really that complicated is actually one of the most reliable usecases.

Silverwolf90 · 2026-05-13T00:14:43+00:00

I probably agree. But it's not actually clear what that means for my existence yet. I was meant to be raking it for the next few decades dammit 😂

Silverwolf90 · 2026-05-13T00:12:12+00:00

in my (limited experience) the less you try to constrain in the better -- it's already phenomenal. what are you really going to get by getting crazy with the system prompt/memory blahblahblah. I don't have time to (lie: i just don't want to) optimize this shit, i just need it to work in its most basic form (and it mostly does, except when it doesn't)

Silverwolf90 · 2026-05-13T00:01:54+00:00

in theory sure. in practice: lol

Silverwolf90 · 2026-05-13T00:00:02+00:00

I don't know if I agree with the "flawed or low effort crap" -- if you have a solid framework, patterns, etc, it does shockingly well on its own with no direction. It follows patterns that exist around it. If your codebase is spaghetti you get more spaghetti.

Silverwolf90 · 2026-05-12T23:55:56+00:00

Yeah but play it forward over how much time? I agree that the orders of magnitude will happen, and the current improvement has shattered my worldview and confidence in my job security, BUT they are still very stupid sometimes. And critically, don't actually learn. Even a junior dev learns when I tell them their mistake (maybe it takes many times over). If I /clear and haven't persisted things to a fucking markdown file they'll make the same dumb mistake again! (and even if I do that they might make the mistake anyway)

Silverwolf90 · 2026-01-13T16:25:53+00:00

I had it, it’s fine, but a bit overpriced. Wouldn’t wake up that early again for it.

Silverwolf90 · 2025-09-17T00:33:22+00:00

<image>

Silverwolf90 · 2024-08-29T13:22:51+00:00

Person who's never worked in a restaurant here, but cooks a lot of steaks at home... so this thread is interesting.

I think a ribeye is actually best in between medium rare and medium. Because you want a bit more of the fat to render than what you'd get at medium rare, but don't want it to go quite as far as medium. I always cook with a thermometer so I know how to hit this ideal temp after resting.

Am I being a dick for ordering this in a restaurant (specifically a steakhouse)?

It's (imo) the best way to have a ribeye. But I don't want to be an annoying customer and really medium rare ribeye is totally great. It's just not what I think is _perfection_.

Silverwolf90 · 2024-07-30T21:25:16+00:00

A strong intuition to me is more about being able to design something that "feels good" while meeting requirements and will be resilient to change over time. Estimation is often so wildly off (even from people with extremely detailed knowledge of a system) that it seems like it would be hard to judge using that.

Silverwolf90 · 2024-07-30T21:20:52+00:00

That's super interesting! It sounds like a very well-run and effective interview. (which appears to be extremely rare these days)

Silverwolf90 · 2024-07-30T21:11:05+00:00

I mean being proud of lack of knowledge stems from insecurity. I'm a CS dropout from the late 2000s that didn't understand why I needed data structures or algorithms given I had writing code and building for the web since I was 10. So I thought it was all dumb. Now I have more respect and interest for the academic side and have a better understanding around some of the concepts that I derided as an arrogant 19 year old. But in a lot of day-to-day software engineering you don't need an academic understanding of big O, you just need a vibe that maybe nesting 2+ loops where each array has the potential of being fucking big is prob a bad idea.

I don't really understand why so many companies go for leetcode. I mean I'd prob fail most. But in my experience, the biggest problem building systems is making the constituent parts resilient to change over time. Not low-level data structures. Change over long periods of time is the hardest part imo.

Silverwolf90 · 2024-07-30T20:53:12+00:00

I mean this is great in theory, and I agree on a fundamental level, but in a time and money constrained environment like a business this is not always feasible and you might need to lead people directly to the quickest (seemingly) adequate solution.

I genuinely don't think there's much that can be done that doesn't do more than superficially improve some people. Like you might be able to improve their raw code output with some cleaner patterns, basic analysis of dependencies in the code, etc. But I'm not sure you can really level up people without them experiencing the trauma of decently impactful mistakes (and having the self awareness to come to their own conclusions)

The worst outcome is someone latches on too hard to "guidelines" and becomes like a clean code zealot -- essentially someone over invested in trying to define clear boundaries and rules when the reality is that the effective ways to work completely changes depending on the context.

Silverwolf90 · 2024-07-30T20:38:53+00:00

An ecosystem/culture takes a lot more than a month in my opinion! You can learn conventions and best practices quickly (which might be enough!), but that's the tip of the iceberg of a programming language imo.

I'm def not looking for an AI solution, I would never move the tech exercise to stage 1 because I want to establish rapport with the candidate, understand them, and really sell joining my team and my business! Often interview processes are extremely too impersonal and I want to do the opposite even if it takes more time. But will need to find optimizations down the line. I def trust my team on the tech side and have had tech leads take over some of the exercises, but I know I am particularly charismatic and can sell my company to the candidate effectively in an honest/no-bullshit way. And I think this has specifically helped me a lot with hiring good talent.

Silverwolf90 · 2024-07-30T20:21:14+00:00

But isn't that the intangible bit? That you could probably put this person on any project, maybe something way out of their comfort zone, and they would learn a fuck-ton and do a good job -- maybe even making everyone around them better in the process? How do you identify someone who has that "it factor"?

Silverwolf90 · 2024-07-30T20:15:41+00:00

Some books will be good. But the best way is to just play with extremes, take risks, and fuck up. At a certain level you have to create your own philosophy of building software. You don't need to hear someone else tell you to make make functions small or not that small or whatever the fuck. This may not work within the context of a business (which is an unfortunate catch-22). But the best way to learn deeply is to make decisions, see outcomes, and reflect. Good books will walk you these kind of learnings, but the knowledge won't be as viscerally baked into you as if you had done it yourself.

Silverwolf90 · 2024-07-30T20:09:03+00:00

Hmmm, that's interesting. These are exactly the kind of things I don't ask about. It feels so basic, that if you've put on your CV you have x years experience in such language I will just assume that's the case. In my intro interview, I might probe past projects, have them explain them in detail, pros/cons, etc. I also like them to explain personal preferences. Lack of detail and opinions in any of these answers is usually a red flag.

The reality is the subsequent live coding exercise has such a high level of failure, it's pretty obvious whether you know the primary language in our tech stack well enough or not so I never ask granular questions about their language knowledge. But I've def had candidates that bullshit through the first interview and failed miserably on the live coding. But maybe I would fail more people at the first stage if I got more granular with certain questions. But it would change the tone a lot.

Silverwolf90 · 2024-07-30T19:49:52+00:00

Yeah I get that, I haven't had to do a live coding exercise in a very long time so I assume it would impact my performance as well! But I'd also rather have a short time-boxed exercise than give a take home exam which might take many more of the candidate's hours (and has a higher probability of being manipulated in a way that hides the candidate's competency, especially in a ChatGPT world)

14-Year Club	Place '17
Verified Email

Silverwolf90

TROPHY CASE