I read somewhere that somebody could access a config value during run time but not during design time. Whats the difference between run time and design time in this context?
+1
A:
Run time is when your program runs. Design time is when your program is designed.
fig
2010-04-12 12:29:42
+1
A:
design time is when you design some code
run time is when you execute the code you designed
oedo
2010-04-12 12:29:53
+1
A:
Design time is when you are creating a design based on the requirements, or creating some UML diagrams.
Run time is when you are implementing your design and running the code.
KhanS
2010-04-12 12:34:29
+2
A:
Design time is when when somebody signs off our word documents and our UML diagrams with a cheery "That looks fine!" Run time is when we execute our code and it fails with a horrible crash and burn.
The advantage of a technique like TDD is that it compresses the gap between design time and run time to the point where they are the same thing. This means we get instant feedback on how our design actually works when translated into code, which should result in a better design and fewer embarrassments when our code goes live. YMMV.
APC
2010-04-12 12:35:18
I wonder if, applying enough TDD or similar techniques, the gap closes so much that you get to nap time directly. Something like the old 'you end up with a one-line program that does not work'.
Adriano Varoli Piazza
2010-04-12 12:44:22
@AdrianoVaroliPiazza - With TDD we start out with "a one-line program that does not work" and move towards something more substantial which actually does work.
APC
2010-04-12 12:52:50
I know, I know. But your phrasing is actually opposite to that, and I felt jestful.
Adriano Varoli Piazza
2010-04-12 12:56:09
@AdrianoVaroliPiazza - I have re-read my post in the light of your comments and I see what you mean. I have re-edited it somewhat. Thanks for your input
APC
2010-04-12 13:19:56
A:
As a developer, you must aim for the ideal equilibrium between design time (let's take it to mean 'the time you spend designing and developing the app', though it's a bit incorrect) and run time, which I take to mean 'the time the user stands looking at the hourglass waiting for his important report to be rendered'.
Too much focus on 'design time' and you might run out of the scheduled programming time, and your client will pull out of the contract, he'll badmouth you, and kittens will die. Too little, and your program will, as they say, suck. Remember that 'shipping is a feature, one your program should have'.
Unless what they meant by "run time" is "runtime" and that means something else entirely.
Adriano Varoli Piazza
2010-04-12 12:43:00
+2
A:
Are you talking about .NET applications? In that case design time probably means something more specific - when your GUI is presented within the Visual Studio designer. This gives you a working view of your application, but it is running in a design time environment. Many .NET controls have a DesignMode property that allows you tell whether the control is running in design time view or not.
Dan Diplo
2010-04-12 12:43:09