Learn when to stop! Don't over-engineer your code.

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :| :mrgreen: :geek: :ugeek: :arrow: :angel: :clap: :crazy: :eh: :lolno: :problem: :shh: :shifty: :sick: :silent: :think: :thumbup: :thumbdown: :salute: :wave: :wtf: :yawn: :facepalm: :bravo: :dance: :beard: :morebeard: :xmas: :HeHe: :trollface: :cookie: :rainbow: :monkeysee: :monkeysay: :happybday: :headwall: :offtopic: :superhappy: :terms: :beer:
View more smilies

BBCode is ON
[img] is OFF
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: Learn when to stop! Don't over-engineer your code.

Re: Learn when to stop! Don't over-engineer your code.

Post by jballi » 12 Feb 2020, 22:16

"It's done. It's all done. "It's the best code ever!"

I'm guilty of adding a lot of comments to my code. Although I do it for the developers that I might share the code with in the future, I mostly do it for myself. I write a lot of stuff for fun and to keep learning. The comments help me to remember what the code is for and what is does.

Re: Learn when to stop! Don't over-engineer your code.

Post by Subaru » 04 Dec 2019, 12:36

I am no programmer, but this reminded me of two things. One is something I could apply to myself; just replace keyboard with pencil/pen in "Put down the keyboard" and stop adding shadows where they're not supposed to be in a drawing.. being self-taught entirely (nevermind primary school's art lessons) I tend to be constantly overdoing it with shading. Like with that one horse drawing.

The other is what I think an old presentation I downloaded loong ago, using (pre-*cough*Adobe takeover) .swf for playback, all zipped. Still trying to find where'd I put it on my hdd, but I think it was titled "Pardon my french, but this code is C.R.A.P." by Alberto Savoia and Bob Evans. A real fun watch.

Definitely on track, this sounds just like the kind of humour I remember from that presentation :D :
Note: This post is rated PG-13 for use of a mild expletive. If you are likely to be offended by the repeated use a word commonly heard in elementary school playgrounds, please don’t read any further.
CRAP is short for Change Risk Anti-Patterns – a mildly offensive acronym to protect you from deeply offensive code. CRAP was originally developed and launched in 2007 by yours truly (Alberto Savoia) and
my colleague and partner in crime Bob Evans.
Source: https testing.googleblog.com /2011/02/this-code-is-crap.html Broken Link for safety

Re: Learn when to stop! Don't over-engineer your code.

Post by jeeswg » 12 Sep 2019, 05:39

Great video! :thumbup:

Learn when to stop! Don't over-engineer your code.

Post by SOTE » 11 Sep 2019, 09:23

Funny and a good warning.

Programmers! Learn when to stop! Don't over-engineer your code.

https://www.youtube.com/watch?v=-AQfQFcXac8

Top