I treat myself as a product. So I ran the jobs to be done method on myself - 9 things I actually switched to, walked through step by step, down to 4 jobs. My work and my posts sit under those jobs.
How this was run: it is a desk interview. Nobody asked me these questions live. Every quote below is lifted word for word from one of my own posts, and where a post says nothing, the cell is left empty. The grouping and the job sentences were drafted with Claude from those quotes. They are a first pass.
The customer is me, day to day, at work and after it. In jobs to be done, a job is the progress someone is trying to make. You find it by looking at a switch - the moment they hired something new and fired what they had.
So only switches count here. Each one has to have happened, it has to have replaced something, and I have to have written about it. Things I only thought about are left out until the last step.
A switch does not happen in one moment. The method walks it through eight stages, starting at the commitment because that is what people remember best, then back to the first thought. Open one to read it in my words.
“This site is the first thing I've shipped in years that's fully mine.”
“But something kept nagging at me..”
“it just got hard to keep up with the tech stack, and tough to do code and POCs”
“VSCode with Cline and LM Studio basically got me to actually open a terminal again”
“then Cursor made it less painful”
“Claude changed it for me, not because it writes the code, but because it keeps up with where my head is going”
Not in the post. Still to ask.
“I'm not giving that feeling up again”
“Now I don't leave them.”
“by the time I had something working I'd already see like three more things that needed to change”
“because I knew I wouldn't finish, most of the time I wouldn't even start..”
Not in the post. Still to ask.
Not in the post. Still to ask.
“something changed for me about a week into building this site..”
“it didn't make me relax my standards, it's actually the opposite”
“I do a quick 10 second test on a page, is it communicating what it's supposed to”
“It started with my character sheets.”
Not in the post. Still to ask.
Not in the post. Still to ask.
Not in the post. Still to ask.
Not in the post. Still to ask.
Not in the post. Still to ask.
“getting the small facts right mattered more to me than polish”
“my next video is basically a script”
“so I had it interview me instead and learn from how I actually talk, and I rewrote this post that way”
“If a tool is going to write for me, design for me or publish for me, it has to meet the same bar I hold myself to”
Not in the post. Still to ask.
“I wanted to see if my taste could carry over to a tool”
“I used to give a lot of examples of what I meant and what I didn't like, and then I would harden the eval..”
“Months later I still felt my posts didn't sound like me”
“I write the ideas first and then ask AI to expand them, I don't ask it to start from scratch”
“It got cleaner over time, not because the model changed, but because the corrections added up.”
“in July I started building one for myself on my Mac”
“dictation tools became really good, still I had issues”
Not in the post. Still to ask.
“The first problem was my own name.”
“Parakeet is faster and it's the only one that can type as I speak, but in my tests it turned Venkatesh into Vaynkutesh”
Not in the post. Still to ask.
“The first thing I asked for was that it works fully in my local for free”
“it's my first utility product that I created for myself that works”
“Every change starts as a spec, a feature or a bug written down first, the spec names a branch, then comes a plan, then a test, and only then the code.”
“I didn't want to just talk about AI-driven development, I wanted to use it from my side”
Not in the post. Still to ask.
Not in the post. Still to ask.
Not in the post. Still to ask.
Not in the post. Still to ask.
“that's why I went spec-first”
“And it's enforced, not just a habit.”
“We filmed the empty flat, added the floor plan, and walked through it in 3D.”
“Looking at one wall at a time in 2D, we couldn't see how it all comes together.. does the sofa go with the paint?”
“For the last two years I tried free apps and Procreate..”
“last year I also paid for Marble, by Fei-Fei Li.. that didn't work either”
“The free apps weren't good enough, and drawing the rooms ourselves on the iPad didn't get us there.”
“Then I tried Opus 5.5, and it was such a pleasant surprise.. it could fulfil my vision.”
“We still want the designer to design it, we just want to get the most out of them by knowing what we like before we sit down.”
“Bidri looked okay wall by wall, but not as a whole home.. so that was a reject, and 3D settled it in one look.”
“So I did the Stanford machine learning specialization, all four courses, about four months, alongside the job.”
“The first time I really felt that was with cloud, about seven years back.”
“Certifications don't replace that, what they add is structure..”
“Then I moved into leadership, and the work started changing a lot faster.”
Not in the post. Still to ask.
“at that level you're expected to have a point of view on day one”
“I went after three things, machine learning, human behaviour and design thinking.”
“it didn't really change what I was aiming for, it changed how often I get there”
“I wrote what each offer says, decided when it's allowed to show up, built it, and set up how I'd measure it.”
“They're probably interested in different sides of things.”
Not in the post. Still to ask.
“I came across a talk by David Khourshid on state machines and really liked that way of thinking”
“I started with a long list of nice moments I could show people, and then I asked, okay, when would what happen?”
Not in the post. Still to ask.
“I think a page that does less is better than one that keeps changing on you.”
“I don't know yet if it helps.”
Two forces drive a switch - the push of what is wrong today and the pull of the new thing. Two resist it - habit, and anxiety about the new thing. The push is where the job shows itself.
“That gap between thinking and building, that used to be where my momentum died..”
“it keeps up with where my head is going, fast enough that I don't lose the thread”
“It wasn't that I couldn't learn it again, I just couldn't get myself to break the ice..”
Not in the post. Still to ask.
“a flow with one step too many because fixing it would take another hour I didn't have”
“for the first time I feel free to hold myself to the standard that I actually have”
“I knew these were off and I left them anyway”
Not in the post. Still to ask.
“The old constraints kept me from starting.”
“Now I can go from an idea to a finished video in my own voice”
Not in the post. Still to ask.
“At one point I said it all felt more childish than credible”
“Someone describing me uses words I'd never say and reaches for fancy language, and that's not a small miss, it's a different person.”
“it gives me something I don't need to correct”
Not in the post. Still to ask.
“does this sound like me, or does it sound like someone describing me?”
“I wanted my surname typed, it is Vemuri, but the software kept using it as memory..”
“it should work for your pronunciation, your dictionary”
“If a tool you can download already gets your words right, you probably don't need to build anything..”
“a stack like this can get obsolete pretty quick anyway”
“mostly works and looks right aren't the same thing”
“I think taste without checking is just an opinion.”
“You can build something, it mostly works, and you ship it.”
“I didn't want everything to be slop and unmaintainable”
“Each drawing shows a single wall well, but you can't tell how two walls look against each other”
“it's worth seeing the whole of it before the work starts”
Not in the post. Still to ask.
“I also wouldn't have committed to an industrial ceiling in a home without seeing one first”
“it was a different kind of engagement every few months, a different domain, different constraints, a different idea of what good looks like”
“What I didn't have was a technique to get there every time, instead of by feel.”
“For most of my career, I basically learned on the job.”
“almost everyone with a strong opinion on it has something to sell”
“I wanted the site to cater to each of them differently, instead of giving everyone the same thing”
“I like using my own site to try new tech and see how it actually works.”
Not in the post. Still to ask.
“The first version did too much. It changed the page six times in forty seconds.”
Now the switches get compared with each other. Two belong together when the same kind of push started them, even if what I built looks nothing alike. This grouping is a first pass, and it is the step I expect to change most.
In these three the push is speed. The idea moved faster than my hands, so I did not start. None of them is about picking between options or fitting a tool to me.
Here the generic thing already worked. Speed was not the problem. The push was the last part that was wrong for me, and only me.
These are about trust before a decision. Building was already possible. What was missing was a way to see or prove the result before it became permanent.
The trigger comes from outside. The work changes and I am expected to know. What I hire is exposure, and my own products are where I get it first.
Each group becomes one sentence. It names the situation, the progress and the outcome, and it never names a product. Then the three sides of the job - what it has to do, how it has to feel, and how I want to be seen.
When I am holding a clear picture of how something should work, with only evenings to build it, enable me to keep up with the idea while it is still moving, so that I can finish it to the standard I actually have.
When I am using something that works for most people but not for my name, my words or my taste, enable me to teach it what is mine, so that I can use what comes back without correcting it.
When I am about to commit to something I will have to live with, enable me to see the whole of it and check it first, so that I can make the call myself and stand behind it.
When I am expected to have a point of view on something new, enable me to learn it on something of my own first, so that I can speak from what I have done.
The work is on the work page.
84 of 108 cells have an answer in my own words. The other 24 are the questions for a real interview - mostly what kept the old way in place, and what happened between the first thought and the commitment.
I have said I want to build these. Nothing has been hired or fired for them so far, so by the method they stay as candidates until a switch happens.
Discovery is continuous, it doesn't stop.. and I think sensing and shaping the problem is as important as solving it. So this page doesn't end at 4jobs. It ends at what I haven't looked at yet.
Below are 33guesses across a day, a week, a year and the big moments. Each one is what I think I use today, and what seems off about it. These are guesses, not findings. I drafted them with Claude from my tools and my notes, and I haven't checked them against what I actually did. A guess only becomes a switch when I actually hire something for it.
I'm up before the work day starts, and this hour is actually mine.
Today · My phone, and whatever I remember from last night's session
Seems off · Work mail and my build ideas show up in the same feed.
Today · Coffee, a sketch, some reading
Seems off · The hour just goes if nothing holds it.
I keep it simple and pick one thing that stands out.
Today · What I remember of my wardrobe, and whatever is at the front of the shoe shelf
Seems off · I end up wearing the same few pairs and forget the rest.
Back-to-back conversations, and each person expects me to remember the last one.
Today · Scrolling the chat, the calendar invite, my memory
Seems off · What I committed to is spread across calls that nobody wrote down.
Today · A notes doc for each person
Seems off · I write the notes and then they don't come back up at the next one-to-one.
I get a few free minutes and there's an idea that's only half there.
Today · Voice memos, messages to myself, my transcriber
Seems off · They pile up and I basically never open them again.
A client problem comes in and nobody can say exactly what the problem is.
Today · My course notes in Obsidian, the design tools skill
Seems off · The frameworks are in my notes, not in the room when I need them.
Today · Going over the day in my head on the way home
Seems off · I made a lot of decisions and there's nothing to show for it, so the day feels empty.
The studio day is done, and now I get to build.
Today · Re-reading the status board and the last session
Seems off · Every evening I spend the first part just remembering where I was.
Today · The spec board, and my mood
Seems off · The board tells me what's important, not what I have the energy for.
I'm deep in a build and the agent is doing half the typing.
Today · Render checks, CI, and looking at it myself
Seems off · To know it actually works I have to check a terminal, a pull request and a browser tab.
Today · The blog and reel skills, when I remember to run them
Seems off · Publishing feels like a second project, so I keep pushing it.
I close the laptop but my head is still on it..
Today · A note to myself, and a few tabs left open
Seems off · Next day I start from the tabs, not from the note.
Work commitments and my own builds, and only one calendar.
Today · The calendar and the spec board, side by side
Seems off · They're two separate things and they never meet.
I'm halfway through a lecture and the notes keep growing.
Today · The course knowledge base, in Obsidian
Seems off · I take notes faster than I use them.
I have to sum up the week for people who weren't in it.
Today · A status deck that I write as the week ends
Seems off · Writing it takes the same afternoon I'm reporting on.
A free day, and too many ideas.
Today · My mood.. the newest idea usually wins
Seems off · A new idea always beats the one that's half done.
Today · Bank alerts, and my memory
Seems off · Every tool bills on a different date, in its own dashboard.
Appraisals at work, and a new financial year at home.
Today · Memory, scattered notes, self-reviews
Seems off · The best things someone did in the year are the ones everyone forgets.
Today · An accountant, a spreadsheet, and a rush in March
Seems off · The numbers are in too many logins.
Long evenings indoors, which is the best building weather.
Today · A feature spec and good intentions
Seems off · There's no deadline in the season, so the scope keeps growing.
Home, family, and the busiest weeks to travel.
Today · Shopping at the last minute
Seems off · I remember what each person would love when it's too late.
Today · Checking fares when I remember
Seems off · By then the good options are gone.
The year is ending. A trip, and then a blank page.
Today · Git history, my photos, my memory
Seems off · What I did in the year is split across repos, posts and trips.
Today · The travel reel skill
Seems off · Picking the photos is the slow part, so nothing gets posted.
A country I haven't been to yet.
Today · Blogs, saved map pins, friends
Seems off · Every guide is written for someone else's taste, not mine.
Today · Photos, and the odd note
Seems off · By the flight home I've already lost the details.
It shows up fully formed and I get really excited.
Today · The excitement, and my Real Win Worth It notes
Seems off · When I'm excited I skip the test.
Something of mine goes public.
Today · The blog skill, and a post I write afterwards
Seems off · I write the story after the energy is gone.
Today · A quick look at analytics
Seems off · I look at the numbers without a question in mind, so they don't tell me anything.
A room that matters, and not much time.
Today · The storytelling framework, and a deck
Seems off · I only rehearse in my head, and in my head it always goes well.
Time for a different hair colour.
Today · My imagination, and a brave stylist
Seems off · I only get to see it when it's already done.
I wonder what all of this work adds up to.
Today · A resume, the site, long walks
Seems off · The resume lists my roles, not what I made.