<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-35975337</id><updated>2011-09-28T13:40:45.575-05:00</updated><title type='text'>Metaphor Crash</title><subtitle type='html'>Do you believe what you see, or see what you believe?</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>18</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-35975337.post-507094800964775928</id><published>2008-08-12T11:12:00.006-05:00</published><updated>2008-08-12T11:34:10.538-05:00</updated><title type='text'>Atomic powered Project Integrity Management</title><summary type='text'>When creating a system for keeping up with massive ongoing change, there are many things to consider and it is easy to become bogged down in the details of it all. This may explain why so few projects ever follow through with their configuration management plans. While it is obvious to many people involved with a project that some kind of change control and configuration structure is needed, it </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/507094800964775928/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=507094800964775928&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/507094800964775928'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/507094800964775928'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/08/atomic-powered-project-integrity.html' title='Atomic powered Project Integrity Management'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://lh3.ggpht.com/_YeVVfegW8Vc/SHkWArdv6tI/AAAAAAAAvk8/K8TkI8cWMKI/s72-c/IMG_8826.JPG' height='72' width='72'/><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-8743331422170275556</id><published>2008-07-25T15:11:00.002-05:00</published><updated>2008-07-25T15:13:50.670-05:00</updated><title type='text'>In bookstores now! (not really)</title><summary type='text'>As promised, this is the "dust cover summary" of what this blog is about. If this sounds interesting, maybe you will periodically come back and read the new installments. If not, then you are no worse off.Project Integrity ManagementCopyright © 2008, M@January, 2005. After over four years and half a billion dollars, the FBI software system modernization project codenamed Project Trilogy was </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/8743331422170275556/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=8743331422170275556&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/8743331422170275556'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/8743331422170275556'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/07/as-promised-this-is-dust-cover-summary.html' title='In bookstores now! (not really)'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-8603240291859069164</id><published>2008-07-25T14:43:00.001-05:00</published><updated>2008-07-25T14:44:40.721-05:00</updated><title type='text'>Oh, the tedium!</title><summary type='text'>I have received comments on my blog that indicate that some readers may doubt my genuineness on the topic of Project Integrity Control. Probably through some fault of my own, some people have gotten the impression that I am holding back to keep people coming back and that there may not even be anything to the whole topic. The fear is, apparently, that they will invest great amounts of their time </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/8603240291859069164/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=8603240291859069164&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/8603240291859069164'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/8603240291859069164'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/07/oh-tedium.html' title='Oh, the tedium!'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-4493808833454425917</id><published>2008-07-23T16:17:00.001-05:00</published><updated>2008-07-23T16:17:33.926-05:00</updated><title type='text'>Sharpening the Focus on ICIs</title><summary type='text'>In order to show how mapping each item in a project to a ICI an make managing the project easier, it is necessary to define some type of structure that we can talk about. In this installment I will talk about the structure of an ICI and why it is so flexible.As I have already pointed out, the first thing we know about an ICI is that it has a unique identifier. This can be in any form that you </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/4493808833454425917/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=4493808833454425917&amp;isPopup=true' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/4493808833454425917'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/4493808833454425917'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/07/sharpening-focus-on-icis.html' title='Sharpening the Focus on ICIs'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-2066821743704086402</id><published>2008-07-23T10:24:00.001-05:00</published><updated>2008-07-23T10:24:41.044-05:00</updated><title type='text'>ICI Basic Training</title><summary type='text'>Last time I talked about how every part of a project must be uniquely identifiable and explained how the Integrity Control Item (ICI) can be used to perform this task. What I didn't really explain was what an ICI looks like, where it lives, and what it can do other than be unique. While being unique is a full time job for many celebrities, it is not extremely useful on its own. If we are going to</summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/2066821743704086402/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=2066821743704086402&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/2066821743704086402'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/2066821743704086402'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/07/ici-basic-training.html' title='ICI Basic Training'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-5191509824625097021</id><published>2008-07-18T15:28:00.003-05:00</published><updated>2008-07-18T15:34:37.062-05:00</updated><title type='text'>A huge floating mass of metal or a collection of units?</title><summary type='text'>In my last article I talked about the need for a unique identifier for each Integrity Control Item (ICI). I am going to expand on that concept this time around. If you end up following this series all the way through, when you look back you will see that the IM is so critical to getting control of your project that without it, there isn't much chance of pulling it off successfully. It will, one </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/5191509824625097021/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=5191509824625097021&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/5191509824625097021'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/5191509824625097021'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/07/huge-floating-mass-of-metal-or.html' title='A huge floating mass of metal or a collection of units?'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-6800379564060649664</id><published>2008-07-17T16:05:00.006-05:00</published><updated>2008-07-17T16:22:41.685-05:00</updated><title type='text'>Digging in to Project Integrity Management</title><summary type='text'>What is "Project Integrity Management"? How is it different from Configuration Management? How does it make it any easier to prevent the dreaded project meltdown? I'm glad you asked.As mentioned in a previous article, Configuration Management attempts to control elements of a project, specifically controlling and managing the constant change of information associated with the project. The amount </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/6800379564060649664/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=6800379564060649664&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/6800379564060649664'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/6800379564060649664'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/07/what-is-project-integrity-management.html' title='Digging in to Project Integrity Management'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-7391072857238996649</id><published>2008-07-16T09:25:00.004-05:00</published><updated>2008-09-10T23:20:40.104-05:00</updated><title type='text'>Why creating software really is like building cars</title><summary type='text'>I would like to start by admitting that I am cursed. (SPOILER WARNING: if you are considering hiring me, please stop reading now!) I am an albatross to companies that hire me. It is not that I sabotage them or fail to do my job, it is just that I have an uncanny ability to take jobs for companies that are starting to unravel. For whatever reasons, I have had a really bad run of projects in my </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/7391072857238996649/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=7391072857238996649&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/7391072857238996649'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/7391072857238996649'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/07/why-creating-software-really-is-like.html' title='Why creating software really is like building cars'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-6063564683629299616</id><published>2008-07-14T14:49:00.002-05:00</published><updated>2008-07-15T16:19:50.757-05:00</updated><title type='text'>Your first big challenge...getting the developers on board.</title><summary type='text'>Your In my last article I put for the theory that the most important thing to do when considering a new methodology, especially something as far reaching as CM (or as I have renamed it, Integrity Management - I can do that, its my article), is make sure you have the support of your developers. They are smart folks and it is much better to have them on your side than against you. So how do you do </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/6063564683629299616/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=6063564683629299616&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/6063564683629299616'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/6063564683629299616'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/07/your-first-big-challengegetting.html' title='Your first big challenge...getting the developers on board.'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-2782526740347187458</id><published>2008-07-13T14:04:00.005-05:00</published><updated>2008-07-14T10:48:09.310-05:00</updated><title type='text'>Where Does the Slippery Slope Start?</title><summary type='text'>So where do projects go wrong? If you are like me, you have been on a lot of projects and they always seem to be going along pretty well, then all of a sudden it starts to crumble. Deadlines begin to loom, hours get longer, and weird things start happening in the code that never happened before. As if that weren't enough excitement, the client finally pops into reality and starts to actually look</summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/2782526740347187458/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=2782526740347187458&amp;isPopup=true' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/2782526740347187458'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/2782526740347187458'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/07/where-does-slippery-slope-start.html' title='Where Does the Slippery Slope Start?'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-8729045962840140738</id><published>2008-07-03T11:28:00.002-05:00</published><updated>2008-07-03T11:32:14.332-05:00</updated><title type='text'>The Six Mysteries of Software Lameness</title><summary type='text'>As this series continues, I think it is becoming clear where it is going. Yes, I lured some folks in with some pretty attention-getting verbiage, but let's face it. If I had just come out and said "I am planning to do a series of articles about the value of Configuration Management in software projects!" you could have heard the wind blowing and crickets chirping as people avoided this blog like </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/8729045962840140738/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=8729045962840140738&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/8729045962840140738'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/8729045962840140738'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/07/six-mysteries-of-software-lameness.html' title='The Six Mysteries of Software Lameness'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-3133406470664921702</id><published>2008-07-01T14:00:00.001-05:00</published><updated>2008-07-01T14:00:59.794-05:00</updated><title type='text'>Configuration Management - A process, not a toolset</title><summary type='text'>One of the first questions that usually comes up when talking about Configuration Management is "What software should I use?" While the choice of tools is important, this should not be the first decision made. I would argue that you can't even answer that question until you have gone through a lot of other stuff first.In many ways implementing CM is similar to software development itself. With a </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/3133406470664921702/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=3133406470664921702&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/3133406470664921702'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/3133406470664921702'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/07/configuration-management-process-not.html' title='Configuration Management - A process, not a toolset'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-6900216276346939771</id><published>2008-07-01T09:20:00.001-05:00</published><updated>2008-07-01T09:22:09.337-05:00</updated><title type='text'>The difference between a developer and a programmer.</title><summary type='text'>Why is software development so hard? It could be argued that software development is so hard because programming is so easy. Since this seems to be contradictory, I will explain what that means.Whether or not most people realize it, the titles "developer" and "programmer" are not interchangeable. Nearly all of us (myself included) start out as programmers. We learn the programming languages, the </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/6900216276346939771/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=6900216276346939771&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/6900216276346939771'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/6900216276346939771'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/07/difference-between-developer-and.html' title='The difference between a developer and a programmer.'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-699826509463090609</id><published>2008-06-30T10:04:00.005-05:00</published><updated>2008-06-30T12:35:54.393-05:00</updated><title type='text'>Why Software Projects Fail</title><summary type='text'>OK, enough analysis and example. Whether you agree with my approach, my points, or even my page layout (yes, I know some of you hate it, but then again, it is my page right?), I think nearly all of us can agree on one point: Software has plenty of room for improvement.In the big scheme of all things technical, programming is pretty new. Not only that, but since languages change over the course of</summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/699826509463090609/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=699826509463090609&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/699826509463090609'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/699826509463090609'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/06/why-software-projects-fail.html' title='Why Software Projects Fail'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-8469222373415530845</id><published>2008-06-27T08:00:00.003-05:00</published><updated>2008-06-27T08:15:36.332-05:00</updated><title type='text'>Software Engineering Revisited</title><summary type='text'>The response to my previous article about Software Engineering (or the lack thereof) resulted in an impressive number of responses. This is apparently a topic that a lot of people have an interest in. Someone posted a link to the article on Reddit.com and I have to say, those folks are brutal critics. But as with most critics, they have a very annoying way of being right.I chose to introduce the </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/8469222373415530845/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=8469222373415530845&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/8469222373415530845'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/8469222373415530845'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/06/response-to-my-previous-article-about.html' title='Software Engineering Revisited'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-6261813326616673703</id><published>2008-06-26T09:57:00.001-05:00</published><updated>2008-06-26T11:53:19.093-05:00</updated><title type='text'>Software Engineering? Maybe not.</title><summary type='text'>A plane crashes, killing all 287 people on board. A bridge collapses plunging thirteen motorists to their watery graves. A construction crane buckles and crushes an apartment building, killing several workers and residents. We have all heard these stories on the news and they are always followed by outrage, someone asking how this could have happened, and many extensive investigations into the </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/6261813326616673703/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=6261813326616673703&amp;isPopup=true' title='20 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/6261813326616673703'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/6261813326616673703'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2008/06/software-engineering-maybe-not.html' title='Software Engineering? Maybe not.'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>20</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-5849267917279642938</id><published>2006-10-26T12:37:00.000-05:00</published><updated>2006-10-26T13:45:08.261-05:00</updated><title type='text'>The Coming Desktop Metaphor Crash Part I</title><summary type='text'>The world of computers is reaching a critical juncture. At stake are the past fortunes of some very large “old school” companies such as Microsoft and the future fortunes of some up and coming “rebel” companies like Google and Yahoo.As the prevalence of always-connected broadband internet access increases, some subtle but powerful shifts are taking place. The future looks a lot less like the Bill</summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/5849267917279642938/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=5849267917279642938&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/5849267917279642938'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/5849267917279642938'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2006/10/world-of-computers-is-reaching-critical.html' title='The Coming Desktop Metaphor Crash Part I'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-35975337.post-6114640700382264380</id><published>2006-10-18T17:07:00.000-05:00</published><updated>2006-10-18T17:27:34.402-05:00</updated><title type='text'>Welcome to the Crash</title><summary type='text'>What is Metaphor Crash?In his essay “Once there was the command line”, Neil Stephenson introduces the concept of Metaphor Shear with a hypothetical occurrence that nearly all of us can, unfortunately, relate to. He described it as the moment when the document that he had just been working on suddenly disappeared from his computer screen with no warning. What was a few seconds before a very </summary><link rel='replies' type='application/atom+xml' href='http://metaphorcrash.blogspot.com/feeds/6114640700382264380/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=35975337&amp;postID=6114640700382264380&amp;isPopup=true' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/6114640700382264380'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/35975337/posts/default/6114640700382264380'/><link rel='alternate' type='text/html' href='http://metaphorcrash.blogspot.com/2006/10/welcome-to-crash.html' title='Welcome to the Crash'/><author><name>M@</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry></feed>
