DEV Community: John Lee

The More I Work With AI, the Stranger My Focus Problem Gets

John Lee — Sat, 17 Oct 2026 07:57:46 +0000

I work with AI tools all day. Research, drafts, code: AI makes the first pass, and I review and fix it.

Some days a work document just won't go in. I reread the same sentence a few times and nothing sticks. Must be tired, I figure, and move on.

Then five minutes later an interesting conversation snaps me right back.

If I were actually tired, the conversation should have felt just as foggy. It didn't, and that's the strange part.

The "empty tank" story doesn't hold up

The usual explanation: you have a fixed amount of mental energy for the day, and once it's spent, you're done. But that story can't explain snapping back to full clarity mid-conversation. An empty tank stays empty.

Research on mental fatigue tells a different story. In one 2.5-hour repetitive-task study from 2015, raising the reward partway through made the same people's fatigue drop and their performance improve. A boring task does the opposite: it produces strong tiredness and reluctance on its own, but a 2008 study on vigilance-type tasks shows that subjective fatigue doesn't reliably track with how much performance actually drops.

So the brain isn't one battery. Sleepiness, overload, plain dislike of the task, boredom, and overstimulation are different problems that all look the same from the outside: fog.

Treat all five as one thing and the fix is always "rest."

Working with AI all day makes the mix-up worse

The easy, well-defined work goes to the AI tools first. What's left for you is review, judgment calls, reading things where the answer isn't obvious. That's exactly the kind of task most likely to produce boredom or resistance fog, not real exhaustion.

But when the AI has handled most of the typing and the research, "I worked a lot today, I'm wiped" is still the easiest story to reach for at the end of the day. What actually ran out usually isn't stamina. It's the supply of judgment calls you had to keep making.

Get the cause wrong and the fix runs backward: meditating to calm down when you're actually sleepy, or pushing through when the real problem is resistance.

A 30-second check before you rest

When the fog hits, sort the cause before you do anything about it.

Heavy eyes, yawning: you're sleepy. Get some sunlight and move, or take a short nap.
Rereading the same line: you're overloaded. Dump what's in your head into a note and cut the scope to one thing.
Everything else sounds more appealing than this one task: you're resisting it. Write one line on why it matters, then focus on it for five minutes.
Itching to switch screens: you're bored. Slow down and stay with one thing.
Thoughts racing but narrow and impatient: you're overstimulated. Cut the input and slow your breathing.

If five minutes of the right fix doesn't clear it, take a real break: twenty minutes or so. How you rest follows the cause too. If it's not sleepiness, resting means a walk or light movement, which a 2021 study found edges out watching TV for getting your head and motivation back. If it is, resting means a short nap. Five and twenty minutes are starting points, not the answer.

One thing to skip during those twenty minutes: Reels, or any recommended-content feed. Switching between short clips increases boredom instead of relieving it, a 2024 study found. Participants expected switching to help and got the opposite. Whatever you were doing also takes longer to get back into once you've been somewhere else.

How I set up the day

Diagnosing the fog handles the moment. There's also a slower layer: how the day is set up so less of it happens in the first place. Working through this, here's what I'd prioritize first.

Mornings start outside, before the feed. I get outside for fifteen to twenty minutes right after waking, before opening anything. A 2022 meta-analysis found that enough bright daylight measurably helps alertness.

The post-lunch slump isn't a malfunction. Sleep pressure builds through the morning and naturally peaks around midday regardless of what you ate, so changing your lunch doesn't make it disappear. The fix is not scheduling your hardest calls into that window.

When there's another focus block in the evening, the temptation is to push through on coffee. But that cup cuts into the night's sleep, and the next morning starts foggy. A 2023 meta-analysis found that on days with caffeine, people actually slept 45 minutes less on average: about 9 minutes longer to fall asleep, 12 more minutes awake during the night, and 11 minutes less deep sleep. A cup of coffee (about 107mg) needs roughly 8.8 hours before bedtime to avoid that loss. So coffee stops in the early afternoon, and evening work runs without caffeine.

Next time the fog hits

Nobody stays sharp all day. The fog will come. Check one thing before you rest: is this sleepiness, or is this resistance.

AI PM and Solutions Architect: The Market by Posted Salary

John Lee — Sat, 17 Oct 2026 07:57:40 +0000

Start researching this function and you'll meet numbers like these. "Senior AI PM total comp $320K–520K." "AI PM postings nearly tripled in two years." They circulate separately, and both wobble the moment you trace them. The first sits in a recruiting firm's salary guide with no sample and no method; the second appears in content-site posts with no source at all.

Here's what measurement looks like: a tally of salaries actually posted in 12,397 US job ads (Axial Search, January–June 2026) puts the median at $194K, a long way below the claim. But the units differ: $320–520K is total compensation, equity included; $194K is the median of posted salary bands. Compare total comp against posted salary and much of the gap is just whether you count equity. Compare posted bands with posted bands and AI labs still stand apart: one Anthropic PM posting lists $305,000–460,000, about 1.6x the market's posted median. That's one lab posting's band, though, not a statistic about "the floor at labs."

No corner of this series shows better why every number carries its source and its unit.

One name, two directions

Two live postings, side by side, make it visible.

Build-side (AI PM): Anthropic, PM for Claude Code model performance, $305–460K. Owns the product's evaluation roadmap and model launch planning, and the requirements include having personally built agentic eval suites (SWE-bench-style). The evals from the Application piece are, here, a hiring criterion.

Sell-side (Solutions Architect): Anthropic, Applied AI Architect, $240–315K. Works alongside sales, product, and engineering as the customer's technical advisor from discovery through deployment, with requirements of eight-plus years in roles like Field CTO, solutions architect, sales engineer, or product manager, plus hands-on building experience.

Same company, same function, different directions: build-side answers for its own product's metrics, sell-side answers for the customer's deployment. Moving between them isn't hard, though; that architect posting lists PM experience as qualifying, and the market treats the two directions as neighbouring careers.

Sell-side is less covered

Job-hunt content talks mostly about the PM side. Pay runs in two directions, though. Inside the same lab, the build side earns more: in the two postings above, the PM band starts at $305K and the architect band at $240K. Where sell-side pay has climbed is outside the labs. What AI vendors pay solutions architects has moved to a different tier from classic enterprise software. On levels.fyi, OpenAI solution architects show a median total comp of $418K and Databricks $353K (checked 3 September 2026). The caution that matters isn't self-reporting; levels.fyi verifies against offer letters. It's the sample. Neither page discloses sample size, and for a niche role like this a median can rest on a handful of entries.

