TianCaiBenBen
VIM or any other kind of editors are just tools.
Tool are designed for specific jobs; And people choose tool to complete their job with personal preference; This is just like some soldiers are good at using sword and some prefers to ax;
There is no good or bad tool; There is only proper tool for specific job; And there is only tool that user has preference;
I am OK that the author do not like VIM; It is author's choice and taste;
But the author give the user of VIM especially who want to learn VIM a WRONG impression that VIM is NOT GOOD and is HARD to learn and is HARD to customize which are totally the author's own opinion; Not the true fact about VIM;
Writing this comments, just want to remind those who do not know what VIM really is, Please try it yourself; Do not just listen to this author's personal blah blah.
Try VIM yourself.
And if the emotional issue involves, providing the domestic service will not guarantee that she will satisfy with what you did for her. She may complain about other things.
Some people, not necessary has mental issue, will never appreciate what they already have because they always desire to what they do not have right now. They never feel satisfaction.
no appreciation no satisfaction in those people's heart
I told manager that at the daily stand-up meeting, people just say - what I did yesterday - what I am doing currently
Most of the time, each one of us does not care about what other people did yesterday or is doing what today.
Only manager care.
Though manager get pissed off I still do not want waste my time on it.
2. Ideally, you should only test API not API's implementation but most of the mock framework will tie your test code directly against your API implementation. Once your API implementation changed, your test code fails, you have to rewrite test code, which is waste of time.
Someone may argue that it because you write bad test code; Talking is easier than doing;
So, usually, I prefer to doing the functional integration test than the unit test, which is productive for me. (I know people will throw out thousands of reasons about the benefit of unit test and "correct" way of writing unit test.)
Anyway, I will avoid unit test as possible as I can and ONLY do my designed integration test, which works for me.
3. And writing unit test for code coverage is stupid; Some manager even brag about the unit test coverage, which is totally a false confidence about the quality of the code underline; This is even stupid;
4. Writing unit test for those requirement-always-change area is waste of time;
5. TDD is a BIGGEST JOKE, which weights too much on writing auto testable code over writing working functional productive code;