Showing posts with label continuous integration. Show all posts
Showing posts with label continuous integration. Show all posts

Wednesday, July 14, 2010

this was a rather good day DocBookWebsite'ing

Migrated all relevant web-sites to DocBook Website. Simple HTML from DocBook documents looks quite a little different and not so appealing. I can only recommend using DocBook Website.That's another good reason, why I want to spread the good word of DocBook in Berlin. Have a look at the block "my most exciting web-sites" in the right column here!
Update / 2010-07-15:
If goals are easy to achieve, you don't delay them for very long, you just do them. With DocBook Website things are easy to achieve, and I keep simplifying, improving, and renovating my web-site(s). I guess, the need to change will saturate rather sooner than later.
Hayek.name is now as short and as nice, as it has never been before.
BTW: Now I removed xmllint'ing my documents from my Makefile, as it kept spitting out weird messages. Alright, I agree, that sounds rather silly, but … I use nxml-mode, and that constantly validates my documents, so I assume, I am on the safe side.

The next step:
Continuous Integration. That means, each web-sites gets recompiled, as soon as its sources got modified. Pretty cool stuff, serious!
For now I am using the Unix batch command. Pretty neat as well, of course, but not as neat as Continuous Integration, that's for sure.

Monday, November 23, 2009

my new book: Tarek Ziadé: Expert Python Programming

This book is a litte like like Pragmatic Project Automation for the python community. This book isn't really, what I was searching for, but actually it is much, much better. It provides me with a serious level of considering how to make a software project using python a success.

I think, it's a big marketing mistake, to print on the cover and certainly also elsewhere, that this book is targeted towards people with a "sound background in Python programming". I actually think, people with a serious background in computer science (maybe beyond the BSc/BA level) and some knowledge of the specifics of, how python implements the usual more or less "modernistic" (i.e. starting with Simula 67) progamming language features, certainly will gain good profit of enjoying this book. Do yourself a favour and get both, the paper book and the PDF! So maybe you can print one or the other page, and put it on your fellow project managers' desks.

(To be continued ...)

A note to my mates: yes, I got the PDF, and I also got the PDF of the PragProg book.

using associative arrays in your code

How many lines of code does it take for your new piece of code, before you introduce an associative array?


How many lines of code does it take for your new piece of code, before you introduce a class?

Yes, I know, Bourne shell doesn't come with the concept of associative arrays, of course it also doesn't know classes or object orientation. Right, a simple 20 or 30 lines shell script for copying and renaming files may not have the need for associative arrays or classes. But if your script gets longer, pls rethink, whether Bourne shell is the right choice for your task, or whether you make really good use of ruby, perl, or python!

Your next steps may be writing unit testing and using continuous integration. It's not your customer, who should request it, it should be your serious professional style, your way to deliver proper services. If you are not familiar with the terms, look them up -- I provided you with proper links to interesting and informative articles.