Tip#47: Stop doing “I don’t know about it but I know” If you look closely you'll see some code where you don’t mention a dependency (AWS, GrphQL) yet implementation clearly relies on it. Stop fooling yourself! If you don’t know the dep. you're not supposed to know how it works!

Tip#7: Don’t allow optionals to rule the world Optionals have their usage but NOT EVERYTHING is optional 👉 Enum with associated values can be very handy 👉 Enum reduces impossible behaviours (A & B can’t be nil at the same time) 👉 Don’t use optionals by default (hello GraphQL)

Tip #33: Use reactive programming wisely React prog. is cool but like usual: find a good balance. With great power comes great responsability. 👉 Your Rx code MUST be readable 👉 Don’t use Rx in plain models 👉 Prefer async/await 👉 Your value is NOT async? Then don’t make it so!

Tip #44: It’s OK to fail You can’t succeed everything nor in in the first try. Most important is to LEARN. 👉 Ask yourself WHAT failed 👉 Ask yourself WHY it failed 👉 Ask yourself WHAT you learned 👉 Ask yourself WHAT you’d do to make it succeed next time

Tip #12: Don’t give the wrong naming to the wrong class. People tend confuse naming with role. It’s not because you're naming something “potato” that it magically make it one! 👉 THINK about what your objet DO before naming it

Tip #29: Look to other platforms Sometimes we think we know more than others or that our community is the best. Maybe it’s true 😆. But you still have nice things to learn from others 😉 👉 Look to other languages 👉 Look to other frameworks

Ever tried to run `swift package run` from Xcode build phase? Here's how to do it👇 swiftunwrap.com/article/runnin…

Tip#16: Keep your processes simple Don’t complexify your validation processes. The more you add the less efficient you are. It’s bureaucracy. 👉 Use Trunk Based Development 👉 Communication over documentation

Interesting article swiftwithvincent.com/blog/bad-pract… But one thing as I already said: don't put side effect inside your init! That's by far the BEST way of avoiding issues.

Java interoperability... in Swift. By the Swift team 👀 forums.swift.org/t/jextract-swi…

Even though you probably want your object to be initialized only once, this is yet another case/reason why having side effect in init is not a good idea forums.swift.org/t/observable-i…

(Backend) developers still find ways to surprise me. Latest idea: sending ids that can't be used as such. Because they are in the form of "Object:ID". So frontend need to parse them to get the ACTUAL id and send it to backend (whenever needed). 🙃

Seriously there are some things that are broken like hell in SwiftUI. Just stumbled on this bug: stackoverflow.com/questions/7073… Worst thing: if set a custom TextField style, it gets called 3 times. 🤦‍♂️

I would avoid using Xcode 16.2 for now: - It increased our app size by 35Mo - Previews are not working with iOS18 🤡

Over the years SwiftUI has improved. But I'm also seeing countless bugs in each version. Some very important like this one (I face it too). forums.developer.apple.com/forums/thread/… But after many months... still not fixed :(

I'm more and more frustrated of using #SwiftUI. It has countless bugs, even on simple things. Is it worth filling a bug ticket? Feels like Apple won't never fix them :(

Just stumbled on this exact "bug". forums.swift.org/t/nsstring-con… I'm started to wondering if I should laugh or cry 😅😂

Just discovered that using containerRelativeFrame inside a HStack inside a ScrollView retriggers everytime you scroll. Moving to LazyHStack would fix the issue but I can't for various reasons. So in short: don't use ScrollView + HStack + containerRelativeFrame 😅

Finally had time to check what was going on with my project when compiling with Xcode 16.2/16.3 Assets.car gets way bigger (57-> 161mb). Some assets go from 2mb to 20mb. Opened a ticket to apple. Hopefully it will get fixed.

I always thought that setting iOS environment was "complex": installing Xcode, Xcode dev tools, simulator, probably ruby + fastlane, etc... And then... I tried to make some backend development for my company. iOS environment setup is so easy 😂