TECHNICAL SKILLS:

Languages: PERL, LINUX, SQL, PHP, XML, SOAP, REST, JSON, XSLT, HTML, JAVASCRIPT, CSS, AJAX, BASH

Software and Technologies: WEB SERVICES, APACHE, BIND, ORACLE, MySQL, WORDPRESS, GIT, GOOGLE AdWords, SVN, SOLARIS, MS OFFICE, PHOTOSHOP, UBUNTU

PROFESSIONAL EXPERIENCE:

Confidential, Atlanta, GA

Application Developer

Responsibilities:

• Developed and maintained XSLTs for Confidential ’s custom email publishing system directly affecting millions of customer communications daily.
• I used XSL to transfrom XML from various other departments into SOAP reuquest that could be digested into the email system.
• Also I built HTML templates using HTML and CSS along with Confidential ’s custom API.
• Other tasks involved using Web Services such as SOAP to send and receive XML requests, analyzing and scoping requirements for new projects, mainting existing email templates and XSL stylesheets, and building custom tools for business applications.
• The custom tools for the most part consists of HTML, CSS, and Javascript web applications using Perl on the backend to access and display data from an Oracle database.
• Database querying and tailing log files on Unix servers were used to track down any errors errors.

Confidential, Atlanta, GA

Application Developer

Responsibilities:

• Develop custom apps to manage URL redirects, test web connections, scrape pages for content. Also manage and install server software, Apache, MySQL, JIRA...
• An example application that I wrote would be the Confidential redirect tool which keeps track of redirected URLs in a relational database.
• Each redirected URL has associated redirect rules for zip code and such that are also kep in the database and managed by a front end web tool that I built with HTML, CSS and Javascript.
• There are back end programs written in Perl that interface with the database updating records, writing out a text file to be used by Apache’s mod - rewrite module, and also validating that redirects are redirecting using various Perl modules.
• Other duties involved updating various pages using the standard web languages as well as trouble shooting page errors. SVN was the source control in use.

Confidential, Atlanta, GA

Application Developer

Responsibilities:

• This application used HTML, CSS and JAVASCRIPT on the front end and PERL DBI and ORACLE on the back end to send golf tips to Confidential periodically by FTP.
• The app allows the data entry person, usually a golf editor for PGA.com, to submit golf tips that they have collected from professionals in the golfing community. The tips are stored in an Oracle database on the back end.
• When the golf editor is ready to send a new batch of tips he just selects the ones he wants to send by clicking a check box, hits send, and the records are extracted from the database, written to an XML file and Ftp’d over to Confidential .
• Essentially this is an ongoing process of maintaining a feed of articles and videos from Turner Sports websites (nba.com, pga.com, pgatour.com, nascar.com) to Confidential .
• This involves making statement changes to XSLT’s or JSP’s on an ongoing basis whenever a request for a new article or video type comes in. The XSLT is update on our APS system or the JSP is updated on our CMS systems.
• Normally I use many of my basic UNIX skills to accomplish this task as I prefer not to use graphical FTP or SSH programs, it’s normally all command line. So the process may involve ssh’ing into the remote server, using Vi to edit the file, then as I publish a new article or video on our CMS development system to test the process I may “tail” the logs on the CMS or APS to check for errors and what not.
• This process has taught me most of what I know about using the Turner Sports CMS as well as how the different events are triggered within a “profile.”
• This project involved the creation of an XSLT on the APS, a new CMS profile, a new APS profile and Perl script to run in cron
• Since this feed was outside of the usual CMS/Newsroom tools feed we would normally use for Confidential we utilized the PGA Championship micro site feed.
• The process involved automatically downloading the PGA Championship XML from their site using wget inside a Perl script that ran periodically. The XML was then cleaned up a little in Perl then ran against an XSLT (using XMLPusher) to filter only the particular stories we wanted to send to JulySystems. The XML is then place on the July server through FTP.

Confidential, Atlanta, GA

Application Developer

Responsibilities:

• This application used HTML, CSS and JAVASCRIPT on the front end to display orders that need to be fulfilled to the IMV production department which consisted of approximately 12 people.
• The app allowed the data entry person to update records as well as keep track of renewal and expiration of new orders. PERL and shell scripting was used on the backend to automate certain process via cron.
• Such as importing of new orders dialing and shipment of the orders to our 3rd party vendor for fulfillment.
• The shipping of orders took place through emailing of EXCEL files created from the database.
• Records where extracted via PERL and shipped vi “sh” shell scripting and using mconnect.
• This app held all of the available IMVI products with description, photos etc.
• HTML, CSS and JAVASCRIPT used for front end user interface.
• PERL DBI used to update Oracle database with new items, as well as display those items in a search.
• This tool used HTML, CSS, JAVASCRIPT on the front end and PERL, XML and shell scripting on the backend.
• It allowed the consulting department consisting of 10 people to submit orders to a 3rd party vendor via XML files that are pulled from an Oracle database, via cron, nightly using PERL.
• During this time XML files from the vendor were retrieved and parsed and the database was updated.
• Parsing took place with no special module, just PERL and regular expressions.
• Orders were entered into the database by an IMVI consultant or externally by customers.
• When the customer updated their data an email is automatically sent to the consultant.
• This was a non-production app.
• Its intended use was to register domain name with Tucows through the Tucows API. HMTL, CSS and AJAX where used on the front end.
• AJAX was used for nicer ender user experience by fetching customer data from an Oracle database in the background.
• Gained a thorough understanding of DNS, Web and Email Severs during my tenure.
• For example understanding how email is sent and received on a core level such as using telnet, mconnect or mailx to send email from the command line.
• Also using tools such as nslookup to trouble shoot domain routing problems.
• Developed a clear understanding of BIND’s “named” configuration files
• Develop a more thorough understanding of Apahce httpd.conf file

Confidential, Atlanta, GA

Application Developer

Responsibilities:

• Developed content management forms to update clients shopping cart and web based photo album.
• HTML, CSS and JAVASCRIPT are used for form creation and validation.
• Parsing the XML files used by the FLASH/PayPal cart and updating them with new XML content updates the cart.
• During this process, no SQL type databases were used, which made the management tool a bit more portable.
• The XML file is parsed into a temporary DBM database using the SDB File module.
• The data is manipulated as needed in the DBM database, written back to XML and the DBM is destroyed. Image::Magick is used to convert uploaded images to jpeg as well as resize.
• Used HTML, CSS and JAVASCRIPT to created content management for video site.
• The clients could upload new flash videos and have them displayed on the site.
• This involved updating XML files with PERL.
• Developed content management system using HTML, CSS, JAVASCRIPT, PERL, MySQL }
• Designed the database (MySql) and created the content management application for the site.
• The typical cast of characters (HTML, CSS, JAVASCRIPT) was used for the forms. JAVASCRIPT handled the form validation while HTML and CSS was used for overall look and feel.
• PERL and MySQL where used on the backend to store new records as well as display them to the end users of the site.