macca321

Yes, real developers know the quirks of ie6 Vs Firefox 3

About 15 years ago I implemented "cache namespacing" for memcached, where you build a final cache key for a stored item (e.g. "profile_page") by doing an initial multiget cache query for all the "namespace" version values (e.g "user_123", "team_456" might be needed for "profile_page"), which you combine together as a prefix for the final cache key.

You can then invalidate any final cache key that uses one of the namespaces by incrementing the namespace key.

I haven't come across this technique mentioned elsewhere since, but it's very useful.

See the namespaces section in the now 404ing memcached FAQ https://web.archive.org/web/20090227062915/http://code.googl...

I guess nosql, edge caching and materialised views make it less applicable than it used to be (when inelastically scaling single/replicated SQL instances were the only game in town and taking load off them was vital).

Or is this technique now a first class feature of various cache client SDKs?

It'd be very interesting to know Hashi's internal strategy around this.

- Maybe do nothing, and as long as OpenTofu doesn't attempt to extend Terraform they are in not that different a position than pre-MPL.

- Add so many features OpenTofu can't keep up?

- Add some sneaky code to latest versions of hashi providers which makes them not work with unofficial terraform binaries?

You can exfiltrate secrets that aren't in the state, but are in accessible resources during a plan using an http data source with the secret encoded into the url

I wonder if a non commercial Terraform Cloud "offering" like https://github.com/leg100/otf is "competing" with Hashicorp...

In the long run, I wonder if all video will be signed via blockchain-or-other-trusted-3rd-party. You'd need everything from the camera to the the editing software to support it though.

I would really like a client-side js library that lets you sync localstorage to consumer cloud storage (onedrive/gdrive etc)

The thing people like about Facebook is looking at other peoples photos, safe in the knowledge that they don't know you are looking at their photos.

It would be a lot harder in the Culture to get someone to be your human footstool.

I use it because my mum, who has Parkinsons, can work her Facebook Portal.

I think a process like this works well for enabling the success of the kind of people who like the sound of a process like this.

In a polyglot shop, it can actually be quite handy that HCL is it's own relatively simple language.

Better to return a union of custom result types. Save exceptions for when stuff goes really wrong.

What action am I meant to take in response to these stories? Put £5k aside to buy shares?

Carter

I don't like it either, but one advantage is that the settings can be live updated when the config files change

Teeth are a luxury.

Lobby government for green energy

Mortgage repayments are much cheaper than renting, at least where I am in London

This is an article from 2008 by the person who invented REST.

Probably for the API access to Zendaya's Insta and Twitter accounts

You should see the crazy Psion devices my dad used to spend £500 on in the 90s. There's a market

Or, "how to stifle innovation with bureaucracy".

This is a SAAS product if ever there was one

The title is correct, but the article misses the most important thing. The reason you should not divide them is that delivery of a non trivial feature requires change at each layer of the stack.

Conway's Law etc etc

Are they happy with 8hr a day? I keep worrying that I'd have to put in 12 hr shifts to keep up with the graduate hires.

I reckon JMESPath should be first choice in 2020, as it's properly specified, so you can find x-language implementations that behave the same.

I though we could call it UnREST

FIOH from the article is better ŧhough

Worth reading "The Hypermedia Maturity Model" afterwards

https://8thlight.com/blog/jason-desrosiers/2018/05/30/the-hy...