GraphQL back-end for a React app*
* Real name obfuscated because of an NDA
Started in as a part of my work as Ruby developer, UI designer and tech lead for Speed & Function
Business role
The web app was the company’s attempt to involve the end clients into the process of submitting and editing documents for their legal cases.
What it was about
A law firm based on the East cost, specializing in franchises
The application had a nice modern UI design, and offered the end clients a versatile project dashboard and document editors, with maps, diagrams, messaging etc.
My responsibilities
I worked as a back-end Ruby developer, alongside a front-end engineer and another back-end developer
- Correcting web typography
- Creating service objects for performant filter search
- Generating upsell proposals for current clients
- Videocalls with client’s team
- Writing unit tests with RSpec
Interesting things I did on this project
- Rewriting clumsy legacy HTML into correct, consise, semantic HTML that looks beautiful even with no CSS
- Rewriting controllers to reduce the number of SQL queries & lower DB utilization
What I discovered while working there
With small number of endpoints, GraphQL will only make it longer
