> One thing I think we could have done better with Code Words is added short bios
I'm rather glad you didn't.
Sean felt justified not reading it because he believed the writer was "a novice", and I think he have acted differently if he knew this was an experienced and successful commercial programmer.
But because he didn't, the rest of us can learn something really interesting: That twenty years of research-experience cannot immediately recognise itself blub to twenty years of commercial-experience.
Maybe those guys writing software that does things have figured something out as well?
I totally read the article; I'm very surprised it was written by a professional but it wouldn't have changed my judgement of it. I thought it was poorly written and meandering, but I probably should have kept that to myself. I guess we all have different standards.
> Maybe those guys writing software that does things have figured something out as well?
At this point, I really think the article should speak for itself. If you think it says something important or even coherent, then you know, it was for you, not for me.
I don't think you should keep your opinions to yourself. However, when you present your opinions with sarcasm and ad hominem attacks, you are bringing down the conversation to a level that is not conducive to any meaningful discussions. I don't think that was your intention, but I do think it was the result.
I'm rather glad you didn't.
Sean felt justified not reading it because he believed the writer was "a novice", and I think he have acted differently if he knew this was an experienced and successful commercial programmer.
But because he didn't, the rest of us can learn something really interesting: That twenty years of research-experience cannot immediately recognise itself blub to twenty years of commercial-experience.
Maybe those guys writing software that does things have figured something out as well?