I've been puzzled several days over this reaction, so I decided that I must give it some time and try to understand where the ad hominems came from, and in which way developers were hurt from my post.
But now that you have decided that my post actually was an ad hominem (not pointing out where that crime was committed) - and told everyone else too - it might not change your attitude. But the fact of the matter is that after several years designing (and also programming) complex systems I learned something about developers and their perspective on User Interfaces, which I essentially tried to summarize in my post (but that was not an attack, it was a description of a "perspective problem" for ALL developers, including myself when in that role).
And below I'm going to state the same thing again, but now trying to explain in more elaborate terms also to you Luc what I was actually saying (but be aware, I have no other way of stating the well known fact) :
Developers generally don't think the SAME WAY as users. Just like an arrow can point forward it can also point backwards. Developers are not stupid people. They make great sofware (including some crap, but that's not what we're talking about here). Developers think from the "inside-out-perspective" (because they know how the software functions under the hood, on the "Inside") while users think the exact opposite way, from the "outside -> in" (what the user wants to do, not how the software were programmed). Compared to users the developers thus often thinks "backwards" (the inside out, instead of outside in). Again, the user's starting point is an idea of what he wants to do and not how the software functions (which in most cases is irrelevant).
Hence the term "backwards", which may not have the same meaning in English as in Swedish (which is my native language), but I explained in context in which meaning I used the term. And it was NOT in any derogatory sense. Developers are smart people.
WHY SURPRISED THEN?
Moreover, I thought everyone in the IT industry knew about this problem (developers not having the user's perspective). I took this knowledge for granted. And given that I thought everyone knew this problem as a fact (well, I still do, but now with a few exceptions), from that perspective I was surprised, and it also seems only strange to me that every time I have (in this forum) pointed out some very odd ways of how the Bongo UI was designed, then you have chimed in and tried to explain HOW THE SOFTWARE WORKS.
One word - Irrelevant. I have tried to explain to you, at least two times, why some of your comments from that perspective has been entirely irrelevant (see again the "developers perspective", which truly IS irrelevant)
Exactly that part about how the software functions is the irrelevant part when users, sometimes other users than me as well, say the exact same thing - that some part of the UI is counter intuitive. And not only "counter intuitive, but even "backwards" in the meaning I explained above - someone knowing the software very well from the inside was thinking in the exact opposite way ("backwards") compared to regular users, and so he/she designs the UI...well, he/she assumes a workflow flowing backwards is the most natural way to approach it.
But it isn't.
DIDN'T EVERYONE KNOW THIS?
At least all professional developers I know in Scandinavia as well as other professionals I know from all over the world, understands this "developer perspective problem" and considers it a given, and so they consult UI experts to avoid this well known trap.
UI - User Inversed?
No, UI's are not IK-chains. UI typically involves Forward thinking, not Inverse thinking. Forward, not backward.
So when I tried to explain that developers think about UI's from a different perspective than users generally do, that is just a well known fact out there, it's certainly not an "ad hominem"!
DEVELOPERS ARE (PROBABLY) NOT THE PROBLEM
Having said all this, it's easy (well, easier) to deal with the actual UI-problem - just let someone else take care of the final decisions regarding UI design (that's also how I dealt with the problem myself as a chief architect for a big logistics system- I let others do what I would not be very good at after designing all the back end stuff).
I find it hard to believe that developers living near Redmond/Seattle wouldn't know about this "UI-backwards-perspective" problem, which to me means that the information from users regarding problems with the UI gets filtered and stuck before it even reaches the developers.
But selfish as I am I want McNeel to listen to people who actually understands UI:s (there are even exceptions among developers being aware of the dev-perspective trap, and so they can "switch hat" to the user's perspective and still make good UI:s), which eventuallly will lead to a better product for me (and better sales for McNeel, but never mind)