Aria Stewart (aredridel) wrote,
Aria Stewart


Too much time spent on interfaces makes too many special parts, and too much assembly required.

Too much time focusing on the whole with no thought of re-use makes a hard to maintain solid whole.

Too much time spent writing tests makes code that fails where the tests don't cover

Too much time spent writing untested code makes code that fails where the tests should be.

Too much time focusing on the right way to make something Object-Oriented or Functional makes one forget the user interface, or worse, the user.

Too much time finding patterns means code that isn't gets neglected.

Too much time just coding means ignoring the obvious patterns you repeat.


  • rpc.statd goes wild!

    I came in to work today to find my mac workstation spinning running rpc.statd at 100% CPU. A quick dtruss -n rpc.statc showed that it was looping…

  • Useful Javascript

    I just created a drop-down menu with an option to add your own entries. Feel free to use. The skinny. Demo.

  • (no subject)

    I just asked my OpenSRS/Tucows domain reseller rep about AAAA (IPv6) glue records: They are planning to support them soon! In the mean time, they…

  • Post a new comment


    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded