For quite a while now, I've been doing most of my writing using XML - even to the point of writing my last book in XML.As I've mentioned this to people they've asked me a number of questions about my experiences, and that's been enough to prompt this little article on the whole thing.
It's only just over a year since I got my first ebook reader.Now I only buy paper books when I really have to.I wrote my last book thinking of it primarily as a paper book, but that will be the last time, in the future electronic forms will be at the front of my mind.These changes will completely alter the landscape of books, but other than that, the next steps aren't that clear.
I've spent a lot of my writing energy writing patterns.From time to time I get asked questions about why I do that and what makes a good pattern.This is a brief article about how I look at patterns with my suggestions for people who are interested in writing patterns themselves.
My IEEE column on the valuable contributions that patterns can make to understanding software design.
One of the frustrations of the software development field it's hard to choose between different techniques and tools.Often when someone talks about this they are asked for 'hard data' that the technique or tool is better than alternatives.It's an understandable request, but in the end it's a doomed one.For a start weCannotMeasureProductivity。
Andrew Koenigfirst coined the term "antipattern" in an article in JOOP, which is sadly not available on the internet.The essential idea (as I remember it ) was that an antipattern was something that seems like a good idea when you begin, but leads you into trouble.Since then the term has often been used just to indicate any bad idea, but I think the original focus is more useful.
Every so often I get someone who not just disagrees with something I've said, but is also alarmed that I've said it."When a guru like you says something, lots of people will blindly do exactly what you say".
Making and editing video used to be an expensive exercise, but now cameras and editing software are cheap.As a result many loud-mouths like me have got into making videos to help spread their ideas.There's many reasons to do this, it's a medium with lots of possibilities, it suits people like me who talk well on stage, and there's good evidence that people will pay for video - which is good both for one's income and as evidence that people take it seriously.Despite these reasons, so far I've not taken the plunge.
I don't not write much production code these days, but I still spend quite a few hours writing code.This code is a particular form of code, meant for explaining ideas in books.Book code isn't quite like real code, there are some different forces to consider when writing it.
I write about design, and it's my view that even when you are discussing somewhat abstract design patterns it's useful to provide source code examples.当然，这会导致人的想法，代码示例是模式，但我认为风险是由代码提供了精确抵消。有好几次我不太肯定的想法，但一个代码示例有助于澄清对我来说。所以在我设计的写作，我总是尽量提供代码示bet188足球例。
一个关于最引人注目的东西Manifesto for Agile Software Development是它的值的格式“我们赞成x过度y”我不记得是谁与想法，或者它如何出现了上来。这可能只是冒泡，我们就四处征集，但它独特的格式，导致几人再次使用该格式尝试。
上周，我在我的签名系列得到了最新的书：xUnit Test Patterns杰拉德梅萨罗斯。我一直在与杰拉德用它打开和关闭了几年，所以我相当熟悉其内容，但不知何故，看到物理拷贝给了我不小的震动。不知怎的，它并没有明白了我的那本书有多大， - 883页，轻松的最大的书在我的系列。
所有这些网站是用简单的XML文件，并转换成HTML。我觉得这个作品真的很好，而且手段我从来没有关于处理HTML格式的烦恼。（不花哨布局是我的风格，你可以告诉）。我甚至写a whole book that way。
1: a new word, usage, or expression.
2: a meaningless word coined by a psychotic.
微软已经发布了一个新的名为社区资源PatternShare。这个想法是从众多模式的作者汇集模式的总结和讨论提供以及它们之间的相互联系的进一步探索的平台。大部分的工作是由Ward Cunningham，其模式血统是首屈一指的领导。你会从我自己在那里找到的模式，GOF，POSA，Hohpe /伍尔夫，埃文斯和微软。
关于模式的书籍普遍的抱怨是，他们没有什么新告诉经验的开发人员。（我也曾有过一些这些最近在亚马逊的评论和The Server Side或许，因此我感觉在目前敏感。）不只是这是真的，但它的模式的整点。
我的成功作为一个作家的副作用之一 is that I've become a minor geek celebrity.It is very minor, usually only taking effect in geek conferences (although I have had people wander up to me in a restaurent a couple of times in San Francisco.) Before it happened I really didn't think much about it, other than a mild hankering after fame.Now it's happened I'm more aware of it - and all in all I hate it.
From time to time people ask about how you get a book into my signature series.There are lots of book series out there and each series has its own way of deciding what to accept.Here's how I decide
From time to time I run into people who want to get a smalltalk and give it a spin to see what the fuss is about.My oldfavorite introductory smalltalk bookwent out of print, but I just discovered you can nowdownload it from heretogether with lots of other smalltalk related material.The material is hosted by Stéphane Ducasse, who was a co-author on an excellent book onreengineering patterns。
I wasn't cool enough to be in the first wave of invitations, but I have now got ontoGoogle+, the Maybe Next Big Thing in social networks.It seems somewhat appropriate to mark this Momentous Event by writing a little bit about how I've used social networks so far, and some uninformed speculation about the impact of Google+
If you read many standards documents, apart from the need for excessive amounts of coffee, you'll also need to be wary of the overloaded meaning of some words.
It's one thing to idle away your productive hours reading this blog, but some people like to translate it too.So I'd like to welcome aThai translationwhich is being done by a team of people led by Wee Witthawaskul.About fifteen years ago I visited Thailand as a typical backpacker western tourist.I have fond memories of the river buses in Bangkok, hiking near Pai, snorkelling at Ko Pi Pi, and some great food.I first met Wee while he was working with Ralph Johnson, he's now joined me at ThoughtWorks.
XML has been around for a while now, and it's used a lot - indeed a lot more than it should be.Like most tools XML is good for some things and not for others