I am a machine learning engineer. I've been in the domain almost 12 years now (different titles and roles).

In my current role (and by no means that is unique), I don't know how to write less code.

Here are problems I am facing: - DS generating a lot of code - Managers who have therapy sessions with Gemini, and in which their ideas have been validated - No governance on DS (you want this package? import it) - No governance on Infrastructure (I spent a couple of months upskilling in a pipeline technology that were using: reading documentation and creating examples, until I became very good it...just for the whole tech to be ditched) - Libraries and tools that have been documentation, or too complex (GCP for example)

The cognitive overload is immense.

Back few years ago, when I was doing my PhD, immersing in PyTorch and Scipy stack had a huge return on investment. Now, I don't feel it.

So, how do I even write less code? Slowly, I am succumbing to the fact that my tools and methods are inappropriate. I am steadily shifting towards offloading this to Claude and its likings.

Is it introducing risks? For sure. It's going to be a disaster at one point. But I don't know what to do. Do I need a better abstraction? Different way to think about it? No clue

I've seen some success teaching data scientists how to write better code. SWE concepts like modularity, testing, and refuse. Things that they normally ignore or choose to throw out the window.

(Disclosure: I'm a corporate trainer)

I appreciate that. I am not a position though to advocate for such a change :)

[deleted]

What is DS?

Data Scientists