# My Job Hasn't Changed. My Day Has. > Source: > Published: 2026-08-14 12:25:08+00:00 Times are changing, my role is changing, my focus is changing, my impact is changing. But in essence – I'm still doing the same. I still build products that drive impact. Only my day-to-day looks completely different. The shift is happening, sooner or later, if you want it or not. Whether or not you can cope, is all up to you. In the past, I was neck-deep in code. That was what the majority of my time consumed. I liked it, building things, building products. These days, that's all done by an endless amount of AI agents. I barely touched any code in the past half year – if not even longer. The work that used to go into a feature now goes into the process that produces the feature. Instead of losing the first hour of my day to Slack and email, I built a small stack of scheduled agents that hand me a briefing before I even open my laptop ([already wrote about that one](https://dev.to/jensreynderstech/pushing-my-own-boundaries-using-ai-to-start-the-day-already-briefed-4871)). Instead of reading every pull request line by line, I set up a review loop where agents do the first pass and I stay on the hook for whatever they flag. None of it started as a plan. Each piece started as one specific annoyance I got tired of and fixed. That's the actual mechanism: improve one small thing, it saves you time, you reinvest that time into the next small improvement. Compounding, not a grand strategy. The question I try to ask myself daily is simple: how can I do my job a bit better today than I did it yesterday? Not more. Not faster. Better. I also don't run ten parallel AI workflows across different projects at the same time because someone told me that's what a serious AI-software engineer does now. If I have multiple projects going on, I only focus on one project at a time. That's the amount of mental space I have right now, and I've stopped treating that as a shortcoming. The time that used to go into implementation didn't disappear, it moved upstream. I now spend more of it making sure we're building the right thing in the first place: more time actually in front of the client trying to understand what they're after, less time assuming I already know because I've built something similar before. More attention to how the product actually gets used, not just what the ticket describes. As a tech lead, my impact is measured by how well my team performed and how healthy the product and codebase are. In the past it was difficult, because there are still code delivery expectations. These days, I have more time and mental space to focus on the conditions I create for the team: whether the setup lets people move fast without breaking things, whether they have enough context to make good calls without pulling me into the room, whether we spend review time on things that actually matter instead of formatting nitpicks. I build less myself and design more of the environment other people build in. That's a different kind of impact, but it's still impact — and a bigger lever than anything I could ship solo. So what am I, if not someone who writes code all day? Mostly a decision-maker. Engineers have always automated the boring parts of the job so they don't have to repeat them — AI agents are just the biggest thing we've had to offload to yet. I hand agents the execution: writing the implementation, doing the first pass on a review, drafting the report. What stays mine is the follow-up and the outcome — whether it actually solved the problem, whether it holds up, whether it's worth shipping at all. That's the shift in one line: I used to get paid mostly for output, now I get paid mostly for judgment. The code was always a means to an end. It just used to eat most of my day, and now it barely does. That's the honest answer to what I actually do now versus what I did two years ago. And I think that's great! I like that my impact increased, I like that I can focus on the outcomes instead of outputting code. And the best part of it, I still tinker and build stuff!