Tim Lake

At Funraise I worked on the Systems Team, alongside fantastic developers, where we worked on features across the site, identified/fixed bugs, & managed the Postgres database.

On a daily basis my work consisted of working on the Funraise backend using Java to provide new features to our users, address a bug, or update data in the database to correct some edge cases that users encountered. Whenever those edge cases were encountered, we would write up a ticket in JIRA so that a fix can be implemented as soon as possible either by myself or another member of the team.

I brainstormed with my teammates for creative solutions to bugs that users ran into that were resolved through dataase and/or code changes that either they or I worked on following those brainstorming sessions.

I wrote many fixes over the years at Funraise ranging from small changes to complex refactoring of sections of the backend code to not only address the bug but improve the code for better maintenance in the future.

I also worked on numerous features including the much desired Salutations feature. This feature included changes across multiple systems such as from within the organization's Setting in Platform, the Giving Forms that are the essential piece to Fundraising, the Giving Form Settings in Platform, the Fundraiser Sign Up/Settings on a Campaign Site, multiple integrations, as well as our import and export tools.

During my partnership with DnD Tonight I worked on the server for players to use during the live stream. I collaborated with Corporate Streams, who was running the media during the stream, and the game master on what features to provide to the players and the live stream.

I wrote the server in C++ and the website in HTML, JavaScript, and CSS. I used websockets to send real time information from the website that the players used to my server which would process those requests and hand them off to CasparCG, which is the media server that the live stream used.

My server performed validation on the data that was provided in order to ensure the quality of the data shown on the stream. The player inputs also ensured the proper data in each field. The validation was based off of the core rules of Dungeons and Dragons 5e, including all states that a player would manage including death saves. All of these features that the player can set in the website reflect on the stream.