Loggerlala
SERP Dominator
2
MONTHS
2 2 MONTHS OF SERVICE
LEVEL 1
300 XP
Stack Overflow, one of the best programming Q & A website have listed some of the world's most controversial programming opinions they ever received since the first day when the question was posted on the site last 2009.
Although the questions was only available among select users but it garnered some of the most awesome and sometimes awkward answer. The answers of the questions about the controversial programming opinions were listed on programming.overflow.com. The answers were submitted by different Stackoverflow users which were also listed below.
Here's the Top 10 Controversial Programming Opinions Listed in Random Orders:
1. Programmers who don't code in their spare time for fun will never become as good as those that do: by Rustyshelf
Even the smartest and most talented people will never become truly good programmers unless they treat it as more than job.
2. Unit testing won't help you write good code: by Chad Okere
The only reason to have Unit tests is to make sure that code that already work doesn't break.
3. The only "best practice" you should be using all the time is "User Your Brain." by Steven Robbins
Too many people jumping on too many bandwagons and trying to force methods, patterns, frameworks, etc. onto things that don't warrant them. Just because something is new, or because someone repected has an opinion, doesn't mean it fits all.
4. Most comments in code are in fact a pernicious form of code duplication: by Ed Guiness
We spend most of our time maintaining code written by others (or ourselves) and poor, incorrect, outdated, misleading comments must be near the top of the list of most annoying artifacts in code. Much better to concentrate on making the code readable, refactoring as necessary, and minimizing idioms and quirkiness.
5. "Googling it" is okay!
Google is one of the most valuable resources aside form the intense memorization and stacks of programming books. Anyone can access it within seconds, what is important is that you understand the material, use it as a means to an end of a successful programming solution.
6. Not all programmers are created equal.
The performance of one developer can be 10x or even 100x that of another.
7. I fail to understant why people think Java is the best "first" programming language to be taught in universities.
I believe that first programming language should be such that it highligts the need to learn control flow and variables, not objects and syntax.
8. If you only know one language, no matter how well you know, you're not a great programmer: by glenatron
Some programmers have an attitude that if they're really good at C# or Java or whatever other language they started out learning then that's all they need. Programmers should not believe it, every language that you learned has taught us something new about programming and those who restrict themselves with only one language will never be as good as they could be.
9. It's OK to writer garbage code once in a while: by jfar
Sometimes a quick and dirty piece of garbage cod is all that is needed to fulfill a particular task.
10. Print statements are a valid way to debug code: by David
I believe it is perfectly fine to debug your code by littering it with System.out.printIn (or whatever print statement works for your language.) Often, this can be quicker than debugging, and you can compare printed outputs against other runs of the app. Just make sure to remove the print statements when you go to production (or better, turn them into logging statements).
The lists of controversial programming opinions were submitted by Stackoverflow users. If you have some opinions about programming just add it in the comment space provided below.
Although the questions was only available among select users but it garnered some of the most awesome and sometimes awkward answer. The answers of the questions about the controversial programming opinions were listed on programming.overflow.com. The answers were submitted by different Stackoverflow users which were also listed below.
Here's the Top 10 Controversial Programming Opinions Listed in Random Orders:
1. Programmers who don't code in their spare time for fun will never become as good as those that do: by Rustyshelf
Even the smartest and most talented people will never become truly good programmers unless they treat it as more than job.
2. Unit testing won't help you write good code: by Chad Okere
The only reason to have Unit tests is to make sure that code that already work doesn't break.
3. The only "best practice" you should be using all the time is "User Your Brain." by Steven Robbins
Too many people jumping on too many bandwagons and trying to force methods, patterns, frameworks, etc. onto things that don't warrant them. Just because something is new, or because someone repected has an opinion, doesn't mean it fits all.
4. Most comments in code are in fact a pernicious form of code duplication: by Ed Guiness
We spend most of our time maintaining code written by others (or ourselves) and poor, incorrect, outdated, misleading comments must be near the top of the list of most annoying artifacts in code. Much better to concentrate on making the code readable, refactoring as necessary, and minimizing idioms and quirkiness.
5. "Googling it" is okay!
Google is one of the most valuable resources aside form the intense memorization and stacks of programming books. Anyone can access it within seconds, what is important is that you understand the material, use it as a means to an end of a successful programming solution.
6. Not all programmers are created equal.
The performance of one developer can be 10x or even 100x that of another.
7. I fail to understant why people think Java is the best "first" programming language to be taught in universities.
I believe that first programming language should be such that it highligts the need to learn control flow and variables, not objects and syntax.
8. If you only know one language, no matter how well you know, you're not a great programmer: by glenatron
Some programmers have an attitude that if they're really good at C# or Java or whatever other language they started out learning then that's all they need. Programmers should not believe it, every language that you learned has taught us something new about programming and those who restrict themselves with only one language will never be as good as they could be.
9. It's OK to writer garbage code once in a while: by jfar
Sometimes a quick and dirty piece of garbage cod is all that is needed to fulfill a particular task.
10. Print statements are a valid way to debug code: by David
I believe it is perfectly fine to debug your code by littering it with System.out.printIn (or whatever print statement works for your language.) Often, this can be quicker than debugging, and you can compare printed outputs against other runs of the app. Just make sure to remove the print statements when you go to production (or better, turn them into logging statements).
The lists of controversial programming opinions were submitted by Stackoverflow users. If you have some opinions about programming just add it in the comment space provided below.