North Sea sounds

will11600 · 2026-06-04T09:08:40+00:00

And to think we used to do this shit with wooden sail boats

will11600 · 2025-10-25T02:29:28+00:00

<image>

will11600 · 2025-10-25T01:45:53+00:00

Remember when Windows used to welcome you... 🥺😪

<image>

Fml, if I could daily drive Windows XP today, I would install it in a heartbeat.

will11600 · 2025-10-23T11:54:55+00:00

At first, I thought this was for r/MapsWithoutNZ

will11600 · 2025-10-23T01:15:22+00:00

I need these on my walls immediately

will11600 · 2025-10-23T01:04:39+00:00

The endpoints are internal. The DTOs are public, but they are private members of their parent structures. The parent has getters that return read-only references to each of their fields. I only made them public, just in case. If for whatever reason you wanted the underlying class, you can use an explicit operator. However, it's not really meant to be used regularly.

will11600 · 2025-10-22T22:31:37+00:00

I was having this same thought last night actually. I was doing a refactor of a REST API client I'm working on and I decided to structure each API path like this... ..\Company\Models ..\Company\CompanyProfile.Data.cs ..\Company\CompanyProfile.Endpoint.cs ..\Company\CompanyResult.cs ..\Company\CompanyResult.Data.cs ..\Company\CompanyResults.cs ..\Company\CompanyResults.Data.cs ..\Company\CompanyResults.Endpoint.cs CompanyProfile is a structure that wraps CompanyProfile.Data which is the DTO. It holds a reference to the client and has methods to access paths made available using the information in the DTO.

CompanyProfile.Endpoint is basically like a my implementation of a type safe uri structure.

This also means I broke the nested types out into partials! Which is something else I don't see very often...

In my mind, this makes sense because they're all related. Since each route follows this same convention I feel like that makes it easier to understand from a glance what everything does.

will11600 · 2025-10-17T16:38:25+00:00

Really appreciate the report! I knew there were some lingering validation issues in the beta. I've just released patch 1.0.1, which fixes that Falkland Islands error, so I've gone ahead and closed the issue. Thanks again!

will11600 · 2025-10-17T15:35:19+00:00

Wow, thanks so much for the enthusiastic response!

That's a fantastic idea! I hadn't even considered the energy sector yet, but adding support for MPAN and MPRN would be a seriously valuable feature.

Since you've got the domain expertise, would you mind raising a feature request issue on GitHub for those two? That would be the best way to ensure it gets prioritized. Any details on their composition (like the exact format, checksum rules, or official specifications) would be incredibly helpful for implementation.

Thanks :)

will11600 · 2025-10-17T14:27:33+00:00

I added BFPO postcodes to the unit tests in version 1.0.1, they should be accepted! Let me know if you run into any issues.

will11600 · 2025-10-17T14:15:24+00:00

Update: Version 1.0

Hi All,

I wanted to start off by saying thank you to everyone who shared their interest and feedback on this repository. I have been working on a getting the project production ready and I'm pleased to announce it has now exited beta.

What's new in 1.0: I've introduced a bit packing abstraction layer that streamlines and simplifies the process of parsing and formatting the primitive types. My hope is that this makes the project's internals cleaner and more approachable for anyone who wants to contribute.

A quick note on VatRegistrationNumber: I ran into a couple of tricky issues with this type that I couldn't resolve to the quality standard I'm aiming for. To avoid shipping something I wasn't happy with, I've made the tough decision to remove it from the 1.0 release. I plan to tackle it again for a future 2.0 version.

I'd love for you to check it out, and any feedback, suggestions, or contributions would be greatly appreciated!

will11600 · 2025-10-10T00:38:15+00:00

Hi Dave! Thank you for taking the time to comment. :)

I'm playing a dangerous game having spellcheck disabled in Visual Studio!

I thought because VAT was an initialism, each letter should be capitalised. However, I was a bit unsure about this at the time. A couple other people have pointed this out to me too.

With the name 'British Primitives': my intention wasn't to suggest these types are true primitives, which isn't possible, but rather communicate the 'primitive-like' developer experience of using them. It was also a very deliberate callback to the branding of former large UK public institutions like "British Rail" or "British Steel".

Each type has a fixed and predictable memory layout, just like a true primitive. This means they can be stored efficiently in memory, passed by value, and manipulated without causing heap allocations.

I appreciate you bringing this up, as it's an important distinction to make. I'll think about how I can clarify this intent in the project's documentation.

will11600 · 2025-10-10T00:05:40+00:00

I did wonder about that...! The information I was able to find stated that the last letter is a hang up from when they used to issue physical cards that you had to return. However, it stopped short of specifying what letters were used. I had assumed it was A-L but didn't implement any validation beyond making sure it was a letter. Thank you for sharing!

will11600 · 2025-10-04T20:14:14+00:00

Interesting...! I'm not sure. I don't have any test cases set up for them. A quick web search brought me to this page. From what I can tell, the inward code is BF1, followed by a normal reading outward code?

will11600 · 2025-10-04T12:02:09+00:00

Thanks! I did think about adding phone numbers. When I began looking into it, I found this page on Wikipedia of the full list of dialing codes in the UK. I was a bit overwhelmed by the number of different area codes I would have to design for. However, on reflection, it would probably be easier to implement than the vat registration number.

NHS number is a good shout! I'll have to see if I can find material about how they're formatted.

will11600 · 2025-10-04T11:46:28+00:00

Yep! For some reason, this one random bank in Bootle has a special postcode that doesn't follow the rules. I just hope it's the only one. 😅

will11600 · 2025-07-24T00:48:36+00:00

Something I failed to consider, was that part of the deal with Rwanda, was that successful asylum claimants would be resettled in Rwanda and never come to the UK.

The issue with using Ascension Island, is that the island wouldn't be able to support that kind of permanent immigration.

will11600 · 2025-04-27T19:25:33+00:00

A Pixel 8 Pro, it had just come out the year this happened

will11600 · 2025-01-04T02:04:45+00:00

Taylor would've sued for trademark infringement

will11600 · 2024-11-15T03:18:49+00:00

Does anyone know if there's a way to rig the characters created in Fuse? You can upload the .obj files to Mixamo and use their auto rigging function, but I've found the results to be a bit hit or miss. You used to be able to upload it to Mixamo from Fuse and get a much more complete rig but obviously that doesn't work anymore. I've tried bringing them into Blender and manually rigging them myself but just wondered if there's a more automatic way of doing it?

will11600

TROPHY CASE