@@seanallen it’s my pleasure 🙌😎!but definitely that’s what I first do, like 👍 the video to make sure I contribute 😄. You’re an inspiration because i remember when you first started this journey and all the struggles you’ve mentioned in your videos at the beginning . I’ve been following you for awhile and look now how you became an iOS developer master and how you play with the iOS ecosystem. This means, hard work and persistence pay off. You have been one of the honest RU-vidr and this channel you should have more subscribers. Keep up the good work 😎🙌
Last week I was trying to learn about KeyPaths but the learning materials I was using wasn't quite landing for me, and then this beauty of a video comes out, and it makes sense now. I rarely comment on videos but just wanted to express my gratitude, your teaching style works so well for me. I'm new to the world of Swift, having just started a year ago. An area I'm struggling with is bugs. It can be so difficult to go into a codebase of experienced programmers and identify where they've gone wrong, as a newbie. This brings me to a suggestion I have for a series you could think about: Footage of you fixing bugs, from assignment to resolution. It would be great to see the full end-to-end process of how you approach it, what research you do, how you use debugging tools, and see a plethora of solutions. It would work best if these were real bugs that you haven't looked into prior to recording. Also, content on Combine would be interesting too!
I appreciate the kind words. I've thought about how to do videos like that in the past, but every code base is so different (some easier to navigate than others). I understand it's still valuable to see the process, but I don't have access to an app where I would be unfamiliar to the codebase to play out the scenario.
Ah, that makes sense. Definitely a shame. Would going into open source projects be a possible solution? Or even engaging with your community to solicit opportunities from people who have encountered bugs they'd like you to fix? Either way, appreciate the response and your videos, please do keep it up!
I'd go more for an implementation through an extension or in some other place to "clean" it. Using keypaths is not as efficient as the closure method too. Not too slow that it'll make a difference for most apps, but worth a consideration. I personally still prefer the closure option for being consistent across the app
I don’t know where else to ask you experts questions like this, so I want to ask a general swift data question. I’m really confused on this because it seems like Paul Hudson and Stuart Lynch are saying different things. General question with SwiftData: Is this set up correct? ----------------------------------------------------------- Game needs ONE location Locations can be assigned to many different games. @Model final class location { var id: UUID var text: String } @Model final class game { @Attribute(.unique) var id: UUID … var location: location? }
I’ll never write code the same again! 🎃 This was good. By the way, this symbol is called a backslash “\” This is called forward slash (or slash, for short) “/“
Thanks Sean! Would it be correct to say that a key path is like a closure since a closure is a reference to a function (not the result of calling the function) and a key path is a reference to a property (not the value of the property)?
