For a long time we’ve treated frameworks as the target of software development. But if systems are meant to be regenerated and replaced safely, the real compilation target has to be the architecture itself.
When code becomes cheap to generate but expensive to understand, the most durable systems will be built from implementations meant to die. This series explores architectures where we regenerate rather than maintain.
We'll be releasing Objective-C, Java, C# open source SDK libraries for this soon. We already have JavaScript and Python plus a command line tool (wlist) out at https://github.com/wunderlist/
Oh we used those too, but in this case there were also native libraries. I was a regular user of jad, even sometimes recompiling and replacing stuff (ooooweeee) in production.
I guess a lot of teams are going through these same things right now. If anyone has more topics they're curious about, add them here or on the post and we might add to the series. Thanks!
A beautiful thing that this demonstrates is that no matter how old a concept is, there's always room to explain it clearly so that those who didn't already understand it have the benefit of finally being enlightened. I learned this many years ago as an author, thinking that my most basic ideas weren't worth writing down. It turns out that what's obvious to one person isn't obvious to everyone else.
Thanks for the reminder and for the clear explanation of how git deploy might work!
Thanks Joren! Great points about opening and closing. Conferences use the word "Keynote" really loosely, but I think they're best when used to open and/or close to set the context and mood for the event.