A bit of a bizarre post since to_sgid has existed forever to generate signed global ids. Global IDs are probably one the most powerful and underrated features of Rails but regular global ids are only supposed to be used internally (e.g. job params) and never sent to the client.
If there’s a gotcha it’s that _signed_ global ids are only signed, not encrypted, and very few people seem to know about the optimised method (globalid::Locator.locate_many) for loading a batch of global ids
I'd love to see some more detailed write-up on how to switch to Warpbuild for different tech stacks. I tried a few months ago when the instructions were basically just to change the runs-on type but IIRC it failed with an error around setting up ruby (and caching it?) and there were no clear instructions on how to proceed.
I worked on agent-based systems >20 years ago, including large research projects and standardisation/interoperability work.
Ultimately, that effort failed but I don’t see any awareness of that considerable volume of work reflected in today’s use of the word “agent”. If nothing else, there was a lot of work on the use-cases and human factors.
It’s just a bit disheartening to know that so much work, by hundreds of researchers (at least), over 10+ years, has just slipped into irrelevance
I've been using https://www.tinycert.org/ for years which basically lets you create your own certificate authority and issue certs (which obviously aren't trusted by everyone but can be trusted by you/your team). It's ideal for generating SSL certs for ephemeral apps e.g. review apps on Heroku since it can all be done using an API
A lot of people complained that GDPR was too onerous on small firms and that they should be exempt. According to LinkedIn https://ie.linkedin.com/company/exactis-llc Exactis has just 10 employees (obviously some error possible. Call it 15-20?)
Now do you think small firms can’t hold large quantities of damaging data?
Probably the most famous wartime loss was the Lusitania off the Old Head of Kinsale. Its fame is partly that it was a Cunard ship like the Titanic, and partly because of the controversy around her cargo. Although it was a passenger liner, it was sunk by a German U-Boat because it was thought to be smuggling arms from the then-neutral US to England.
It's good but not perfect since the lifeguard thankfully rescues them before they drown but it's still a good exercise. I can do this exercise fairly reliably but I'm not perfect either.
Particularly when the wrong flag is used. In this case, Gaelige is given the Scottish flag when it's actually the official language of Ireland in the EU. Scots and Irish Gaelige are not the same language. And Scotland is not an EU member (it's membership, sadly, is by virtue of the UK's membership)
If you outside the EU, it really isn’t about “anyone coming after you”. Even within the EU the enforcement actions currently err of the side of a stern warning rather than fine (except in the most deliberate cases). Though that may change.
Either way, you shouldn’t be doing it out of fear. You should be complying for practical business reason
1. This is how you should be treating personal data.
2. In exchange for complying with GDPR, you get access to a market of >700m people. If you’re a service provider, it’s illegal for any EU business to be your customer without GDPR compliance.
And some of the screenshots reveal an approach to hiring which is sorely lacking. At this stage, every single LinkedIn email and cold outreach email from a recruiter gets marked as spam.
Not a single one seems to understand that hiring should be treating people as… well, people with lives and desires. Not just a resource to plug into a hole; not a fool to be tricked into changing jobs so the recruiter can hit their targets.
Any innovation in this space is welcome and I hope there are enough "decent" companies to make it a successful business.
fwiw, part of the advantage of going freelance was side-stepping all the bullshit hiring assumptions.