[ETR #96] Tokens or Time?


Hi fellow data professional!

This week I’ve gotten back into something I haven’t even attempted since my college intern days: Meal prepping.

Prep is a priority for me since I’m watching my son (and our pets) solo while my wife is away for work.

And, I hate to say it but, I somewhat agree with Sam Altman’s controversial quote about not understanding how people parented before widespread AI adoption; when used properly, AI-generated “parental assets” like meal plans, budgets and workout routines can buy back some serious time that can be converted to precious father-son bonding opportunities.

If you’re job searching while parenting or even while working a demanding job I’m sure you’ve thought about or implemented automations to carve out precious extra minutes.

With discussion about rising energy costs and AI subscription costs steadily increasing, working devs and learners are grappling with a choice I didn’t have to make while learning data science.

What is more valuable: (AI usage) tokens or your time?

We are entering an era of 'Peak Token Volatility.' With AI expected to drive an 8% spike in national electricity costs by 2027, the industry is moving away from unlimited 'all-you-can-prompt' plans toward metered, high-efficiency system designs.

I ask you this question not just out of intellectual curiosity but because I believe this may soon be integrated into interview processes, especially those dealing with system design.

Although AI wraps resource allocation in a shiny new layer, weighing tool cost against finite dev time isn’t a new discussion.

One of the pillars of data engineering (and software engineering in general) is the deployment of automatic systems that enable the seamless delivery of data.

Expect interview questions that probe your ability to free up time blocks by utilizing the appropriate AI stack within an org's budget constraints.

Scenarios like—

  • How would you use an LLM “planning agent” to streamline requirements gathering so we don’t have redundant meetings about expectations?
  • What guardrails would you implement to ensure we don’t blow through our allotted token budget on one project?
  • How would you transform source data so you use the least amount of tokens possible when training an LLM to execute your project tasks?

Notice none of these questions are: What prompt would you use for x? Or why this agent over that agent?

You may even see future take-home assignments with constraints like “Use an LLM or agentic workflow to complete this in 2 hours max.”

To this working engineer, there’s some merit to those concerns but for a manager they want you to demonstrate you’re a resource-minded dev.

And even while job searching you may hit a wall where you’d literally rather pay an AI subscription to streamline applications rather than “grind out” responses to 5-10 per day.

Maybe you’re confident enough in your existing coding skills to crank out a Python-based automation with minimal generated code. Or you may be willing to hand all your work to Claude.

Pay attention to your personal threshold.

Because resource consumption issues are only projected to compound so soon the choice could be tougher.

But even with rising costs, no ROI will be as satisfying and productive as “buying back” the most finite resource of all: Time.

So I ask you...

Thanks for ingesting,

-Zach Quinn

Medium | LinkedIn | Ebooks

Extract. Transform. Read.

Reaching 20k+ readers on Medium and over 3k learners by email, I draw on my 4 years of experience as a Senior Data Engineer to demystify data science, cloud and programming concepts while sharing job hunt strategies so you can land and excel in data-driven roles. Subscribe for 500 words of actionable advice every Thursday.

Read more from Extract. Transform. Read.

Hi fellow data professional! SQL Lite, the database you most likely learned SQL on, is built atop 100k lines of source code. Sound like a lot? Compare that to Chromium, the engine for Google Chrome, which boasts 30+ million lines of code under the hood. Shortly after acquiring Twitter/X, the world's first trillionaire, Elon Musk, famously asked engineers to tell him how many lines of code they wrote per day, igniting a debate among engineers throughout the software and data domains. When I...

Hi fellow data professional! If you read my note on Tuesday you’ll know I’m coming off of the data engineering week from hell that seeped into my personal life, and delayed the launch of something cool I was planning to share with you; if you want to know more about that, scroll to the end of this message. Last week a flagship data source had a major problem and since it’s within my ownership area, I was the one with the knowledge and responsibility to fix it. I wanted to share the experience...

Hi fellow data professional! Hardly a work day goes by without receiving a request from a data analyst. They range from the mundane “Can you add this column?” to the occasional emergency “The data didn’t load all weekend and the leadership call starts in 15 minutes!” At the end of a jam-packed week I received an unusual request: Help with a Python script. My teammate wanted to know: Best practices How to commit to GitHub What the best way to deploy is They admitted the task was simple,...