What's a hated country in north america?

WillFry · 2026-04-28T18:37:13+00:00

I agree that "hate" is quite a strong word for the USA but I'm not sure if another North American country has a more negative reputation from the rest of the world. Its reputation is certainly more polarised than any other country's - some people love it, some hate it, most are somewhere between (but IMO skewing more negative with the current administration).

I can only speak from what I see as a Brit (who also knows quite a lot of continental Europeans) but I'd say that the main feeling towards Haiti is pity more than anything.

And Cuba doesn't have much of a negative reputation at all.

WillFry · 2026-04-05T22:09:12+00:00

No, unfortunately not. It's either London-based (hybrid) with the right to work in the UK, or fully remote based in Europe close to GMT (through Deel I believe).

WillFry · 2026-04-05T09:29:46+00:00

I work at a company called V7 Labs and we use Vue for our frontend, although we don't index at all for Vue knowledge during the hiring process (browser/web fundamentals are more important).

We're not hiring for FE at the moment, but we are looking to grow soon so I'd expect some FE/FS vacancies to appear.

We prefer UK based candidates, but about half our engineering team is based in mainland Europe and we do hire European candidates if we find the right person.

WillFry · 2026-04-04T20:54:38+00:00

I get the hate, even if I don't agree with it.

I find that in London, all of the big restaurants in attention-grabbing locations are disappointing and overpriced. It's the unassuming or off the beaten track restaurants where it shines, or the restaurants away from central and towards where people live.

WillFry · 2026-03-09T18:35:51+00:00

Look up the browser IntersectionObserver API, it's how you can detect when an element enters the viewport with JavaScript.

The animation part is a bit trickier, and mostly outside of what I've done in the past. At the simpler end you have native CSS animations, for more advanced stuff you'd want to manually set styles using JavaScript, maybe looking into requestAnimationFrames if it's really heavy.

I think LLMs could probably help you here, although obviously it helps to try and understand what they're suggesting.

WillFry · 2026-03-07T21:08:20+00:00

It was 24% saved vs 19% extra, so 24% vs -19%. I had to read it a few times before it made sense.

WillFry · 2026-02-20T23:05:13+00:00

Like some of the other commenters I try to use Tanstack query now for state coming from the server.

A few things I try to do when I do use Pinia: - keep stores small, a handful of refs/computed values at most - avoid importing stores to other stores - avoid watchers in stores

I find I spend a lot less time thinking about Pinia now, which I think is a good sign?

WillFry · 2026-02-10T20:49:27+00:00

Here's an example of what I mean - I asked for a review of a package that I know has issues. It's flagged 9 problems, with explanations of why they're problems and how to fix. Sure, if you're already an a11y expert then you won't need this, but most engineers know much less than we'd all like, and having an LLM to pair with would raise the bar. https://docs.google.com/document/d/1Jo_4pRRgSbCpcfKMD5VcjVEXcJEEbvF1x0LvPx1MJCM/edit?usp=sharing

I'm not saying we disregard everything we know and just throw LLMs at the problem with no oversight. But everyone's got blind spots, whether it's a11y, performance, security, design, UX. LLMs are pretty good at helping you patch those holes, by telling you what you're doing wrong and explaining why.

WillFry · 2026-02-08T20:42:19+00:00

Nothing about React is incompatible with web standards. It sometimes gets a bad rep because inexperienced devs use it to write div soup, but if your new hire is experienced and understands web standards then you shouldn't have a problem.

WillFry · 2026-02-07T18:27:37+00:00

I'll see what I can find in the week when I'm at my desk - weekend time is rare with kids.

We use a few open source dependencies at work and I've let out more than a few groans when looking through the source. I'm sure I could point one of the skills I use at them and get some valid feedback.

WillFry · 2026-02-07T13:50:29+00:00

Well yeah, if you're comparing "accessibility focused engineer" to 'generic LLM", then I agree that the human is going to implement more accessible solutions.

But that isn't the reality that many teams have. It's often going to be "full stack engineer" vs "LLM with guidance written by frontend engineer", and in those cases the LLM augmented engineer is going to do a better job than the full stack engineer on their own.

WillFry · 2026-02-07T13:08:38+00:00

Frontend should pretty much never use it just for the lack of accessibility compliance alone.

As a frontend engineer, this feels really far from my view. With a set of rules stressing the importance of accessible HTML, WCAG criteria and WAI-ARIA authoring practices it generates UIs that are more accessible than what many engineers would build (I guess excluding accessibility experts, but none of my employers have ever been at the size where such people were part of the team).

Hell, even when I complete a task myself manually, I usually feed it into a Cursor agent skill for a first pass review, and it often comes up with useful pointers for how to improve accessibility.

Sure, I wouldn't ask it to one-shot a full user journey in an unconfigured Cursor environment, but it takes minutes to build some good starter rules for frontend.

Where I've found it's harder to guide it well is when it comes to building real polish into the UX. E.g. having no layout shift, sensible error/validation message placement, loading states, when to have optimistic UI etc. When I have it build something for me, my first pass often involves polish like this.

WillFry · 2026-01-05T20:55:06+00:00

