HNHacker News
TopNewBestAskShowJobs

pauloortins

259 karma · joined April 25, 2013

submissionscomments
pauloortins··on Ask HN: If you were starting your career today, which language would you learn?
Why no one suggested C#?
pauloortins··on 5 reasons to avoid code comments
You never had problems with out-of-date comments ?
pauloortins··on What I learned using unit tests/TDD
I wrote about using unit tests with TDD. You can use unit tests without TDD. Of course, some of the TDD benefits are also achievable when we use only unit tests.
pauloortins··on What I learned using unit tests/TDD
I recommend to use. But I never used, so I prefer to not talk about something that I can't explain how to use.

But yes, I think that Continuous Integration is a good practice.

pauloortins··on What I learned using unit tests/TDD
Nobody said that they are same thing. People often said that they use both.
pauloortins··on What I learned using unit tests/TDD
What would be a good evidence for you about the TDD influence in design ?
pauloortins··on What I learned using unit tests/TDD
Type testing can be replaced by static types but you still have to test all the others stuffs in your code.
pauloortins··on What I learned using unit tests/TDD
I disagree with you at this point. When using TDD we tend to do a better code design and we avoid to write unnecessary code.

Take a loot at http://www.ime.usp.br/~aniche/files/tdd-and-design-draft.pdf

pauloortins··on What I learned using unit tests/TDD
When talking about this common scenario, there are two ways of think. Some people argue that you shouldn't expose private methods only to test them. You should do it through the public method to keep the encapsulation. Others argue that yes, you should expose these methods to make easier to write tests and to identify possible bugs.

It depends, we have to analyze each case and choose the advantages and disadvantages.

pauloortins··on What I learned using unit tests/TDD
I love clean and well-written code but to achieve clean code we should be able to refactoring without break our code. This is the point for TDD.
← PreviousPage 2 of 2