RE: Assembly programmers do it a byte at a time

I don't mind someone knowing all this stuff, provided they realize that
none of it is actually programming.  There is a distinct line between
programming and architecture; architecture has to do with how we
program, but in the end the business goals rule the decision.  As long
as a programmer realizes that things like encapsulation and
normalization are nice to have, but that the real answer is to write
maintainable code in a reasonable time frame, then I have no problem
with them understanding those concepts.

I just get upset when someone comes into a perfectly running shop and
starts harping about how the shop needs to change over to the
architecture du jour, or else they don't know how to program.

Ah bullshards.  In the end it's all machine code, and the idea is to get
the best working, most maintainable machine code possible in the time
available.

Joe


> From: Alan Campin
> 
> Seems to me to be most important that you understand the concepts of
> software engineering. How many people working on the AS/400 know
anything
> about functional decomposition, encapsulation, information hiding,
> coupling, abstraction or normalization?
> 
> In other words, how many people know how to program on the AS/400? How
can
> you program in ILE if you don't understand these concepts? Pretty hard
to
> move forward if you don't have the basics.