نقل قول نوشته شده توسط saeed_Z_F مشاهده تاپیک
که با این تفاسیر اینها به برنامه نویسی مربوط نمیشه یه برنامه نویس (یا همون کدنویس )خوب (یا همون حرفه ای ) باید به syntax زبان و چگونکی استفاده و ترکیب آنها مسلط باشه طراحی و معماری توسط کسی دیگه انجام میشه .
نقل قول نوشته شده توسط sinpin مشاهده تاپیک
ااما یک برنامه نویس الزاما نباید مسایل طراحی رو بدونه (که اگه بدونه میشه برنامه نویس ارشد) و گاها کافیه که فقط یک کلاس دایاگرام یا use_case رو متوجه بشه.
چند روز پیش داشتم کتاب Professional ASP.NET 2.0 Design CSS, Themes, and Master page
که نویسندش Jacob J. Sanford هست را برگ می زدم. اول فصل سوم این کتاب یه توضیحاتی داده که شاید شنیدنش برای شما هم قشنگ باشه.

ابتدا بیوگرافی ایشون



Jacob J. Sanford is currently a Project Lead with the Rapid Application Development Team at the Florida
Department of Children & Families. He began developing web applications more than 10 years ago using
primarily classic ASP with various relational databases. Over the years he has dabbled in other web
application development languages such as ColdFusion and PHP. However, he has been working almost
exclusively with the .NET Framework since its 1.0 release. He is a regular contributor to 2MinuteTips.com
and makes frequent presentations at local and regional .NET events. Having worked in all aspects of the
SDLC, he has been focusing his recent efforts primarily on accessible web design (especially as it pertains
to .NET applications). He also spends an inordinate amount of time ‘‘playing’’ with the latest (alpha and
beta) web technologies, especially Microsoft Silverlight. He is married and as of writing this book has
one son, but by the time you read it, he will have two. (Welcome to the world, Hayden.)


حالا صحبت هایی که به نظرم قشنگ اومدن.. البته شاید خیلی بدیهی باشه و لی بد نیست بخونین

الیته ایشون در مورد یک developer صحبت می کنه





In a perfect world, perhaps, a developer is simply a person who crunches out code. No need
to meet with clients and gather their requirements; that is the job of the project manager.
No need to design or ensure the integrity and security of the database infrastructure; that is the
job of the DBA. No need to worry about IIS configuration issues or the segregation of environment
platforms (e.g., development, acceptance testing, production); that is the job of the network guys.
And certainly no need to worry about color schemes, graphics, or logos used in the application; that
is the job of the graphic designer.
But more and more, this is becoming less and less acceptable. In an interview, it is no longer uncommon
to hear that the potential employer wants to know that the developer they hire can carry a
project all the way from the requirements gathering to production and maintenance. For any of
the steps involved in the Software Development Life Cycle, it is becoming increasingly hard to say
‘‘that isn’t my job.’’ Everything is your job
. As a developer, you are expected to gather customer
requirements, develop proof-of-concept designs, make decisions on application and database platforms,
create and maintain databases for your projects, administer the IIS of the web servers (at least
at the development region), and work with your clients through acceptance testing and eventually
production moves and maintenance.

موفق باشید