Staff Software Engineer - Forethought.ai
Worked on the platform team, building services and infrastructure that power all the company’s products. I Automated Elasticsearch management, index resizing, and refreshing with zero-downtime migrations. Architected and led the execution of the service that proxies all machine learning model inference requests for all products handling more than 28M reqs/day. Led the initiative for exposing controls across all products to customers through self-serve mechanisms with authentication and authorization built-in Designed and Implemented circuit-breakers to avoid service exhaustion when downstream microservices fail. Laid out foundations for reusable components for internal tools used in various internal applications across teams, including machine learning training and deployment.
7 Reasons you should use ES6
I am a Systems Engineer and developer with more than 6 years of experience. I started my career at a small web development studio that outsourced engineers to work at a large agency in upper NYC. I applied with zero background experience and only a few semesters in engineering; I was hired after completing a few Java programming exercises correctly. Whether I was hired with low expectations to do trivial parts or to learn to develop something is still being determined to this day. What is clear is the results a few months there had in me.
We live in a software revolution. It is just a matter of when it will explode. What happened a very long time ago with (big) hardware in the industrial revolution is going to happen again with software (and then again with ai). We live in a day where Machines aren’t specific anymore. A 3D printer can make a piece designed to be made by a machine half the world away. We don’t need to import highly specialized machinery from Germany to build car parts. We can print metal, circuits, and everything, anywhere. We will need the design of that required piece, and we’ll be able to print it anywhere from Australia to Manhattan.
“Crypto Wars” is the name of the US government’s attempts to limit the public’s and foreign nations’ access to cryptography strong enough to resist decryption by national intelligence agencies. Restricting access means weakening encryption to allow the government to intervene in any encrypted information. The people won the crypto wars in 2005 and were allowed to encrypt as desired.
From Joel on Software
As we progress toward better software, reading has become one of the most important things to do. Practice makes perfect, yes. Implementing all sorts of algorithms makes you the wizard of that specific language. But it is reading that expands your mind on new concepts. This time, it’s Joel on Software. Almost every programmer I know has heard of Joel’s blog. And yet, very few have read it deeply.