jsty

> This issue caused CF to irreversibly ban them though

Do you have a source for that? The article only mentions them being throttled + the screenshot with the support engineer saying they seem to be breaking the ToS and asking them politely to move back into compliance.

From a customer support PoV, soft deletes have the wonderful property that you can assuage the upset / irate individual on the other end of the phone that their data can indeed be recovered from whatever mishap they just engineered and do so with a simple query.

Yes - backups can help - but without live backups (WAL shipping or equivalent) you still risk some form of data loss. And if you have those, you just have soft deletes on a system level rather than an in-DB level + a vastly more complex system of partial restores.

No - GPLv2

https://github.com/oracle/graal#license

To hazard a guess - the delayed delivery of Aurora to Argonne National Labs, originally planned (in different form) for 2018 and now expected "late 2022"

https://insidehpc.com/2020/08/exascale-exasperation-why-doe-...

> the treasury feels that spending money, like eating people, is always wrong

I feel the Treasury would be more likely to hand out free soylent green than start spending money

> The end client should be the one to determine status and shoulder the responsibility if it turns out to be incorrect.

I'd say the opposite, the incentives / risk structure are otherwise completely misaligned. If the end client says you're outside IR35 and you should be in, they get whacked for income tax + 2x national insurance (employer and employee contributions). If they say you're inside and you should be outside they only have to pay the employer NI contributions.

That's a recipe for blanket "inside IR35" decisions, which is exactly what happened to the detriment of many genuinely independent contractors.

> Would it be reasonable for any company to hire Holden? If not, is there any chance for Holden to productively rejoin society?

> I am concerned, however, that a judgment like this will have a chilling effect on the hiring of certain groups of people.

My personal viewpoint on this is that - depending on the range of offences committed - there's some professions / occupations that should get closed off for a good while. You don't want your fraud-convicted individual working in finance or accounts, nor someone convicted of theft, assault, etc. working in people's homes, particularly potentially vulnerable individuals.

The latter case seems to be what Charter is accused of here. It's commendable to hire those that have served their time - to help them rehabilitate and repay any debts to society - but you need to ensure they're not put in a position where they might be tempted to offend again.

If you have access to BBC iPlayer, "The Capture" is a really good fictional programme / drama exploring the possible implications re. justice and politics

I had one of these a few years back and it was really helpful with developing breathing technique for high-intensity sports. I know a number of people with asthma found them very useful.

$650 was way off the mark for what I paid, definitely under £100, and Amazon UK currently has them at £65.

The Art of Multiprocessor Programming - Herlihy & Shavit

Yes, as long as you make the source available to customers under a GPL-compatible license (i.e. with no restrictions on their modification or distribution), you can charge whatever you like.

Unsure if it works exactly the same in the US, but in the UK there are ways to set up a holding structure via a share-for-share exchange and get pre-clearance of tax neutrality from HMRC (the tax authority).

If so, you can defer the decision on structuring to nearer the liquidity event when you should be able to get professional advice to implement the optimal structuring for you at the time.

The section titled "An Overview of Velox" gets into the meat of it - you give it some data and an optimised plan of the operators you want applied (expression, evaluation, aggregation, etc.) - Velox then executes that plan as efficiently as possible given the available compute resources.

That way multiple top-level systems like analytics databases, dataframe implementations, etc. can all share the same underlying execution engine.

> The fire suppression system somehow broke most of the hard drives in the server room

Possibly another case of loud noise when the gas is released - see e.g.

https://www.theregister.com/2018/04/26/decibels_destroy_disk...

https://www.bbc.co.uk/news/technology-37337868

Oh I don't think it's bad at all, just that in a toss up between the two it'd be better to include it - particularly given the chance of it being brought up in interviews. Having to then admit there's another employment you didn't include might not be the best optics.

> I don't think anyone who leaves within that period would even write this in their CV

Oh that's interesting, I'd have taken the opposite view - that having a 2 month gap on your CV would be interpreted by most HR depts as worse than explaining a 2-month job as "not a good fit"

Edit: I guess I should clarify that I don't see gaps in CVs as a bad thing, but from personal experience I know some HR depts have an irrational fear of them.

