If you're not using a framework, you're doing it wrong

I'm really enjoying learning Rails at the moment. One of the things that strikes me about it is how easily it meshes with my own ideas. This is what I would have written if I had the skill and the time. Suddenly a huge chunk of infrastructure code doesn't have to be written.

What Rails gives you is flexibility. Many people write their own libraries of code, or CMS systems from scratch, or use one of the major open source projects as a basis for their applications. Within the limited domain of these programs you can have pretty good productivity, but it's hard to adapt them to changing requirements without major rewrites or hacks. In Rails on the other hand, the infrastructure is cleanly separated from the application code. There is a lot less to change so refactoring is far cheaper.

For all but the simplest "Hello world" application I'd recommend using a good framework. It will have already solved your problems before you even knew they existed. Rails is my choice, but there are others.

I've joined a gym

Five weeks ago I decided to visit a gym for the first time. My local leisure centre has a 'kickstart' programme of five weekly appointments with an instructor to get you started. For someone like me who's never used a gym before it's a real help to have someone to guide you.

The idea of going to a gym never appealed to me before, but I'm actually rather enjoying it. The great thing that a gym has to offer is variety. Everything you need is all in one place. That helps to keep it from getting boring too. I don't do more than ten minutes or two sets on any one exercise.

No measureable results yet, but I definitely feel fitter, and I'm able to exercise harder now than I could when I started, and that's the measurement that counts.