I originally began "programming" around the age of 12 working primarily with PHP (using MySQL as a database), although I also had a limited understanding of Perl and C++.
When I entered college, I had no intention of pursuing any coursework dealing with the computer sciences, but through the workings of some cosmic joke (i.e., the algorithm in the course placement software filling one of my first-choice classes before it reached my entry) I ended up in Computer Science: An Accelerated Introduction. It was a semester of basic logic structures implemented in Python. And then I took a deep breath and dove into the next course, Data Structures and Algorithms, taught using Java. On to Web Programming and the Theory of Databases, taught using PHP and PostgreSQL. Then the Soul of the Machine which looked at how computations worked at the processor level along with examples in MIPS and C, and finally Software Design and Development put exemplified how to construct an application from requirements to deployment in a team environment.
I joined the team at REX Labs to build the REX social media platform, moving quickly from basic API solutions to the more complex task of architecting a reliable search infrastructure and data ingestion pipeline. With over 20 different external data sources and counting that were dynamically queried when our internal database lacked resources for our users, I was tasked with building a fault-tolerant, reliable service that responded automatically to overload and refusal. Along the way, I switched from Ruby to Elixir, utilizing it to scale-out the architecture at the same time as reducing the resources and the bottom line cost of running the platform.
Learning Elixir led to a change in my programming path, and I have since committed myself to understanding the Erlang/OTP platform it runs on. I found myself a regular presence in the Elixir Slack before eventually taking over the NYC Elixir meetup group to nurture the local community.
With shifting priorities in my career, I was welcomed as a member of the Timber.io team as the Senior Backend Engineer. With my deep knowledge of Elixir, I have taken on the task of crafting a reliable, scalable inbound pipeline for accepting, parsing, and storing client logs.
AutobiographerMar 27, 2017
This user hasn’t posted yet.