Tech Blog

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

Working Remotely Works
Posted by Alex Orlovsky, Principal Software Engineer

Last month, I had a Star Trek moment. While riding the Downeaster north to Portland, Maine, I alternated between coding and communicating with colleagues in Boston, Minnesota, and California via video conference and text message. I glanced out the window at the pink glow the low winter sun was casting across the snowy fields and […]

Why We Switched To A Third Party Visualization Library
Posted by Kyle Ruddy, Senior UI/UX Software Engineer

Every big data company has to grapple with a complex issue: how to deliver data to users in a way that’s intuitive to use, easily comprehended, and aesthetically pleasing. This problem can be particularly vexing at fast-moving startups, because the engineering team must support the evolving needs of customers. Starting With Flexibility Like most startups, […]

From Customers to Code – The Journey From Account Manager to Software Engineer
Posted by Ryan Whitten, Software Engineer

Four years ago, I joined Pixability as an intern on our Customer Success team. Back then, you could count the entire company on two hands. A few years later, I was managing accounts for some of the world’s leading brands and agencies. But at the beginning of 2016, I started to sense it was time […]

Taking off the Training Wheels: My Engineering Internship
Posted by Marguerite Basta, Engineering Intern

The moment I accepted Pixability’s summer engineering intern position, I knew my programming training wheels were coming off. Over the previous year, I had learned much studying computer science at university, but my perspective of software development was impeded by a lack of real-world programming experience. My studies had padded out the skills section of […]

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 […]

Page 1 of 3123