1 step or many lines?

Hi,

I'm wondering how most developers think when coding with regards to steps of
code. Is it best to have as much done as possible on one line, making the
code faster, or is it better to break it up a bit so that it's more readable
& easier to debug? As a simple example, concatinating strings, or setting up
an ADO object in code. For that matter, is it best to set as many properties
using the properties box instead of in code? Does this also increase code
efficiency?

Thanks for your ideas
Ant
.

Relevant Pages

  • Re: 1 step or many lines?
    ... > I'm wondering how most developers think when coding with regards ... Unless you're writing in APL, ...
    (microsoft.public.vb.general.discussion)
  • Re: D2006 after 1MB -> 2MB ram
    ... > One sheet per application containing all required code, documentation etc. Compare that to today:) ... > best regards ... > The best components for the best developers ...
    (borland.public.delphi.non-technical)
  • Re: In need of .NET advocacy
    ... naked pointer in C++ has deterministic clean-up, but you have to call delete ... The tools help you with coding if that's what you mean. ... >the market of .NET developers will get a big boost. ... and some things worse than other languages. ...
    (microsoft.public.dotnet.general)
  • Re: grown out of coding
    ... I now find I'm really tired of coding - sure, ... I have a bunch of questions that pop to mind immediately. ... or systems software or tools where your end-users are developers? ... or does it sound like a luxury to "just" be able to react as needed? ...
    (comp.databases.pick)
  • Re: Conscious antipattern behavior
    ... >as an indication that the language or the ... >are informal standards of good coding practice ... refactoring unless the customer is at the door screaming. ... and are usually not met if the developers try to do any proper design ...
    (comp.lang.cpp)