gbuk2013

A (US based) PM on our team really liked to use “backlog grooming” until we sent him a few BBC articles about the connotations - he immediately changed his lingo :)

in our repo it would fail the CI due to no comment / exception linting rules before the review would even run :)

My VPS runs a DNS and mail, Postgres servers, web hosting with a couple of wordpress instances, a web app and several regular websites.

While there are infinite arguments to be made about individual diets, literally no one can do wrong by heavily cutting refined sugar intake.

> every living member of it's military, has never seen a single real battle

How I wish for a world where the same could be said for every other army!

I run Qwen3-Coder-Next-UD-Q4_K_XL and other than the initial wait to initialise context (which takes less than 2 minutes) subsequent prompts return in less than a minute, usually less than 30s.

If your performance is significantly slower then you are probably doing it in CPU - there was some fiddling required to get it to use GPU (I use llama.cpp)

Leaving aside the fact that there are not enough octogenarians in the Commons to pass any legislation, there’s no need to for ageist statements like that.

Not really, more like succeed without having to do anything.

The key is the perspective of what success is: it’s the state where the resource does not exist, or is the action having deleted the resource. But 200/202 is perfectly capable of expressing the distinction in the latter case as well.

> Then you'd return 202 on a request to delete any invalid element, which really doesn't sound right

It depends on your use-case if you care about this or not. If you do care you will have to handle it either way somehow.

But if you want an idempotent API then a success is more appropriate IMO than an error.

Response is implementation detail: a 404 on second request is one way to do it, a 202 would be another, or 200 with some sort of response to distinguish (e.g. { changed: boolean }).

Idempotency just means no state mutation on subsequent request.

You’re right - it’s not a campaign as such - it’s a set of scenarios (currently 22) in increasing difficulty. I haven’t played for a while after getting stuck but checking now I got stuck on the 5th scenario - even worse than I thought. :)

I played Zero-K several years ago and it didn’t stick in my mind as much but maybe worth revisiting it - thanks!

Reading about it seems to suggest that it’s even deeper in terms of strategy and tactics so I will probably struggle even more. :(

I used to play the original TA a lot and BAR is very well done. Much harder than the original though - I had no trouble with TA campaigns but I have not even made it halfway with BAR before hitting skill wall. Not a teen anymore so it’s hard to motivate myself to try and push through. :)