If only the WIP commits were non-Free then relicensed to Free for each release, then the legal uncertainty would probably have the desired effect - no packager / distro worth their salt would touch any non-release with a barge pole. Such an unorthodox approach would risk scaring them off completely though.

In a roundabout way it's pretty much trying to re-invent the trademark system (ie. "don't distribute this code and call it MyProject without it being an authorised release"). Quite frankly far easier to just get a trademark if that's the desired effect.

Love the idea of a space specialised to deep work, although if you're offering a space to work I don't think "no screens" should extend to a disconnected laptop.

If you're offering people to disconnect completely for several hours, some form of "we'll hold your phone / offer an emergency contact number" service would be attractive. Like it or not people - especially parents - have gotten used to being contactable at all hours in emergencies, and it would get rid of a major anxiety I think a lot of people feel when going off-grid.

Not sure how prevalent LinkedIn or a similar service is in Japan, but I'd imagine it'd be pretty easy to track how many clicks a customer was getting and investigating any that had anomalously high click / hire ratios.

App Engine Flexible [0] (i.e. the new version) is a lot more permissive - it's basically a managed container service.

Also - Google is perfectly good enough at turning down services on their own, we don't need to give them any ideas!

[0] https://cloud.google.com/appengine/docs/flexible

I won't try and read into whether or not there's ageism anywhere in the tweet stream, but certainly when talking about hiring the magic words are "find experienced engineers to run it". This is very much legal and ethical in the UK - we're not precluded from setting an experience-based hiring bar. I'm sure if a 25 year old had come along with two browsers under their belt they'd gladly have been hired into a leadership role too.

IIRC there was an ad involving a dog food manufacturer feeding their own dogs the food they made. "Dogfooding" then became synonymous with using your own product.

The "contracted for development" setup is common amongst multi-territory IP-heavy businesses. You choose a country to hold all the IP and have other locations sell development services to that country's legal entity.

You can do it to fiddle around with tax, but it's separately quite sensible to hold all your IP in a single region & entity to minimise the complexity - otherwise you'd have every territory licensing IP to every other territory, a.k.a an absolute mess.

Not just Oil & Gas companies - but oil and gas nations. There's quite a few geopolitically important countries that either derive a large proportion of their GDP / foreign exchange from hydrocarbons, or rely on them so heavily there's no practical path for transition by 2050.

Compared to the difficulty in getting these nations to play a full and productive part in any transition (requiring essentially restructuring a large chunk of their economies), settling up with extractor companies will be a walk in the park.

The AWS builders library has quite a few good patterns / design principles

https://aws.amazon.com/builders-library/

Which would be about the same amount of spreadsheets plus a few extra battle scenes

I think it would be a fairly novel interpretation of "persons carrying on a business in common with a view to profit" required to catch out contributors to an open source project.

Outside of a project that takes contributions / donations without a legal entity to receive them and parcels those out amongst the contributors, I can't think of a reasonable situation that would enable such a definition.

I'm on the side of the original wording here as far as correctness is concerned - "has proven to be" is a common expression for "in our experience, it is", whereas "has been proven to be" would give the connotations of formal proof.

This is just one of those quirks of human language. Yes it's occasionally annoying similar things have very disparate meanings, but English in particular is never going to shake them off.

> the Kafkaesque experience makes me think question our reliance on other Google services, like Cloud and Workspace

This last paragraph should really give pause for thought to anyone at Google whose OKRs involve revenue from non-Enterprise business customers.

Anecdotally speaking - I've considered running Google ads for my company more than a few times, and every single time the thought of a spurious "account violation" for those ads spreading and knocking out our Workspace and Cloud accounts has stopped me doing so - and I've spoken to a fair few other business owners who have reasoned likewise.

> Clearly they have the budget for a 32M failure. I’m inclined to think they’d be saving money.

The company would, but the relevant executive would be worse off. A $xx million consulting engagement failing is the consulting firm’s fault (politically speaking). Hiring and directing a $y million team that fails is the fault of the exec in charge.

Executives in large companies are frequently not the bumbling idiots they’re portrayed as - their decisions make perfect sense in terms of protecting and advancing influence within the company, which wins out over good execution in driving decisions.