Sure - I've used two of the three. Wordpress on my personal blog), and movable type as coeditor of ajaxian. Wordpress wins out for me for several reasons:
any crazy plugin you can think of you can find and install very easily for WP - the community is huge and helpful
while neither admin UI is really that great, wordpress' is a bit more intuitive then movable type's
six apart is trying to run a business, more power to them, but the WP team is trying to build the best open source blogging engine first, and make some money second. it shows
speed of development - the WP team is over hauling the admin interface to have live preview, adding true multi-user blogs, and other neat stuff with 1.6 - from what I've read in the community the MT platform has been relatively stagnant with the 3.x versions.
Are there any decent reviews of civ 4 around? I'd prefer something not on a mega-corporate game site like gamespot, because they are just way too annoying. Whatever happened to user-run games sites? I miss the old games domain...(sigh).
You have to write tests as you change features. Lets say you have a simple change, tweaking a short method to do something different. First you write a test for its exisiting functionality, make sure it passes. Then add a test for the new functionality, run it and watch it fail. Make your change and make the test pass. This would also be the point where you can do some refactoring or clean up, or extend the test to catch boundy conditions.
With legacy code, you just have to start writing tests with the code as you go, writing tests for functionality that you need to understand or review. If you try and take x number of weeks to write test cases, your doomed to fall behind and have obsolete tests when you are dumb.
Slashdot Mirror
anyways, thats my
- Rob Sanheim
Are there any decent reviews of civ 4 around? I'd prefer something not on a mega-corporate game site like gamespot, because they are just way too annoying. Whatever happened to user-run games sites? I miss the old games domain...(sigh).
You have to write tests as you change features. Lets say you have a simple change, tweaking a short method to do something different. First you write a test for its exisiting functionality, make sure it passes. Then add a test for the new functionality, run it and watch it fail. Make your change and make the test pass. This would also be the point where you can do some refactoring or clean up, or extend the test to catch boundy conditions.
1 177052/002-8698615-6720004?v=glance
With legacy code, you just have to start writing tests with the code as you go, writing tests for functionality that you need to understand or review. If you try and take x number of weeks to write test cases, your doomed to fall behind and have obsolete tests when you are dumb.
Also, see Working Effectively With Legacy Code by Michael Feathers --> http://www.amazon.com/exec/obidos/tg/detail/-/013