Architecture in a Box (Permalink)
April 10th, 2009Programming used to be about moving bits, so programmers memorized the power of 2 and ASCII or EBCDIC. Then it was about control flow, and programmers learned how to loop over an input deck and perform an operation for each element of the deck (and how to handle the pesky EOF case, which may force you to read twice from the file). Then it became about data structures, and programmers learned how to build their own linked lists of records, trees of records, traversals, and so on. But advances in programming languages and environments have made most of that knowledge obsolete, even dangerous. Today, programming is about design and architecture. But are advances in frameworks making this knowledge irrelevant as well?