- $\cdot{}$ A customer wanted the ability to show sections of stored surveys
- conditionally. For legacy reason, this had to be done in CFML and was further
- constrained by existing surveys which could were not under our control. After
- finding the relevant CFML, I constructed additions to the in-house developed
- markup language and corresponding processing CFML. This feature has been in
- use for the last six months without affecting other survey features.
- \newline{}
- $\cdot{}$ Motivated by the difficult setup process, I decided to automate the
- setup of new Coldfusion developer stations. Adobe's coldfusion installer
- script has user interaction, so initial scripting was done with Expect. To
- make the installer more maintainable by the other programmers, this was
- converted to ruby and bash. Several development systems have since used
- this installer.
- \newline{}
- $\cdot{}$ Because the old svn systems were difficult to work with, I converted
- several of them to git repos served by gitosis. I set up the gitosis server
- and taught some coworkers how to use ssh-keys for easier interaction with it.
- \newline{}
- $\cdot{}$ VisionTree's store of surveys, written in their custom markup, has
- syntax errors which sometimes cause real customer data loss. In order to
- combat this, I talked with developers creating the surveys and with those who
- wrote the parsing code about the types of errors and which were most common.
- I wrote a ruby gem generate error reports in xml. From there, it was easy to
- write a server for an internal site that presents all the data to the other
- developers. After creating the site, I modified the internal gedit plugin to
- present the same data within gedit on developed as they are developed, before
- they are pushed live for customers.
+ \begin{itemize}
+ \item
+ The old svn systems were difficult to work with, so I converted them
+ to git repos served by gitosis and later gitolite. Thanks to ssh keys,
+ Visiontree is now able to merge branches more often and more easily.
+ \item
+ The git systems mentioned above are used by a lot of people, internal devs
+ as well as third parties. After helping several fellow developers
+ serially and individually, I created a class to explain how to use git.
+ I have given this class several times. Developers from around the country
+ have attended.
+ \item
+ One former developer created a suite of ruby scripts to hand HL7 protocol
+ communications. To make the service more reliable, I have documented the
+ process of installing the scripts as different users and on new machines,
+ as well as automated parts of it.
+ \item
+ A customer wanted the ability to show sections of stored surveys
+ conditionally. I made additions to the survey markup, ``vtjson'', and
+ processing code, while remaining compatible with existing surveys.
+ \item
+ I decided to automate the setup of new Coldfusion developer stations with
+ Expect. Later, I translated into ruby and bash, languages the other
+ developers are more familiar with.
+ \item
+ VisionTree's surveys have syntax errors which sometimes cause customer
+ data loss. In order to combat this, I generated an error reporter. Errors
+ were presented by an internal website and a gedit plugin.
+ \end{itemize}