Jared Scheib

Converted large open source web app to TypeScript from JavaScript.

• Helped engineer & build open-source, enterprise data visualization, monitoring, & database management web app, Chronograf, the GUI for the InfluxData Platform for time series data. Specific emphasis on role-based access control and other general web app security via OAuth2. • In React, I've created innumerable React components and containers; wrote just as many Redux action creators and reducers, as well as corresponding AJAX requests against a dedicated RESTful API server (which also proxied many database and monitoring queries out to other services); used React Router to create a Single-Page App experience and to ensure user authorization to navigate and use large-scale web apps; and worked on a lot of data visualization (using dygraphs) of time series data. • Additionally, at Tagasauris I built React + Redux web app prototypes such as a custom, segment-based video player, to explore the user experiences possible when applying machine learning to video, such as hypervideo and automated video editing. I also wrote a lot of AJAX/database requests against Firebase, which we used as our data store.

Key areas of work: API design & implementation; Key-value database transactions; Authentication & Authorization; Testing; Routing; Compatibility with Protocol Buffer & JSON. Most recent project: I spearheaded the effort to refactor the RESTful API server of an open source, enterprise, single-page app from one where all users had the same permissions to manipulate the same resources, to one where every user belonged to an organization and was independent from each other, with varying permissions to manipulate their organization's resources as determined by an admin via role-based access control. This required implementing an API middleware for authorization as well as revamping the server's database layer to operate on the intended resources that belonged to the specified organization. A user would also belong to a specific organization, and could belong to multiple and switch between them, and in this scheme a user could only operate on the users belonging to their organization for which they also had the appropriate permissions (via RBAC). Organizations themselves could be created and administrated by a special kind of admin. Users who had successfully authenticated via a configured OAuth2 provider would be issued a JWT by the server, which would be validated and authorized by server middleware for appropriate privileges against the requested resources. I've also worked heavily on request handling, routing, JSON encoding and decoding, marshaling and unmarshaling to/from Protocol Buffers for persistence in BoltDB and for communication over gRPC, and error handling. Recently, we have adopted spec-driven API development, where an API is only implemented after proposing, iterating, and gaining approval for its specification in OpenAPI (f/k/a Swagger). APIs that I've written largely conform to the JSON API specification. The vast majority of my Golang work has been done using Test Driven Development (TDD).