For something in the financial space, I don't see much (or really, any) tests in the code repository. CI also only has ESlint and prettier running.
How are you ensuring the application will remain maintainable in the future, you are not breaking existing stuff and integration with the actual platform is always up-to-date?
In short, what's the testing strategy for something that claims to deal with $6M a month?
If there is none, you likely want to read up a bit on things like Testing Pyramid, automated test strategies (unit-, integration- and end-to-end testing).
Hardware can do any "magic" software can, which should be obvious since software runs on it. It's just not as cost-effective to modify it after shipping, which is why the tech sector is moving to more sw less hw (simplified, ofc, there are other reasons).
All the American cars (Ford, Chevrolet, GM...) are much cheaper in Europe than eg. German cars from their trifecta (and other Europe-made high end vehicles from eg Sweden, Italy or UK), and on par with mid-priced vehicles from the likes of Hyundai, Kia, Mazda...
Obviously, some US brands do not compete on price, but other than maybe Jeep and Tesla, those have a small market penetration.
Gives them proof they did their best to "protect minors" even if they circumvented the GeoIP rule: someone trying and realising it still does not work might get X percentage to not bother further thinking there was something smarter at play and not just GeoIP (which there is).
When that happens, most VPN providers will face similar destiny.
Which means that we'll all have to run our own VPNs, possibly masquerading as HTTPS traffic, if that remains viable against government interference (eg. they might ask to re-encrypt all traffic by ISP-level certs, and block any traffic unreadable by them).
Is there a mesh wifi system that can run open source firmware? I imagine that might be the best bet for VLAN tagging too in the "affordable" sense too.
Not that I'm aware of, and I suspect that the whole idea of mesh radio is necessarily so closely tied to the specific hardware that for this to be practical, there's have to be some canonical physical implementation available for developers to program to.
For what it's worth, what I settled on is EnGenius's FitXpress products. But I'm not necessarily recommending that, I'm a bit ambivalent to it. Within its normal operational envelope it works well, but its range is far lesser than the TP-Link device I replaced, and rebooting one of the WAPs in the mesh takes seemingly forever (like, 10 minutes!).
In that particular example (drunk neighbour damaging your property with reckless driving) is really — in most of Europe, I would guess as Serbian laws are largely copied over from different EU country laws — handled by the insurance.
Basically, insurance against damage to others is obligatory for anyone to get the car registered and on the road.
If someone drives an unregistered, uninsured vehicle, a consortium of all insurance companies pay for the damage, and sue the perpetrator in a civil case.
In general, you can argue your level of damage with the insurance company, and can even take them to court.
In Serbia, drunk driving actually precludes the liability of the insurance company too, but they still need to pay out the damages first, and bring a civil case against the driver to get compensated. For that, they need a criminal conviction.
(I've had the unfortune to be hit by a drunk driver, luckily no other harm than to the property as both cars have been totalled, and his insurance argued a lower value for my almost new car)
I am guessing here the "intent" can also be "aware of it but did not invest enough to curb it while it is profiting off it".
Yeah, I know how car insurance works and just figured it’d be overly verbose to specify some scenario where the neighbour was driving some uninsured vehicle like a tractor and the incident happened outside of public roads.
I do think I still managed to make my point though, preventing civil lawsuits arising from possibly criminal behaviour is unrealistic. That would make it extremely difficult for individuals to seek compensation for almost any damage they might suffer, they’d have to first wait for months or years before the police gets back to them.
>I am guessing here the "intent" can also be "aware of it but did not invest enough to curb it while it is profiting off it".
Fraud by negligence is a fairly exotic concept and to my understanding usually specifically relies on laws regarding negligent misrepresentation. I’d be surprised if that would work in Sweden.
>For liability for fraud to come into question, the prosecutor has to be
able to prove that the crime is deliberate. This means that the criminal
act has been committed consciously or intentionally. Liability for fraud
is conditional on the objective requisites being covered by the perpetrator’s intent. It is not possible to judge a person to be liable for fraud because someone has been paid too much compensation as a result of negligence, or because the person did not know about certain obligations in
conjunction with the compensation. Carelessness is thus not sufficient.
It must be possible to prove that the perpetrator has committed the act
intentionally. This intent must cover all elements of the criminal act.
The great problem with fraud crime is to prove the intent. The actual
circumstances surrounding what really occurred are often a lesser pro-
blem. The assessment of the intent is complicated by the fact that the
rules concerning social insurance can be difficult to understand.
The difficulty in proving intent has meant that several assessors have
considered that the fraud regulations do not work quite as they should.
Proposals have therefore been made that negligence should be sufficient
for judging that a person has misled the Social Insurance Agency or
some other payment-issuer within the compensation and benefit systems
(Örnemark Hansen, 1995). This criticism against the intention require-
ment has led to the new Benefit Crime Act (2007:612).
Generally legal system has negligence, and once someone is provably informed of the negative consequences but keeps being negligent, "willful negligence", which is much closer to intent (I see it defined as "intentional disregard...").
IANAL, but common sense tells me there should be a link to willful harm.
How are you ensuring the application will remain maintainable in the future, you are not breaking existing stuff and integration with the actual platform is always up-to-date?
In short, what's the testing strategy for something that claims to deal with $6M a month?
If there is none, you likely want to read up a bit on things like Testing Pyramid, automated test strategies (unit-, integration- and end-to-end testing).
reply