> A Home Office spokesperson said: “Over 10 million people have already successfully used eVisas to prove their immigration status. ..."
So how many people did not successfully use it? Could be 100 million for all we know. Do they think just throwing out a large number without anything to compare it to is somehow proving something?
> Do they think just throwing out a large number without anything to compare it to is somehow proving something?
Welcome to the last 20 years of UK public policy communications. Politicians and their consultants know that people in general are not that smart and do not question big numbers or have the skills to
I've had issues with this e-visa implementation and was told I could not board flights.
As a someone in tech, I feel this a classic case study of how NOT to roll out a release and develop a solution.
The release was chaotic, none of the airlines staff were trained on how to use this. So they still insisted on the expired cards and then picked on the expiry dates.
Next, almost everyone makes you generate a verification share code in front of them by logging into the e-visa website even if the rules say I can print it out and just use the code. It takes a few minute to get on the website and generate one.
This solution assumed that everyone has access to a smart phone and a good wifi connection to make this work.
> Whoever built this didn't test it on the ground.
God this happens all the time. Software written by people that don't use the software themselves. It has happened to me so many times, I come across a piece of software with weird bugs or interactions that would be immediately fixed if the developer just spends 5 minutes using the software like an end user would. Dogfood all the things!
> Software written by people that don't use the software themselves. It has happened to me so many times, I come across a piece of software with weird bugs or interactions that would be immediately fixed if the developer just spends 5 minutes using the software like an end user would. Dogfood all the things!
My experience is completely contrary: developers typically do care deeply about such things. The problem is rather that very commonly managers actively disallow these poor developers to apply their diligence to the software that they develop.
I really have a strong feeling that you want to participate in the ugly vendetta against software developers that has been going on for decades ("Replace all software developers"; current season: "Replace them with AI").
Don't do that. Rather fight the people who are really responsible (who are often (project) managers or Scrum masters).
"I really have a strong feeling that you want to participate in the ugly vendetta against software developers that has been going on for decades ("Replace all software developers"; current season: "Replace them with AI")."
Paranoia?
There are a lot of devs who don't really like what they develope so don't spend any time dogfooding it. Has nothing to do with devs who are blocked by management.
>
There are a lot of devs who don't really like what they develope so don't spend any time dogfooding it.
Note that in my comment I wrote nothing about dogfooding - for a very good reason:
It is well-known that dogfooding leads to software that has rather few bugs, but also dogfooded software often shows a tendency to be "biased towards programmers and power users". So, there often exist very good reasons if the programmers actively don't dogfood their software, and rather trust someone else (who is very trusted by the programmers) that the workflow that the programmer should implement does make sense for the user, even though most programmers would implement this very differently.
So did we, although we were in the end able to persuade them to let us board the flight by showing a screenshot of my friend's eVisa status from the UK government website (so secure!)
To be fair to the airlines here, if they get it wrong then the UK government fines the airline. This is why they are pretty risk averse, and also why I'm surprised that the screenshot worked.
I bet you 100% it was built not by in house team but farmed out to an agency for £££££ millions. They will have been saying in their case studies some absolute nonsense about how they saved the government millions rather than burned loads of money too.
It'd be lovely if articles like this named the people responsible for actually building the systems. It's almost certainly never a government department.
They'll have paid one the many software/technology companies to build this thing. Who will be hiding their shoddy crap behind their client (the government department that paid for it). There are some patterns that I'm sure would start to arise from naming the consultancies that are churning out crap.
I have identical twin boys - when signing up for a bank account app and while completing all the associated hoops for ID, the second to do it got the rather dystopian error message 'an account has already been registered with this face'
I wonder how it's possible they didn't think about this problem. Considering everyone involved in building this feature, not a single person thought about the possibility of twins or simply people who are very alike? Also, can't people open multiple accounts?
I imagine that it probably went like this "what about identical twins?" / "Don't worry about that for now, we'll solve for it before we go live, but it's not in this milestone". Then someone pulls rank and decides the product is "good enough, we can't wait for all bugs to be fixed" and gets it deployed.
Just look at the "falsehoods programmers believe about ..." articles that pop up from time to time. There are plenty of complexities in the real world that people either don't know about, aren't front of mind when they are tackling a larger problem, or simply don't want to deal with in the here and now. Lost knowledge and new problems are part of the reason why programmers are discouraged from rewriting software from scratch and why businesses in general are hesitant to replace legacy systems that still work.
Based on my experience I assume someone mentioned the risk, others said it’s unlikely and only a small percentage, that we should care about the 99% for now. Then the issues isn’t revisited until someone impacted complains enough.
p99 is ok for web stuff, not for systems that impacts people in their life, but I’ve seen too often things being dismissed because they are edge cases (which becomes an actual real issue at the scale of a country of course)
Because it probably does the dystopian tracking well enough, they don't care if it's not 100% accurate. Edge cases in the new world have no recourse, citizen.
I suspect this case has origins less to do with the programming itself, and more to do with UK bureaucracy just not giving a shit, as with the post office scandal where authorities, including the legal system, blindly believing in the outsourced systems led to hundreds of false prosecutions and thirteen suicides (https://en.wikipedia.org/wiki/British_Post_Office_scandal).
> A Home Office spokesperson said: “Over 10 million people have already successfully used eVisas to prove their immigration status. ..."
So how many people did not successfully use it? Could be 100 million for all we know. Do they think just throwing out a large number without anything to compare it to is somehow proving something?
> Do they think just throwing out a large number without anything to compare it to is somehow proving something?
Welcome to the last 20 years of UK public policy communications. Politicians and their consultants know that people in general are not that smart and do not question big numbers or have the skills to
I've had issues with this e-visa implementation and was told I could not board flights.
As a someone in tech, I feel this a classic case study of how NOT to roll out a release and develop a solution.
The release was chaotic, none of the airlines staff were trained on how to use this. So they still insisted on the expired cards and then picked on the expiry dates.
Next, almost everyone makes you generate a verification share code in front of them by logging into the e-visa website even if the rules say I can print it out and just use the code. It takes a few minute to get on the website and generate one.
This solution assumed that everyone has access to a smart phone and a good wifi connection to make this work.
Whoever built this didn't test it on the ground.
> Whoever built this didn't test it on the ground.
God this happens all the time. Software written by people that don't use the software themselves. It has happened to me so many times, I come across a piece of software with weird bugs or interactions that would be immediately fixed if the developer just spends 5 minutes using the software like an end user would. Dogfood all the things!
> Software written by people that don't use the software themselves. It has happened to me so many times, I come across a piece of software with weird bugs or interactions that would be immediately fixed if the developer just spends 5 minutes using the software like an end user would. Dogfood all the things!
My experience is completely contrary: developers typically do care deeply about such things. The problem is rather that very commonly managers actively disallow these poor developers to apply their diligence to the software that they develop.
I really have a strong feeling that you want to participate in the ugly vendetta against software developers that has been going on for decades ("Replace all software developers"; current season: "Replace them with AI").
Don't do that. Rather fight the people who are really responsible (who are often (project) managers or Scrum masters).
"I really have a strong feeling that you want to participate in the ugly vendetta against software developers that has been going on for decades ("Replace all software developers"; current season: "Replace them with AI")."
Paranoia?
There are a lot of devs who don't really like what they develope so don't spend any time dogfooding it. Has nothing to do with devs who are blocked by management.
> There are a lot of devs who don't really like what they develope so don't spend any time dogfooding it.
Note that in my comment I wrote nothing about dogfooding - for a very good reason:
It is well-known that dogfooding leads to software that has rather few bugs, but also dogfooded software often shows a tendency to be "biased towards programmers and power users". So, there often exist very good reasons if the programmers actively don't dogfood their software, and rather trust someone else (who is very trusted by the programmers) that the workflow that the programmer should implement does make sense for the user, even though most programmers would implement this very differently.
So did we, although we were in the end able to persuade them to let us board the flight by showing a screenshot of my friend's eVisa status from the UK government website (so secure!)
To be fair to the airlines here, if they get it wrong then the UK government fines the airline. This is why they are pretty risk averse, and also why I'm surprised that the screenshot worked.
I bet you 100% it was built not by in house team but farmed out to an agency for £££££ millions. They will have been saying in their case studies some absolute nonsense about how they saved the government millions rather than burned loads of money too.
How did they roll it out embassy without having at least some old systemd or a human in the loop backup working?
> ... without having at least some old systemd ...
Back in my day, visas were handled by init scripts. And we like it that way!
But with systemd you can start deportation procedures while waiting for the rest to resolve.
It'd be lovely if articles like this named the people responsible for actually building the systems. It's almost certainly never a government department.
They'll have paid one the many software/technology companies to build this thing. Who will be hiding their shoddy crap behind their client (the government department that paid for it). There are some patterns that I'm sure would start to arise from naming the consultancies that are churning out crap.
One of the reasons I’m applying for a British passport. Existing purely in some mystery database like that seems risky long term
She could have used a boat. Comes with a free hotel stay and no documents needed.
Jokes aside, when helping someone I know return to the UK, I wasn't sure if I have a stroke or someone who wrote the guidance had a lobotomy.
Clear as mud.
I have identical twin boys - when signing up for a bank account app and while completing all the associated hoops for ID, the second to do it got the rather dystopian error message 'an account has already been registered with this face'
I wonder how it's possible they didn't think about this problem. Considering everyone involved in building this feature, not a single person thought about the possibility of twins or simply people who are very alike? Also, can't people open multiple accounts?
I imagine that it probably went like this "what about identical twins?" / "Don't worry about that for now, we'll solve for it before we go live, but it's not in this milestone". Then someone pulls rank and decides the product is "good enough, we can't wait for all bugs to be fixed" and gets it deployed.
Issues get closed to make the metrics look good, not because they’re actually fixed.
Just look at the "falsehoods programmers believe about ..." articles that pop up from time to time. There are plenty of complexities in the real world that people either don't know about, aren't front of mind when they are tackling a larger problem, or simply don't want to deal with in the here and now. Lost knowledge and new problems are part of the reason why programmers are discouraged from rewriting software from scratch and why businesses in general are hesitant to replace legacy systems that still work.
Based on my experience I assume someone mentioned the risk, others said it’s unlikely and only a small percentage, that we should care about the 99% for now. Then the issues isn’t revisited until someone impacted complains enough.
p99 is ok for web stuff, not for systems that impacts people in their life, but I’ve seen too often things being dismissed because they are edge cases (which becomes an actual real issue at the scale of a country of course)
Which is pretty absurd because twins aren’t even that uncommon. I would bet most people on the planet know or are related to twins.
Because it probably does the dystopian tracking well enough, they don't care if it's not 100% accurate. Edge cases in the new world have no recourse, citizen.
It's one of those items way down on the list of "Falsehoods programmers believe...", way below everything on the names list (https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...).
The article doesn't give much more information than the title. Almost zero details.
I suspect this case has origins less to do with the programming itself, and more to do with UK bureaucracy just not giving a shit, as with the post office scandal where authorities, including the legal system, blindly believing in the outsourced systems led to hundreds of false prosecutions and thirteen suicides (https://en.wikipedia.org/wiki/British_Post_Office_scandal).
The Home Office does manage to be both cruel and incompetent, which is the worst possible combination.
It's the second worst.
oups.
The story is about the British system not the EU one
The system has to be bad. By design. This is so the policy in the civil service of open borders and international welfare can be implemented properly.
https://spectator.com/article/the-british-dream-by-david-goo...
It's more to do with Civil Service's hatred of working class.