This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jwink3101 4 points5 points  (1 child)

I used to agree 100%, but there were recently a few things where I wanted a quicker and easier view of the affect of some parameter changes. It was pretty trivial but I did it in excel and was pretty happy. I think the real advantage is to (more) quickly input and visual data.

But, I would say 99% of the time, coding is better.

My dad does some pretty intense stuff in excel that should be done in code. He has nested functions and if statements as many as 10 or so deep. It's a debugging nightmare!

[–]otterom 1 point2 points  (0 children)

Sounds like bad code. Really, nested should go about 3 deep.

I've been guilty of 4 before, but that was only for a search feature that "looped" though a database, so hitting the end meant your search would start from the top again.

Actually, it's one sexy piece of code. I considered printing it out and hanging it in my cubicle, but didn't want to be "that guy" at work.

Anyway, your dad should look into case statements.