What's your most controversial programming opinion?
stackoverflow.com
What's your most controversial programming opinion?
1–10 of 53 posts
Re: What's your most controversial programming opinion?
#2Re: What's your most controversial programming opinion?
#3http://www.stlport.org/resources/StepanovUSA.html
I find OOP technically unsound. ...
I find OOP philosophically unsound. ...
I find OOP methodologically wrong. ...
http://www.infoq.com/presentations/The-DCI-Architecture (at around 39:30) You cannot do object-oriented programming in Java.
What the first calls OOP, the second calls "class-oriented programming". What the second calls proper OOP, I think is more along the lines of what the first advocates.Re: What's your most controversial programming opinion?
#4It seems as if people argue for the language they picked up first / have most experience in.
I believe the correct answer is not a direct answer, but something along the lines of "it doesn't matter, so long as you learn several, well".
Re: What's your most controversial programming opinion?
#5Re: What's your most controversial programming opinion?
#6I assume that's increasingly controversial :)
Re: What's your most controversial programming opinion?
#7I am often intrigued by people debating what language should be the first language other dev's learn. It seems as if people argue for the language they picked up first / have most experience in. I believe the correct answer is not a direct answer, but something along the lines of "it doesn't matter, so long as you learn several, well".
I learned C first, stopped studying C when I tried to make a GUI for win32. ~2 pages of code for an empty window. ~5 lines in Python.
So, the ideal first language is whatever is easy to understand and fast to accomplish something. Instant gratification, in other words.
Re: What's your most controversial programming opinion?
#8Re: What's your most controversial programming opinion?
#9i think some developers put too much stock in unit testing and it gives them (and their managers, customers, and co-workers) a false sense of security. they end up wasting time and not really preventing as many bugs as they think it will. application logic changes and they have to write twice as much code to change the application and all of the tests that depended on that logic.
writing a regression test for a complicated routine or library is one thing, but writing a test for every method of a class just for the warm fuzzy of their test framework telling them they have 100% coverage is silly.
Re: What's your most controversial programming opinion?
#10Here's mine: if you haven't gone through a respectable 4 year CS program, odds are I'm not going to want to hire you since your brain isn't wired to think about algorithms and data structures instead of code and servers.