LEMON - On Drupal diseases and cures

Editor's Notes

• #2: Good afternoon. Welcome to LEMON- Drupal diseases and cures. \n
• #3: My name is Jody Hamilton. Making lemonade since drupal 4.7\n\nZivtech Lead Developer, business owner, engineer, teacher, manager, quality freak\n\n
• #4: What is a Drupal lemon?\nA site that makes experienced drupal developers laugh and cry at the same time. Measure in WTFs per minute.\n\n
• #5: What is a Drupal lemon?\nA site that makes experienced drupal developers laugh and cry at the same time. Measure in WTFs per minute.\n\n
• #6: What is a Drupal lemon?\nA site that makes experienced drupal developers laugh and cry at the same time. Measure in WTFs per minute.\n\n
• #7: What is a Drupal lemon?\nA site that makes experienced drupal developers laugh and cry at the same time. Measure in WTFs per minute.\n\n
• #8: What is a Drupal lemon?\nA site that makes experienced drupal developers laugh and cry at the same time. Measure in WTFs per minute.\n\n
• #9: What is a Drupal lemon?\nA site that makes experienced drupal developers laugh and cry at the same time. Measure in WTFs per minute.\n\n
• #10: How many lemons are there?\nWhy are there so many?\nThe rise of the ‘site rescue’ job\nThis is bad for Drupal’s reputation\n\n - Lack of experts\n - new field\n - learning curve\n - Difficulty of field is underappreciated (ie you wouldn’t treat something ‘difficult’ like surgery the same way) The easiness of using drupal or basic site building also stands in confusing contrast to the difficulty of custom application development in drupal or excellent and advanced site building.\n - Rush jobs\n - Cheap jobs\n- Hard to assess Credentials\n - lack of certification\n - too complex for decision makers\n - Drupal has a completely transparent and inscrutable system for measuring dev quality\n- Drupal makes it easy to mess up (by being complex and flexible). With great power comes great need for training. Beware those who ‘know just enough to be dangerous’\n
• #11: How many lemons are there?\nWhy are there so many?\nThe rise of the ‘site rescue’ job\nThis is bad for Drupal’s reputation\n\n - Lack of experts\n - new field\n - learning curve\n - Difficulty of field is underappreciated (ie you wouldn’t treat something ‘difficult’ like surgery the same way) The easiness of using drupal or basic site building also stands in confusing contrast to the difficulty of custom application development in drupal or excellent and advanced site building.\n - Rush jobs\n - Cheap jobs\n- Hard to assess Credentials\n - lack of certification\n - too complex for decision makers\n - Drupal has a completely transparent and inscrutable system for measuring dev quality\n- Drupal makes it easy to mess up (by being complex and flexible). With great power comes great need for training. Beware those who ‘know just enough to be dangerous’\n
• #12: How many lemons are there?\nWhy are there so many?\nThe rise of the ‘site rescue’ job\nThis is bad for Drupal’s reputation\n\n - Lack of experts\n - new field\n - learning curve\n - Difficulty of field is underappreciated (ie you wouldn’t treat something ‘difficult’ like surgery the same way) The easiness of using drupal or basic site building also stands in confusing contrast to the difficulty of custom application development in drupal or excellent and advanced site building.\n - Rush jobs\n - Cheap jobs\n- Hard to assess Credentials\n - lack of certification\n - too complex for decision makers\n - Drupal has a completely transparent and inscrutable system for measuring dev quality\n- Drupal makes it easy to mess up (by being complex and flexible). With great power comes great need for training. Beware those who ‘know just enough to be dangerous’\n
• #13: How many lemons are there?\nWhy are there so many?\nThe rise of the ‘site rescue’ job\nThis is bad for Drupal’s reputation\n\n - Lack of experts\n - new field\n - learning curve\n - Difficulty of field is underappreciated (ie you wouldn’t treat something ‘difficult’ like surgery the same way) The easiness of using drupal or basic site building also stands in confusing contrast to the difficulty of custom application development in drupal or excellent and advanced site building.\n - Rush jobs\n - Cheap jobs\n- Hard to assess Credentials\n - lack of certification\n - too complex for decision makers\n - Drupal has a completely transparent and inscrutable system for measuring dev quality\n- Drupal makes it easy to mess up (by being complex and flexible). With great power comes great need for training. Beware those who ‘know just enough to be dangerous’\n
• #14: How many lemons are there?\nWhy are there so many?\nThe rise of the ‘site rescue’ job\nThis is bad for Drupal’s reputation\n\n - Lack of experts\n - new field\n - learning curve\n - Difficulty of field is underappreciated (ie you wouldn’t treat something ‘difficult’ like surgery the same way) The easiness of using drupal or basic site building also stands in confusing contrast to the difficulty of custom application development in drupal or excellent and advanced site building.\n - Rush jobs\n - Cheap jobs\n- Hard to assess Credentials\n - lack of certification\n - too complex for decision makers\n - Drupal has a completely transparent and inscrutable system for measuring dev quality\n- Drupal makes it easy to mess up (by being complex and flexible). With great power comes great need for training. Beware those who ‘know just enough to be dangerous’\n
• #15: How many lemons are there?\nWhy are there so many?\nThe rise of the ‘site rescue’ job\nThis is bad for Drupal’s reputation\n\n - Lack of experts\n - new field\n - learning curve\n - Difficulty of field is underappreciated (ie you wouldn’t treat something ‘difficult’ like surgery the same way) The easiness of using drupal or basic site building also stands in confusing contrast to the difficulty of custom application development in drupal or excellent and advanced site building.\n - Rush jobs\n - Cheap jobs\n- Hard to assess Credentials\n - lack of certification\n - too complex for decision makers\n - Drupal has a completely transparent and inscrutable system for measuring dev quality\n- Drupal makes it easy to mess up (by being complex and flexible). With great power comes great need for training. Beware those who ‘know just enough to be dangerous’\n
• #16: How many lemons are there?\nWhy are there so many?\nThe rise of the ‘site rescue’ job\nThis is bad for Drupal’s reputation\n\n - Lack of experts\n - new field\n - learning curve\n - Difficulty of field is underappreciated (ie you wouldn’t treat something ‘difficult’ like surgery the same way) The easiness of using drupal or basic site building also stands in confusing contrast to the difficulty of custom application development in drupal or excellent and advanced site building.\n - Rush jobs\n - Cheap jobs\n- Hard to assess Credentials\n - lack of certification\n - too complex for decision makers\n - Drupal has a completely transparent and inscrutable system for measuring dev quality\n- Drupal makes it easy to mess up (by being complex and flexible). With great power comes great need for training. Beware those who ‘know just enough to be dangerous’\n
• #17: How many lemons are there?\nWhy are there so many?\nThe rise of the ‘site rescue’ job\nThis is bad for Drupal’s reputation\n\n - Lack of experts\n - new field\n - learning curve\n - Difficulty of field is underappreciated (ie you wouldn’t treat something ‘difficult’ like surgery the same way) The easiness of using drupal or basic site building also stands in confusing contrast to the difficulty of custom application development in drupal or excellent and advanced site building.\n - Rush jobs\n - Cheap jobs\n- Hard to assess Credentials\n - lack of certification\n - too complex for decision makers\n - Drupal has a completely transparent and inscrutable system for measuring dev quality\n- Drupal makes it easy to mess up (by being complex and flexible). With great power comes great need for training. Beware those who ‘know just enough to be dangerous’\n
• #18: Let’s study this up close.\nWhat can we learn from Drupal lemons?\nI’ve been blessed with great opportunities throughout my life to learn from the worst\nPerhaps life has given me lemons\nBy studying worst practices we can desire and form best practices\nA lemon is always rushed and/or foolishly designed. On the cellular level it is starved for quality. The deeper you look the more you see problems.\nQuality means meeting professional standards throughout the process, not meeting specs by the end. Quality is holistic, is a mindset.\nBefore coming to the web I worked mainly in quality control, as a chemist. In pharmaceutical development quality control is taken extremely seriously, obviously its regulated by the FDA. They work to standards of quality at every stage in the process and the QC people are highly trained scientists. In software development quality control is often just testing the end result, sometimes outsourced. If time or budget gets short it can get skipped entirely. \n
• #19: Let’s study this up close.\nWhat can we learn from Drupal lemons?\nI’ve been blessed with great opportunities throughout my life to learn from the worst\nPerhaps life has given me lemons\nBy studying worst practices we can desire and form best practices\nA lemon is always rushed and/or foolishly designed. On the cellular level it is starved for quality. The deeper you look the more you see problems.\nQuality means meeting professional standards throughout the process, not meeting specs by the end. Quality is holistic, is a mindset.\nBefore coming to the web I worked mainly in quality control, as a chemist. In pharmaceutical development quality control is taken extremely seriously, obviously its regulated by the FDA. They work to standards of quality at every stage in the process and the QC people are highly trained scientists. In software development quality control is often just testing the end result, sometimes outsourced. If time or budget gets short it can get skipped entirely. \n
• #20: Let’s study this up close.\nWhat can we learn from Drupal lemons?\nI’ve been blessed with great opportunities throughout my life to learn from the worst\nPerhaps life has given me lemons\nBy studying worst practices we can desire and form best practices\nA lemon is always rushed and/or foolishly designed. On the cellular level it is starved for quality. The deeper you look the more you see problems.\nQuality means meeting professional standards throughout the process, not meeting specs by the end. Quality is holistic, is a mindset.\nBefore coming to the web I worked mainly in quality control, as a chemist. In pharmaceutical development quality control is taken extremely seriously, obviously its regulated by the FDA. They work to standards of quality at every stage in the process and the QC people are highly trained scientists. In software development quality control is often just testing the end result, sometimes outsourced. If time or budget gets short it can get skipped entirely. \n
• #21: Let’s study this up close.\nWhat can we learn from Drupal lemons?\nI’ve been blessed with great opportunities throughout my life to learn from the worst\nPerhaps life has given me lemons\nBy studying worst practices we can desire and form best practices\nA lemon is always rushed and/or foolishly designed. On the cellular level it is starved for quality. The deeper you look the more you see problems.\nQuality means meeting professional standards throughout the process, not meeting specs by the end. Quality is holistic, is a mindset.\nBefore coming to the web I worked mainly in quality control, as a chemist. In pharmaceutical development quality control is taken extremely seriously, obviously its regulated by the FDA. They work to standards of quality at every stage in the process and the QC people are highly trained scientists. In software development quality control is often just testing the end result, sometimes outsourced. If time or budget gets short it can get skipped entirely. \n
• #22: Let’s study this up close.\nWhat can we learn from Drupal lemons?\nI’ve been blessed with great opportunities throughout my life to learn from the worst\nPerhaps life has given me lemons\nBy studying worst practices we can desire and form best practices\nA lemon is always rushed and/or foolishly designed. On the cellular level it is starved for quality. The deeper you look the more you see problems.\nQuality means meeting professional standards throughout the process, not meeting specs by the end. Quality is holistic, is a mindset.\nBefore coming to the web I worked mainly in quality control, as a chemist. In pharmaceutical development quality control is taken extremely seriously, obviously its regulated by the FDA. They work to standards of quality at every stage in the process and the QC people are highly trained scientists. In software development quality control is often just testing the end result, sometimes outsourced. If time or budget gets short it can get skipped entirely. \n
• #23: Let’s study this up close.\nWhat can we learn from Drupal lemons?\nI’ve been blessed with great opportunities throughout my life to learn from the worst\nPerhaps life has given me lemons\nBy studying worst practices we can desire and form best practices\nA lemon is always rushed and/or foolishly designed. On the cellular level it is starved for quality. The deeper you look the more you see problems.\nQuality means meeting professional standards throughout the process, not meeting specs by the end. Quality is holistic, is a mindset.\nBefore coming to the web I worked mainly in quality control, as a chemist. In pharmaceutical development quality control is taken extremely seriously, obviously its regulated by the FDA. They work to standards of quality at every stage in the process and the QC people are highly trained scientists. In software development quality control is often just testing the end result, sometimes outsourced. If time or budget gets short it can get skipped entirely. \n
• #24: Let’s study this up close.\nWhat can we learn from Drupal lemons?\nI’ve been blessed with great opportunities throughout my life to learn from the worst\nPerhaps life has given me lemons\nBy studying worst practices we can desire and form best practices\nA lemon is always rushed and/or foolishly designed. On the cellular level it is starved for quality. The deeper you look the more you see problems.\nQuality means meeting professional standards throughout the process, not meeting specs by the end. Quality is holistic, is a mindset.\nBefore coming to the web I worked mainly in quality control, as a chemist. In pharmaceutical development quality control is taken extremely seriously, obviously its regulated by the FDA. They work to standards of quality at every stage in the process and the QC people are highly trained scientists. In software development quality control is often just testing the end result, sometimes outsourced. If time or budget gets short it can get skipped entirely. \n
• #25: Let’s study this up close.\nWhat can we learn from Drupal lemons?\nI’ve been blessed with great opportunities throughout my life to learn from the worst\nPerhaps life has given me lemons\nBy studying worst practices we can desire and form best practices\nA lemon is always rushed and/or foolishly designed. On the cellular level it is starved for quality. The deeper you look the more you see problems.\nQuality means meeting professional standards throughout the process, not meeting specs by the end. Quality is holistic, is a mindset.\nBefore coming to the web I worked mainly in quality control, as a chemist. In pharmaceutical development quality control is taken extremely seriously, obviously its regulated by the FDA. They work to standards of quality at every stage in the process and the QC people are highly trained scientists. In software development quality control is often just testing the end result, sometimes outsourced. If time or budget gets short it can get skipped entirely. \n
• #26: Let’s study this up close.\nWhat can we learn from Drupal lemons?\nI’ve been blessed with great opportunities throughout my life to learn from the worst\nPerhaps life has given me lemons\nBy studying worst practices we can desire and form best practices\nA lemon is always rushed and/or foolishly designed. On the cellular level it is starved for quality. The deeper you look the more you see problems.\nQuality means meeting professional standards throughout the process, not meeting specs by the end. Quality is holistic, is a mindset.\nBefore coming to the web I worked mainly in quality control, as a chemist. In pharmaceutical development quality control is taken extremely seriously, obviously its regulated by the FDA. They work to standards of quality at every stage in the process and the QC people are highly trained scientists. In software development quality control is often just testing the end result, sometimes outsourced. If time or budget gets short it can get skipped entirely. \n
• #27: the ''slingshotter,'' the ''adventurer,'' the ''marshmallow,'' the ''nomad'' and the ''weaver''\nUsability Lemon (developers who do not develop for usability are not web developers, much as designers who do not work in HTML/CSS are not web designers)\nInfested Lemon (bug-laden)\nFanboy Lemon (lots of junky contrib modules)\nDesperado Lemon (PHP dev wrote lots of custom code instead of using key modules)\n\n
• #28: the ''slingshotter,'' the ''adventurer,'' the ''marshmallow,'' the ''nomad'' and the ''weaver''\nUsability Lemon (developers who do not develop for usability are not web developers, much as designers who do not work in HTML/CSS are not web designers)\nInfested Lemon (bug-laden)\nFanboy Lemon (lots of junky contrib modules)\nDesperado Lemon (PHP dev wrote lots of custom code instead of using key modules)\n\n
• #29: the ''slingshotter,'' the ''adventurer,'' the ''marshmallow,'' the ''nomad'' and the ''weaver''\nUsability Lemon (developers who do not develop for usability are not web developers, much as designers who do not work in HTML/CSS are not web designers)\nInfested Lemon (bug-laden)\nFanboy Lemon (lots of junky contrib modules)\nDesperado Lemon (PHP dev wrote lots of custom code instead of using key modules)\n\n
• #30: the ''slingshotter,'' the ''adventurer,'' the ''marshmallow,'' the ''nomad'' and the ''weaver''\nUsability Lemon (developers who do not develop for usability are not web developers, much as designers who do not work in HTML/CSS are not web designers)\nInfested Lemon (bug-laden)\nFanboy Lemon (lots of junky contrib modules)\nDesperado Lemon (PHP dev wrote lots of custom code instead of using key modules)\n\n
• #31: the ''slingshotter,'' the ''adventurer,'' the ''marshmallow,'' the ''nomad'' and the ''weaver''\nUsability Lemon (developers who do not develop for usability are not web developers, much as designers who do not work in HTML/CSS are not web designers)\nInfested Lemon (bug-laden)\nFanboy Lemon (lots of junky contrib modules)\nDesperado Lemon (PHP dev wrote lots of custom code instead of using key modules)\n\n
• #32: Symptoms can be misleading. They could come from any or multiple layers of the stack\n \n
• #33: Symptoms can be misleading. They could come from any or multiple layers of the stack\n \n
• #34: Symptoms can be misleading. They could come from any or multiple layers of the stack\n \n
• #35: Symptoms can be misleading. They could come from any or multiple layers of the stack\n \n
• #36: Symptoms can be misleading. They could come from any or multiple layers of the stack\n \n
• #37: Symptoms can be misleading. They could come from any or multiple layers of the stack\n \n
• #38: Symptoms can be misleading. They could come from any or multiple layers of the stack\n \n
• #39: Symptoms can be misleading. They could come from any or multiple layers of the stack\n \n
• #40: Symptoms can be misleading. They could come from any or multiple layers of the stack\n \n
• #41: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #42: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #43: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #44: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #45: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #46: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #47: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #48: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #49: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #50: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #51: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #52: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #53: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #54: Warning signs...\n\nIgnoring the chain of command:\n inappropriate use of JS or CSS to deal with markup or logic-level problems (this indicates short-sighted or critically under-experienced web developers)\n the last two indicate developers who either don’t know Drupal well or don’t respect the integrity of the CMS or do not care about the future of the site (fixed budget/fixed specs much?)\n \n\n
• #55: Not every problem site is a lemon\n\nStaff usability (need a manual?!) problems are a bigger indication than public usability (closer to the structural)\n\nProblems that are mainly coming from CSS, JS, or server-side can cause bad symptoms but are easier to isolate and fix\n\nProblems may be coming from mostly just one place: a bad module for example\n\nA true lemon will have deep structural problems that have infected the code, configuration and content\n
• #56: Not every problem site is a lemon\n\nStaff usability (need a manual?!) problems are a bigger indication than public usability (closer to the structural)\n\nProblems that are mainly coming from CSS, JS, or server-side can cause bad symptoms but are easier to isolate and fix\n\nProblems may be coming from mostly just one place: a bad module for example\n\nA true lemon will have deep structural problems that have infected the code, configuration and content\n
• #57: Not every problem site is a lemon\n\nStaff usability (need a manual?!) problems are a bigger indication than public usability (closer to the structural)\n\nProblems that are mainly coming from CSS, JS, or server-side can cause bad symptoms but are easier to isolate and fix\n\nProblems may be coming from mostly just one place: a bad module for example\n\nA true lemon will have deep structural problems that have infected the code, configuration and content\n
• #58: Not every problem site is a lemon\n\nStaff usability (need a manual?!) problems are a bigger indication than public usability (closer to the structural)\n\nProblems that are mainly coming from CSS, JS, or server-side can cause bad symptoms but are easier to isolate and fix\n\nProblems may be coming from mostly just one place: a bad module for example\n\nA true lemon will have deep structural problems that have infected the code, configuration and content\n
• #59: Not every problem site is a lemon\n\nStaff usability (need a manual?!) problems are a bigger indication than public usability (closer to the structural)\n\nProblems that are mainly coming from CSS, JS, or server-side can cause bad symptoms but are easier to isolate and fix\n\nProblems may be coming from mostly just one place: a bad module for example\n\nA true lemon will have deep structural problems that have infected the code, configuration and content\n
• #60: Indicators and contraindicators are easy, but coming to a conclusion can be more difficult.\nDiagnosis is not easy and cannot usually be done ‘at a glance’ (or without a contract) except in the most extreme cases\n\nLack of adherence to semantic sense\nAsk for an honest opinion about your site and the level of your devs, ie in person (i’ve often had potentially useful observations that i would not feel comfortable sharing via email, conference call, or in situations that could politically threaten my status as a consultant)\n
• #61: Indicators and contraindicators are easy, but coming to a conclusion can be more difficult.\nDiagnosis is not easy and cannot usually be done ‘at a glance’ (or without a contract) except in the most extreme cases\n\nLack of adherence to semantic sense\nAsk for an honest opinion about your site and the level of your devs, ie in person (i’ve often had potentially useful observations that i would not feel comfortable sharing via email, conference call, or in situations that could politically threaten my status as a consultant)\n
• #62: Indicators and contraindicators are easy, but coming to a conclusion can be more difficult.\nDiagnosis is not easy and cannot usually be done ‘at a glance’ (or without a contract) except in the most extreme cases\n\nLack of adherence to semantic sense\nAsk for an honest opinion about your site and the level of your devs, ie in person (i’ve often had potentially useful observations that i would not feel comfortable sharing via email, conference call, or in situations that could politically threaten my status as a consultant)\n
• #63: Indicators and contraindicators are easy, but coming to a conclusion can be more difficult.\nDiagnosis is not easy and cannot usually be done ‘at a glance’ (or without a contract) except in the most extreme cases\n\nLack of adherence to semantic sense\nAsk for an honest opinion about your site and the level of your devs, ie in person (i’ve often had potentially useful observations that i would not feel comfortable sharing via email, conference call, or in situations that could politically threaten my status as a consultant)\n
• #64: Indicators and contraindicators are easy, but coming to a conclusion can be more difficult.\nDiagnosis is not easy and cannot usually be done ‘at a glance’ (or without a contract) except in the most extreme cases\n\nLack of adherence to semantic sense\nAsk for an honest opinion about your site and the level of your devs, ie in person (i’ve often had potentially useful observations that i would not feel comfortable sharing via email, conference call, or in situations that could politically threaten my status as a consultant)\n
• #65: Indicators and contraindicators are easy, but coming to a conclusion can be more difficult.\nDiagnosis is not easy and cannot usually be done ‘at a glance’ (or without a contract) except in the most extreme cases\n\nLack of adherence to semantic sense\nAsk for an honest opinion about your site and the level of your devs, ie in person (i’ve often had potentially useful observations that i would not feel comfortable sharing via email, conference call, or in situations that could politically threaten my status as a consultant)\n
• #66: A site can meet spec and have no serious bugs and still be a lemon.\nStaff may feel that all sites or all drupal sites have the kinds of frustrations they have, and devs may persist that feeling of ‘normal’ problems and even villify the software.\nThe lack of ability to easily expand and change the site, enormous difficulty upgrading the site, bug regressions, the need for a staff handbook, the need for excessive end-user help text, and site slowness are warning signs of a lemon in disguise.\nOften the seriousness of the problem is never known or is not acknowledged as true if diagnosed. These organizations may take it as a matter of course that you throw out crappy sites after a few years and then build a new crappy site and not see this as a problem. Experiencing the alternative will shed light on the problem.\n
• #67: A site can meet spec and have no serious bugs and still be a lemon.\nStaff may feel that all sites or all drupal sites have the kinds of frustrations they have, and devs may persist that feeling of ‘normal’ problems and even villify the software.\nThe lack of ability to easily expand and change the site, enormous difficulty upgrading the site, bug regressions, the need for a staff handbook, the need for excessive end-user help text, and site slowness are warning signs of a lemon in disguise.\nOften the seriousness of the problem is never known or is not acknowledged as true if diagnosed. These organizations may take it as a matter of course that you throw out crappy sites after a few years and then build a new crappy site and not see this as a problem. Experiencing the alternative will shed light on the problem.\n
• #68: A site can meet spec and have no serious bugs and still be a lemon.\nStaff may feel that all sites or all drupal sites have the kinds of frustrations they have, and devs may persist that feeling of ‘normal’ problems and even villify the software.\nThe lack of ability to easily expand and change the site, enormous difficulty upgrading the site, bug regressions, the need for a staff handbook, the need for excessive end-user help text, and site slowness are warning signs of a lemon in disguise.\nOften the seriousness of the problem is never known or is not acknowledged as true if diagnosed. These organizations may take it as a matter of course that you throw out crappy sites after a few years and then build a new crappy site and not see this as a problem. Experiencing the alternative will shed light on the problem.\n
• #69: A site can meet spec and have no serious bugs and still be a lemon.\nStaff may feel that all sites or all drupal sites have the kinds of frustrations they have, and devs may persist that feeling of ‘normal’ problems and even villify the software.\nThe lack of ability to easily expand and change the site, enormous difficulty upgrading the site, bug regressions, the need for a staff handbook, the need for excessive end-user help text, and site slowness are warning signs of a lemon in disguise.\nOften the seriousness of the problem is never known or is not acknowledged as true if diagnosed. These organizations may take it as a matter of course that you throw out crappy sites after a few years and then build a new crappy site and not see this as a problem. Experiencing the alternative will shed light on the problem.\n
• #70: A site can meet spec and have no serious bugs and still be a lemon.\nStaff may feel that all sites or all drupal sites have the kinds of frustrations they have, and devs may persist that feeling of ‘normal’ problems and even villify the software.\nThe lack of ability to easily expand and change the site, enormous difficulty upgrading the site, bug regressions, the need for a staff handbook, the need for excessive end-user help text, and site slowness are warning signs of a lemon in disguise.\nOften the seriousness of the problem is never known or is not acknowledged as true if diagnosed. These organizations may take it as a matter of course that you throw out crappy sites after a few years and then build a new crappy site and not see this as a problem. Experiencing the alternative will shed light on the problem.\n
• #71: some lemons are unusual. these are the grotesque distorted results of organizational politics rather than technical failures.\nintegrating with other software in strange and difficult ways based on vendor relationships without regard for technical concerns\nan unnecessary convoluted mediawiki integration to justify previous expenses\ncomplex unnecessary video conversion/hosting system\na separate cms creates the blocks?\nyou can’t do basic drupal tasks?\nit’s drupal static?!\n
• #72: some lemons are unusual. these are the grotesque distorted results of organizational politics rather than technical failures.\nintegrating with other software in strange and difficult ways based on vendor relationships without regard for technical concerns\nan unnecessary convoluted mediawiki integration to justify previous expenses\ncomplex unnecessary video conversion/hosting system\na separate cms creates the blocks?\nyou can’t do basic drupal tasks?\nit’s drupal static?!\n
• #73: some lemons are unusual. these are the grotesque distorted results of organizational politics rather than technical failures.\nintegrating with other software in strange and difficult ways based on vendor relationships without regard for technical concerns\nan unnecessary convoluted mediawiki integration to justify previous expenses\ncomplex unnecessary video conversion/hosting system\na separate cms creates the blocks?\nyou can’t do basic drupal tasks?\nit’s drupal static?!\n
• #74: AKA birth of a lemon / how to make sure you get a lemon\nRisk Factors...\nSubcontracting\n Designers as developers\nInternal staff with little Drupal background\nNot doing your homework\nOrganic site architecting\nToo many cooks, too little chefs\nUnderpaying (if you think experts are expensive, wait until you hire an amateur)\n you get what you pay for (compare to other fields, some things you don’t want to cheap out on)\nMistaking an amateur for an expert = understandable \nTreating an expert like an amateur (ie not taking good advice you paid for) = foolish\n\n
• #75: AKA birth of a lemon / how to make sure you get a lemon\nRisk Factors...\nSubcontracting\n Designers as developers\nInternal staff with little Drupal background\nNot doing your homework\nOrganic site architecting\nToo many cooks, too little chefs\nUnderpaying (if you think experts are expensive, wait until you hire an amateur)\n you get what you pay for (compare to other fields, some things you don’t want to cheap out on)\nMistaking an amateur for an expert = understandable \nTreating an expert like an amateur (ie not taking good advice you paid for) = foolish\n\n
• #76: AKA birth of a lemon / how to make sure you get a lemon\nRisk Factors...\nSubcontracting\n Designers as developers\nInternal staff with little Drupal background\nNot doing your homework\nOrganic site architecting\nToo many cooks, too little chefs\nUnderpaying (if you think experts are expensive, wait until you hire an amateur)\n you get what you pay for (compare to other fields, some things you don’t want to cheap out on)\nMistaking an amateur for an expert = understandable \nTreating an expert like an amateur (ie not taking good advice you paid for) = foolish\n\n
• #77: AKA birth of a lemon / how to make sure you get a lemon\nRisk Factors...\nSubcontracting\n Designers as developers\nInternal staff with little Drupal background\nNot doing your homework\nOrganic site architecting\nToo many cooks, too little chefs\nUnderpaying (if you think experts are expensive, wait until you hire an amateur)\n you get what you pay for (compare to other fields, some things you don’t want to cheap out on)\nMistaking an amateur for an expert = understandable \nTreating an expert like an amateur (ie not taking good advice you paid for) = foolish\n\n
• #78: AKA birth of a lemon / how to make sure you get a lemon\nRisk Factors...\nSubcontracting\n Designers as developers\nInternal staff with little Drupal background\nNot doing your homework\nOrganic site architecting\nToo many cooks, too little chefs\nUnderpaying (if you think experts are expensive, wait until you hire an amateur)\n you get what you pay for (compare to other fields, some things you don’t want to cheap out on)\nMistaking an amateur for an expert = understandable \nTreating an expert like an amateur (ie not taking good advice you paid for) = foolish\n\n
• #79: AKA birth of a lemon / how to make sure you get a lemon\nRisk Factors...\nSubcontracting\n Designers as developers\nInternal staff with little Drupal background\nNot doing your homework\nOrganic site architecting\nToo many cooks, too little chefs\nUnderpaying (if you think experts are expensive, wait until you hire an amateur)\n you get what you pay for (compare to other fields, some things you don’t want to cheap out on)\nMistaking an amateur for an expert = understandable \nTreating an expert like an amateur (ie not taking good advice you paid for) = foolish\n\n
• #80: An ounce of prevention...\n\nPrevention is the main point of this talk. I want you to understand what a lemon is, how hard it is to fix, and think about how to adjust your process and get the help you need (whether you’re a dev or a decision maker) to ensure you don’t create them. You may need training, a longer timeline, a consultant, less features, a change in philosophy, etc.\n\nGet good advice as early as possible. Before you write the RFP if possible! The later in the process the problems are dealt with the more expensive it will be. ‘You can hire me now... or you can hire me to fix it later...’\n\nA sterile growing environment (adequate time, staff, sleep, planning, thoughtfulness). Do you take time to think or are you rushed to put out fires? A series of crises does not make for good results, and is not an inevitable way we have to work.\n\nHiring\nAn expert lead gardener who is heeded\nVetting drupal developers (open source)\n\nContinual pest control (not wait for an infestation and then bomb the greenhouse)\n\nPeer review\n\nAn effective ticketing, development, version control systems and surrounding process\n\nThinking long term (a Drupal site should be always ready to adapt and grow with your organization and not treated as a one-time project that will probably be thrown out like the site it’s replacing)\n\n\n
• #81: An ounce of prevention...\n\nPrevention is the main point of this talk. I want you to understand what a lemon is, how hard it is to fix, and think about how to adjust your process and get the help you need (whether you’re a dev or a decision maker) to ensure you don’t create them. You may need training, a longer timeline, a consultant, less features, a change in philosophy, etc.\n\nGet good advice as early as possible. Before you write the RFP if possible! The later in the process the problems are dealt with the more expensive it will be. ‘You can hire me now... or you can hire me to fix it later...’\n\nA sterile growing environment (adequate time, staff, sleep, planning, thoughtfulness). Do you take time to think or are you rushed to put out fires? A series of crises does not make for good results, and is not an inevitable way we have to work.\n\nHiring\nAn expert lead gardener who is heeded\nVetting drupal developers (open source)\n\nContinual pest control (not wait for an infestation and then bomb the greenhouse)\n\nPeer review\n\nAn effective ticketing, development, version control systems and surrounding process\n\nThinking long term (a Drupal site should be always ready to adapt and grow with your organization and not treated as a one-time project that will probably be thrown out like the site it’s replacing)\n\n\n
• #82: An ounce of prevention...\n\nPrevention is the main point of this talk. I want you to understand what a lemon is, how hard it is to fix, and think about how to adjust your process and get the help you need (whether you’re a dev or a decision maker) to ensure you don’t create them. You may need training, a longer timeline, a consultant, less features, a change in philosophy, etc.\n\nGet good advice as early as possible. Before you write the RFP if possible! The later in the process the problems are dealt with the more expensive it will be. ‘You can hire me now... or you can hire me to fix it later...’\n\nA sterile growing environment (adequate time, staff, sleep, planning, thoughtfulness). Do you take time to think or are you rushed to put out fires? A series of crises does not make for good results, and is not an inevitable way we have to work.\n\nHiring\nAn expert lead gardener who is heeded\nVetting drupal developers (open source)\n\nContinual pest control (not wait for an infestation and then bomb the greenhouse)\n\nPeer review\n\nAn effective ticketing, development, version control systems and surrounding process\n\nThinking long term (a Drupal site should be always ready to adapt and grow with your organization and not treated as a one-time project that will probably be thrown out like the site it’s replacing)\n\n\n
• #83: An ounce of prevention...\n\nPrevention is the main point of this talk. I want you to understand what a lemon is, how hard it is to fix, and think about how to adjust your process and get the help you need (whether you’re a dev or a decision maker) to ensure you don’t create them. You may need training, a longer timeline, a consultant, less features, a change in philosophy, etc.\n\nGet good advice as early as possible. Before you write the RFP if possible! The later in the process the problems are dealt with the more expensive it will be. ‘You can hire me now... or you can hire me to fix it later...’\n\nA sterile growing environment (adequate time, staff, sleep, planning, thoughtfulness). Do you take time to think or are you rushed to put out fires? A series of crises does not make for good results, and is not an inevitable way we have to work.\n\nHiring\nAn expert lead gardener who is heeded\nVetting drupal developers (open source)\n\nContinual pest control (not wait for an infestation and then bomb the greenhouse)\n\nPeer review\n\nAn effective ticketing, development, version control systems and surrounding process\n\nThinking long term (a Drupal site should be always ready to adapt and grow with your organization and not treated as a one-time project that will probably be thrown out like the site it’s replacing)\n\n\n
• #84: An ounce of prevention...\n\nPrevention is the main point of this talk. I want you to understand what a lemon is, how hard it is to fix, and think about how to adjust your process and get the help you need (whether you’re a dev or a decision maker) to ensure you don’t create them. You may need training, a longer timeline, a consultant, less features, a change in philosophy, etc.\n\nGet good advice as early as possible. Before you write the RFP if possible! The later in the process the problems are dealt with the more expensive it will be. ‘You can hire me now... or you can hire me to fix it later...’\n\nA sterile growing environment (adequate time, staff, sleep, planning, thoughtfulness). Do you take time to think or are you rushed to put out fires? A series of crises does not make for good results, and is not an inevitable way we have to work.\n\nHiring\nAn expert lead gardener who is heeded\nVetting drupal developers (open source)\n\nContinual pest control (not wait for an infestation and then bomb the greenhouse)\n\nPeer review\n\nAn effective ticketing, development, version control systems and surrounding process\n\nThinking long term (a Drupal site should be always ready to adapt and grow with your organization and not treated as a one-time project that will probably be thrown out like the site it’s replacing)\n\n\n
• #85: An ounce of prevention...\n\nPrevention is the main point of this talk. I want you to understand what a lemon is, how hard it is to fix, and think about how to adjust your process and get the help you need (whether you’re a dev or a decision maker) to ensure you don’t create them. You may need training, a longer timeline, a consultant, less features, a change in philosophy, etc.\n\nGet good advice as early as possible. Before you write the RFP if possible! The later in the process the problems are dealt with the more expensive it will be. ‘You can hire me now... or you can hire me to fix it later...’\n\nA sterile growing environment (adequate time, staff, sleep, planning, thoughtfulness). Do you take time to think or are you rushed to put out fires? A series of crises does not make for good results, and is not an inevitable way we have to work.\n\nHiring\nAn expert lead gardener who is heeded\nVetting drupal developers (open source)\n\nContinual pest control (not wait for an infestation and then bomb the greenhouse)\n\nPeer review\n\nAn effective ticketing, development, version control systems and surrounding process\n\nThinking long term (a Drupal site should be always ready to adapt and grow with your organization and not treated as a one-time project that will probably be thrown out like the site it’s replacing)\n\n\n
• #86: An ounce of prevention...\n\nPrevention is the main point of this talk. I want you to understand what a lemon is, how hard it is to fix, and think about how to adjust your process and get the help you need (whether you’re a dev or a decision maker) to ensure you don’t create them. You may need training, a longer timeline, a consultant, less features, a change in philosophy, etc.\n\nGet good advice as early as possible. Before you write the RFP if possible! The later in the process the problems are dealt with the more expensive it will be. ‘You can hire me now... or you can hire me to fix it later...’\n\nA sterile growing environment (adequate time, staff, sleep, planning, thoughtfulness). Do you take time to think or are you rushed to put out fires? A series of crises does not make for good results, and is not an inevitable way we have to work.\n\nHiring\nAn expert lead gardener who is heeded\nVetting drupal developers (open source)\n\nContinual pest control (not wait for an infestation and then bomb the greenhouse)\n\nPeer review\n\nAn effective ticketing, development, version control systems and surrounding process\n\nThinking long term (a Drupal site should be always ready to adapt and grow with your organization and not treated as a one-time project that will probably be thrown out like the site it’s replacing)\n\n\n
• #87: Incurable / Systemic\nThe definition of a lemon (car) is that you need a replacement not another trip to the mechanic.\nWith a website you often need to at the minimum salvage parts (content, users, design), which means that you may be in a position in which the replacement may be harder (more expensive) than having done it right originally.\n\nMany lemon owners opt to throw good money after bad, perhaps to save face or for political reasons\nThe bigger lemon (is your boss the lemon??): http://www.flickr.com/photos/lodigs/89161130/\nSometimes the organizations that have the lemon sites are lemons themselves - the website project may not be the only thing that was mismanaged. Working with these clients you may find that the problem is not technical, and that any project will be doomed. This takes the fun out of the lemonade challenge (when hiring for a site rescue you’ll want to convince a potential vendor that the organization has learned from the past mistake - many good devs will avoid these projects) We have seen this kind of lemon eventually made moot when either higher ups scrap the entire project, or the organization is sold or goes under.\nThe worst offending sites rarely are granted proper treatment. Most sites that ask for a site audit are actually in pretty good shape. We’ve been brought in for training staff to use their lemon when a good site would require minimal training. Because most lemons are never cured, the most important takeaway is prevention.\n
• #88: Incurable / Systemic\nThe definition of a lemon (car) is that you need a replacement not another trip to the mechanic.\nWith a website you often need to at the minimum salvage parts (content, users, design), which means that you may be in a position in which the replacement may be harder (more expensive) than having done it right originally.\n\nMany lemon owners opt to throw good money after bad, perhaps to save face or for political reasons\nThe bigger lemon (is your boss the lemon??): http://www.flickr.com/photos/lodigs/89161130/\nSometimes the organizations that have the lemon sites are lemons themselves - the website project may not be the only thing that was mismanaged. Working with these clients you may find that the problem is not technical, and that any project will be doomed. This takes the fun out of the lemonade challenge (when hiring for a site rescue you’ll want to convince a potential vendor that the organization has learned from the past mistake - many good devs will avoid these projects) We have seen this kind of lemon eventually made moot when either higher ups scrap the entire project, or the organization is sold or goes under.\nThe worst offending sites rarely are granted proper treatment. Most sites that ask for a site audit are actually in pretty good shape. We’ve been brought in for training staff to use their lemon when a good site would require minimal training. Because most lemons are never cured, the most important takeaway is prevention.\n
• #89: Incurable / Systemic\nThe definition of a lemon (car) is that you need a replacement not another trip to the mechanic.\nWith a website you often need to at the minimum salvage parts (content, users, design), which means that you may be in a position in which the replacement may be harder (more expensive) than having done it right originally.\n\nMany lemon owners opt to throw good money after bad, perhaps to save face or for political reasons\nThe bigger lemon (is your boss the lemon??): http://www.flickr.com/photos/lodigs/89161130/\nSometimes the organizations that have the lemon sites are lemons themselves - the website project may not be the only thing that was mismanaged. Working with these clients you may find that the problem is not technical, and that any project will be doomed. This takes the fun out of the lemonade challenge (when hiring for a site rescue you’ll want to convince a potential vendor that the organization has learned from the past mistake - many good devs will avoid these projects) We have seen this kind of lemon eventually made moot when either higher ups scrap the entire project, or the organization is sold or goes under.\nThe worst offending sites rarely are granted proper treatment. Most sites that ask for a site audit are actually in pretty good shape. We’ve been brought in for training staff to use their lemon when a good site would require minimal training. Because most lemons are never cured, the most important takeaway is prevention.\n
• #90: Incurable / Systemic\nThe definition of a lemon (car) is that you need a replacement not another trip to the mechanic.\nWith a website you often need to at the minimum salvage parts (content, users, design), which means that you may be in a position in which the replacement may be harder (more expensive) than having done it right originally.\n\nMany lemon owners opt to throw good money after bad, perhaps to save face or for political reasons\nThe bigger lemon (is your boss the lemon??): http://www.flickr.com/photos/lodigs/89161130/\nSometimes the organizations that have the lemon sites are lemons themselves - the website project may not be the only thing that was mismanaged. Working with these clients you may find that the problem is not technical, and that any project will be doomed. This takes the fun out of the lemonade challenge (when hiring for a site rescue you’ll want to convince a potential vendor that the organization has learned from the past mistake - many good devs will avoid these projects) We have seen this kind of lemon eventually made moot when either higher ups scrap the entire project, or the organization is sold or goes under.\nThe worst offending sites rarely are granted proper treatment. Most sites that ask for a site audit are actually in pretty good shape. We’ve been brought in for training staff to use their lemon when a good site would require minimal training. Because most lemons are never cured, the most important takeaway is prevention.\n
• #91: Incurable / Systemic\nThe definition of a lemon (car) is that you need a replacement not another trip to the mechanic.\nWith a website you often need to at the minimum salvage parts (content, users, design), which means that you may be in a position in which the replacement may be harder (more expensive) than having done it right originally.\n\nMany lemon owners opt to throw good money after bad, perhaps to save face or for political reasons\nThe bigger lemon (is your boss the lemon??): http://www.flickr.com/photos/lodigs/89161130/\nSometimes the organizations that have the lemon sites are lemons themselves - the website project may not be the only thing that was mismanaged. Working with these clients you may find that the problem is not technical, and that any project will be doomed. This takes the fun out of the lemonade challenge (when hiring for a site rescue you’ll want to convince a potential vendor that the organization has learned from the past mistake - many good devs will avoid these projects) We have seen this kind of lemon eventually made moot when either higher ups scrap the entire project, or the organization is sold or goes under.\nThe worst offending sites rarely are granted proper treatment. Most sites that ask for a site audit are actually in pretty good shape. We’ve been brought in for training staff to use their lemon when a good site would require minimal training. Because most lemons are never cured, the most important takeaway is prevention.\n
• #92: Incurable / Systemic\nThe definition of a lemon (car) is that you need a replacement not another trip to the mechanic.\nWith a website you often need to at the minimum salvage parts (content, users, design), which means that you may be in a position in which the replacement may be harder (more expensive) than having done it right originally.\n\nMany lemon owners opt to throw good money after bad, perhaps to save face or for political reasons\nThe bigger lemon (is your boss the lemon??): http://www.flickr.com/photos/lodigs/89161130/\nSometimes the organizations that have the lemon sites are lemons themselves - the website project may not be the only thing that was mismanaged. Working with these clients you may find that the problem is not technical, and that any project will be doomed. This takes the fun out of the lemonade challenge (when hiring for a site rescue you’ll want to convince a potential vendor that the organization has learned from the past mistake - many good devs will avoid these projects) We have seen this kind of lemon eventually made moot when either higher ups scrap the entire project, or the organization is sold or goes under.\nThe worst offending sites rarely are granted proper treatment. Most sites that ask for a site audit are actually in pretty good shape. We’ve been brought in for training staff to use their lemon when a good site would require minimal training. Because most lemons are never cured, the most important takeaway is prevention.\n
• #93: The ‘Works’ = version upgrade plus structural overhaul, possibly including redesign or design cleanup. If this does not include a redesign or new features, it requires minimal management, client attention, or paperwork (minimizing these things will lower cost and this project can be done by folks who do not thrive on conference calls and email chains. This person needs to concentrate). It may require a hero. It is unglamorous work that will likely be underappreciated.\nSome common techniques:\nContent type simplification\nPHP format extraction\nTemplate extermination\nDatabase decrudifying\nThe cure is to delete mercilessly on all levels, not to add another layer of bandages\nThe need to save content, users, and to minimize or avoid any downtime makes the treatment difficult\n
• #94: The ‘Works’ = version upgrade plus structural overhaul, possibly including redesign or design cleanup. If this does not include a redesign or new features, it requires minimal management, client attention, or paperwork (minimizing these things will lower cost and this project can be done by folks who do not thrive on conference calls and email chains. This person needs to concentrate). It may require a hero. It is unglamorous work that will likely be underappreciated.\nSome common techniques:\nContent type simplification\nPHP format extraction\nTemplate extermination\nDatabase decrudifying\nThe cure is to delete mercilessly on all levels, not to add another layer of bandages\nThe need to save content, users, and to minimize or avoid any downtime makes the treatment difficult\n
• #95: The ‘Works’ = version upgrade plus structural overhaul, possibly including redesign or design cleanup. If this does not include a redesign or new features, it requires minimal management, client attention, or paperwork (minimizing these things will lower cost and this project can be done by folks who do not thrive on conference calls and email chains. This person needs to concentrate). It may require a hero. It is unglamorous work that will likely be underappreciated.\nSome common techniques:\nContent type simplification\nPHP format extraction\nTemplate extermination\nDatabase decrudifying\nThe cure is to delete mercilessly on all levels, not to add another layer of bandages\nThe need to save content, users, and to minimize or avoid any downtime makes the treatment difficult\n
• #96: The ‘Works’ = version upgrade plus structural overhaul, possibly including redesign or design cleanup. If this does not include a redesign or new features, it requires minimal management, client attention, or paperwork (minimizing these things will lower cost and this project can be done by folks who do not thrive on conference calls and email chains. This person needs to concentrate). It may require a hero. It is unglamorous work that will likely be underappreciated.\nSome common techniques:\nContent type simplification\nPHP format extraction\nTemplate extermination\nDatabase decrudifying\nThe cure is to delete mercilessly on all levels, not to add another layer of bandages\nThe need to save content, users, and to minimize or avoid any downtime makes the treatment difficult\n
• #97: The ‘Works’ = version upgrade plus structural overhaul, possibly including redesign or design cleanup. If this does not include a redesign or new features, it requires minimal management, client attention, or paperwork (minimizing these things will lower cost and this project can be done by folks who do not thrive on conference calls and email chains. This person needs to concentrate). It may require a hero. It is unglamorous work that will likely be underappreciated.\nSome common techniques:\nContent type simplification\nPHP format extraction\nTemplate extermination\nDatabase decrudifying\nThe cure is to delete mercilessly on all levels, not to add another layer of bandages\nThe need to save content, users, and to minimize or avoid any downtime makes the treatment difficult\n
• #98: The ‘Works’ = version upgrade plus structural overhaul, possibly including redesign or design cleanup. If this does not include a redesign or new features, it requires minimal management, client attention, or paperwork (minimizing these things will lower cost and this project can be done by folks who do not thrive on conference calls and email chains. This person needs to concentrate). It may require a hero. It is unglamorous work that will likely be underappreciated.\nSome common techniques:\nContent type simplification\nPHP format extraction\nTemplate extermination\nDatabase decrudifying\nThe cure is to delete mercilessly on all levels, not to add another layer of bandages\nThe need to save content, users, and to minimize or avoid any downtime makes the treatment difficult\n
• #99: The ‘Works’ = version upgrade plus structural overhaul, possibly including redesign or design cleanup. If this does not include a redesign or new features, it requires minimal management, client attention, or paperwork (minimizing these things will lower cost and this project can be done by folks who do not thrive on conference calls and email chains. This person needs to concentrate). It may require a hero. It is unglamorous work that will likely be underappreciated.\nSome common techniques:\nContent type simplification\nPHP format extraction\nTemplate extermination\nDatabase decrudifying\nThe cure is to delete mercilessly on all levels, not to add another layer of bandages\nThe need to save content, users, and to minimize or avoid any downtime makes the treatment difficult\n
• #100: The ‘Works’ = version upgrade plus structural overhaul, possibly including redesign or design cleanup. If this does not include a redesign or new features, it requires minimal management, client attention, or paperwork (minimizing these things will lower cost and this project can be done by folks who do not thrive on conference calls and email chains. This person needs to concentrate). It may require a hero. It is unglamorous work that will likely be underappreciated.\nSome common techniques:\nContent type simplification\nPHP format extraction\nTemplate extermination\nDatabase decrudifying\nThe cure is to delete mercilessly on all levels, not to add another layer of bandages\nThe need to save content, users, and to minimize or avoid any downtime makes the treatment difficult\n
• #101: Seeking expert advice\nWho can benefit from a site audit?\nLow budget lemons: simplify, remove features, go lean\n
• #102: Seeking expert advice\nWho can benefit from a site audit?\nLow budget lemons: simplify, remove features, go lean\n
• #103: Seeking expert advice\nWho can benefit from a site audit?\nLow budget lemons: simplify, remove features, go lean\n
• #104: Seeking expert advice\nWho can benefit from a site audit?\nLow budget lemons: simplify, remove features, go lean\n