Tech Blog

Our engineers share what it takes to build Pixability's powerful technology.

Our Engineering Process – Part II: Doing “Done Done”
Posted by Pete Martin, VP of Engineering

Introduction At Pixability we always look for areas to improve and systematize our development processes. Often changes are motivated by a particular need or objective. In this post I will describe how the SCRUM methodology, and principles behind the Continuous Delivery motivated some of the processes we adhere to today. There are certainly other roads […]

Taking the Python 3 Leap
Posted by Dan Kolsoi, Backend Software Engineer

Why Upgrade to Python 3? Forget the type annotations, asynchronous generators & comprehensions, and many other cool features — the single most important reason for upgrading is that Python 2 is approaching its End of Life in 2020. Even Instagram is making the switch. With the majority of Python’s most popular packages supporting both versions, […]

Our QA Strategy in an Agile Environment
Posted by Andrew Fernsten, QA Director

At Pixability, our QA team is made up of a director, two manual testers, and two automation engineers. Our Engineering department operates on a two week sprint cycle where the QA team spends the first three days on regression, followed by an application release. During the rest of the sprint, you’ll find us testing sprint […]

Our Engineering Process – Part I
Posted by Pete Martin, Vice President of Engineering

In this series, we share our thoughts on how we select engineering and development processes at Pixability. While this post is non-comprehensive, it should give you an introduction to how we operate and what we believe in. In Part I, we discuss the team, the basics of SCRUM, and our approach to dividing our work […]

Debugging Javascript Apps
Posted by Doug Turcotte, Web UI Engineer

Debugging Javascript 101 Every engineer has experience debugging — often quite a bit of it — so it can be a challenge to approach the topic without stating the obvious. However, even when people are familiar with the necessary tools and tricks, they may still have blind spots. So here’s a holistic overview of debugging […]

Balancing Business and Engineering Risk
Posted by Dan Golder, Product Manager

What’s a higher priority: this bug that impacts a handful of customers or this user story that’s vital to our company goals? Where should the user land after completing this form? What should that dialog box say? Should the user be able to relate one of these new objects only to a single thing or […]

Data Science @ Pixability: How Scrum Works for Us
Posted by Angela Ambroz, Data Scientist

Like many data scientists, I work in a field that did not formally exist when I finished university. The novelty of the field — and its amorphous boundaries — give data science teams both the liberty to and the challenge of defining not only what data scientists do, but how they do it. Scrum is […]

K.I.S.S. your Database
Posted by Pete Martin, VP of Engineering

Over the last 20 years I fought a fierce battle against RDBM schema constraints and enhancements of all kinds. We are talking about things like: not-Null column constraints check-constraints (enumeration values limitations, regular expression checks) foreign key constraints But also: default values embedded comments Adding schema constraints was for the longest time believed to be […]

A technical design pattern for handling complex views in web apps
Posted by David Colwell, Head UX/UI Wrangler

When you first start building an app, you often start with simple views. But in the real world of enterprise apps, nothing ever stays simple. Users or product managers ask for new features, new bits of information, and new ways to get to the specific set of data they need to do their job. Soon you need to start relating data, computing values or generating display strings, and filtering one collection of data based on selections from another. It gets complicated!

Agile Morphing Part 2: Chaos Days
Posted by Pete Martin, VP of Engineering

Overview In this short blog series, we examine how software development teams evolve and grow in size, from one engineer to close to 25. As Pixability reaches the end of this stage in its development, we are again preparing for an Agile reformation, of sorts. In the first post in this series, we looked at […]

Page 1 of 212