1. 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.

    Stuart Halloway is a founder and President of Relevance. 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.

    Seen at Reaktor Dev Day 2013
    reaktordevday.fi
    blog.reaktordevday.fi

    # vimeo.com/77199361 Uploaded 8,009 Plays 7 Comments

Software dev

Jonathan Payne

Browse This Channel

Shout Box

Heads up: the shoutbox will be retiring soon. It’s tired of working, and can’t wait to relax. You can still send a message to the channel owner, though!

Channels are a simple, beautiful way to showcase and watch videos. Browse more Channels.