Central Ohio Software Symposium

June 6 - 8, 2014

Narcissistic Design: 10 Steps to Complex Code and Job Security

Sunday - Jun 8 2:15 PM - Dublin III

Stuart Halloway

Stuart Halloway

President of Cognitect

The software industry changes rapidly, but you can protect yourself
from these changes by creating code that is complicated enough that
only you can maintain it.

Of course you should not engage in obvious bad practices. The good
news is that you don't have to. You can follow idiomatic industry
practice and stay buzzword compliant with the latest trends, while
quietly spreading complexity throughout systems. Better yet, the
symptoms will show up not in your own code, but in other code that
uses your code, directly or indirectly. You will be a hero as you
lead larger and larger teams burning the midnight oil to keep systems
alive.

Practice these principles, and your code will have an
infectious complexity that guarantees you will always be needed to
maintain it.

  • Use OO, and don't forget those setter methods!
  • Prefer APIs over data.
  • Start with DSLs.
  • Always connect (and never enqueue).
  • Create abstractions for information.
  • Use static typing across subsystem boundaries.
  • Put language semantics on the wire.
  • Write lots of unit tests.
  • Leverage context.
  • Update information in place.

Video Preview

About Stuart Halloway

Stuart Halloway is a founder and President of Cognitect, Inc. (www.cognitect.com). He is a Clojure committer, and a developer of the Datomic database.

Stuart has spoken at a variety of industry events, including StrangeLoop, Clojure/conj, EuroClojure, ClojureWest, SpeakerConf, QCon, GOTO, OSCON, RailsConf, RubyConf, JavaOne, and NFJS.

Stuart has written a number of books and technical articles. Of these, he is most proud of Programming Clojure.

Learn more about Stu's presentations on his wiki.