= 27d567bc2d48d9f40e9ccc20ea370b15)
OrphanWilde comments on Open Thread, January 1-15, 2013 - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (333)
I take non-programmers seriously about programming all of the time. That's pretty much in the job description.
Just because I'm not stupid doesn't mean I'm not wrong. Indeed, it takes some serious intelligence to be wrong in the worst kind of ways.
About implementation, or about what to implement?
In practice the two are, in my line of work, very difficult to separate. The what is almost always the how. But both, out of practical necessity. When the client insists on a particular implementation, that's the implementation you go with.
I would assume that's high-level -- "use Oracle, not MySQL"
That's part of it, but no, that's not what I'm referring to. Client necessities are client necessities.
"Encryption and file delivery need to be in separate process flows" would be closer. (This sounds high-level, but in the scripting language I do most of my work in, both of these are atomic operations.)