465 karma · joined March 26, 2012
Also, it's perfectly fine if other people post that content it's just not okay if you are the one who wrote it and posted it so it doesn't stop the content from being posted just WHO can post it.
On top of that, if you are banned from a subreddit (even a default one) the moderators can basically choose to ignore you and you are SOL. There's the whole 90/10 rule where if you are posting something from the same source too often, you can be seen as a spammer and banned. It's very easy to break this rule. For example, if you make a few self posts, make tons of comments, post links to 5 different websites, then post 1 link to your website, you are breaking the rule and if a mod sees it you can be banned (comments/self posts don't count towards the 90/10 rule so your 5 posts to 1 self promotion post is breaking the rules). I wish they would just let the upvote/downvote system do its job and weed out content people don't want instead of forcing people to post a bunch of crap they wouldn't normally post just to make their profile look good so they can post about their own projects once in a while.
I think there might be subtle differences is how we are mocking objects and how we organize our code that might make mocking have different outcomes. That's why I would like to see actual examples that can be deeply analyzed. I suspect that it's in fact the way the code is written and what the underlying platform allows that makes one more suitable than the other rather than mocks being fundamentally a poor choice.
The higher you get the more time it takes for tests to run, the more difficult it is to identify where a failure is, the more brittle those tests will be because of inter-dependencies, and the more complex it is to write the test. The difficult part is understanding your system well enough to know where your unit tests aren't sufficient.