Just wanted to add that the position is REMOTE for US residents only.
21 karma · joined November 1, 2018
Gravity Legal is a fast-growing SaaS platform that helps small and medium-sized law firms accept client payments and manage money. Both the backend and frontend are primarily written in Typescript. The frontend uses React, MobX, Bootstrap and Webpack frameworks. The backend uses TypeORM for persistence. AWS deployment makes use of a number of AWS technologies: Lambdas, Aurora RDS, Cognito, SQS, SNS, S3, CloudFront, EC2 etc. We use Serverless Framework for packaging and deployment.
You will share responsibility for the overall design, evolution and operation of the platform with other technology leaders in the team. You will work with the marketing team to understand business requirements and help translate into technical architecture and design and be an expert on technical aspects of the platform, performing design and code reviews, merging code to the master branch, making deployments and troubleshooting the production system.
More details about the job and company at https://gravitypayments.com/careers/?gh_jid=4800641002
The coronavirus has thrown a lot of curveballs and each has sent impacted groups looking for answers. As OP correctly concludes, there are no good answers. Only worse and bad ones.
Besides the original problem, the OP's analysis is well presented and brings out the worse in this not so well thought out solution. I hope IB is listening and is willing to adjust their model to address issues pointed out by the OP.
1. Earlier use of VMs and now Docker containers -- It was around 2004 that I got introduced to VMware tools to create, configure and run VMs. Life was never the same after that. No more fretting about installing pre-beta software for the fear of hosing my perfectly working system. There was a time when I had multiple servers running VMWare hypervisor, each running multiple systems. Then around 2014 I switched to using Docker containers for similar purposes and haven't had a need to use VMs.
2. Jupyter notebooks/pandas/plotly -- Can't imagine how one can explore data without this.
3. SQLite -- Perfect for writing unit tests for code that deals with SQL databases.
What I liked: 1. No grand philosophical statements about functional programming paradigm or how awesome is React. (Most tutorials I have seen spend more ink on these than on the real stuff) 2. Easy way to install the tutorial and validate exercises. 3. Using React to teach React (the tutorial is a React program but this aspect is not emphasized).
My suggestions to the Author: 1. Leverage the fact that the tutorial itself is a React program to go one level deeper. This probably would require its own set of pages, each page emphasizing a different aspect such as Router and other components. It took me a while to appreciate that Components are not only for visual elements but they can also change behavior (example: Router). 2. Use HMR to load only the Solution component so that only that part of the page changes when the reader saves his edits. This will be a great showcase of React's power of applying only delta changes to a page. 3. This is a minor nit: the color of numbers in the tutorial is too close to the color of the background. Please use a different color.