Senior LAMP Web/Application Developer
With over 6 years of combined programming, database, systems design/implementation
and web application development experience, I am extremely well motivated with an
unquenchable desire to learn. I posess a proven track record of successful,
well written and deployed applications. I really like object oriented
design and have been expanding my understanding of design patterns.
I’m currently employed as a full–time web developer by DomainTools
in Seattle‚ WA. For more information on my previous employment‚
download my
resumé, email me at [javascript protected email address],
or check out my
LinkedIn profile.
Some of my skills
Languages:
- Proficient in: PHP 4.x/5.x, JavaScript, HTML, MySQL
- Intermediate skills: AJAX, CSS, DOM, Perl, XML, PEAR, PECL,
JQuery, YUI, RegEx, MVC, Java
- Familiar with: C/C++, C#, Ruby, UML, XSLT, SQLite
Tools:
- Database: MySQL 5.0, relational database structures, PHPMyAdmin
- Editors: Komodo Edit/IDE, Eclipse, Notepad++, Vi/Vim, some
Visual Studio
- Source Control: CVS, Subversion, Perforce
- Environment: Apache 2.x, Android SDK 1.6/2.0, PHPUnit
- Tracking: Pivotal, Trac, Bugzilla, FogBugz
- Content: Wordpress, b2evolution, Expression Engine, Drupal
- Platforms:
- Microsoft Windows – XP, Vista
- Linux – Fedora Core 4, CentOS 5.x, Ubuntu 7.x/8.x/9.x
- VMware – ESXi/Infrastructure Client, Workstation, Player
Some of my portfolio
These are some things I have done
for my own projects and for previous employers. The work I am
most excited about is positioned on the back end which is
difficult to showcase here. Not all of these projects are
currently accessible but were all at one time public facing to
millions of customers. Code samples are available upon request!
Flicka is my passion to learn and implement an awesome Android
application. It brings Flickr to the mobile platform
utilizing the Android SDK in creative ways. Working with an
enthusiastic designer, the front end looks as good
as the code underneath! That's why I co-founded
MokaSocial.
The Xunlai Tournament House
was a large project which involved tieing game login
to the website at the Guild Wars website.
It was a very involved project using sockets to
communicating with authenication servers to login,
tableless layouts, and was available in several
languages using XML language files. I had to coordinate
with several teams and the NOC to make sure deployment
and the site's operation went smoothly.
The Xunlai Tournament House
had quite a few newer layout features such as CSS/JS
dialog boxes, YUI based drag and drop spanning multiple
pages, JS resorting in the target area, and tabbed
sections – to name a few things. All this was
fully cross browser compatible.
The back end
required several checks to ensure tight security in
voting and the login in mechanisms. After the tournament
was completed, a script would collate and then deliver
the winners and their points to the server team. Winning
points in this web feature meant users could be awarded
items in game which made this a very popular application
for our users.
The
Official Guild Wars Guild Ladder uses AJAX to
update pagination and sorting. Clicking on a guild
will reveal statistics and graphs created data points
fromn all the entries for that parricular guild for
the season.
The
Official Guildwars Challenge Mission Ladder was a
project that involved interfacing with several teams.
I needed server developers to provide the right data
to the MySQL tables on an hourly basis. I needed
designers to help decide how they wanted the info
displayed. I needed the internationalization team to
help translate the content into 9 languages. There
were a lot of moving parts for me to track.
The ladder features AJAX driven updates pulling information
on the fly from a database, agregating and calculating
averages and then caching them in a memory table.
The ArenaNet company website
started as a chunky design that was hard to update.
Working with a designers and artists, we created a
site that changed our online presence to a modernized
look and feel.
My contributions were primarily in converting all
the content to utilize the Expression Engine content
management system. Some aspects were simple straight
ports of pages into the CMS. Other aspects involved
understanding how the system paginated articles, created
breadcrumbs, and so on.
Last modified: April 24, 2010