Expanded Thoughts on Swift’s Type Inference

This article expands on a previous op-ed about clean coding in Swift, specifically regarding type inference. The author reflects on feedback from developer Rob Napier, who argues that type inference is acceptable when the result is unambiguous. The key insight is that well-designed types and descriptive function names (e.g., `birdDetailsFromStorage()` returning a `BirdDetails` struct) make inferred types obvious to both the compiler and human readers. The article stresses that code authors control clarity through intentional naming and predictable return types, turning type inference into a legitimate tool for simpler, clearer code. It concludes with a warning against misleading function names, which would require explicit type annotations as a 'punishment.'