I planned, designed and implemented solutions for automating Parity's release processes.
I planned, tested and implemented whole solutions, as well as domain-specific tools, with an emphasis on robustness and reliability, for internal needs.
I participated in many different client projects since the company did not yet have its own products. Most of my time was spent on front-end development and shell scripting for CI and tooling needs. Outside of coding, I evaluated technologies and shared feedback about my developer experience. Finally, I also proposed some improvements for software development processes within the company.
I contributed to a huge 4-years-old-plus codebase for a Django application which had been migrating its templates to React. The work entailed maintaining a marketplace for trading assets and leveraging royalties from them. The back-end features relied heavily on document processing (e.g. parsing assets' catalogs), while the UI allowed for fine-grained user-interactions related to trades and sales, such as auctioning assets, requesting valuations, presenting sales and resales histories, etc.
I developed a high-frequency trading UI for an exchange broker which made use of WebSockets for real-time live trading data. The UI was entirely customizable, as it allowed for arbitrary stateful widgets to be placed and removed from a tiled grid using drag-and-drop gestures and keyboard shortcuts. Widgets could also be detached from the grid and moved into a pop-up, while still maintaining interaction with the main window. The UX was tailored towards experienced traders accostumed to "Bloomberg Terminal"-ish interfaces, thus navigation was keyboard-focused, featuring lots of shortcuts. Interactions within and between components made heavy use of event listeners.
I evaluated the business viability of several different technologies by developing prototypes and documenting my experience while doing so. The criteria entailed: tooling and editor support, developer productivity, debuggability, ecosystem maturity, onboarding cost, etc. Among the trialed technologies, notably: React-Native, Flutter, CMSes, miscellaneous tools for project maintenance.
I built an interactive 3D model for Drawbridge, a cybersecurity-related hardware product, using Three.js and React.
First I validated the viability of F# through prototypes such as: ergonomic interop between C# and F#, serialization and encoding libraries, websockets, asynchronous task execution model, etc. After successfully landing a back-end + app MVP, I worked mostly as a front-end developer using the Elm architecture for Fable (Elmish).
I worked on a Vue SPA which enabled international students to send university applications from anywhere to anywhere in the world.
As a front-end developer, I queried a GraphQL endpoint for filtering and presenting universities. GraphQL Mutations were used primarily for saving favorite lists, editing the profile, filling out applications, etc. On the social network side of the app, WebSockets were used for real-time interaction with other students, such as chat messages, friend requests, etc.
Outside of API interactions and coding the UI, I also coordinated the responsiveness and presentation efforts with the design team.
I joined in the startup's early days, just after graduating from college. Although my performance was commended, I ended up not staying in the company for long due to personal issues I was going through outside of work. Despite my short stay, I managed to greatly improve the administrative dashboard and miscellaneous components throughout the application, such as a custom PDF viewer and embedded video players.", "The product was a digital learning platform for university students. Its stack was based on Rails + ERB with React for a few specific pages.
During college I was hired as an intern for developing a nationwide government health telediagnosis platform. This was a government-funded research internship position in which I got to interact with various teams, health institutions and public servants.
The platform revolved around contextualizing and presenting information from a massive PostgreSQL database, backed by PostGIS, for doing geographically-aware health data aggregation throughout all cities and states across Brazil.
My job was to rewrite the system from Django (Python 2) to Laravel (PHP 7). My most particular contribution was designing an API layer on top of Laravel's ORM which resembled Django's, as well designing reusable Controller abstractions for the APIs.
During college I was hired as an intern for developing a Cordova-based UWP MOODLE mobile app. This was a government-funded research internship position in which I had FUNCERN (a government agency for fostering tech innovation) as my stakeholder.
The app's main novelty was that it automatically and seamlessly persisted all visited content for offline access. Instead of using MOODLE's PHP extensions, I created a .NET WebAPI by reverse-engineering MOODLE's native functionality and database.