ArenaNet<\/h2>\n
I worked at ArenaNet from May 2017 to March 2019 as a tools programmer for an internal editor and engine.<\/p>\n
- \n
- Worked on a multi-tool, 3D game editor with C#<\/strong> and WPF<\/strong><\/li>\n
- Created native tools and engine features with C++<\/strong><\/li>\n
- Used C++\/CLI<\/strong> to perform editor\/engine communication<\/li>\n
- Developed a cinematics editor with scrubbable timeline<\/li>\n
- Added cinematics features to the engine<\/li>\n
- Refactored curve editor for new types, features, and performance<\/li>\n
- Enabled editing of inherited resource content to increase flexibility and productivity for world designers<\/span><\/li>\n
- Interacted with cinematic, world, and VFX artists frequently for support and quick feedback loops<\/span><\/li>\n
- Constructed unit tests to ensure stability of editing features and resource deserialization<\/span><\/li>\n
- Created a Node.js<\/strong> console application to help automate daily tasks<\/li>\n<\/ul>\n
DoubleDown Interactive<\/h2>\n
I worked at DoubleDown Interactive from September 2013 to September 2016 with a large team of mobile developers, QA testers, and artists.<\/p>\n
- \n
- Developed casino games with JavaScript<\/strong>\u00a0and a modified LimeJS<\/strong><\/a> framework<\/li>\n
- Componentized sub systems for better plug & play of shared code<\/li>\n
- Utilized Google Closure<\/strong><\/a> Library and Templates<\/li>\n
- Created an custom WYSIWYG editor with nw.js<\/a><\/strong>\u00a0(formerly node-webkit) and dat.GUI<\/strong><\/a><\/li>\n
- Worked with C#<\/strong> and Unity<\/strong> to develop a better level editor<\/li>\n
- Used PHP<\/strong> and Postman<\/strong><\/a> to develop and test\/debug API requests<\/li>\n
- Created a few small tools with Python<\/strong><\/li>\n
- Developed unit tests for newly developed systems<\/li>\n
- Created a simple automation and test tool<\/li>\n
- Contributed greatly to internal documentation<\/li>\n<\/ul>\n
![\"IMG_3945\"](\"http:\/\/www.coreyabel.com\/wp-content\/uploads\/2017\/01\/IMG_3945-225x300.jpg\")
<\/a><\/p>\nAt DDI, I was a source of knowledge for both programmers and artists, and I would always take the time to answer questions and assist with bugs or new solutions. \u00a0I could remember our\u00a0codebase fairly well, so I rarely had to look something up when working with someone. \u00a0This ability helped immensely when I was\u00a0writing documentation, as well as when I got contacted for help while on vacation.<\/p>\n
After my departure, my co-workers missed me. \u00a0My manager put a photo of me on a cardboard cutout of Ellen and placed it next to his desk.<\/p>\n
DoubleDown Casino<\/h3>\n
![\"DoubleDown](\"http:\/\/www.coreyabel.com\/wp-content\/uploads\/2013\/03\/IMG_1336-300x225.png\")
<\/a><\/p>\n![\"img_1337\"](\"http:\/\/www.coreyabel.com\/wp-content\/uploads\/2016\/12\/IMG_1337-300x225.png\")
<\/a>iTunes Store<\/a> – Google Play Store<\/a><\/p>\nThe DoubleDown Casino app was developed with an HTML5 game framework that was run on desktop browsers, iOS, and Android. \u00a0It features many different casino games (slots, roulette, blackjack, and video poker). \u00a0Two of the best parts about working on the app is the amount of shared code between the games and the millions of people that play the app.<\/p>\n
I started out working on just casino game content, but a good chunk of time was spent refactoring systems to make it easier for development of new games. \u00a0One major focus was componentizing large sections of code we had. \u00a0Each game relied on common code to function. \u00a0The idea was to not reinvent the wheel each time, and the first few games were incredibly similar. \u00a0Having the same code run for each game did not work as well when the content we were tasked to develop was becoming more unique and deviating from the standard common code.<\/p>\n
The first componentization was for our server response parsing. \u00a0Not all responses were equal for the same kind of feature, and not all games had the same set of features. \u00a0I mostly worked on improving on the details after a fellow developer did the initial work. \u00a0\u00a0My goal was to tidy up the processed data as well as make the parsing more flexible. \u00a0Our default parsing was initially written during a time with less developer time and resources, and it included many hard-coded values to check for in the server response. \u00a0For backwards compatibility purposes (and to prevent some regression testing), those were left in, but I added the ability to override options with data per game.<\/p>\n
For each user interaction, the parsed data was fed to a\u00a0very long method that scheduled a series of actions, animations, and sounds. \u00a0The method kept growing as new games with different features were developed. \u00a0I was tasked to work on a new game that repeated a section of the long method with different data, but I did not want to copy\/paste a large chunk of code and hack it in. \u00a0I took the individual features of the core game code and put them into separate component classes that could be removed or replaced per game. \u00a0Each component defined actions to take on specific events. \u00a0In a new system, I mimicked the the previous long method by just dispatching a few of these events that the components registered for. \u00a0I was also able to sequence the order of the components that got triggered for each of those events.<\/p>\n
With the high-level execution only requiring a few event dispatching calls, it made it easy to override and customize for a particular game. \u00a0It was also incredibly easy to add new features specific to a game or create common, reusable components. \u00a0By segmenting the core code into components, each game’s level data could define what functionality it needed and which order each feature would get called on triggered events for\u00a0scheduling tasks. \u00a0Each part could get replaced\u00a0with an advanced shared-code version, one custom to the particular game, or removed if the game didn’t have that feature.<\/p>\n
Level Editor<\/h3>\n
![\"Level](\"http:\/\/www.coreyabel.com\/wp-content\/uploads\/2013\/03\/unnamed-300x175.png\")
<\/a>We needed a way to visually edit the scenes we were creating, so I spent time working on two different level editors.<\/p>\nOur first editor was initially created during a hectic week where teams could create whatever they wanted. \u00a0Four developers created a WYSIWYG editor by running our game framework within a WebKit renderer. \u00a0nw.js<\/a> (formerly node-webkit) was used to display the local web page and give us some Node.js functionality for saving & loading. \u00a0dat.GUI<\/a>\u00a0was used for displaying editable properties of a selected object. \u00a0We developed a serialization system for both JSON and XML and a deserialization for JSON.<\/p>\n
I worked on the transform gizmos, property inspector, tree view, history, UI paneling, sprite sheet generation, and XML serialization. \u00a0History was recorded by serializing objects at the start and end of editing and trimming down just to the changed properties. \u00a0Undoing & redoing just made the objects deserialize the subset of properties recorded.<\/p>\n
For each class,\u00a0we created a map of property names to getters and setters. \u00a0This property list could be iterated over for both serialization and showing the properties in the object inspector. \u00a0The inspector would use default settings for editing each property, but a separate list was used to modify and tweak the controls and add extra functionality<\/p>\n
The second editor was developed with Unity. \u00a0This was done to reduce the amount of “editor” programming we had to to, as well as let the artists use something more familiar (the artists never used the first editor). \u00a0We developed a C# plugin for Unity that included more MonoBehaviour components and specific\u00a0version that inherited from the base classes provided by Unity. \u00a0It also included various menu options (exporting, validation, etc.).<\/p>\n
Most of my work was done fine-tuning the export process to make the usage of it easier for developers. \u00a0We hadn’t yet got to the stage were we could export from Unity or our own custom level editor to completely override the level files in our packages. \u00a0My goal when working on the project was to decrease the amount of changes from the exported scene to what was usable. \u00a0I also focused on making multi-scene exporting less of a hassle for developers and allowing artists to use more features for animations. \u00a0I worked on turning prefab objects and instances into Google Closure templates and calls to reduce duplication between our different layouts.<\/p>\n
Test Tool<\/h3>\n
Some of the sloppiest code I ever wrote was the most useful. \u00a0I needed a quick way to test a bunch of different settings on almost all of our game content due to new A\/B tests we were going to do. \u00a0I wrote a independent file that I could load on top of the app to inject functionality. \u00a0The tool was able to automatically go through all scenes, do verification at various steps, take screenshots, switch layouts, switch A\/B settings, etc. \u00a0Theses actions were performed without restarting the app. \u00a0It was extended later to switch between resolutions and languages, which was not something our app was structured to do.<\/p>\n
The Google Closure Library does not use a\u00a0module pattern that will hide “private” members in a closure. \u00a0“Private” properties are only denoted with the use of an underscore in the property name. \u00a0So all properties are accessible, and the rest of our code base followed the format of the Google Closure Library. \u00a0I knew all of the properties that had to be manipulated, so my code modified many\u00a0properties that shouldn’t have been touched. \u00a0I also wrapped major methods to collect and redefine data when the methods were called.<\/p>\n
We had automation already (which could take screenshots), but it took several minutes for one game to do a complete pass and wasn’t easy to add the verification steps that I needed. \u00a0I didn’t need the waiting and many of the validation tests that the automation had. \u00a0I wrote my own simple automation in the tool to be able to go through all games in about five minutes, so rapid testing was possible for my A\/B work.<\/p>\n
The Integrated Agency<\/h2>\n
I did contract work with five other developers and artists for interactive apps on mobile devices from May 2012 to July 2013.<\/p>\n
ICGN Annual Conference<\/h3>\n
![\"icgn\"](\"http:\/\/www.coreyabel.com\/wp-content\/uploads\/2013\/06\/icgn-300x204.png\")
<\/a>iTunes Store<\/a> – Google Play Store<\/a> – Development Site<\/a> (user: icgntest, pass: ws7zas)<\/p>\nA UI designer and I created an app for the\u00a0International Corporate Governance Network Annual Conference.\u00a0 I helped implement features and converted a website for app deployment.<\/p>\n
- \n
- Converted static pages to run as a single-page application<\/li>\n
- Used HTML5 Web Storage<\/strong> for saving items retrieved from a database at 60 minute intervals<\/li>\n
- Used PhoneGap<\/strong><\/a> to deploy app on iOS, Android, and Windows Phone and store files locally<\/li>\n
- Optimized CSS for mobile<\/li>\n
- Loading\/unloading of images to reduce memory footprint<\/li>\n
- Utilized Sched.org’s RESTful API for managing user schedules<\/li>\n<\/ul>\n
Internal Sales Tool for Avid Technology<\/h3>\n
![\"\"](\"http:\/\/www.coreyabel.com\/wp-content\/uploads\/2013\/03\/avid-01-300x225.png\")
<\/a><\/p>\nAvid Sale Tool Development Site<\/a><\/p>\n
We created an internal sales tool for Avid Technology<\/a> to help sell their suite of hardware and software to news stations and video production studios. Development was done on an online site, while we served a local version on an iPad. I worked with another programmer, a UI designer, and a sound designer.<\/p>\n
- \n
- Created a database-driven, single-page iPad app<\/li>\n
- Used CSS<\/strong> to layout and create website based on designer’s mockups<\/li>\n
- Used JavaScript<\/strong> with AJAX to request JSON from the SQLite3<\/strong> database<\/li>\n
- Interactive elements and animations handled by JavaScript library jQuery<\/strong><\/li>\n
- Other animations created with CSS3 transitions<\/li>\n
- Developed an admin section for user-friendly editing<\/li>\n<\/ul>\n
Jack & Jill’s ABC’s of Christmas<\/i><\/h3>\n
![\"jackandjill\"](\"http:\/\/www.coreyabel.com\/wp-content\/uploads\/2013\/05\/jackandjill-300x225.png\")
<\/a><\/p>\niTunes Store<\/a> – Video<\/a><\/p>\n
Jack & Jill’s ABC’s of Christmas<\/i> is an interactive eBook for children covering different aspects of Christmas. Users can swipe to transition to another letter apart of a large scene and touch to interact with items. I worked with another programmer, an artist, and a sound designer \/ musician.<\/p>\n
- \n
- Programmed in Lua<\/strong> using the Moai SDK<\/strong><\/a> for iOS and Android<\/li>\n
- Exported and edited artwork from Adobe Flash<\/strong><\/li>\n
- Adapted Cocos2d-x<\/strong><\/a> WinRT build (C++<\/strong>) to have Lua<\/strong> bindings for a Windows 8 “Metro” release<\/li>\n
- Converted ActionScript 3 code to Lua<\/li>\n<\/ul>\n
Magical Fairy Friends: Dorothy the Rainbow Fairy<\/i><\/h3>\n
![\"mff\"](\"http:\/\/www.coreyabel.com\/wp-content\/uploads\/2013\/05\/mff-300x224.png\")
<\/a><\/p>\niTunes Store<\/a> – Google Play Store<\/a> – Amazon App Store<\/a><\/p>\n
Magical Fairy Friends: Dorothy the Rainbow Fairy<\/i> is an interactive eBook for children focusing on a fairy that is responsible for rainbows. It’s aimed to explain rainbows to young girls. It has sliders similar to pop-up books and a few more complex interactive elements (coin toss into a three-teir fountain, bendable hose). I worked with another programmer, two artists, and a sound designer \/ musician.<\/p>\n
- \n
- Programmed a children’s eBook in ActionScript 3<\/strong> with Adobe Flash<\/strong><\/li>\n
- Used Adobe AIR<\/strong> to deploy app on iPad and Android<\/li>\n
- Optimized artist’s work for mobile devices<\/li>\n<\/ul>\n
Amazing Elephant<\/h2>\n
Initially brought on to do a Flash game, I was then responsible for creating an iOS app for Thai recipes. I then progressed to doing additions to ImportFood.com and then a complete overhaul of several sections, while still maintaining some of the older look. I worked from June 2011 to December 2012.<\/p>\n
ImportFood.com<\/a><\/h3>\n
![\"importfoodrecipe\"](\"http:\/\/www.coreyabel.com\/wp-content\/uploads\/2013\/05\/importfoodrecipe-300x224.png\")
<\/a>![\"importfoodsearch\"](\"http:\/\/www.coreyabel.com\/wp-content\/uploads\/2013\/05\/importfoodsearch-300x224.png\")
<\/a>ImportFood.com is an online retailer that sells imported food and cookware from Thailand, along with fresh local produce. The site provides recipes, videos, and other featured articles on Thai food and Thailand.<\/p>\n- \n
- Revamped static recipe, video, and feature pages into dynamic database-driven pages using PHP<\/b>, MySQL<\/b>, JavaScript<\/b>, and jQuery
<\/b><\/li>\n- Provided rich snippets markup for Google search results<\/li>\n
- Developed an AJAX-driven admin page<\/li>\n
- Wrote a C++<\/strong> parser to grab unique ingredients from hundreds of recipes<\/li>\n
- Added ability to let users add all the ingredients of a recipe to their ShopSite<\/a> shopping cart<\/li>\n
- Created a tool in PHP and JavaScript to search for recipes by their ingredients<\/li>\n
- Created a login and ability for users to upload images to recipes and earn rewards<\/li>\n
- Wrote a PHP parser to grab text, images, comments, and other content for the database from static pages previously generated with a non-templated Adobe GoLive site<\/li>\n
- Programmed a fuzzy word matching tool in PHP using a modified Levenshtein distance algorithm<\/a><\/li>\n
- Rewrote fuzzy word matching tool in C++ for a site-wide auto-suggestion search ability with CGI<\/b><\/li>\n
- Took inventory and provided information for Google Product Listings<\/li>\n<\/ul>\n
ThaiCuisine.com<\/a><\/h3>\n
![\"thaicuisine\"](\"http:\/\/www.coreyabel.com\/wp-content\/uploads\/2013\/05\/thaicuisine-300x224.png\")
<\/a>ThaiCusine.com has a database of Thai restaurants in the US. Users are able to find restaurants and submit reviews and photos.<\/p>\n- \n
- Revamped review site similar to ImportFood.com<\/li>\n
- Developed an AJAX-driven admin page<\/li>\n
- Admin page included color highlighting to indicate user-submitted issues and provided methods to auto-correct issues in formatting<\/li>\n
- Added ability to automatically add links in user reviews<\/li>\n<\/ul>\n
Thai Sidewalk Chef<\/i><\/a><\/h3>\n
![\"cookinggame\"](\"http:\/\/www.coreyabel.com\/wp-content\/uploads\/2013\/05\/cookinggame-300x200.png\")
<\/a>I created a game for ImportFood.com’s Facebook page. In the two stages, the user collects ingredients and then follows a recipe to cook that dish. Several dishes were created.<\/p>\n- \n
- Created game on Facebook using ActionScript 3 <\/strong>and Adobe Flash<\/strong><\/li>\n
- Levels driven by XML<\/strong><\/li>\n
- Used Adobe Photoshop<\/strong> to edit artist’s images<\/li>\n
- Used Facebook API to keep scores of users<\/li>\n<\/ul>\n
Authentic & Popular Thai Recipes<\/a><\/i><\/h3>\n
![\"authenticandpopularthairecipes\"](\"http:\/\/www.coreyabel.com\/wp-content\/uploads\/2013\/05\/authenticandpopularthairecipes-225x300.jpg\")
<\/a>I developed an iOS app for both iPhone and iPad that featured ImportFood.com’s recipes with pictures and videos.<\/p>\n- \n
- Used Objective C<\/strong> and iOS SDK<\/strong> to develop a native app in Xcode<\/strong><\/li>\n
- Stored data in a SQLite3<\/strong> database<\/li>\n
- Implemented fuzzy, auto-correcting search by name or ingredients<\/li>\n
- Used Handbrake and other tools for batch converting video and images<\/li>\n
- Implemented In-App Purchases and provided downloadable content<\/li>\n<\/ul>\n
Thai Street Vendor Videos<\/a><\/h3>\n
I helped edit many videos of Thai street vendors using Adobe Premiere<\/strong>. I managed their upload to YouTube and provided a YouTube alternative to our Flash player on mobile devices.<\/p>\n
Nintendo of America – Aerotek Staffing Agency<\/h2>\n
I spent a few months in crunch mode from May to July in 2007 as a tester on Metroid Prime 3: Corruption<\/i> until its completion.<\/p>\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Accretive Technology Group I have been at Accretive Technology Group since April 2019 as a senior lead software engineer. Worked on client and server applications with TypeScript Used React & Redux for single-page applications Server developed with Node.js and Koa Live service monitoring GUI automation ArenaNet I worked at ArenaNet from May 2017 to March […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-2","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.coreyabel.com\/index.php?rest_route=\/wp\/v2\/pages\/2","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.coreyabel.com\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.coreyabel.com\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.coreyabel.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.coreyabel.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2"}],"version-history":[{"count":10,"href":"https:\/\/www.coreyabel.com\/index.php?rest_route=\/wp\/v2\/pages\/2\/revisions"}],"predecessor-version":[{"id":343,"href":"https:\/\/www.coreyabel.com\/index.php?rest_route=\/wp\/v2\/pages\/2\/revisions\/343"}],"wp:attachment":[{"href":"https:\/\/www.coreyabel.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Stored data in a SQLite3<\/strong> database<\/li>\n
- Levels driven by XML<\/strong><\/li>\n
- Created game on Facebook using ActionScript 3 <\/strong>and Adobe Flash<\/strong><\/li>\n
- Used Adobe AIR<\/strong> to deploy app on iPad and Android<\/li>\n
- Exported and edited artwork from Adobe Flash<\/strong><\/li>\n
- Used JavaScript<\/strong> with AJAX to request JSON from the SQLite3<\/strong> database<\/li>\n
- Used PhoneGap<\/strong><\/a> to deploy app on iOS, Android, and Windows Phone and store files locally<\/li>\n
- Created native tools and engine features with C++<\/strong><\/li>\n