The fast-growing title lives on this side too. Salesforce hires Agentforce Forward Deployed Engineers continuously in the US, and Australian postings come and go. But FDE bands vary widely by company and level (one Salesforce all-levels US posting runs $88,970–287,910 base, up to $316,750 in the big metros), so read the company and the level, not the title. What this direction wants is someone who can both build and explain what they built in front of customers. Few people do both, which is why it pays.

A warning about the titles

LinkedIn's 2026 fastest-growing US jobs list has no PM and no solutions architect in its top 25; #1 is AI Engineer, #2 AI Consultant. Growth-rate lists structurally favour small bases, so absence isn't decline. But the list does show where new demand points. And there's precedent: Airbnb retired the traditional PM title in 2023 and merged product management with product marketing into one group. When every product is an AI product, the "AI" in "AI PM" may simply evaporate.

What the first piece said applies with full force here: prepare for the work the role does, not the title. Proving a product's value in numbers, and landing deployments that survive at a customer, outlast whatever the title becomes.

The Australian numbers

Permanent solutions architects in Sydney run AUD $165–220k (Morgan McKinley $165–220k, Robert Half $180–213k, 2026 guides). For contracts, the mainstream benchmark puts roles like LLM architect and agent architect at $1,430–1,490 a day (Talent International, March 2026). Figures like $2,000–3,500 a day or a "20–35% AI premium" come from a single specialist recruiter, so don't set expectations there. In the mainstream guides, the AI premium shows up only at the top of the band, if at all.

The evidence differs by direction

Build-side: metric movement attached to something you shipped (conversion, cost, retention), plus a record of running an eval roadmap.
Sell-side: the fact that what you deployed at someone else's shop is still in production. Not a demo; a deployment that's alive three months later.

The two Anthropic postings above are senior roles. The junior path opens lower on the sell side: vendor solution-engineer and FDE bands come first, and a side project is evidence that works there. If you have one, treat it like a product. Get ten people using it and measure their usage: build-side evidence. Deploy it for another team or company and keep it running: sell-side evidence. The title comes after.

That completes all five functions: what each one measures and what it has to show. From here, the series moves to guides: actually producing each function's receipts.

AI Governance: The Rules Got Delayed, the Hiring Didn't

John Lee — Sat, 17 Oct 2026 07:57:33 +0000

Last year the headline was "AI regulation is coming." What actually happened was the reverse. Australia shelved its mandatory guardrails for high-risk AI in December 2025, settling instead for an AI Safety Institute inside the industry department, a body that tests models and tracks risks with no regulatory powers, on AUD $29.9M over four years. The EU pushed obligations for standalone high-risk systems (hiring, credit scoring) back sixteen months to December 2027, with product-embedded AI following in August 2028.

Hiring moved differently. The share of Australian employers posting at least one AI-mentioning ad grew from 5.8% to 8.5% in a year (Indeed Hiring Lab Australia, April 2026), and governance roles sit inside that growth. On 3 September 2026, an unquoted search for AI governance on Indeed Australia returned 1,553 postings, a broad match with data-governance roles mixed in; the exact phrase "AI governance" returns 139. A specialist recruiter's July scrape of actual AI-governance ads counted 32. The field is still small. The named roles are real, though. Transport for NSW has an AI governance specialist role at AUD $137–154k, a Melbourne-based seat pays $170–185k, and Macquarie and IAG both posted AI risk and governance positions in August (since closed). The specialist recruiter (Galileo Search) puts its Sydney rate card for senior levels at large companies at a $230k package, superannuation included (July 2026).

Of the five functions AI jobs sort into, this installment covers Governance. If the rules got delayed, why the hiring?

Some rules never got delayed

Around 80% of governance postings come from financial services and insurance (Galileo Search, from 32 live ads scraped in July 2026). That is no coincidence: for them, nothing got postponed.

APRA CPS 230: the operational-risk standard for banks, insurers and super funds. In force since July 2025, with pre-existing vendor contracts due to comply by July 2026. In April 2026 APRA sent a supervisory letter aimed squarely at AI (map your AI supply chain, put board-level accountability on it) with an explicit warning that enforcement may follow.
The Privacy Act amendment: from 10 December 2026, organisations using automated decisions that can significantly affect individuals must state in their privacy policy what information feeds which kinds of automated decisions.
ASIC's position: in a July 2025 speech, ASIC's chair said the regulator is in no rush to add AI regulation: existing law is technology-neutral, it already applies to AI, and ASIC will enforce it as it stands. Its 2024 review (23 licensees, as of December 2023) found nearly half had no policies on consumer fairness or bias, and the same speech reported a follow-up review of 40 market intermediaries with similar gaps.

What companies are hiring for right now is not "preparing for AI regulation." It's someone who can work the regulation that already applies.

Tools barely register

A contrast with how the automation market split along tool lists. In today's live Australian postings it's hard to find one requiring governance software (IBM watsonx.governance, Credo AI, OneTrust and the like); effectively zero on SEEK. The one exception: earlier this year a Transport for NSW ad listed Credo AI and IBM Watson experience as preferred. But the screening centre of gravity is frameworks: NIST AI RMF, ISO/IEC 42001, APRA CPS 230 and 234. The currency here is reading standards and applying them to an organisation, not tool fluency.

ISO 42001 is a name worth knowing. It's the international certification for AI management systems. As of April 2026, counting only publicly announced certifications, roughly 350 organisations hold it; no official register exists. Early holders include AWS, Microsoft, Anthropic, and KPMG Australia. A small field means an early mover's value is large.

Less a new job than an extension of an old one

In IAPP's 2024 governance report, 68% of privacy professionals had taken on AI governance as an additional duty. The default pattern is risk and privacy people widening their remit rather than companies hiring from scratch. The specialist recruiter says the same, drawing candidates from three feeder tracks: technology risk, model risk, data governance.

The extension pays, though. In IAPP's 2025–26 salary survey (fielded March–April 2025; 1,600+ respondents across 60 countries), privacy-only roles have a global median of USD $123k; add AI governance and it's $169.7k.

Why this matters even if you never switch

Two reasons to know this field even if you stay a builder.

First, apply to a bank and words like human oversight, exception handling, and audit trail come back as interview questions. The regulation above is what put them there.

Second, builders who keep records are rare. Show, in writing, who approved your automation, what gets logged, and how it rolls back when it goes wrong. That alone makes you stand out in regulated-industry hiring.

Next up: Product & Architecture, the most inflated-numbers corner of this series, so we clean up the numbers first.

