@OJFord | Hacker News

> I do wish I had an easier way to split up a commit that accidentally included several unrelated changes though.

Perhaps it's what you want something easier than, but I have `uncommit` aliased to `reset HEAD^`, and use it often as `git uncommit -p` (then amend, then the 'uncommitted' changes are unstaged ready to go in a different commit if they were wanted just elsewhere, or removed if not).

Ha, I only meant your children's. Did it not used to be 12y as long as with a meal (and adults) or something?

Otherwise that's pretty much the same as the UK, except the 16/18 distinction is drink/buy rather than low/high ABV. (That's my recollection anyway - I'm almost as far past needing to care for myself as I am away from caring for anyone else!)

In my reading, the point of 'as a Pole' is to say 'look I bear no ill will towards Poles, I want the best for Poland as much as the next citizen', it's not claiming authority, it's disclaiming bias against.

Very good point.

It's worse than not fixing it, the trend is to make it worse, by removing soft furnishings etc.

Saw an article recently on loud restaurants (the loudest in the world are in London, followed by SF iirc) - the top few in London were measured as so loud that per the law (I assume it's not known/adhered to) they have to provide staff with hearing protection from the injurious volume!

Ok, I think I see why it's a bit weird '1,2,3 when i=1 and j=3 it swaps them anyway' sort of thing?

But i-loop comes through 'afterwards', so when i=3 (value now 1) and j=1 (3) it sets them straight.

It still seems quite intuitive, but I think I cheated by skimming over it initially and thinking it was clear, whereas actually I've thought about it more now.

(Not to compare myself to anything like him, I'm no mathematician at all, but I'm reminded of an amusing Erdós anecdote in which he apparently paused mid-sentence in some lecture, left the room, and came back some time later continuing 'is clearly [...]' or similar!)

I wonder how teenage alcohol abuse compares across countries, France in particular comes to mind since it's common to introduce wine relatively early (in moderation, and perhaps diluted, of course). I thought there was quite a young supervised with-meal drinking age too, but having searched for it perhaps that's changed (or I was wrong). If it's not some forbidden fruit maybe the run off with a bottle of vodka thing doesn't happen so much.

> UK pub culture doesn't tend to be that intentional about meeting particular people but rather hanging out where others may or may not show up.

Interesting, other than 'the locals' propping up the bar, that's not my experience at all.

I think going to each other's homes (on a smaller scale and in a less organised way than 'a party') is more common now. For whatever reason, I wouldn't like to say, could be fashion, could be the other side of 'the pub is too expensive', or something else.

Why is this algorithm at all surprising?

(I'm really not trying to brag - I assume I must be missing something, that I'm naïve to think it obviously works, and it actually works for a different reason.)

In plain English - 'for every element, compare to every element, and swap position if necessary' - .. of course that works? It's as brute force as you can get?

I think it's because if unbundled it would collectively cost a lot more, and nobody actually uses everything (or even more than one, maybe two) much anyway, so it's sort of a costless value-add to bundle them. 'Huh yeah maybe I'll use that occasionally.'

I'm sure they'll have run focus groups or whatever with proposed unbundled pricing to see which services people would pay for and how it stacks up.

You only need one of {AND, OR} too.

((a or b) is (not ((not a) and (not b))), and vice versa.)

Standard would be pozidriv, probably PZ2. You could certainly get torx if you preferred though (or Phillips or flat, if you really hate yourself!) - UK.

Each of your projects could use a distinct terraform workspace; the hypothetical `terraform <plan|apply> --nuke` would already need to look across all workspaces, considering all state. Or/also it could look at multiple remote states.

> Then there are also platform or connectivity level cloud resources (e.g. Transit Gateway and subnets that are mapped into the internal organisational network address space in AWS) that a random terraform project ought not to manage.

Not a 'random' one sure, personally I'd still want it somewhere. I suppose the hypothetical command might want an optional whitelist of non-tf-managed stuff to ignore though. (But then, you could whitelist it just by writing the terraform and importing it?)

> Lastly, if there is an actual need, a resource that terraform does not know about can be manually imported

The hard/annoying part that I'd like this command for is discovering these resources. i.e. it's not just that terraform does not know about them, it's that I probably don't. Or at least I don't realise they're not captured in terraform.

A very easy one to overlook is security group rules: unless you define them inline in terraform (i.e. ingress/egress blocks on a security group resource) then adding additional rules outside of terraform does not cause a diff. So you might be testing them out by manually poking around, and then you forget to terraform them/remove them, and they're left there forever with terraform blissfully unaware, and if you ever happen to notice it might not be obvious whether they're needed or not.

Essentially, it'd be useful for enforcing that terraform's used for everything; maintaining 'IaaC' hygiene.

> I have never seen a square (Robertson?) screw in the wild, I assume that's regional.

Almost exclusively Canadian I believe.

You can get them though, I bought a Kreg pocket hole jig in the UK which came with some for some reason, and had no problem getting bits for them (Amazon I think).

I'd never seen them (IRL) before that either.

It's also just annoyingly redundant, and breaks searching, completion, etc.:

    @app.cond('is foo')
    def is_foo():

    @app.cond
    def is_foo():

I found it a very effective way of learning a new script (devanagari) but I'd have really struggled to answer sentence based questions without studying at all outside the app. (I'm reading Snell's textbooks on Hindi, and have finished the Duolingo course.)

Yeah exactly, GitHub would be sold, not turned off.

And that would worry people, sure, new owners may not look after it, etc., but there'd be plenty of time and warnings to move off it.

> They had an Illy logo which helped a bit.

Interesting, does it? Obviously tastes differ, but I'm trying a tin at the moment because I ran out and could get it same day vs. waiting for delivery from my usual roaster subscription - I may as well be drinking any old thing off the supermarket shelf, don't find it superior at all.

Possibly the blend just isn't too my taste, it also doesn't seem to be as fine as I think I would grind it, but I think the main thing is freshness. Despite its vacuum seal it's still months old, vs. I usually receive beans within a few days of roasting and grind on demand.

I've hitherto assumed it didn't because it wasn't, short of calling every single `*:Describe*` API anyway.

But the existence of aws-nuke makes me think (I haven't looked into what it's doing yet) there must be a better way of discovering used services/resources. Through billing perhaps?

But that's what I mean, if that's how it works, nuke needs to account for it. I assume it already does for other dependencies, because there are a lot of them - including that do make more (obvious) sense.

You're not the only one to complain about the documentation though, so it's easy to see how aws-nuke apparently missed it!

What I mean is 'yes that's a weird interaction' but, if that's how the AWS service works (however weird) then it's an aws-nuke bug that the ordering isn't correct (to account for that weirdness)?

Though 'not at all documented' makes that harder of course. I haven't used it.