|
5 years ago, my data science “superpower” was code optimisation. I could take a piece of analysis code that took 30 minutes to run, and with a few tweaks, make it run in 2 seconds or less. Spoiler alert: the secret is vectorisation using NumPy. It was a trick I picked up while doing my Computer Science Masters, where several assignments included strict runtime constraints. In fact, I got so good at doing this, that I often found myself spending hours optimising code, even when the potential benefits were trivially small - shaving off microseconds and making my code marginally more elegant and precise. By the time I’d finished, my code was a work of art. Here’s the thing… Nobody cared. Yes, writing functional, efficient code is important. But at the end of the day, unless you’re working in a high-performance computing environment (such as stock-trading or self-driving cars), it usually doesn’t matter if your code runs in 2 seconds instead of 10. This is the trap so many technical people fall into. We optimise the wrong things. We spend hours perfecting code that already works well enough for the business problem at hand. The business doesn’t care if your code is beautiful. They care if it solves their problem. Focus on getting the right answer to the right question quickly. Optimise for business impact, not the elegance of your code. Talk again soon, Dr Genevieve Hayes |
Twice weekly, I share proven strategies to help data scientists get noticed, promoted, and valued. No theory — just practical steps to transform your technical expertise into business impact and the freedom to call your own shots.
Earlier this year, entrepreneur Mark Cuban posted the following on X: “There are generally two types of LLM users: those that use it to learn everything, and those that use it so they don’t have to learn anything.” As this quote suggests, AI has the potential to dramatically expand what data scientists can do. But used without care, it also has the potential to quietly erode the expertise that makes them valuable in the first place. Given my expertise took over 20 years for me to build, I’ve...
A few years back, when ChatGPT was in its infancy, stories relating to AI hallucination-induced mishaps made the news on pretty much a daily basis. From lawyers filing briefs referencing non-existent cases to government reports riddled with fake citations, you could watch people learning the limitations of AI in real time. And no organisation was too big to avoid embarrassment. Although these incidents do still occur, people are now at least starting to become aware of the very real...
Each week, it seems like there’s yet another announcement of technical workers losing their jobs to AI. In Australia, for example, tech giant Atlassian recently laid off 1,600 workers - 10% of their global workforce - “to steer more spending into AI”. Now, granted, not every AI-related job loss is necessarily as it first appears. Some experts point to AI-washing. That is, companies using AI as cover for restructuring decisions they would have made anyway. But regardless of the reason, the...