AI Enablement: Helping Employees Actually Use AI

John Lee — Sat, 17 Oct 2026 07:57:27 +0000

Companies bought the AI licences. Their staff aren't getting much out of them. In a Gartner survey of 574 Australian employees in the first quarter of 2026, 85% had been given enterprise AI tools, only half reported clear guidance, training or support for using AI, and 86% were also using personal AI tools. The only Australian data that measured actual use is still the government trial. It's from the first half of 2024, so it's dated, but in that trial (7,769 licences across nearly 60 agencies) a third of participants used Copilot daily. For reference, Microsoft's own default bar for an "active user" is one use in 28 days.

That the gap is a people problem is what executives themselves report. BCG surveyed 1,000 CxOs in 2024. Their answer: 70% of AI implementation challenges are people and process, 20% technology, 10% algorithms. That 70/20/10 started life as a BCG partner's rule of thumb in 2018 and got survey backing in 2024. Field experience first, measurement later. Australia has a sharper local number. In Hays' survey (fielded February–March 2026; 7,000+ respondents across Australia and New Zealand, 5,223 in Australia; a recruiter's own-database poll), 60% of respondents use AI at work. And 78% of those users have never received formal training from their employer.

Of the five functions AI jobs sort into, this installment covers Enablement.

Hiring for that gap has started

Three Australian postings confirmed in August 2026 (listings expire, so the substance stays here):

AI Enablement Lead: a Melbourne government agency (via recruiter Talent), AUD $190–206k. One person owning the AI roadmap, responsible-AI governance, and the organisational learning program.
AI Academy Lead: an ASX 150 company (name withheld), AUD $180–240k package, superannuation included. First assignment: get 300–500 Copilot premium users (mostly executives) actually using it. Prompt libraries, role-specific playbooks, internal how-to videos. And the duties say it outright: "Measure engagement, adoption and learning effectiveness and use insights and feedback to continuously improve the enablement approach."
AI Adoption Specialist: ABC, the national broadcaster. Workshops, prompt libraries, capability clinics.

The backgrounds asked for aren't engineering. They're learning and development, change management, digital adoption, communications. One consultancy's ad copy states this function's reason to exist better than any brochure: "Most 'do AI' with a licence rollout, lunch and learn, and a completion dashboard. 6 months later, the work hasn't changed much. We're not doing that." (Novigi, AI Adoption Coach posting)

The job isn't teaching. It's measuring.

Anyone can run a workshop. What this role gets paid for comes after. One finding from the Australian government trial is practically useful here. The more training people got, the more confident they were, and it showed up in numbers. Participants who received three or more forms of training were 28 percentage points more likely to say they felt confident than those who got one form (per the summary report; it's a between-group comparison, so self-selection bias remains). The trial measured that far. What this role builds is the next thing: before-and-after data.

In BCG's June 2026 survey (close to 12,000 frontline employees, managers, and leaders in more than a dozen markets), 42% of frontline employees who use AI regularly said they save eight hours a week, a full workday. Yet 66% receive limited or no guidance on what to do with that time, and more than half are not reinvesting it into more strategic work. That is why reported time savings alone don't prove productivity. The UK Department for Business and Trade's Copilot pilot (1,000 licences, Q4 2024) reached the same conclusion: 72% satisfaction and small observed time savings, but it "did not find robust evidence" of productivity improvement. This function's receipts are the measurements that close that gap. Adoption before and after. Active use by team. Hours actually recovered.

Two things to watch

First, this is still a thin job category. Posting volumes are far below AI engineering; the titles are scattered (Enablement Lead, Adoption Specialist, Academy Lead, Transformation Lead); and the fact that two of the three postings above are recruiter-fronted or name-withheld is itself a sign of how early this is. Second, absorption is a real risk: HR and L&D are claiming this territory, and single postings often bundle several functions into one hire; the Melbourne role above does. Safer than going all-in on the title: add this skill to whatever you already do.

One counter-signal for honesty. On its January and July 2026 earnings calls, Microsoft said paid Copilot seats grew from 15 to 30 million, with average weekly engagement "on par with Outlook and Teams." That's the vendor talking, and the 15 million was only about 3% of the commercial M365 seat base. But if the shelfware era really is ending, the person who can prove "I got it used" only gets more valuable.

If you build, you're not underqualified — you're ahead

The backgrounds listed are education and change, but the postings themselves tip the scales toward people who build. The ASX 150 ad says it verbatim. They want someone who "genuinely lives and breathes AI, actively experiments with the technology themselves." The role is "very much a 'roll your sleeves up and do' opportunity, rather than a role that purely sets strategy or oversees delivery." Someone who has actually built things has the edge over an L&D generalist.

And the good thing about this function: the portfolio can be built before the job switch. Build one prompt library for your current team and measure how many people use it, before and after. Run one workshop and record what usage looks like two weeks later. A few before-and-after numbers like that are this function's résumé.

Next up: Governance — the strange market where the rules got delayed and the hiring didn't stop.

What AI Engineer Job Ads Actually Screen For

John Lee — Wed, 09 Sep 2026 07:29:22 +0000

Decide to become an AI engineer and the first thing you meet is a framework list. Learn LangChain? People say LangGraph is rising. What about CrewAI, AutoGen? Picking wrong feels like it will cost you a year.

The posting data settles that anxiety first. An agent-specialist job board tallied 1,135 of its own listings from March–May 2026 (the site doesn't name its operator, so read it as a snapshot). More than half of those ads name no framework at all. The ads that do name them average 2.31 each: LangChain in 392, LangGraph 256, LlamaIndex 150, CrewAI 106, AutoGen 74; and even LangChain, the market default, appears alone in only one of its eight listings. This is not a pick-one game.

The salary data points the same way, harder. Postings that name frameworks have medians of $185–190K, roughly $20K below the agent segment's overall median of $213K. Naming frameworks doesn't buy you a premium. For scale: the posted-salary median across 43,480 US AI-engineering ads is $176,000 (Axial Search). The agent segment sits a bit above that, though the two tallies differ in window and method, so don't read the gap as precise.

Of the five functions AI jobs sort into, this installment covers Application.

The sentences that repeat in real postings

Strip away the framework lists and read what senior postings ask for, and different words keep coming back. Two engineering ads and one PM ad that states the same demands from the other side. Condensed here; originals at the links.

"Design evaluation harnesses and quality scoring — we use Langfuse, rubrics to measure safety, effectiveness, and personalization." (Future, Applied AI Engineer, $215,000–250,000)
"Improve our observability and instrumentation to profile agent behavior… design and implement infrastructure for low-latency agent execution." (Harvey, Senior and Staff Software Engineer, Agents, $193,400–340,000)
A role partnering with engineering and AI leadership across LLM orchestration, latency, caching, reliability, evaluation, observability, and cost; the phrase "cost per successful outcome" comes from here. (HighLevel, Principal PM, Conversation AI)

What the three postings share isn't a framework name; it's evals and operating numbers. And an eval isn't anything exotic: it's automated grading of whether your system answered well, against a set of reference answers you wrote: a golden dataset.

You can put down the fine-tuning worry

The fear that this job requires training models keeps a lot of builders out. In a survey of 1,340 practitioners (LangChain's own survey, late 2025), 57% do not fine-tune at all. The working baseline is a base model plus prompting plus retrieval (RAG), tightened by evals. In the same survey, 57.3% already run agents in production and 89% have some form of observability. Learning evaluation and operations gets you closer to the ads than going back to ML math does.

Tool names barely appear in the ads

Eval tools are only starting to register in job ads. In UK posting counts (ITJobsWatch, 2 September 2026), just two names show up at all: LangSmith (38 postings over six months) and Langfuse (31); Braintrust has no page. The salary columns aren't readable yet either; last year's samples were two or three postings each. That thinness is the signal: what companies screen for isn't a tool name but whether you can design evaluations and read operating numbers.

One protocol is the exception. MCP (Model Context Protocol) shows up in 17–24% of postings for every one of the five frameworks, the only thing in that data that cuts across all of them. Its security problems are growing just as fast, so "I can use MCP" has to mean "I can use it safely."

One fast-growing title deserves a caution: Forward Deployed Engineer, embedded with customers and accountable through production, grew 729% in a year on US Indeed's index. But the same title spans two pay tiers: an FDE at a frontier lab and an FDE at an ordinary enterprise are different jobs. Don't judge by the title alone.

The actual size of the Australian market

If you're reading from Australia, set expectations from local numbers. On SEEK, "ai engineer" returns 1,177 listings, "langchain" 30, and "llm" 101 (2 Sep 2026; keyword matches, so treat ratios loosely). LLM-specific roles are still few. The named hiring is real: Commonwealth Bank, including its subsidiary Bankwest, is hiring GenAI and agentic engineers, and recruiter listings run to AUD $230–340k. Rough bands: $130–165k mid, $165–200k senior, $200–230k+ principal (aggregated from recruiter guides such as Big Wave Digital, not official statistics).

So what do you build?

Not a framework mastered; one small thing finished. Build a retrieval-backed Q&A over some documents and write fifty reference answers yourself. Automate the grading, measure latency and cost per request, and keep the records. Those are the words the postings above keep repeating.

What this project gives you is hands-on experience with evaluation and instrumentation. It does not substitute for the production-scale experience the senior ads also want. But juniors who arrive having done it are rare. You'll touch a couple of frameworks building it. You don't need to finish learning them first.

Next up: Enablement, the role that helps employees actually use AI well.

Why YouTube Only Teaches You n8n

John Lee — Thu, 03 Sep 2026 15:56:44 +0000

Open YouTube to learn automation and you get n8n, Make, Zapier. The enterprise-market tools from the last piece (Boomi, Workato, UiPath) are almost nowhere. The job ads clearly want them; the content layer barely mentions them.

The easy answer is views: beginners are the audience, so beginner tools win. That's half of it; the other half is where the money comes from. Follow who pays the teacher.

The first money: affiliate commissions

n8n runs an affiliate program for creators: 30% of referred cloud-subscription revenue, for twelve months. Every viewer who signs up through a creator's link becomes recurring income for that creator, and Make runs a similar program. Zapier has no affiliate program open to ordinary creators; it holds the same shelf space through search dominance instead.

Enterprise vendors don't pay creators this kind of commission. There is no per-signup commission open to individuals. Workato and UiPath do run partner revenue programs, but the money arrives after a partner agreement and a closed enterprise deal. A video can't collect on that, so a YouTuber teaching Workato has effectively nobody to collect from.

Which means a creator's menu was set before the first video went up.

The second money: the community business

The monetization point in automation education now sits below the videos, on Skool, a community platform. The two biggest automation communities there, AI Automation Agency Hub (330,000+ members) and AI Automation Society (440,000+), are both free.

The free tier brings people in, and what's sold behind it differs by operator. AI Automation Society sells a $129-a-month membership to its 440,000 free members; the AAA Hub side sells an accelerator priced above $5,000 to its 330,000 (pricing disclosed only on a sales call; that figure comes from student accounts). Where the published numbers allow an estimate, at AI Automation Society, the paid share sits under 1%: 447,000 free vs 3,700 paid is 0.8%. Strictly a paid-to-free count taken on the same day, not a conversion rate.

Skool adds a competition on top. Skool Games ranks community owners each quarter by the new subscription revenue they add in 90 days, and the leaderboard counts at most $100 a month per subscription. The contest is built for low-priced volume, and the curriculum that sells at volume is a low-barrier tool. The answer, again, is n8n. High-priced accelerators aren't subscriptions, so the leaderboard doesn't count them at all.

The other side is nearly free, and invisible

Enterprise education is much bigger and barely shows up on YouTube. UiPath Academy reported 1.6 million learners (UiPath, 2023). Salesforce Trailhead issued 2.6 million+ AI and data badges in the fifteen months from June 2023, about 40% of them going to Salesforce's own employees. Workato's courses and exams cost nothing.

Workato aside, what's free is the training, not the credential. UiPath's official exams run $150–300, and Salesforce's free first attempt at its AI certifications ended at the close of 2025. The credential track itself is churning under the AI transition: Microsoft retired its Power Automate certification this year and replaced it with an agent certification.

Creators teaching the enterprise tools do exist. There are channels devoted to Power Automate, and the Salesforce world supports a paid-course market of its own. But since no vendor pays per signup, those creators have to earn outside the vendors, at a much smaller scale. Which leaves learners looking at an inverted world: the education that costs money is the most visible, and the education that's nearly free is the hardest to find.

This is not a scam story

Some things deserve saying in the other direction. The big accelerator's review score is solid: 4.7 on Trustpilot across 548 reviews, though the account actively invites customers to review, so read it with that in mind. A different community backs itself with a full-refund 90-day guarantee tied to landing your first client (Maker School, $184 a month). Freelance-market guides put n8n rates at $40–100 an hour, $125–250 senior (agency tallies, not marketplace statistics). Real people earn real money in this market.

The problem isn't fraud. It's distortion: several hundred thousand people are being trained toward the smallest part of the market companies actually pay for, and the direction was set by the teachers' revenue structure rather than the learners' needs.

How to use the content layer anyway

Learning n8n is fine in itself — the last piece showed real jobs on it and real enterprises adopting it. Three things to keep.

Check whether a channel teaches only the tool its affiliate links point at. A curriculum with one tool as every answer is a funnel, not a curriculum.
Before paying for a course, sweep the free tier: vendor academy training costs nothing, enterprise ads recognise vendor certifications, and a $150–300 exam is cheaper than most paid courses.
Spend what's left, money and hours, on records. Whoever's hiring reads a workflow with an error rate and throughput attached before any certificate. That was the last piece's closing table.

Next up is Application: what AI engineer job ads actually screen for, once you set the framework names aside.

There Are Two AI Automation Job Markets

John Lee — Wed, 02 Sep 2026 07:53:05 +0000

Automation is the door most people pick when they start an AI career. You watch n8n videos on YouTube, join a community, take a course, and start preparing for a job or an agency. The sheer number of people learning it tells you something: the two biggest free automation communities alone hold 770,000+ members combined (as of August 2026, overlapping signups included).

Then you open the job ads and the names look wrong. "8+ years hands-on Boomi." Workato, Celigo. Tools you have never seen on YouTube, paying more than the ones you have. Somewhere around here you start wondering whether you learned the wrong thing.

You didn't. There are two markets, and YouTube only shows you one of them.

The AI Operator Map split AI careers into five functions. This installment covers Automation, one of them.

The two markets, side by side

	Startup & agency market	Enterprise market
Who hires	Startups, agencies	Large companies, regulated industries
The tools	n8n, Make, Zapier	Boomi, Workato, Power Automate, UiPath
Typical titles	AI Automation Specialist, GTM Engineer	Integration Engineer, RPA Developer
Where you learn	YouTube, communities, paid courses	Vendor academies, certifications (often free)

The startup side's speed shows up in job ads. In an analysis of 1,000 GTM and RevOps postings (Bloomberry), those roles grew 205% in Jan–Sep 2025 over the same months a year earlier, with a median salary of $127,500. The tools the ads name: Zapier in 39% of postings, n8n in 28%, and Workato doesn't appear on the published tool list at all.

The enterprise side barely exists on YouTube. But the hiring is steady, and learning it costs less, not more. Workato's courses and exams are free, and UiPath's academy training is free too (the official certification exams start at $150). And don't let the "8+ years" ads scare you off: those are the top of this market, not its entrance. The entrance is already paved: free academy, certification to pass screening, junior integration and RPA developer postings.

Two titles in that table deserve a definition. A GTM engineer automates go-to-market work, meaning sales and marketing operations. An RPA (Robotic Process Automation) developer builds software robots that take over repetitive on-screen work people used to do. And the enterprise column itself has two grains: Boomi and Workato are integration platforms (iPaaS) that connect systems to systems, while UiPath's core is RPA.

So why did the market split in two? To see it, you have to take the word "automation" apart.

"Automation" is not one thing

Job ads and interviews talk past each other because one word is covering four different distinctions. Split them and the ads start making sense.

1. Who is in whose loop?

Sometimes the human owns the process and the automation helps. A support ticket comes in, a workflow classifies it and drafts a reply, but a person reads it and hits send. Sometimes the automation owns the process and the human is a checkpoint: invoices flow through untouched, and only the ones over a threshold land on someone's desk.

The first is AI-in-the-loop (the AI joins your loop). The second is human-in-the-loop (you join the automation's loop). A lot of material online uses the two interchangeably; there is a research paper whose whole point is untangling them, and its test is a usable one: who owns the process? Get this distinction right in an interview and the conversation moves up a level.

2. Who decides the path?

Put a trigger on an n8n flow and drop an LLM node in the middle, and the path is yours. The AI summarizes or classifies in its assigned slot; the next step is always known. The industry calls this a workflow. An agent is different: you give it a goal, and the AI decides what to do next and which tools to use. What you own are the goal and the guardrails.

Anthropic, the company behind Claude, gives blunt guidance here: use the simplest pattern that passes your evaluations, and save agents for problems where you cannot script the path in advance. An "agentic" keyword in a job ad does not always mean the job is building agents. If you can explain why something needed to be an agent, you stand out.

3. Where does the human watch from?

Some roles approve every action (in the loop). Some watch a running system and step in when something looks off (on the loop). Some hand the whole thing over (out of the loop). This isn't new either: since the 2010s the RPA industry has used a similar split between attended robots (assisting at someone's desk) and unattended ones (running headless). Tools keep changing; the axis stays. When an enterprise ad asks for "human oversight" and "exception handling," this is the axis it's talking about.

4. Autonomy comes in levels.

Researchers have proposed an L1–L5 scale. At L1 the human makes every decision and the AI only executes. At L3 the AI leads and the human gives direction and feedback. At L5 the human keeps an emergency stop and little else. Gartner expects task-specific agents inside 40% of enterprise applications by the end of 2026, up from under 5% in 2025. Agents inside everyday enterprise apps are about to be common.

The two markets, re-read through the four axes

What YouTube and the courses teach is mostly automation that stays near a person: it runs while you watch, and you fix it when it breaks. Enterprises use plenty of near-a-person automation too — attended robots next to call-centre agents, for one. But the point where the two markets' prices split is the other kind: automation that runs all night with nobody watching, brings only the exceptions to a human, and passes a security review.

The price bands differ from the start. n8n cloud starts at €20 a month; Workato's average contract sits in the mid-$60,000s a year (Vendr, 2026). Feature lists don't explain that. What does: large companies, especially in regulated industries, review a tool's security before adopting it and demand a contract that says who is liable when something goes wrong. Zapier holds a SOC 2 certification, but SOC 2 attests that security controls were audited; it doesn't substitute for specific regulations. Handling data covered by HIPAA, the US health-privacy law, requires a liability agreement (a BAA) that Zapier declines to sign, so organisations that need one can't pass it through review. What an enterprise product sells includes those contracts and that review-readiness, not just features.

The tool you're learning is not a dead end

Three things are happening at once.

There are already good jobs on startup-market tools alone. That's the GTM engineer above: hired by startups, working in Zapier and n8n.
Enterprises have started using startup-market tools. Delivery Hero (53,000 employees) used n8n Enterprise to cut account-unlock time from 35 to 20 minutes on average, reclaiming 200 employee-hours a month (n8n's published case study); BMW is wiring n8n into an internal platform (independent scan by Bloomberry).
The enterprise tools themselves are being rebuilt around agents. UiPath has re-positioned the whole company on "agentic automation," and Workato is opening its automations to be called by agents.

Whichever direction you take, though, the last thing you have to show is the same.

What companies actually buy

Not "I can build it" — "it ran, and here is the record." The further the automation gets from human hands, the heavier the record they ask for.

Where the human sits	The record they ask for
Human owns it, automation assists	Before-and-after: what got faster, by how much
Automation runs, human supervises	Error rate, throughput, run logs, intervention log
Human hands-off	Full monitoring setup and audit trail

In portfolio terms: swap the workflow screenshots for an error-rate graph. Certificates don't appear anywhere in this table. Paid courses aren't the problem; it's that the record still has to be built after the course ends.

If you're learning n8n right now, nobody is telling you to stop. Know who owns the process in the thing you're building, know where the human watches from, and start attaching error rates and throughput. If I were screening, I'd look at that one record before ten certificates.

Why does YouTube only teach the kind that runs next to a person? Next up, we follow the money.

The AI Operator Map: AI Jobs Sort on a Different Axis

John Lee — Wed, 02 Sep 2026 07:52:45 +0000

A while back a message landed in my LinkedIn inbox. A recruiter at an AI-specialist firm here in Australia: they were placing AI talent with clients across the country, my profile had stood out, would I be keen for a chat. I said yes, but honestly not for the role. I wanted to know what demand for AI people actually looks like in this market, straight from the people who sit behind the job ads.

Which is how that call turned into two interviews running at once. They were measuring me against their ladder, three tiers from hands-on operator to executive, AUD $70k to $250k and up. I was trying to read the market off them: what problems are companies actually hiring people to solve?

But my question wasn't anywhere on their ladder. Hire two people at the same tier and you can get two completely different jobs: one automating internal workflows, one building products on LLMs. Different experience required, different evidence to show. The ladder had no row for that distinction. The call ended and I still didn't have my answer.

So I went and checked myself: job postings, salary guides, national statistics. Every number in this piece carries its source and its definition; the stage is the Australian market, and global surveys are marked as such. You'll see why by the end.

The names the market uses collapse into five

Strip away the titles, group by "what problem does this person solve", and you get five functions. Not an industry standard — a grouping I built from the postings and the surveys.

Function	The problem it solves	Titles the market actually uses
Automation	Rebuild workflows that logic-based tools never could	AI Automation Specialist, Integration Engineer, GTM Engineer
Application	Build products where the model does the data work CRUD used to do	AI Engineer, LLM Engineer, GenAI Engineer
Enablement	Move an existing workforce onto AI	AI Enablement Lead, AI Adoption Specialist, AI Academy Lead
Product & Architecture	Design the path from AI spend to revenue	AI Product Manager, AI Solutions Architect
Governance	Make AI cleared to ship	AI Governance Specialist, Model & AI Risk Manager

Five rows and the map would be done, except the moment you search by title, the table starts coming apart.

Titles churn. Functions persist.

It isn't just titles — the credentials around them churn too. This year's evidence alone:

Microsoft retired the Power Automate RPA developer certification (PL-500) in June 2026 and put a new agent certification (AB-100) in its place. The credential name swapped; the automation function underneath didn't move.
"Chief AI Revenue Officer" circulates in content everywhere. I could not find a single person who actually holds the title.
Forward Deployed Engineer postings grew 729% in a year on Indeed's data, and the role sits across two functions, Application and Architecture, so it fits no single cell.
One Melbourne government posting for an AI Enablement Lead bundles the AI roadmap, responsible-AI governance, and the organisational learning program into one hire.
In IAPP's survey, 68% of privacy professionals have taken on AI governance as a second hat.

So the unit is the function, not the title. In the postings, small organisations bundle several functions into one person, and the bigger the company, the more each function gets its own team. Adoption itself tracks size too: per the Australian Bureau of Statistics' 2024–25 business survey, 35% of large businesses use AI, 22% of mid-sized, and 11% of small and micro businesses.

Tools track company size as well. n8n, the center of gravity of YouTube automation content, didn't make the grid of the 2026 Gartner Magic Quadrant for iPaaS at all (a mention in the text, no more), while the leaders are Boomi, Workato, SAP, Salesforce, and Microsoft. Half the companies running self-hosted n8n have 2 to 10 employees (Bloomberry's certificate-log scan of self-hosted instances; cloud customers aren't captured). n8n is inside big companies too; what splits isn't presence but the procurement and production-approval layer. Why the tools YouTube teaches and the tools companies actually buy differ this much deserves its own piece, so just one line here: enterprise vendors don't pay YouTubers affiliate commissions. SMB tools do. n8n pays 30% of referred cloud-subscription revenue for twelve months.

"Can't I just learn whatever and go?"

I wish. The failure data says it's not that simple.

Quoted failure rates for enterprise AI run anywhere from 30% to 95%, and they measure different things in different units, so they can't be lined up on one scale. Pull out any single number and you almost certainly distort it.

What was measured	Number	Source
Projects predicted to be abandoned after PoC	30%+	Gartner, 2024
Companies that abandoned most AI initiatives	42%	S&P Global, 1,000+ respondents, 2025
PoCs scrapped before production	46% avg	same survey
Companies failing to achieve and scale value	74%	BCG, 1,000 CxOs, 2024
Companies with no tangible enterprise-level EBIT impact	80%+	McKinsey, 2024 survey
PoCs that never reached wide deployment	88%	IDC with Lenovo, 2025
Organisations with no attested P&L impact within 6 months (custom tools)	95%	MIT NANDA, preliminary report, 2025

If you've seen "95% of AI projects fail" somewhere, it comes from the bottom row: a preliminary report, not a peer-reviewed study, built on 52 interviews plus 153 conference surveys and a review of 300-odd public initiatives. The real limits are its six-month window and interview-attested outcomes, and the same report found that roughly 83% of generic chatbot pilots succeed. This is why every number in this series carries its source and its definition.

Where the surveys do overlap, despite their different bars, is an observation: in McKinsey's, BCG's, and MIT's data alike, the successful minority defined the outcome before building and redesigned the workflow instead of laying a tool on top. Correlation, not proven cause, but the direction is consistent. My reading: this market is short on people who know what to measure.

And AI skills already carry a price. Australian job ads asking for AI skills grew little for four years, then doubled from 20,000 to 41,000 in a single year, and those ads carry an average 62% wage premium (PwC AI Jobs Barometer, Australia 2026; by industry it ranges 8–59%). Demand is growing, but which size of organisation you join changes the tools you'll meet and the evidence you'll be asked to show.

Each function has its own evidence

That's why the last column of this map is evidence, not tools.

Function	What counts as evidence
Automation	Workflows live in production; error rate, throughput, monitoring
Application	An eval harness; latency and cost per request; a golden dataset
Enablement	Measured behaviour change; before-and-after on a real workflow
Product & Architecture	Revenue or cost movement tied to something that shipped
Governance	Framework fluency (NIST AI RMF, ISO 42001); a policy that survived a real review

If some terms in the table are unfamiliar, that's fine. What an eval harness is, how you measure behaviour change: each function's installment will unpack them one at a time.

Evidence isn't something you can batch up later. Build with measurement attached from step one and it accumulates alongside the work itself. Which function, measuring what, and how — those are the cells this series fills in.

If you're weighing up your AI career right now, pick the problem you want to solve, not the title. The experience you build solving it becomes the foundation for everything after.

Next up: Automation.

Obsidian Git Sync on iPhone Works Better Than You'd Expect

John Lee — Mon, 24 Aug 2026 08:44:22 +0000

In the previous guide I put my Obsidian vault on GitHub. I promised to write up the mobile setup separately, and this is that write-up.

The short version: on an iPhone, the Git plugin alone handles pull, edits, commits, and pushes. I set mine up back in February, forgot about it, and the phone has been picking up the latest vault every day since. It keeps working after you stop thinking about it.

Your phone runs a different git

On desktop, the Git plugin calls whatever git you have installed. An iPhone has no git to call, so on mobile the plugin switches to isomorphic-git, a JavaScript reimplementation. The author warns in the README that mobile is unstable, and SSH doesn't work there. Authentication is HTTPS with a token, and that's the only option.

The warnings sound like a reason to give up. My vault is 25MB with 319 markdown files, and at that size I've never felt the problem.

The setup

You don't need iSH, Working Copy, or any other companion app. The plugin does everything.

Create a token. On GitHub, generate a fine-grained personal access token. Repository access: just your vault repo. Permissions: Contents, read and write. Give it a name that says what it's for. The reason comes below.
Install Obsidian and the Git plugin on the phone. Create a new vault (turn off "Store in iCloud"), then install and enable Git from the community plugins.
Clone. Open the command palette (on mobile, the default gesture is swiping down) and run "Git: Clone an existing remote repo". It asks more questions than you'd expect. In order:
- Enter remote URL: your repo address (https://github.com/user/repo.git)
- Directory: pick Vault Root.
- Does your remote repo contain a .obsidian directory?: if you commit your settings the way the previous guide does, answer YES. A scary confirmation follows ("DELETE ALL YOUR LOCAL CONFIG AND PLUGINS"). It means the empty vault's config gets replaced by the one in your repo, so go ahead. Your plugins and settings come back from the repo once the clone finishes.
- Depth of clone: leave it empty for a full clone.
- username / password: username is your GitHub account, and the password field takes the token. GitHub rejects account passwords for git, so a token is the only thing that works here.

The clone throws plenty of warning notices along the way. Mine finished fine through all of them. When it's done, Obsidian asks for a restart.

After the restart, finish the settings. Fill in the commit author name and email in the plugin settings; commits from the phone fail without them. "Pull updates on startup" should already be on if your repo carries the settings, so just check it. With that on, the app opens on the latest state every time.

I deleted the token and sync stopped

While writing this I was cleaning up my GitHub token list and saw the vault token marked "Never used". It had been pulling every day for months. I figured it was a leftover and deleted it, and the phone's sync broke on the spot.

A fresh token pasted in brought everything back. And that new token, minutes after a successful push, still shows "Never used". GitHub's Last used label doesn't count git authentication. Trust it while cleaning tokens and you'll cut a working sync, like I did. That's why the token gets a name that says what it's for.

On the phone, I mostly read

My pattern is simple. I write on the Mac and read on the phone. The app opens, the pull runs, and the latest vault is in my hand wherever I am. When a thought lands while I'm out I type a line, and that gets committed and pushed too. Since the writing happens on one side, the conflicts from the previous guide almost never show up on the phone.

That guide said to lower your expectations for mobile. Correction: at this vault size, there was nothing to lower.

Codex PR Review: Automatic Reviews, Triggers, Review Rules

John Lee — Mon, 24 Aug 2026 08:43:54 +0000

Codex's GitHub PR review works better than I expected. Before opening a PR I already review the code several ways, in Claude and in Codex both. I've had the main agent review it, attached a different model as a subagent reviewer, run it in two stages. Code that survives all of that still gets caught by Codex, always one or two things.

This guide covers turning it on. What happens after that is a bigger story, and I pick it up at the end.

Turning it on

Setup itself is three steps.

Set up Codex cloud for the repo. That means installing the GitHub app and granting repo access, and you need push or admin permission to change repo settings.
In Codex settings, toggle Code review on for the repo.
To have every PR reviewed without asking, also turn on Automatic reviews. Leave it off and Codex only shows up when you call it.

Automatic review also means the review lands the moment you open the PR. If you'd rather not collect comments on a draft, leave it off and call Codex when the branch is ready.

You call it from a PR comment.

@codex review: review this PR
@codex security review: look at it from a security angle
@codex review for issues in the database migration: narrow where it looks
@codex fix the P1 issue: have Codex apply the fix itself

To pin review standards into the repo, add a ## Code Review Rules section to AGENTS.md and break it into ### items. Repo-wide rules go in the root file; rules that only apply to one service go in the AGENTS.md closest to that code.

One more thing worth knowing: Codex only posts P0 and P1 findings to GitHub. Small stuff never shows up, so anything that does usually carries weight. That's exactly what makes it hard. Every comment looks correct.

Setup takes five minutes. The rest is the hard part.

What happens once it's on

Codex judges strictly from the code, and both the side filing comments and the side fixing them are built to keep going until they're done. If nobody steps in, the rounds multiply on their own. One security-feature PR passed through 209 review conversations before it merged.

Living through that cycle left me with four response principles: read comments from how the product behaves, weigh them by user impact, understand how the fix relates to the existing code before touching anything, and if it isn't a merge blocker, file an issue or ignore it. Where those principles came from and why each one holds is in 209 AI Code Reviews: Accurate Is Not Necessary. If this guide got your reviews turned on, that post is what to read next.

Managing ChatGPT Memory: Review, Edit, Delete

John Lee — Mon, 24 Aug 2026 08:43:47 +0000

ChatGPT remembers you whether or not you asked it to. If its answers start matching your tone one day, or it explains something on the assumption you do a job you never mentioned, that's memory.

It isn't only ChatGPT. Claude has memory, and so do most of the coding tools shipping now. The model consults it to give you the answer you're more likely to want. Use it without knowing about it and you have no way to explain why an answer came out the way it did.

There used to be a step where you said "remember this" and one line got stored. Not anymore. ChatGPT keeps track of whatever it judges worth keeping from your chats. So this guide is about managing it rather than switching it on.

Two screens are in circulation right now

The memory settings screen started changing in June 2026. The new one has a single memory control and a memory summary. The summary is a written account, organized by category, of what ChatGPT thinks it knows about you, rather than a list of stored items. The old screen has two toggles ("Reference saved memories" and "Reference chat history") and shows the saved items as a list.

The new screen is arriving by plan and region, so your account may still show the old one. What follows describes the new screen, with notes where the old one differs.

Reading and correcting the memory summary

Settings → Personalization → Memory. The path is the same on web and in the app. Many accounts have memory on already, so opening it to see what's in there comes before switching anything on.

Open the memory summary and you get what ChatGPT has written down about you. Most people are surprised the first time they look. You can correct it two ways: type the correction, or highlight a sentence in the summary and delete it. To clear the lot, use "Delete and turn off memory" from the three-dot menu on that page. It does what it says, wiping the summary and turning memory off with it.

On the old screen you get two toggles instead. Saved memories are managed as a list of items; chat history reference has no list at all. If you cleared every saved item and ChatGPT still seems to know you, the second one is on.

One trap: deleting a conversation does not delete the memories that came out of it. Clearing your chat list and clearing your memory are separate jobs, so something you thought you cleaned up can keep feeding into answers.

Seeing what went into an answer

A personalized answer comes with a way to see which information fed it, and you can edit that information from there. Grabbing one answer that came out wrong and deleting the cause is faster than reading the whole summary.

Keeping memory inside one project

Projects have their own memory setting. A project either uses your default memory or project-only memory. Set it to project-only and ChatGPT draws on conversations inside that project but won't pull in memories or chats from outside it. What happens inside the project stays out of your other conversations too. Open the project, then the three-dot menu, then Project settings.

That setting earns its keep if you run work and personal life through one account.

When you want one conversation left out

Use Temporary Chat. A temporary chat doesn't reference existing memories and doesn't create new ones, and it stays out of your history. That beats switching memory off account-wide because of one sensitive conversation. Leave it on, and open a temporary chat for whatever you'd rather not keep.

Getting something out of it

Automatic storing doesn't mean automatic tidying. Two things are worth doing yourself.

Nail down the preferences with a long shelf life. "Code examples in TypeScript, not Python." How you work, which tools you use, how long you want answers and in what language: say it once and it holds for months. Don't store anything that only holds for this week.

Prune it now and then. Open the summary about once a month and fix what's gone stale. Memory only accumulates, it never retires anything on its own, so a project that ended last year can still sit underneath today's answer as an assumption.

The same feature works differently once it reaches your coding environment. What piles up there is a team's rules and decisions rather than a few lines of personal taste, and the harder question becomes what not to store. I wrote about that in Coding Agent Memory.

Connect GitHub to ChatGPT: Obsidian Vault as Project Context

John Lee — Tue, 18 Aug 2026 07:59:31 +0000

Once you finish putting your Obsidian vault on GitHub, what you have is a repository full of md files. On its own that is a backup. It starts being useful when ChatGPT can read it.

Three steps. Connect GitHub to ChatGPT, scope the access down to the vault repository, then create a project and attach that repository to it. After that you just talk inside the project.

Obsidian has an easy time here for a boring reason: the vault is already nothing but markdown files in folders, so there is nothing to export or convert before handing it to a model. The format you read is the format the model reads. An app that keeps your notes in its own database would have stopped you at this step.

Connect GitHub

Open Settings and go to Apps. Depending on your build it may still say Connectors; same place. Find GitHub in the list, connect it, and GitHub's OAuth screen takes over. That screen is where you pick which account and which repositories ChatGPT gets to see.

Slow down here. Clicking through gives away everything, and I picked the vault repository only. Notes carry a lot more private material than code does, and unlike a code repo I have never gone file by file asking whether a given line is fine for someone else to read. You can change the scope later: Settings → Apps, open GitHub, then Choose repositories.

A private vault is fine. Access follows whatever your GitHub account already has permission to see, so there is no reason to make the repo public. There was never a good reason to publish your notes anyway.

If you are on a work account, GitHub may not appear in the list at all. On Enterprise and Edu workspaces an admin has to allow apps in workspace settings before anyone can connect one.

Create a project and attach the vault

Connecting the account is not the end of it. You still create a project and attach the vault repository to that project as a source.

The project is worth the extra step. You can point at a repository from a normal chat, but then you explain yourself again every time. A project shares its sources and its instructions across every conversation inside it. You write "use my vault" once, and the related conversations end up in one place instead of scattered through your history.

A project's detail view separates its chats from its sources, and you add material on the sources side. If the labels on your screen don't match mine, look for the place in the project's sources area where you pick a connected app. This part of the interface changes often.

Write the project instructions while you are there. Two lines were enough for me.

Search my vault notes before answering.
Cite the file path of any note you based an answer on.

The second line matters more than it looks. Without it you cannot tell whether an answer came out of your vault or out of general knowledge. If no path shows up, assume the vault wasn't touched and ask again.

The part that actually pays

Start a conversation inside that project and ChatGPT pulls from your notes without being told to. You stop attaching files and stop re-explaining the background at the top of every chat.

The gap shows up on questions that need your own context. General questions were always answered fine. But what you decided six months ago and why, or what you tried and abandoned, exists only in the vault. "If I've written about this before, read that first and then answer" turns into a request that actually works. That answer does not exist without the vault attached.

Know what gets read before you rely on it. The connector reads markdown, text, and code files, and it does not read commit history. A markdown-first vault loses nothing there, but PDFs and scanned images sitting in your attachments folder do not come through this path.

Right after connecting a vault, give it a moment. Indexing takes a while, so if a note you just committed doesn't turn up, wait and ask again.

Turning conversations back into notes

When a conversation runs long and lands on something worth keeping, ask for it as a note. It has already seen how the rest of your vault is written, so the front matter and title conventions usually come out close to right.

Saving is still your job. The GitHub connection reads; it will not commit to the repository for you from a chat. Paste the note into Obsidian and commit it yourself, which is the reliable option today.