In addition to the time to proficiency issue; will any of the .NET languages allow for the “quickie fix” possible with VBA or Lisp? How long has the Minimum Task Length Savings become with .NET
For example, if I had a specific repetitive task – say 15 or 20 minutes by hand – but it had a readily discernable logic flow, then I’d be tempted to automate with VBA, even if the task was not likely to ever be required again.
Obviously, this is depends heavily on proficiency. As it stands, even a readily discernable logic flow would have to save me several weeks for me to tackle it in C# :realmad:. I hope to have the MTLS down to one week by the end of the year. With the integrated IDE and immediate debugging features of VBA, it may even be faster than Lisp for the +12 line “quickies”. I don’t know enough about VisualLisp, and its IDE to extend the comparison (for that matter, does the warning about VBA also apply to the ActiveX component of VisualLisp)
For those of you who have achieved a good level of .NET proficiency: With the added overhead of firing up VS, the not quite immediate debugging, what do you think would be the best MTLS?