Google, C._D., Programmer discussed on The Changelog
The references we made <hes> but the biggest updates weren't because of the changes in technology they were because of the changes in our experience so that over the last twenty years we've explained the content of the book many times over to different people and as we've done that we discovered better ways explaining things <hes> you know we've also looked at <hes> the reaction to various parts of the book and discovered that weren't really communicating as well as we thought we were <hes> some of the ideas that we had so a classic one of that is dry where dry has come to mean don't cut and paste but the original original don't repeat yourself with has nothing to do with code it was to do with knowledge so we've had to go through an an update that and also in the time there's been changes in the way the industry works <hes> so that we are doing far more intensive cloud type stuff can currency is now everybody's problem <hes> and so we've had to address those new areas as well you have to sort of go back and put yourself into what the world was like twenty years ago <hes> because certainly when we I took on this <hes> this latest venture it's like oh we'll just go through and we'll change a couple of the technological references and we'll be up some of the things that we've had more experience with but it won't be that different and you go back and you read it and then you start to remember you know your see your friends at the time your clients at the time what you were working on and you really start to realize what a different world. It was twenty years ago you know A._O._l.. Was Carpet bombing people with C._D.'s trying to get you to dial up. You know this sort of thing I mean <hes> we didn't have anything in there talking about <hes> security trying to trying to fight against bad actors. 'cause you know at the time it was sort of just a struggle to get you to work. You didn't really have to worry specifically about it being attacked packed for the most part and now that's kind of step one <hes> a lot of things that we promoted in pushed were still very brand new at the time so we were talking a lot about <hes> insisting that you do unit testing and you know that's part of the safety net that hold you up but at the time that wasn't really widely accepted it wasn't as widely practiced so we had advice in there saying you know go off and build your own unit testing framework for your favorite language so you'll have it available which look at I mean. It's kind of hilarious now because now no do not do that. That's a terrible idea. It was a great idea then but times have changed now. That's ubiquitous. It's it's it's everywhere. Don't reinvent the wheel so some things like that changed changed. I certainly think for the better where you know advice that we gave out you know things that we were pushing. We were promoting have become commonplace have become widely accepted so that's kind of heartening on the one hand doesn't remember is the back <hes> when I written a ninety eight ninety nine <hes> that was <hes> before the snowbird meeting that kicked off <hes> the Agile Movement for want of a better word and we were part of that but but <hes> it hasn't happened yet a lot of the vocabulary that has come to become common nowadays <hes> was formed by that movement <hes> and so you know we've had the opportunity to simplify some expectations in light of the the fact that stuff that we were talking about has now become commonplace as part of you know the various different <hes> agile ways of doing things speaking commonplace one of the things that was not really complex at the time of the original launch it was even Google it was just barely out and to be a programmer today in good was your best friend right. You know find the answer. If you've hit hit a wall even then when you wrote the book Google was barely even in the now we did it. They were using using we were using Alta Vista..