The First Rule of Dev Club...
October 26th, 2020
55 mins 48 secs
About this Episode
Welcome to Code Completion! We are a group of iOS developers and educators hoping to share what we love most about development, Apple technology, and completing your code! This time, we are joined by special guest, James McDougall! Be sure to follow them at https://twitter.com/JamesWMcDougall.
Follow us @CodeCompletion on Twitter to hear about our upcoming livestreams, videos, and other content.
Today, we discuss:
- James's path from audio engineer to app developer
- How to get an interview when you don't have experience
- Fudging your resumes, but not lying to the hiring manager
Also, join us for #CompleteTheCode and Compiler Error, two segments that test both your knowledge and our knowledge on Swift, Apple, and all things development!
Your hosts for this week:
Be sure to also sign up to our monthly newsletter, where we will recap the topics we discussed, reveal the answers to #CompleteTheCode, and share even more things we learned in between episodes.
You are what makes this show possible, so please be sure to share this with your friends and family who are also interested in any part of the app development process.
This week's episode of Code Completion is brought to you by Not Phở. Search for Not Phở on the iOS and macOS App Stores today to give it a try. https://apps.apple.com/app/apple-store/id1525104124?pt=14724&ct=CodeCompletion1&mt=8
Complete the Code
Be sure to tweet us with hashtag #CompleteTheCode if you know the answer!
- The UTF-32 view provides access to each character as a 4-byte UInt32, representing the complete range of all 4 billion unicode code points, but in their original, possibly decomposed, forms.
- The UTF-8 view optimizes for memory at a disadvantage to manipulation speed, since each unicode character may be represented by one or more bytes, making length calculations costly, but necessary for many C APIs.
- Easily accessibly by treating a string like a collection, the default view represents normalized characters as they would be displayed on screen, even if they were originally decomposed.
- The UTF-16 view is optimal when interacting with unicode libraries such as Objective-C’s NSString since it vends UInt16 code-points, as is standard in many programing models.