PCSpectra wrote:I firmly believe you...
Conversely if a experienced DBA came onto the project (better for the projectPCSpectra wrote:By virgin developer I meant someone just new to the project...not nessecarily programming in general.
Moderator: General Moderators
PCSpectra wrote:I firmly believe you...
Conversely if a experienced DBA came onto the project (better for the projectPCSpectra wrote:By virgin developer I meant someone just new to the project...not nessecarily programming in general.
Why wouldn't they understand the more readable of the two? Certainly the example VladSun gave used clearer naming conventions, no?Conversely if a experienced DBA came onto the project (better for the project ) that person would not only understand it,
Less typing is the essence of abstractionVladSun wrote: C'mon manLess typing doesn't worth the following much more reading and the headake.
You love that word don't you? I hear that word and I think shampoo for some reason...Less typing is the essence of abstraction
None of the above directly relates to less typing...I also don't think saying "cut down on implementation code verbosity" is accurate either as frameworks usually include a lot of implementation code...an abstraction however will usually hide/encapsulate those gory details from you...they are still there though.jshpro2 wrote:I don't understand your argument. Abstractions spare the programmer from repeating declarations when specifying implementations, they cut down on implementation code verbosity. Side affects of abstraction include extra indirection, diminishing returns (at first) and then ultimately more flexible code.
No it doesn't...that we can agree unequivocally.Regardless it has nothing to do with code indenting
viewtopic.php?f=1&t=93710VladSun wrote:Well, it's a bit off topic but it's close, so I'll ask it:
Why, even professional ones, IT guys use one letter table names aliases in their SQL queries. And it's worse - the more complicated a SQL query is, the more people tend to use aliases. It's like using a one-letter-named variables in programming language, but it seems that while nearly nobody do this in his source code, a lot will do it in SQL...
I really can't understand it