4 ms·
No, I got that you were talking (at least in part) about the business domain. I have had the privilege of mostly working on smaller projects (two to 20 program
by AnimalMuppet 7y ago
No, I got that you were talking (at least in part) about the business domain. I have had the privilege of mostly working on smaller projects (two to 20 programmers), where the connection to what the business is trying to do was pretty clear. Maybe I've also had the privilege of mostly working with grownups. Or, possibly, maybe you're too cynical. (Your experience has driven you to that cynicism; mine hasn't. I have no data on which of our experiences best reflects the wider world of programming.) But I agree that, if you don't know what the user needs, you probably can't code it.
But I think you're overselling Lisp in this context. The kind of programmer you're talking about, given Lisp, won't develop a "business language" that matches the user needs. They will at best just develop a language that matches the product manager's feature request description, and at worst they'll just start hacking away in Lisp without developing any vocabulary at all.
And I think you're misreading where I'm coming from. I can see a lot more than just the code. I totally get that delivering what the user needs is what counts. Just one example: In a hallway conversation, I said we should do X instead of Y because it would be better for the users. The better part of a decade later, I got reminded of that hallway conversation, because it turned out that a litigation-happy competitor had patented Y, and in a court case wanted to apply that patent against us, but couldn't because we didn't actually do Y. I said that the attorneys should say that, if our competitor had patented delivering a worse user experience, they were welcome to the patent on it.