345 karma · joined November 28, 2021
Unfortunately not for other fields like email, notes etc…
IMHO the perfect password app could just keep all previous versions of any field until the user deletes the history.
Haven’t we been burnt by being not cautious enough when COVID hit? Initially most scientists said “we don’t know if it’s airborne” or they said “there are no signs that it’s airborne” and the media turned it into “nothing flying fear” - and a few weeks later it was suddenly airborne.
“We don’t know” is a normal state in science and policies and personal behavior can take unknowns into consideration.
Direct messages are a UX and privacy nightmare IMHO.
They got sued, lost, and now they have to display it more transparently. Absent of EU specifics about how such prices have to be displayed, national courts can make their own rulings based on their national law.
I got deeply depressed and just wanted to die. The pain was just too much - even with controlled pain medication in a hospital setup.
I called the German crisis hotline almost every night and they were usually very very helpful. They listened - sometimes for 1-2 hours. In 90% of my calls I felt way better after calling them. They really are well trained and some of the personalities I talked to were pretty impressive and interesting… They have seen a lot…
I mean the union is correct in this case. Robots will replace jobs. A union’s job is to make sure there are jobs for people in the company they are already in.
Usually unions would speak the truth (“robots = jobs go away”) but pair this with some suggestions: eg trying to upskill the affected worker so that they can be moved to a different department).
While I was working in Germany I always felt better at a company with a strong union.
Also Swift has a lot of other areas where it just lacks any safeguards… Memory issues are still a thing. It’s using ARC under the hood after all.
Infinite recursion is still a thing (not sure if this would even detectable - probably not).
Misuse of APIs.
And it introduces new issues: which methods are being called depends on your imports.
In my experience Swift lulls you into a false sense of safety while adding more potential safety issues and “only” solving some of the less important ones. objc has null ability as well. Which can warn u if used appropriately. objc also has lightweight generics. In practice this is all you need.
if error == NULL and operationFailed then log error Otherwise Let client side do the error handling (in terms of logging)