• +

    Validating (or Invalidating) Designs in 90 Seconds

    We’ve been hard at work on some new designs (coming soon!) that we’re hoping make it easier to get around on the site, and also allow users a rich experience regardless of how many cards or products they link to their PayPerks accounts. But how do we know if the designs are any good?

  • +

    Taming the JavaScript spaghetti monster

    Generators and iterators have arrived in JavaScript and with them comes some powerful new functionality. I’d like to take a quick look at what generators are, their behavior in JavaScript and how to use them to manage asynchronous code.

  • +

    Fintech Hackathon 2013

    FinTech Hackathon 2013
  • +

    Introducing the One Day Sprint

    Last week we tried an interesting experiment: a single day sprint. We wanted to condense our two week process into one day and see if it would yield any insights or highlight problem areas.

  • +

    Why you should be doing code katas (hint: it’s not why you think)

    I’m sure most of us have heard about code katas. I’d like to argue that you should be doing them, but not because of the reasons you think. For those unfamiliar with the term, a code kata is a discrete coding exercise undertaken regularly to keep coding skills sharp. The idea is that developers should spend time practicing their skills so that when they need to code “on the job” they’ll be better at it.

  • +

    Clean Code

    “Like everything metaphysical the harmony between thought and reality is to be found in the grammar of the language.” — Ludwig Wittgenstein

  • +

    Welcome to the PayPerks Tech Blog

    We’ve been hard at work coding, testing, deploying, maintaining, and improving our platform (multiple apps, running on AWS) over the past couple of years. Having directly benefited from the open source community in big ways and small (“surely someone has already written a package for that!”), along with the thoughtful advice of others who have gone before us and taken the time to write about their experiences, we decided as a team it was time to spend some of our time writing about what we’ve done, what we’re doing, and what we recommend you may or may not want to do or not do.