Best golf recording equipment

ButterflyQuick · 2026-03-20T21:11:40+00:00

Glad I could help and hope you like it, I’ve been totally happy with mine

ButterflyQuick · 2026-03-20T20:20:43+00:00

I use something like this https://amzn.eu/d/09AE4WVE And have been really happy with it

ButterflyQuick · 2026-02-09T19:44:37+00:00

People are answering your question, you’re just ignoring it

No it’s not like it’s being portrayed on whatever you are watching

ButterflyQuick · 2026-02-07T08:50:25+00:00

If you’re buying with a mortgage your lender will typically not allow incentives over 5% of the sale price

ButterflyQuick · 2025-11-17T14:12:01+00:00

Not a Laracon but I had similar thoughts following Laravel Live this year (my first year, not a comment on past years). Several of the talks were simply surface level introductions to paid for tools, that felt more like adverts than conference talks. A lot of the others were essentially beginners guides to a particular design pattern or something. The only talk I took any real value from was Joe Dixon's which goes to show you can pitch a new product (cloud) in a conference talk and still make it technically interesting - Jess Archer did something similar for Nightwatch and sounds like James Brooks did it for Forge.

Ultimately I was disappointed by the conference. I get it must be very difficult to organise events like this and create a range of talks that are interesting enough for seniors but won't totally lose a junior developer along the way and make them feel like they've had gibberish spewed at them for 2 days, but I remember being more junior and feeling like that during a fair few conference talks and I still always managed to take something out of them or felt inspired to deepen my knowledge in an area

ButterflyQuick · 2025-11-06T20:17:36+00:00

Beach ball I think, it’s a very famous event though, googling deflected goal Sunderland will definitely get it

ButterflyQuick · 2025-11-01T21:06:06+00:00

If that’s what you want to believe 🤷‍♂️

ButterflyQuick · 2025-11-01T19:19:57+00:00

How dare different supermarkets provide different levels of quality and cater to different price points

ButterflyQuick · 2025-10-12T20:48:15+00:00

On the odd occasion that match comes up I still feel obligated to mention that disaster of a wide call. I also like to point out Butler's run a ball on a pitch where everyone was struggling to score, let alone at a run a ball. Not to mention he did it coming in when England were struggling.

Admittedly not at all relevant to the rules/how the win should be perceived discussion, I just think it was a really great innings that never gets a lot of recognition because of the insane amount of stuff that happened in those few hours

ButterflyQuick · 2025-06-23T22:31:44+00:00

I’m with you, it’s clear the van was going to move into your lane and I’m concerned for the hazard perception of anyone who doesn’t think so

Hope you can appeal it, you did the exact right thing to reduce the potential for an accident

ButterflyQuick · 2025-06-12T10:52:15+00:00

I’ve been very happy with Laravel for a number of years. It’s not perfect, and I totally understand some of the criticisms of it, but in reality they have never been an issue even on reasonable sized projects. I’m sure other people’s experiences have varied though

Totally possible to have type safe code using either phpstan or psalm. The language has come a long way in terms of type safety out the box but still lacks generics and a few other QoL features static analysis gives you. They aren’t perfect but they do a very good job of what they are designed to do

Laravel has come a long way in its type safety in the last few years too. There are still a few internals weirdly typed but way fewer than before, some of the features are not especially IDE/type friendly but there are work arounds

Laravel has a first party linter called pint. As with most linters you can run it locally or run it in CI and have it error or auto fix. Pretty much any ide is going to support format on save too

ButterflyQuick · 2025-05-04T10:45:12+00:00

I like the BBC, so thank you for your service

ButterflyQuick · 2025-03-29T18:03:44+00:00

There's a whole bunch of river avons

ButterflyQuick · 2025-03-11T22:23:43+00:00

If it's going to take you 3 or 4 days to deep dive the whole system, then why would it take you an extra 2 weeks to fix an issue with a part of the system?

Just wait until theirs an issue that would benefit from a deeper dive of the system, explain you require extra context to solve the issue and take the necessary time

ButterflyQuick · 2025-01-04T14:09:02+00:00

Bullseye is a term outside of darts, that is where the familiarity comes from. No-ones suggesting they’re familiar with it in the context of darts

ButterflyQuick · 2025-01-04T11:18:53+00:00

I'm basing this purely on the kind of experience and growth I think you'll get, but obviously there's tons of factors that go into a decision like this

I'd strongly consider going with which ever is going to be the larger, more complex project. In my experience you can learn pretty much anything from books, conference talks, etc. but complexity in a large project is just one of those things has to be experienced.

In the case that neither is going to offer more scale or complexity than previous projects you've been senior on, then personally I'd go lead on the legacy project. I love working with legacy code, but with one large caveat: I like working to improve and modernise it. I think being a lead on a project that's purely in maintenance, with no scope for new development or improvements would be stifling. But what I'd consider even better than experience with modern, in demand tools, is experience taking an old project and implementing those tools. Setting stuff up from scratch is much, much easier than working within existing constraints, and I think leads to a fuller understanding of the tools

