Both, but mostly code formatting. The architecture, if applied to framework properly, can make it that much more easy to pick everything up at a glance. But for our purposes here, lets just say formatting. The problem with referring to documentation that tells you what the code or app does is that it may not have been applied as you think. If I'm doing something with an app, I want to be sure that I'm doing it with the way it actually does work as opposed to how I think it should work. Being able to refer to good documentation is always nice as an option, but is no substitute for running through the lines and clearly seeing what everything does and how its being done.
-----Original Message----- From: Jeffry Houser [mailto:[EMAIL PROTECTED] Sent: Monday, May 09, 2005 5:07 PM To: CF-Jobs-Talk Subject: RE: What makes a programmer look low level When you say "Structure" are you talking about code formatting, or something different? My impression is that you are referring to "code formatting" however structure could mean different things, so... I'd rather see comments than formatted code. I can read unformatted code, or format it as I'm reading it. If by structure, you mean a well-thought out architected application that makes use of CFCs / custom tags / UDFs to encapsulate functionality and data.... As long as the application architecture was documented, I may not complain about the lack of excessive comments within in the code (although I'd still prefer they were there). I'd rather be told what the code does w/o having to figure out. At 04:52 PM 5/9/2005, you wrote: >Is it just me, or do the comments other developers leave throughout their >code mostly get in the way of just reading the raw code? Having read through >all kinds of existing code, I much prefer to have everything scoped and the >code arranged in a consistent, logical format for readability. I'd rather >see structure than comments, basically. So, if the code is difficult to read >because of how its structured, rather than because of what it does, that >would be an indicator of a beginner (or an expert job-security guru.) If the >structure of the code is logical, most experienced developers should be able >to follow along and understand right off the bat. Comments should be sparse, >terse and contain obscure information (not easily seen by parsing through >the lines) as an indicator for an advanced developer. > >Louis Mezo >LogicSynthesis >Tel: 240.498.8951 >[EMAIL PROTECTED] >http://www.logicsynthesis.com -- Jeffry Houser, Web Developer, Writer, Songwriter, Recording Engineer AIM: Reboog711 | Phone: 1-203-379-0773 -- My Company: <http://www.dot-com-it.com> My Books: <http://www.instantcoldfusion.com> My Recording Studio: <http://www.fcfstudios.com> Connecticut Macromedia User Group: <http://www.ctmug.com> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:11:2576 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/11 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:11 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.11 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
