However, there is some jargon that could and probably should be done away with: the computer science stuff.
On the one hand, I agree with you. If people can’t understand, then that’s bad. On the other hand, touches like those give the sequences personality, and that personality may be part of what makes them popular.
Usually, though, there’s a way to phrase IT descriptions such that everyone can understand. I do this for my boss all the time. Maybe giving it a high-tech “personality” and making it comprehensible are not mutually exclusive.
The IT culture stuff is good, what I think wouldn’t pass is specific IT vocabulary or concepts that don’t get introduced within the sequences and that is assumed to be understood.
I seem to recall a reference somewhere of object-level vs class-level distinctions, and someone who’s never heard about OOP would have no idea that we’re basically talking about the programming equivalent of specific emails vs email templates (or “an email”, or whatever helps make them understand, but I’ve found the specifc email vs template example sufficient as a first step for most people I’ve had to explain this to).
On the one hand, I agree with you. If people can’t understand, then that’s bad. On the other hand, touches like those give the sequences personality, and that personality may be part of what makes them popular.
Usually, though, there’s a way to phrase IT descriptions such that everyone can understand. I do this for my boss all the time. Maybe giving it a high-tech “personality” and making it comprehensible are not mutually exclusive.
Yes, I agree.
The IT culture stuff is good, what I think wouldn’t pass is specific IT vocabulary or concepts that don’t get introduced within the sequences and that is assumed to be understood.
I seem to recall a reference somewhere of object-level vs class-level distinctions, and someone who’s never heard about OOP would have no idea that we’re basically talking about the programming equivalent of specific emails vs email templates (or “an email”, or whatever helps make them understand, but I’ve found the specifc email vs template example sufficient as a first step for most people I’ve had to explain this to).