Phillip Caudell @phill@mastodon.notsobig.co

@Qiu like an unstoppable glacier…it’s coming :-)

Finally got around to watching The Curse finale…

🥇 NEW FEAR UNLOCKED

@sandropennisi If you expect nothing from somebody you are never disappointed 😜

@sandropennisi annoyingly unless you have a rapport, ghosting is pretty common. It’s difficult not to take it personally when it's something you've made, and by definition, a product of you.

I find reframing helpful: This person was interested enough to respond to my first message. There's something here. Perhaps they don't think it's a fit right now, and don't want to hurt my feelings.

Send them a casual update when you have something new to try; don't ask for anything. You never know :-)

@mattiem Don't worry, it's not just you. https://en.wikipedia.org/wiki/Dunning–Kruger_effect

@bardi 😂

What have I missed? Did they ever launch that headset?

The reports of my death are greatly exaggerated.

@bardi @Mecid when sizes classes aren't enough, I've found it useful to expose a platform idiom in the environment. This obviously isn't a substitute for platform directives if the API is unavailable, but it's useful to make small UI tweaks.

https://gist.github.com/phillipcaudell/60d5e8c8fe1848b47576356a49719e46

@gernot @keval the AppStorage interface will always return its default value, however if you access the value through the store (e.g UserDefaults.standard.double(forKey:)) you will get the store's default instead.

Yet another reason for having a common interface everywhere!
https://developer.apple.com/documentation/foundation/userdefaults/1416581-double

My job?

I restart Xcode and Clean Builder Folder for a living.

@keval @gernot beware that even if with an optional value the store will always return a default value. Double will return 0 if there is no entry, Bool will return false, etc. This can have subtle and unexpected consequences if you’re expecting nil.

By clearly defining your default values you’re making your codebase easier to reason with, test, etc.

@gernot very cool and similar! Great minds :-)

And yes it’s curious AppStorage works the way it does when the EnvironmentValues system is sat right there.

#SwiftUI: Stop using AppStorage directly. It’s prone to typos, value mismatches and more.

Instead give yourself strongly typed keys and associated defaults, à la EnvironmentValues.

I’ve published my implementation as a package, but you can just as easily wrap AppStorage yourself with a few dozen lines.

https://github.com/notsobigcompany/BigUIUserPreferences

@harry_wood @rwitherspoon definitely having some sort of routine to check your accounts is a good idea.

In my particular instance I checked fairly regularly, but rather sinisterly banking alerts weren’t being sent to me (despite receiving marketing alerts, which is what prompted me to check that day). Assume alerts won’t help you either.

@rwitherspoon frustratingly they won’t tell me the full details, so it’s hard to say what I or anyone could do differently.

But these things ultimately worked in my favour:

- getting a crime number asap
- noting everything the bank says down
- assuming bank is out to screw me

The whole thing made me paranoid; how could I have been compromised in such a catastrophic way?

Turns out (perhaps unsurprisingly) the weakest link in the chain was human. A fake ID was used inside a branch to gain access to my accounts. Additional checks that were supposed to be carried out, weren’t.

The bank issued the fraudsters with a new card and PIN number. And that was it. They had everything they needed.

This time last year I had a life-changing amount of money stolen.

There was no obvious scam. I hadn’t sent any payments. It was just gone.

The police weren’t helpful and the bank did nothing but gaslight me the entire time.

Today the Financial Ombudsman found the bank at fault and have ordered everything to be paid back + compensation.

I cannot begin to express the relief I’m feeling after such an awful year.

Lots of happy crying this morning 🥲