If there’s one thing you need to know about language, it’s this: language is complicated. And that’s the number one reason why Swift’s strings are also complicated: they are designed to do the right thing by default, so you get support for all known languages, plus fantasy languages like Klingon and Elvish, and even emoji – all without having to do anything special.
Although this might seem like a pointless technicality, you’d do well to remember this quote from Frank Chimero: “people ignore design that ignores people.” Our job isn’t just to write great code and hope for the best, but instead to put our users needs front and centre all the time – to make sure we meet their needs and solve their problems.
If your software falls on the first hurdle – if it’s unable to handle their language – then you might as well not bother.
Today you should work through the wrap up chapter for project 24, complete its review, then work through all three of its challenges.
That’s another project finished, and one that has given you a glimpse inside Swift’s inner working – make sure you share the extensions you write with others!
Need help? Tweet me @twostraws!
SPONSORED Catch bugs as soon as they happen and know exactly why a crash occurred. Instabug's SDK grabs all the logs they need to fix bugs, crashes and performance issues in minutes instead of days. Get screenshots, device details, network logs, repro steps, and tons of other critical insights needed to resolve issues and prioritize product backlogs straight from your dashboard. It only takes a minute to integrate!
Link copied to your pasteboard.