dust-jacket

Ah damn. I've only recently moved in to Bitwarden - paid - largely on the basis of a multiple-user shared vault and emergency grants to personal vaults.

I'd really, really like them to not to ruin it or make it massively more expensive.

That and the fact that they rip it up and shake it all about every few years just to seem like they're doing something different.

> Discovering a bug that could put people's lives and/or freedom at risk if they don't do something about it makes it okay to go public immediately

The flipside of course is ... does your disclosure increase the risk?

> aiting to disclose something harmful when the users in danger could otherwise take steps to make themselves safe would be like not warning people entering a building not to go in because of a gas leak until after you've contacted the building owner and the fire department has shown up

I don't think it's like this at all. The risk of a gas leak is not increased by telling people about it and can't be prevented after its occurred. To stretch your analogy, I'd say its more like you've found the gas leak and instead of turning off the gas supply are instead running around outside the building shouting about how there's a gas leak.

I don't feel like its hard to come up with examples where (I would say) its ethically wrong to disclose immediately. If you spotted a company's mistake that might endanger their user's lives or safety, would you put those users at risk simply because there was no obvious financial reward?

If so, I guess we just have different opinions on the ethics involved here.

Yeah having worked _with_ NHSDigital quite a lot over the years, I would not love to work there!

That said, I don't think there's that much wrong with that job description - I've been a software dev/eng for 15yrs and every role has had SQL at its centre. And its much easier to get someone new up to speed on some swanky new UI or scripting tool than it is with SQL IME, so prioritising people who are comfortable with the hard bits sounds fine to me.

No, wait, I've read it a bit more closely. It's all about Data warehousing. OK yeah, that's a data job.

I don't doubt that valid Python can include hard to read code. You xcan write gnarly Python, for sure.

But I'd still argue the average Python codebase tends to be pretty legible and simple to read.

Not having a bug bounty or dedicated email address does not make it OK to go public immediately

Having spent time working in UK healthcare tech, I never understood why everyone was lining up to throw buckets of money at Palantir. Quite apart from being obviously evil and so on, none of their solutions were actually very good.

Unfortunately, it's hard to escape the feeling that friends in high places, some lobbying and some er... reciprocal back scratching might have been instrumental.

See also senior staff at NHS England (or Digitial? can't remember) handing massive NHS compute contracts to AWS, and then leaving the civil service to become... an AWS employee.

Reaaaally?

I think a lot of the readability of python is in the fact you don't need to be recently familiar with it to pick up what its doing most of the time.

Over my career I've dipped in and out of rust, typescript, perl, swift, etc codebases. I'm no expert in any of these, but every single time I have to look something up to understand what this set of arcane symbols or syntax means.

When I dip into Python I just ... read it.

(None of this is to say I prefer Python, just that I really do get the readable thing)

I doubt it. Interns are cheap. They've replaced paid staff with interns!

> PR approval is too boolean. The PR is approved or it's not approved. Real code review, like real life, lives in the middle

This is have-your-cake-and-eat-it. PR approval is a permission so is a boolean. Of course it is. Either the code can be merged or it can't.

What's being described really here is just something to make you feel slightly better about yourself whilst approving code you hate ("we should revisit this..."). Just open a new ticket.

But that wasn't your point. Your point was that, because Russia, it _didn't matter_ if it did constitute stealing.

interesting, I'd assumed the lowest tier of hetzner (4.50/m, 2 cpus, 4GB ram) wouldn't hold up to that.

must be very light, for so much traffic. any more details?

ah, thank you. Haven't worked in java for a bit now, but that was the only one I read where I was like "I'm sure we didn't have to avoid this when I worked on java".

The rest were all very familiar. Well, apart from the new stuff. I think most of my code was running in java 6...

I now really want my city to employ local artists to redraw all the street markings.

Chaos, sure, but beautiful chaos.

I mean fired and resigned when it became clear you'd be fired are the same thing really.

We're not actually entitled to know the exact details of someone's job ending. They worked there. Now they don't. That much is the bit we're entitled to.

Nah, The Register is far more strongly anti-AI. Mention AI and systemd in the same article and watch them froth

I absolutely disagree.

This has been done very professionally. They pulled the article. They handled the personnel matter. They didn't try to pretend it hasn't happened.

Why are people here acting like retracting an article is an attempt to hide something. They literally replaced the whole text with a note from the editor saying "this article was bad".

This is kinda cool. Thanks for sharing.

This is mad but cool. Keep at it.

nice concept, but my 'nearest' was miles away and not really a pub. Hmm.

require commits to be signed.

OK "Jeff Dean once shifted a bit so hard it ended up on another computer" got a proper chuckle from me

No, this is silly. Don't do this. You absolutely keep pushing for a refund and go via you CC provider if they don't respond.

IDK, I think this is too negative a take. It's easy to blame those in charge for not realising that your problem was the important one but ... how many problems were they being presented with?

Sure, in this instance, they prioritised the wrong problems. But perhaps the case wasn't made clearly enough to make it apparent why this was as big a deal as it was.

I mean I'd guess it was because it's somewhere with a higher bar to firing. Redundancy or dismissal are both much more complicated (expensive) than simply making it very clear you'd like someone to leave.

Yeah I thought this was a weird take too. Too often people take privacy for "I can do what I like". IMO deleting something you've sent to someone else is not a privacy concern at all.

ah, didn't realise that, thanks

Yeah, people have such short memories for this stuff. When we ran our own servers a couple of jobs ago, we had a rota of people who'd be on call for events like failing disks. I don't want to ever do that again.

In general, I'm much happier with the current status of "it all works" or "it's ALL broken and its someone else's job to fix it as fast as possible"!

Not saying its perfect but neither was on-prem/colocation

to be clear, that's just a limitation on their free service. If you pay, you can keep your own DNS