atandy
Recent Tech Decisions
47 points

Following

  • Flask

    atandy Job Operative


    I used Flask because it's lightweight and I've used it many times before.

  • Redis

    atandy Job Operative


    I used Redis as a queuing backend because I'm familiar with it, it's fast, and it's well supported with Python libraries.

  • PostgreSQL

    atandy Job Operative


    I used PostgreSQL because it more elegantly handles a lot of existing issues that MySQL has, like storing true UTF-8.

  • jQuery

    atandy Job Operative


    I used jQuery because I live in the early 2000s, and I don't love Javascript.

  • Python

    atandy Job Operative


    I used Python because I love Python.

  • MongoDB

    atandy Job Operative


    I used MongoDB to store entire JSON API responses from external APIs.

  • Amazon S3

    atandy Job Operative


    I stored attachments like resumes on Amazon S3 for speed/ease/long-term thinking about scalability.

  • Keen

    atandy Job Operative


    I used Keen because it was an extension that could be added through Heroku. It was very easy to set up application metrics and dashboards with them.

  • Mailgun

    atandy Job Operative


    I forward all e-mails to Mailgun and appreciate being able to access the objects easily as JSON.

  • Twilio

    atandy Job Operative


    I set up text-message alerts to be sent to me when an error was raised on the web application.

  • Heroku

    atandy Job Operative


    Deployed to Heroku. Mostly a choice out of ease and good command line tools.