FizzBuzz is easy if you're comfortable with modulus or doing your own modulus. I'd be surprised to ever see it in an interview just because most programming tests are puzzles which are worthless if the person knows the solution to the puzzle already.
I've seen code like the fizz buzz enterprise code and had conversations that went:
"Why did you make a class for doing while loops?"
"Because encapsulation is an important part of programming. You should read this book about data hiding so you can get to the next level of programming skill!"
"But you've taken a 5 line solution and made it into a 20 line solution."
"Maybe, but my solution is more testable. You should read this book about unit testing."
"But only because you added code, the core functionality has the same level of testability."
"Maybe, but with this you can exchange loops without knowing the underlying implementation. You should read this book about design patterns."
Ugh cargo cult programming.
Man that brings back some bad memories of some software developers I work with who create voluminous amounts of code to solve very simple problems. They also do it because they 100% believe their way of producing code is superior. I feel like those developers are shit programmers who blindly apply programming methodologies because it's easier than solving the core issues.Ohh god I love that. Had forgotten about it.
Fix code style violation reported in PR#184 ·[email protected]/* <![CDATA[ */!function(t,e,r,n,c,a,p){try{t=document.currentScript||function(){for(t=document.getElementsByTagName('script'),e=t.length;e--if(t[e].getAttribute('data-cfhash'))return t[e]}();if(t&&(c=t.previousSibling)){p=t.parentNode;if(a=c.getAttribute('data-cfemail')){for(e='',r='0x'+a.substr(0,2)|0,n=2;a.length-n;n+=2)e+='%'+('0'+('0x'+a.substr(n,2)^r).toString(16)).slice(-2);p.replaceChild(document.createTextNode(decodeURIComponent(e)),c)}p.removeChild(t)}}catch(u){}}()/* ]]> */· GitHub
I just saw one of these code-reviews a few days ago
LOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOL
Merge pull request #182 from joezeng/patch-1 ·[email protected]/* <![CDATA[ */!function(t,e,r,n,c,a,p){try{t=document.currentScript||function(){for(t=document.getElementsByTagName('script'),e=t.length;e--if(t[e].getAttribute('data-cfhash'))return t[e]}();if(t&&(c=t.previousSibling)){p=t.parentNode;if(a=c.getAttribute('data-cfemail')){for(e='',r='0x'+a.substr(0,2)|0,n=2;a.length-n;n+=2)e+='%'+('0'+('0x'+a.substr(n,2)^r).toString(16)).slice(-2);p.replaceChild(document.createTextNode(decodeURIComponent(e)),c)}p.removeChild(t)}}catch(u){}}()/* ]]> */· GitHub
I've seen code like the fizz buzz enterprise code and had conversations that went:
"Why did you make a class for doing while loops?"
"Because encapsulation is an important part of programming. You should read this book about data hiding so you can get to the next level of programming skill!"
"But you've taken a 5 line solution and made it into a 20 line solution."
"Maybe, but my solution is more testable. You should read this book about unit testing."
"But only because you added code, the core functionality has the same level of testability."
"Maybe, but with this you can exchange loops without knowing the underlying implementation. You should read this book about design patterns."
Ugh cargo cult programming.