In theory, yes, but that's not how policing works.
From personal knowledge of the UK setup, the goals are twofold, mass surveillance plus auto-revenue-generation (intended to raise sufficient to pay for the surveillance infrastructure to minimize the net cost which means auto issuing the absolute maximum number of tickets possible).
Doing validation to ensure correctness of the tickets being issued would be counter-productive to the revenue generation goal; just because police have evidence a crime (like cloning) has happened, does not mean they will not issue the ticket. There is an onus in the UK for the registered keeper of the vehicle to incriminate themselves or someone else for road traffic offences (confirmed by test cases).
Essentially you have to pay up or prove the cloning (and your innocence) yourself - very difficult because you do not have access to the surveillance database that would help you. The core objective of the police is to assert your guilt, not to provide you with any help for your defence.
Is this company asking you to do things for them by any chance? The only time I've seen anything like this was when they were leeching free consultancy for a problem they were unable to solve. They compartmentalized the problem into different sub-components and under the guise of advancement in the process, held an 'interview' on them separately and a follow-up for the feedback (i.e. find out the answers). Once they had all the parts they needed, they said the person had not got the job.
Find different opportunities - this one sounds no good. If they treat you like this in the play nice phase, they will treat you much, much worse if they ever employ you.
I worked on air quality monitoring about 30 years ago and the equipment used a Kalman filter to remove measurement noise and give stability; it had been added to the software a number of years earlier by a mathematics student who was working as a summer job with the company. No-one in the team had heard of it before but it solved lots of the stability issues and was core to the system ever after.
> It is hard for me to articulate how much peps like this reinforce my desire to never start another python project
I completely understand this sentiment. Recent python events have made me wonder if there are some people intent on sabotaging the management of the language.
I loved the incremental improvements and thoughtful process involved up until a couple of years ago but it feels like python will become brittle and break badly if things continue the way they are. It feels like the adults have been driven out the room when it comes to stewardship. I'm not sure how recoverable the situation is.
My experience is that invariably results in "development by veto". Each prototype they say that's not what I want, give me something else (that I'll fail to describe just like the last time) and I'll tell you that is wrong too after you've worked on it for a few weeks.
Occasionally, you'll randomly get something they accept - but only for a few weeks until they come across some missing capability for some other thing they never told you about.
Just 1 or 2 transistors you say? Link to a circuit diagram (or even an ASCII art reply) greatly appreciated - sounds like a fun way to spend an afternoon or an evening.
Really reads like US employment practice meets EU (IE) employment law. In this particular case, the EU employee won despite the huge power asymmetry that normally ensure things go the opposite way.
But I note other comments on collect-ability of the judgement - ignoring it completely is the other US approach and make collection impossible through all sorts of devious delay tactics or even frivolous counter-suits in far off jurisdictions.
I'd like to know how this actually works out and whether collection of any actual money ever takes place.
But Wikipedia has a long article on Hepatotoxicity[0] and that suggests discontinuation of the drugs involved can allow the liver to heal (if discontinued early enough).
As a patient, you need to be conscious to ask questions and retain at least some control over your treatment whenever you can. If you're overwhelmed by what you are being told or concerned about the planned course of treatment, always ask questions, especially about long term implications and risks and how those are addressed. Generally doctors like being asked about medical things and are willing to answer when they are able. [Individual experiences may vary etc.]
The Latin morbus is disease and mortis is [of] death but my experience - and perhaps yours too - is that when discussions of morbidity (i.e. using the word morbid/morbidity) arise, they are often in the context where someone is near death or has died so it is a natural linguistic connection to make.
Remarkably often I find my partner has a different understanding of English words from me - she was schooled in French and can communicate in Italian and Spanish, but is also fluent in English (though spoken with French mannerisms which seem odd to me as a native English speaker). We often find we descend into discussions of the most correct meaning of a word in English which has a Latin root. The dictionary agrees with her mostly but I have an occasional win.
Varies, generally difficult for me in SW Ontario though with some occasional impressive 25MHz propagation with RS59 subject to heavy QSB. But I cannot rely on it for setting a clock...
For humans, not yet progressed to trials though safety has been evaluated for other diseases, so possible for trials to happen quickly?
" the compound has strong potential to quickly transition into human clinics because it has already undergone safety evaluations for other diseases."