Few people is capable to understand the meaning of working in teams. Among other things, on a team we need to set the proper communication channels. My last assignment as employee of a company was Software Architect for a set of projects for a new client on the company. I was in need to do research about the platform where we were working on and I don’t mean the third party pieces, such as language, application server and related stuff, I mean the enterprise application. It was poorly documented, so we need to harvest the code seeking for answers.

I’ve worked on FOSS for years. Currently I have two active projects pyxser and caffeine. Both of them requires a great effort to being completed. Take an overview on their development:

Support my country Chile after the Earthquake on 2010

The official site where is centralized all the information about how to help our country is located at ChileAyuda.

Kontact is my default PIM application. On its configuration we can setup a phone calling program, such as ekiga, skype and others, it just requires a small script, like the one bellow, which I have integrated with KPilot, so I can manage my contacts centered and synchronized.

Dear pyxser users, I’m pleased to announce that I’ve released pyxser-1.4.2r. The current ChangeLog for this release is as follows:

1.4.2r (2010.02.10):

        Daniel Molina Wegener <dmw at coder dot cl>
        * pyxser_collections.c: Added constraint checks for NULL
        pointers removing nested statements.
        * pyxser.c: Removed nested statements.
        * pyxser_tools.c: Added constratints checks for NULL pointers,
        removed nested statements and added strict checking for lists
        since it was crashing with an ambigous list definition that
        can not be handled by PyList_Check().
        * test-utf8.py: Added tests to determine if it continue
        crashing with module serialization.

        Thanks to pyxser users for their feedback.

Netiquette (RFC1855) is a set of standard rules on writing electronic mail. Many of those conventions appears to be lost in time, and bad practices on writing emails are more popular around the Internet. I agree with those rules, but I think that some additional stuff can be used to get more organized electronic mail. Here are some rules, some of them extracted from the netiquette used on mailing lists and Usenet.

One of my most recent projects is a Meta-Parser. The core requirement is to write a dynamic parser, which can be configured, allowing the user to setup certain patterns around the given input and extract those pattern tokens to being exposed to other layers of the main project. Surely this is a challenge, and interesting part of the global project. I’ve finished to work on this part of the project, it is implemented in C++ as the client requires it, and I’ve made a simple model based on the PAC architectural pattern.