Lurie supports his two-language rule with arguments like these:
You don't gain much insight from fluency in only one programming language. "You can easily learn one language and have no grasp of programming," he notes. "Learn two, though, and you learn some of the stuff that all programming languages have in common. You have to focus on the method as much as the syntax."
You make smarter requests when you understand the challenges faced by developers. Until you've experienced the frustration of trying to implement what sounds like a minor change—but isn't—you won't grasp a developer's hostile reaction. "Programming is hard. I don't care what the elite say," Lurie insists. "You're probably asking them to do something ridiculous like change every third instance of 'car' to 'automobile.' If they're going to suffer ... they'd rather be building the next Twitter."
→ end article preview
Read the Full Article