+ Perl, Java, C, Python, Ruby, Javascript, Scheme, Prolog, Smalltalk, Forth, Mathematica and some more, also writing some interpreters and source to source transformers.

+ TCP/IP, socket programming, packet inspection and injection, firewall testing, SMTP, HTTP, ARP, DNS, CORBA, and 20+ proprietary protocols.

+ Oracle, MySQL and SQLite, helping with performance and storage tunning in some cases.

+ Linux/Unix kernel and tools, Win32 apis, ARM, and many libraries.

+ Automated testing tools including Selenium and many specifically created for existing applications, tcpdump, dynamic loader traps, binary debuggers, binary code injection and instrumentation and also desktop applications like Excel, Photoshop and others.

+ I used and even taught how to use UML, Rational Rose, some RUP templates, Erwin, etc. but in the last years replaced them with automated tests, scripts and lighter tools.

+ Source code of many projects like web servers (including Apache), language interpreters, database engines, etc.

- I usually avoid big and complex frameworks and tools like Hibernate, Maven, some XML parsers and others and only look at them when coaching a team that was unable to find a simpler and more reliable way of doing things.

+ I focus on computer science concepts instead of tools, am quick learner and am always ready to learn something new in this same line.

Tools follow needs

I choose mine trying to solve the following problems:

+ Agile development of business applications: tools must

• be easy to learn and use to many developers and even administrators
• only require code very close to the functional description of the implemented task
• be extremely easy to deploy and test
• pose no problematic licensing restrictions
• be portable to many target environments
• be verifiable and maintainable
• not require implementation of complex low level algorithms (e.g. string and pattern searching, image manipulation, etc.)
• have a large user community and documented experience after a long time used in real-world projects

+ Long term career as a developer and architect: tools must

• solve as many problems as possible in a consistent way
• be mature, extensible and long lasting (no fads)
• have a large community and a long time used in real-world projects

+ Quick prototyping and simulation: tools must

• be very expressive, require minimum amount of code
• provide suitable data interchange and user interfaces
• provide extensive libraries

accessible - valid w3c/html4.01 - www.mauriciocap.com.ar