Is kitchen sink syndrome a risk for web products?

This belongs to the list of commonly and frequently asked questions, Is kitchen sink syndrome a risk for web products? As we know that kitchen sink syndrome is considered a risk under project management. Oops, Btw kitchen sink syndrome is unplanned changes to a project. Mainly referred to the changes at scope level and thus sometimes it is also known as Scope creep. Wikipedia offers more about it.

It is considered a risk because:-

  1. It often results in cost overrun.
  2. It can also result in a project team overrunning its schedule.

It may not be true for Web products as:-

  1. The Cost involved is very low.
  2. Time consumption is also very low, if proper open source classes are used.

I have personal experiences where kitchen sink syndrome was proven very profitable. On web we go with release early and release often. Even I remember which started like a normal directory and while development it because a community review center. It happens often due to unplanned and unmanaged actions but web products often enter this cycle as it is managed by a very small and very independent team. Spending time on document/planning sometimes doesn’t work (and is not needed too). Leaving it as an open debatable issue.

WordPress database error: [Got error 127 from storage Engine]

I know I am not blogging for last few days, got busy with new recruits. After almost an year (Last time it was when we hired (mass hiring) few programmers and Marketing guys from Army Institute of Management and other B-Schools) I revamped the whole Mentoring program. I am liking this mentorship program as it has the right blend of tech and non-tech dimension. I will post more about it.

Meanwhile I was getting this error
WordPress database error: [Got error 127 from storage Engine]
WordPress database error: [Got error 127 from storage Engine]
SELECT COUNT(comment_ID) FROM wp_comments Where Comment_approved =”Spam”

Error 127

Initially I thought it can be akismet related error and gave it a day. Today after a good 8 hour sleep I just did a search on Error 127 to find “Error 127 indicates a record has crashed”. When there is a crash you need to do a repair.

How to repair WordPress database error

If you are a non-techy guy (or want simpler solution),

  1. Go to cpanel
  2. MySql Databases
  3. See your database
  4. You will see a button named repair under your blog database, click on it and it will take care of it.

If you are a little techy,

  1. use the phpmyadmin
  2. In the main panel, you should see a list of your database tables. Check the boxes by the tables that need repair.
  3. At the bottom of the window just below the list of tables, there is a drop down menu. Choose “Repair Table”.

Even you can do it manually using REPAIR TABLE `wp_useronline` etc. I just did a search for similar error and saw many going through such phase. Hope this article helps.