mjfisher

Worth knowing cookies are a special case and are covered under the ePrivacy directive, which is distinct from the wider GDPR legislation and specifically deals with storing tracking information in a user's browser.

Can I be both?

Second that recommendation, and I think that podcast would particularly as appeal to a lot of the HN crowd. I listened from the beginning until the early/mid 20th century philosophers and understood so much more about my own perspective on the world as a result.

I see a lot of back and forth about postgres' suitability as a queuing system. I wonder if there's a couple of separable problems here. Postgres backed queues - even very scalable ones - might work well for background jobs in a monolithic app backed by a single DB. Things like backgrounding sending an email etc.

But usually when I reach for a queuing system, it's because I want to decouple a part of the architecture. And in that case, it's probably better to use a dedicated queueing system instead of postgres.

I wonder if the two cases are conflated in a lot of online discussion.

In the UK, pretty much zero. Nobody ever leaves their windows down when they leave their car.

Indeed. Real life hacks are beginning to sound like Neuromancer.

It says something about the state of the world that I was genuinely uncertain whether this was actually a joke right until the last paragraph.

Very well done.

That's interesting and actually the opposite of mine. I wonder if it's stack or methodology dependant? For reference I'm usually using cursor and opus4.6 and for a bigger piece of work:

- Start in ask mode - "I'm planning on doing X to achieve Y; are there any alternative approaches? What problems might I run into?"

- Chat for a bit and get the high level approach, switch to plan mode and ask for a nicely formatted plan

- What's kicked out is already in the rough shape of the discussion so far, so it's a case of following a nicely formatted doc through and highlighting sections of text and asking for clarification or changes

- Hitting "build" and then reviewing what's been done

For a new service I might spend an hour in ask/plan mode - but then it gets 95% of the build itself right first time.

Do you do the same with different results, or is there a different stack/methodology you go through?

I can't speak to this particular case, but most of the delay is likely to be organisational rather than technical at this kind of scale.

Don't think about how hard it is to migrate a VM to a new provider. Think about how hard it is to:

* Get procurement to sign off on a new vendor

* Guarantee that your ISO compliance standards can be met under the new regime

* Make sure that GDPR requirements are met during any data transfer process to the satisfaction of your legal team

* Get the old infrastructure team and the new infrastructure team coordinated enough to be able to plan a migration without downtime

* Mollify the consultants that the CEO's friend said he should hire

* Analyse the migration plan to death to derisk it while at the same time be unable to actually evaluate it small scale due to the points above

How could that possibly, ever have made it through. Every single API for every single service didn't check the JWT?

I think the specific case of having a long conversation with an agent about what you're trying to achieve and why, and then have it update a README or a skill based on that conversation is a useful thing to do. Captured the context of the conversation without having to essentially write the same thing again.

That's usually because the system that runs those things is independent of the timing of the main game loop. And then when someone finally gets around to implementing the pause screen, they still run even with the main game time stopped. And you look at it and think "eh, you know what - looks cool - we'll leave it".

I hope most people have a broader definition of "relevance".

The reintroduction of Red Kites to the UK has been a huge success. I don't get particularly excited by birds normally, but regularly seeing such large creatures (almost 2m wingspans) curving through the sky is nothing short of majestic. They're almost reminiscent of dragons.

I wonder if I'll get to feel the same about golden eagles soon too.

Just to sanity-check my reading of this:

- Zustand exposes itself as a hook.

- MobX does that observer-wrapper thing

- Snapstate instead has an explicit writing step (`scoped()`) at the bottom of a component

If so, I really quite like that. Kudos!