do not bother too much to others. they may have more important things to do than talking on a topic with someone. its waste of time. concentrate and do your job instead of trying to trap and do bs. do some serious business guys.
In my opinion, none of the language will solve the problems with programming or bad programs. The only thing which could help programmers is the way they think of the solution and how they approach to it. Thinking about long term solution for a given problem may help.
"we are a dirt poor country"...man only u r dirt cheap one...
how could one say so confidently to whole nation,...any nation? rethinking needed here...
someone need to speak-up. comcast does the same...they advertise as unlimited speed...u know how much speed u get...how come internet speed be unlimited :-)
its all about fooling consumers and collecting money by bad marketing campaigns....atleast comcast maintains monopoly so nothing could be done to them until we have some good competitors who deliver what they claim...then we will have good and genuine marketing campaigns...in Telecom, most companies boasts the same....some day the justice will be given to 'Unlimited' word and it will find its true meaning again...I'm hopeful...
good idea..corte.si...
I think adding a machine learning method on reordering/prioritizing the links would be a plus...the input data for the machine learning system would be the links user clicks to read as well as links to which user clicks as favorite...
or may be pulling the keywords/tags from a given link's page and then checking how many links are clicked under a certain tag will surely help ordering the links by tags...its just my idea on how to help user to read his preferred links/topics....your inputs are welcome!
there are really nice comments below in this thread on why testing functionality is better than writing unit test cases to test the functions/methods/code.
e.g.
wr1472: test the what not the how
MrEnigma: the higher level the test (i.e. unit ->
integration -> functional) the better they catch things
Keithnoizu: verify requirements not implementation details
we understand that the unit testing is trying to test the functionality and making sure that the acceptance criteria is also met at the same time. I would like to mention one more point is that we should also try to write unit test cases not just only test the functionality but also try to do a good code coverage. unit test cases are tools for:
1. functionality testing
2. comply with acceptance criteria
3. a tool to help good code coverage
4. be iterative. be backward compatible as long as it could. (anyway to add logic based on version of the code change? need to think on this). yes it makes it little bulky but will work and avoid needing code cleanup and redesigns.
let unit tests help come up with min 80% of code coverage.