Chapter 65. Tech Should Take a Back Seat for Data Project Success
Andrew Stevenson
Data has always been a constant in my career. From my early days as a C++ developer tthrough my switch to data engineering, my experience managing increasing velocities and volumes of data for use cases such as high-frequency trading has forced me to lean on cutting-edge open source technologies.
I was one of the fortunate ones. I worked with an elite set of handsomely paid developers, at the peak of the big data revolution. Cutting-edge as we were, managing the technology wasn’t our biggest challenge. Our top challenge was understanding the business context and what to do with the technology. As a dev, I shouldn’t be expected to configure complex infrastructure, build and operate pipelines, and also be an expert in credit market risk.
Time and again, I witnessed business analysts sidelined in favor of data engineers who spent all day battling open source technologies with little or no familiarity with the context of the data or the intended outcome. The technology-first focus often led to Resume++, where technologists were empowered and enamored with technology rather than focusing on business objectives.
The result was slow progress, project failures, and budget overruns. This especially hurt businesses during the 2008 crash, and we’re seeing that impact again starting ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access