Aaron Brady (Developer): Difference between revisions

From Unofficial Homecoming Wiki
Jump to navigation Jump to search
imported>Aggelakis
mNo edit summary
(Added Bits to De-Stub.)
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{wip}}
== Overview ==
[[File:Aaron Brady.jpg|thumb|right|Aaron Brady|250px]]
'''Aaron Brady''' was the lead programmer at [[Cryptic Studios]] from Jan 2005 - Oct 2007. He transitioned to [[Paragon Studios]] to become the director of technology from Aug 2007 - Feb 2009 before moving back to Cryptic Studios to work on Neverwinter.
== Contributions ==
*Wrote high performance real time networking system using UDP and IOCompletionPorts that reduced memory and CPU consumption across all servers.


Position: Programming Department, lead engineer
*Wrote server side shared memory loader to reduce memory usage allowing more instances per server.


Has been a programmer for the City of Franchise since January 2005, one of the [[developers]] to make the jump from Cryptic to NorCal.
*Built analytics system to track user pain points such as where engagement dropped off and what systems were being underutilized.
<ref>https://www.linkedin.com/in/abrady/details/experience/, Linkedin Experience Page</ref>


{{NorCal NavBox}}
{{NorCal NavBox}}
[[Category:Cryptic Studio]][[Category:NorCal Studio]]
[[Category:Cryptic Studio]]
[[Category:NorCal Studio]]
[[Category:Developers]]

Latest revision as of 19:52, 23 August 2024

Overview

Aaron Brady

Aaron Brady was the lead programmer at Cryptic Studios from Jan 2005 - Oct 2007. He transitioned to Paragon Studios to become the director of technology from Aug 2007 - Feb 2009 before moving back to Cryptic Studios to work on Neverwinter.

Contributions

  • Wrote high performance real time networking system using UDP and IOCompletionPorts that reduced memory and CPU consumption across all servers.
  • Wrote server side shared memory loader to reduce memory usage allowing more instances per server.
  • Built analytics system to track user pain points such as where engagement dropped off and what systems were being underutilized.

[1]

  1. https://www.linkedin.com/in/abrady/details/experience/, Linkedin Experience Page