4.4 • 2.4K Ratings
🗓️ 22 November 2022
⏱️ 129 minutes
🧾️ Download transcript
#askatp
:
Sponsored by:
Become a member for ad-free episodes and our early-release, unedited “bootleg” feed!
Click on a timestamp to play from that location
0:00.0 | So I have something to show the two of you. Oh, this is always ominous. Check our slack. |
0:05.9 | Oh, my God. I'm so happy. I'm so happy. So I'm looking at a screenshot, a very, very small, |
0:17.0 | very heavily cropped screenshot from Xcode. On the right-hand side, it's a bunch of green |
0:21.8 | diamonds that have check marks in them. And on the left, test value conversions, a function, test |
0:28.0 | open DB function, test queries, function, test heavy workload function, et cetera, et cetera. Oh my God, |
0:32.5 | I'm so proud of you. Now, I don't know anything really about writing tests in Xcode, but that makes two of us. |
0:39.3 | Are they supposed to all begin with the word test? |
0:41.7 | I think they have to. |
0:42.9 | I don't remember if it's required or not, but it is certainly the convention. |
0:45.8 | It certainly makes your life easier if they do, because you get like wonderful UI integration |
0:51.3 | where you can just click and run one of them and stuff like that. |
0:53.6 | You get the little green check marks. It's fun. Well, this is extremely exciting. So, |
0:56.9 | so this is the FC model replacement that does not have a name or does have a name? |
1:01.9 | Oh, it does. Okay. Are we sharing that name or no? |
1:04.2 | Yeah, not yet. It doesn't really matter. That's fine. It's but DB. I'm calling it but DB. Well, I feel like I don't like when components that I have to write just have really generic names like model or database. This is kind of the convention now with Swift or with Swift UI where you'll have some of it just called like view, list. And I find it it's very difficult to search for that both in your own code |
1:31.3 | and for like you know if you search for stack overflow answers on how to do something or something or |
1:34.6 | whatever I prefer having names that are not just generic words that actually mean something |
1:39.5 | whether it's whether they're prefixed like like FC model, or whether it's like, |
1:44.2 | some kind of other unique name. It's like something where like you can easily search for |
1:48.0 | it in your own code or on Google or whatever, and you can find answers. So that's, so I'm not |
1:53.1 | like, like there's a bunch of SQLite wrappers for Swift that are just called things like |
1:57.2 | SQLite. It's like, well, that's going to be hard to search for. |
... |
Please login to see the full transcript.
Disclaimer: The podcast and artwork embedded on this page are from Marco Arment, and are the property of its owner and not affiliated with or endorsed by Tapesearch.
Generated transcripts are the property of Marco Arment and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.
Copyright © Tapesearch 2025.