Because the arguments are valid - but policy/business/operation related, not code related - and I have made a choice to NOT let that kind of discussion be a part of this community. If he can't live with that - what am I to do?
+Lars Is that right? We are only meant to discuss code here?
But in any case, much of what JM has posted seems to be related to code. What's more, software development is a process. In order to develop good code, you need good process. Good communications. Good quality procedures. Much of what goes in to making good code is policy/management/corporate.
The intent of this community is to focus on code. Discussing process and method in general is fine.
Discussing specifically EMBTs policy/management/corporate culture, the lack of, disagreement with, or failures of - on the other hand - should be done elsewhere.
There even is a specific community for it - clearly marked as such.
Because the arguments are valid - but policy/business/operation related, not code related - and I have made a choice to NOT let that kind of discussion be a part of this community. If he can't live with that - what am I to do?
ReplyDelete+Lars Is that right? We are only meant to discuss code here?
ReplyDeleteBut in any case, much of what JM has posted seems to be related to code. What's more, software development is a process. In order to develop good code, you need good process. Good communications. Good quality procedures. Much of what goes in to making good code is policy/management/corporate.
The intent of this community is to focus on code. Discussing process and method in general is fine.
ReplyDeleteDiscussing specifically EMBTs policy/management/corporate culture, the lack of, disagreement with, or failures of - on the other hand - should be done elsewhere.
There even is a specific community for it - clearly marked as such.
The guidelines are here:
https://plus.google.com/u/0/+LarsFosdal/posts/5XuLKHMWzec