Randy Sakuma

Background

About Randy Sakuma

Experienced Software Engineer with a demonstrated history of working in the computer software industry. Previous programming languages used in my professional work experience includes: C++, C#, Javascript, Typescript, Java, HTML, CSS, SQL, XML. Familiar with IDEs such as Visual Studio, Eclipse, Cocos, and Visual Code. Worked with frameworks/libs such as NodeJS, AngularJS, ASP.Net.Net Core, NgRx, etc. Has familiarity working in Full-stack / generalized code development for web based applications, cross platform apps, Game Programming (RTIS), math and physics algorithms, and data processing. Experienced at working under the AGILE development cycle, using such management tools as versionOne. Familiar with working with shared code repositories and source control. Able to write unit tests and do peer code reviews to insure quality and standard of the shared source code written by team members. Previously worked on projects: Qlikview based data analysis application to parse a DB and compute qualifying data for end users to view. eCQM Translator, an application that reads a government specified xml "instruction" file, and translates it dynamically into sql commands to query a DB and compute according to its specification. Reliable Messaging system, used to communicate between the front-end application to the microservice and backing DB to insure reliability and correct handling of dropped messages and errors. Widget based MVC / MVVM components. Built with Object Oriented design in mind for easy extendibility, reuse, and modulization. Tying behavior to a UI visual element, and making it flexible and customizable enough for designers to take the created widgets and build a webpage simply by placing the pieces where they want. Orders Cart, worked with an ordering system in a web based environment, to record, validate, preload, and auto-suggest behavior for the end-user. Worked in conjunction with a scalable microservice and the backing relational DB tables to insure data is ordered and recorded properly. Notation, worked with a documentation service layer, that reads from user input and historical DB analysis to generate a document recording a patients relevant information and matches it to a 3rd party medical DB for auto-suggestions and validations for allowed actions to take.