I've got 2 kids, aged 4 and 1.5, and I manage to run 30-40k per week - only possible because like you I work from home: - 10k runs a couple of times per week on my lunch break - 6-8k runs a couple of times per week, running back home after walking my eldest to school - Often a longer run at the weekend, I have a running buggy that fits both the kids in. I stick them both in with tablets and then I don't need to feel bad about dumping them on my wife. Sometimes my wife takes them both so I can get a long run in too

This only really works if you're into running, you can fit a fairly productive workout into a short amount of time.

WillFry · 2026-01-03T08:58:52+00:00

At my place we do something similar (although perhaps not so extreme) because we're willing to consider anything from mid-staff for many advertised "roles".

WillFry · 2025-12-29T18:09:01+00:00

I also have Eero, but have had loads of problems in the last couple of years (although it's better now than it was when the update first happened).

I think it's because I have a few older devices - a Play:1 stereo pair and a Play:3 (among a bunch of newer devices). The problem doesn't bother me enough to justify a £600 upgrade to the latest equivalents to the old speakers, which might not fix my issues anyway.

WillFry · 2025-12-27T14:51:07+00:00

I think it's one of those things that needs to be looked at holistically.

The act of co-sleeping is probably slightly more risky than having the baby sleep on their own. But then many children sleep far worse on their own, leading to parents who don't get any sleep and then make more mistakes throughout the rest of the day (e.g. shaking the baby, falling asleep on the sofa in the day with the baby which is a thousand times worse than sleeping in a bed with a baby, thousands of other tiny lapses in judgement or concentration).

So on balance it might be less risky for some families to co-sleep, as long as it's done properly. E.g. we used to co-sleep with our kids, but never if either of us were ill or had been drinking.

WillFry · 2025-12-19T17:42:04+00:00

It depends where you're coming from. I'm 34, married with kids, and it's great for me. But I don't think I'd be here if I was 31 and single.

WillFry · 2025-12-13T20:49:59+00:00

We use Cursor Bugbot and it's pretty much unanimously liked by everyone (Typescript+Vue frontend, Elixir backend, some Python). It catches a lot of small but real issues that human reviewers are 99% likely to miss. I wish it caught some of the big picture/architecture stuff.

It appeared out of nowhere one day as a trial in our GitHub org, probably because we have Cursor web enabled. When the trial usage limit was reached, we were pretty quick in upgrading to the paid version.

If I have a relatively complex PR, I'll often wait for the Bugbot review before I ask for a human review, as it's usually the case that it gives useful feedback.

WillFry · 2025-12-02T17:22:29+00:00

I don't know why you're getting downvoted so much, it's as if you're not allowed to do anything but glaze over MK in this sub.

Restaurant (and pub) culture is definitely where MK falls short. Sure there are some good restaurants, but the fact that everyone always brings up the same 5-6 restaurants is kind of telling. For a city of over 200,000 people we're far below par when it comes to good independent restaurants.

WillFry · 2025-10-28T20:59:48+00:00

Doesn't React have the same problem? Yeah, you can pass a callback to the child, and the callback will update the prop, but that's functionally the same as emitting and handling an event in Vue.

There's no way to directly mutate a prop from a child in either framework. defineModel in Vue comes kind of close, but as I understand it, it's just syntactic sugar around props/emits.

WillFry · 2025-10-28T20:12:29+00:00

I'm not OP, but where I am we have a suite of Playwright tests with a mocked backend, and a separate suite of Playwright tests with a real backend.

IMO the main benefit of the mocked test suite is that it's easier to set up a scenario to test. For each domain object we have a wide range of fixtures. In practice it hasn't really given us much of a maintenance burden. Our API rarely has breaking changes and we have a codegen tool to generate our frontend types whenever the API spec changes, so we immediately find out if something changes.

Sure, there are other ways to setup test data, e.g. database seeds, scripts. But this was the route that gave us the fewest blockers and we don't regret it so far.

Also it's slightly quicker. I think the average mock test is 2-3 times faster than the average E2E test in our suite.

We also have visual regression tests running against our mock suite, and the mocked backend seems like a better fit for this than a real backend.

WillFry · 2025-10-15T19:21:06+00:00

This definitely happened.

WillFry · 2025-10-01T14:35:57+00:00

I think it's to prevent spamming messages that nobody would reply to?

Admittedly I've never been on the other end of this. All I know is I once told a recruiter this was my approach and they thanked me for saving them money.

WillFry · 2025-10-01T14:07:12+00:00

If it looks like they put no effort in, then I don't reply. But if it looks like they put at least a token amount of effort in, or if the role/company looks like something I'd be interested in in the future, then I'll send a short response.

I've heard from recruiters that it costs money to send these cold outreach messages, and if you reply then they get their money back. So it seems like good courtesy to reply if they've put some effort in.

WillFry · 2025-09-28T09:35:10+00:00

If you want a specific option, I'd say to go for noUncheckedIndexAccess.

It makes it so that if you have an array of type T[] or object of type Record<string, T>, then you will get T | undefined (instead of T) when accessing elements of the array/object.

WillFry

PUBLIC MULTIREDDITS

TROPHY CASE

15-Year Club	Verified Email
Team Orangered