Bigger Isn't Always Better

One of the most difficult decisions we make is deciding where we’re going to spend (at least) eight hours a day, five days a week, for potentially years on end. Yet the things we weigh as deciding factors aren’t always in sync with what we actually want from a job, which is a realization that often comes too late.

Read more...


Working With Oncologists @ Flatiron Health

One of the main advantages of being an engineer at Flatiron Health is the opportunity to collaborate with talented individuals from a variety of non-technical backgrounds. For instance, the oncologists we work with provide engineers with important context for our day-to-day work and make our analyses insightful and actionable. Oncologists at Flatiron are engaged with their colleagues in traditional ways: attending standups, reviewing tickets and Google Docs to answer questions,...

Read more...


Don't Cancel The Retrospective

First published on venturebeat.com

Read more...


Hitting the Ground Running: Reviewing Code as a New Engineer

This August, I was extremely fortunate to join Flatiron as a new grad software engineer. The transition to my first full-time software engineering job out of college presented some unique challenges.

Read more...


How To Fixit: Keep it simple. Take a day. Make it fun.

Though the term technical debt often has a negative connotation, it is a common and often healthy side effect of rapid software development. Just as taking on a mortgage can be a well-calculated decision for an informed homeowner, amassing some technical debt to get a product out the door can be necessary. And, just as the buyer pays off that loan over time while thriving in a new home, a...

Read more...


Uniqueness in PostgreSQL: Constraints versus Indexes

While doing a bit of database cleaning, I noticed many tables with more than a few indexes and constraints. In particular, a few tables had both a unique index and a unique constraint for the same column. Constraints and indexes come at a cost: they add write overhead with each INSERT and UPDATE and they can take up significant amounts of space. Since a unique constraint and a unique index...

Read more...


Load more... Loading...