Communicating With Code

Thoughts on the theory and practice of software design.

Monday, November 17, 2014

Links

›
Taking a cue from Julia Evans , linking this here to remind myself to re-read it occasionally: John Allspaw's notes On Being a Senior E...
Sunday, November 9, 2014

Think Big, Act Small

›
There are, I think, two big dangers in designing software (which probably apply to other types of creative activity, as well): No u...
Wednesday, August 20, 2014

Why, What, How?

›
I recently encountered an argument ( Why Most Unit Testing is Waste ) from Jim Coplien arguing forcefully against unit testing a...
4 comments:
Sunday, July 27, 2014

Sources of Accidental Complexity

›
Recalling my preferred definition of solution elegance : TotalComplexity = EssentialComplexity + AccidentalComplexity Elegance = E...
Sunday, June 1, 2014

When Writing Code, Know Your Audience

›
It's well understood that software code is a document written primarily for two different types of audience: The platforms tha...
Saturday, March 22, 2014

Elegance Is Teaching

›
While the design process is a learning process , an elegant design can be considered a teaching tool. In order to justify this argument, I...
Monday, March 10, 2014

Mastery Against Generality

›
LtU pointed me to Design Principles Behind Smalltalk . I'll quote the first design principle named, because it illustrates what I thin...
‹
›
Home
View web version
Powered by Blogger.