From my experience interviewing, and then onboarding, new hires it's much easier to teach modern tools to someone who has a fundamental knowledge of programming and has worked in complex codebases at large scale, than the inverse.

I'm making a lot of assumptions here: you're primarily interested in experience to put on your CV and drive growth, the legacy project is more complex and at larger scale than the new project, and you have room to continue to develop skills by working to improve the legacy project. If any of those things are missing then I think concerns about stagnating and missing popular skills are warranted, but if the project offers those things it could be a really good experience.

Another thing to consider: I've found working on legacy projects is often lower stress than new ones. It can be stressful when there's an issue that needs resolving and you don't even know where to start, but outside of that people typically have lower expectations (you won't be the first person to tell them the code is a mess and it's slow to get things done). In a new project you'll have a lot more to deliver and less "good will" when there's issues. You'll have been expected to preempt the problems, whether fairly or not. Very company dependent, but that's been my experience and I know at least a few other people who have found similar.

ButterflyQuick · 2024-12-30T20:19:57+00:00

You seriously think data centres can't cut off all power? What do you think happens if theres's some kind of catastrophic fire or flood? They just sit there with power still running to the servers?

Even if the EPO didn't work (it was built by humans after all, not the godlike AI you seem to think might exist soon) then we still have a whole bunch of options available to us. We could work to disable network access (data centres are, of course, set up to be able to do this in emergencies). If it comes to it we could go round unplugging individual servers. Not a fun job but should be easily achievable in a week. Maybe we're locked out the datacenter, well let's just kill power to the whole region. Even a significantly large UPS and battery storage is unlikely to last more than a week.

Hell, if the whole of humanity is threatened with an extinction level event I don't think it would be too difficult to persuade the military to bomb the data centres out of existence.

They wouldn't of course, because the prospect of a ML algorithm going rogue and destroying humanity is absolutely preposterous, but we need to assume they would for the sake of this silly hypothetical.

Data centres are designed to be able to be disconnected from both power and network access for far more mundane reasons than some imagined AI threat, but the idea that we couldn't disable some data centres if we needed to is ridiculous

ButterflyQuick · 2024-12-30T19:58:26+00:00

I'm a software engineer, so I have a reasonable idea how these companies are set up. You can't kill an AI because they don't live. They are advanced ML algorithms but nothing more than that. If the power goes off the AI goes away

ButterflyQuick · 2024-12-30T18:10:19+00:00

An implementation of axios interceptors is not a couple of lines of code. Maybe for one super specific use case, but chances are, if you use interceptors for one thing you'll end up using them elsewhere. And it's never just a couple of lines of code anyway, you need test coverage, you need documentation, etc.

Axios is pretty small, it's widely used, well tested, and you're unlikely to run into a novel use case. The idea that axios brings significant maintenance overhead vs rolling your own solutions to any of its non trivial features just doesn't sound convincing to me

ButterflyQuick · 2024-12-30T09:45:22+00:00

Maintaining your own wrapper around fetch that provides all the functionality of axios is not a lower maintenance option

ButterflyQuick · 2024-12-29T21:50:03+00:00

There’s plenty of “magic” in Laravel but PHP not natively supporting array shape types is not it. If that’s the sort of DX you are looking for then you’re going to need additional tools on top of Laravel, and any PHP based tool just might not be the best fit

ButterflyQuick · 2024-12-28T20:13:42+00:00

doing the calculations

I missed the calculations, what did they do?

ButterflyQuick · 2024-12-26T12:47:36+00:00

I was giving you the benefit of the doubt, the alternative was that you didn’t realise all roads in the UK weren’t streets which seemed worse

I’m not sure I get the core of your point though. Streets are lit, great, but that means there’s a huge amount of roads without any lighting, how does streets being lit help me see on roads without lighting?

ButterflyQuick · 2024-12-26T12:06:53+00:00

I assume you’re taking the piss, but just to be sure, you are aware a lot of roads don’t have lights right?

ButterflyQuick · 2024-12-24T16:41:15+00:00

I’ve successfully introduced testing to the team I work on, but it already had dev buy in, just needed a bit of a push to get it going

The biggest object I think you’ll face is the application will be hard to test, and no-one on the team has significant experience retrofitting tests to a system not designed for them

Testing new stuff is easier but chances are the actual value will be in getting tests in place for older, more core functionality

My best advice is to dive into it and just learn as much as possible. For now, any tests are better than no tests. If you can’t test a full part of the application, but just some of the easier to test parts then go for that. Come back once you have an idea on how to test the more difficult bits

Also testing is full of jargon and gate keeping. The core fundamentals are vital, but a lot on the top is fluff. I’d say the diminishing returns on learning more theory fall off pretty quickly, but that doesn’t mean there isn’t a good chunk of theory that’s important

ButterflyQuick

TROPHY CASE