PhD students in ML, how many hours on average do you work? [D]

A recent thread from machine learning PhD students has sparked an important conversation about what productivity actually looks like when your work depends on long-running compute and AI-assisted tooling. The poster describes a familiar rhythm: nine to ten hours a day, fragmented across morning deep work, afternoon meetings, and evening sessions when focus peaks. Weekends are partly rest, partly errands, but work still bleeds through. What stands out is not the hours themselves but the emotional undercurrent — the anxiety of idle compute and the nagging feeling that tools designed to help might actually be getting in the way. These tensions are not unique to academia. Anyone navigating AI-augmented workflows, whether in healthcare exploring Healthcare (insurance, pop health, VBC) - actual AI use cases? or wrestling with How to find missing data across sprawling spreadsheets, faces a version of this same question: when does the tool serve you, and when do you end up serving it?

The poster describes a compelling paradox around coding agents. There is real pressure to use them whenever possible — they promise efficiency and a way to keep pace with relentless conference deadlines. But the experience of waiting for an agent to "think" introduces a strange new category of dead time. You are technically working, yet not actively doing anything. The agent occupies the space where your hands would be on the keyboard, and you hover between engagement and idleness. This mirrors a friction many users feel with AI integrations that disrupt rather than enhance their workspace, much like the experience of being Unable to Remove Floating Copilot Button that adds friction instead of function. When AI tooling creates new problems while solving old ones, the net productivity gain is not as clear as anyone would like to believe.

What makes this discussion valuable is how honestly it frames the emotional texture of modern knowledge work. The poster is not complaining — they are reflecting. In their third year at a top-five program, targeting major ML conferences and core NLP venues, they have built a system that works. But the system demands ambient vigilance. Slurm jobs must always be running. Every idle GPU feels like a missed opportunity. This mindset is common where compute time functions as both resource and measure of effort, but it raises a deeper concern: when productivity becomes synonymous with constant utilization, rest starts to feel like failure. The risk is not just burnout, which is well-documented in PhD programs, but a fundamental misalignment between how we measure work and how valuable work actually gets done.

The broader takeaway extends well beyond machine learning. As AI tools become embedded in every domain — from spreadsheet workflows to clinical data pipelines — the question of how to integrate them without losing agency becomes everyone's question. The promise is real: automation of drudgery, pattern recognition, accelerated iteration. But integration requires intention. If a coding agent replaces active problem-solving with passive waiting, the tool needs reconfiguring, not more of your time. The most productive people in AI-native workflows will not be those who deploy every tool the most aggressively, but those who know which tools to use, when to step back, and how to protect the deep focus that no agent can replicate. That distinction matters now more than ever.