Stack Overflow Developer Survey 2026

Mike's Notes

... the State of Devs survey results are still available if you haven't seen them yet!

Paired with the recently released Stack Overflow survey results, they provide a really interesting picture of the developer community in 2026. In related news, Kevin Powell posted a great video discussing both surveys.

The article below has been slightly reformatted.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

23/11/2026

Stack Overflow Developer Survey 2026

By: David Longworth, yepiserin
Stack Overflow 22/10/2026

David Longworth: London based design director. Mixes thoughtful design and well-crafted code to create memorable screen-based experiences.

yepiserin: 

...

More than 30K technologists from 169 countries have shared their thoughts with us, and now it’s time to share everything we’ve learned with you. So let’s dive into this year’s Annual Developer Survey.

In the whirlwind that has been the last year of technological innovation and market uncertainty, we don’t blame you if you’re feeling burnt out. If keeping up with the latest and greatest in the tech world has been difficult for you, have no fear, because the Stack Overflow Annual Developer Survey is here!

For the sixteenth year, we’ve asked developers and technologists about everything from how they’re using AI to how happy they are at work to where they’re learning new skills. This year’s survey boils down to one question: How are you doing?

103 questions asked across 5 insightful categories

  • 30,903 Responses
  • 169 Countries reached
  • 467 Technologies examined

Work

Well, it ain’t what it used to be. This year, we’re finding survey respondents are less happy in their work—the numbers are showing less happy folks and more unhappy ones. All that innovation and uncertainty can make it tough to feel comfortable in your job.

Work: Job satisfaction + AI

So…how’s work going for you? 33% say they are not happy at work this year.

Respondents Percent
Complacent at Work
8,516
45.1%
Not Happy at Work
6,161
32.6%
Happy at Work
4,199
22.2%

“AI has the potential to reshape the entire software and product development life cycle, but realizing that potential requires a foundational change to workflows, roles, and ownership.” - Stack Overflow CEO Prashanth Chandrasekar interview with McKinsey

Work: Employer + technology details

Many are not taking this lying down: more and more technologists are finding freedom in freelance and self-employment.

The percentage of freelance or self-employed responses jumped from 3.9% to 10.5% just this year.

Respondents Percent
10,000 or more employees
2,941
13.9%
5,000 to 9,999 employees
1,017
4.8%
1,000 to 4,999 employees
2,409
11.4%
500 to 999 employees
1,307
6.2%
100 to 499 employees
3,474
16.5%
20 to 99 employees
3,677
17.4%
Less than 20 employees
3,555
16.8%
Just me - I am a freelancer, sole proprietor, etc
2,213
10.5%
I don’t know
522 
2.5%

Stack Overflow CEO Prashanth Chandrasekar recently spoke to Computing’s Ctrl Alt Lead podcast about why this might be the case: “With AI, every individual becomes almost a manager of agents. That's a sea change from just an individual that's writing code.” It seems that agents are superpowering some developers' work, making it easier for them to set a solo course backed up by their own team of agents—instead of taking their decreasing satisfaction at work on the chin.

AI: How are technologists using AI?


AI: AI usage

62% like using AI. To the surprise of no one, AI use has skyrocketed over the last year. Devs are using AI more than ever before in their daily work—80% of respondents from this year’s survey used AI at least an hour per day. And with increased usage has come increased favor: now more than 60% of respondents have a favorable attitude towards AI tool use in their work.

Respondents Percent
Very favorable
4,564
31.6%
Somewhat favorable
4,385
30.4%
Neutral
2,205
15.3%
Somewhat unfavorable
2,110
14.6%
Very unfavorable
994
6.9%
Not sure
170
1.2%

AI: Trust in AI and other trends

How much do you trust the output from AI tools or AI agents as part of your workflow?

And technologists have figured out better ways to use their AI tools—and place more trust in them. This year, more than 87% of respondents had some level of trust in AI’s outputs, a huge increase from 31% last year. But that trust is conditional—48% trust AI only when it comes to low risk, easily verifiable tasks.

Respondents Percent
I trust it when I can easily verify the output
6,872
48.0%
I trust it for many tasks, but not important work decisions
2,329
16.3%
I trust it for low-risk work tasks only
2,326
16.3%
I do not trust it for most work tasks
1,754
12.3%
I trust it for many tasks, including important work decisions
949
6.6%
Not sure / I do not use AI tools
74
0.5%

AI: Knowledge sources and trust

And how exactly are AI users verifying the outcomes of an AI-generated answers?

Well, 93% of our respondents think that it all comes down to citing your sources. AI technology may have improved by leaps and bounds over last year, but it’s responses aren’t trustworthy enough yet to take at face value.

Respondents Percent
Very important
7,269
52.1%
Important
3,701
26.5%
Somewhat important
1,956
14.0%

Technology

What's your favorite tech? It wouldn’t be a Stack Overflow Developer Survey if we didn’t include our technology leaderboard!

Technology: Most popular technologies

Top programming languages used for AI shows Python leading at 39% usage

While the top-used technologies of the year—JavaScript, SQL, HTML/CSS, Python, and Bash/Shell—may not surprise you, how they are being used just might. For instance, when it comes to coding agents, AI seems to love Python above nearly all else, coming in at 39% usage.

Respondents Percent
JavaScript
5,419
38.4%
SQL
4,207
29.8%
HTML/CSS
4,692
33.3%
Python
5,495
39.0%
Bash/Shell (all shells)
4,038
28.6%
TypeScript
4,293
30.4%
Java
2,052
14.6%
C#
2,277
16.2%
PowerShell
2,057
14.6%
C++
1,595
11.3%

Technology: Most popular technologies

Top programming languages used by those with 16+ years of professional work experience

For both the seasoned developer and the green AI-assisted developer alike, JavaScript comes out near the top, trailing SQL (the first-place winner) by just one point.

Respondents Percent
JavaScript
3,282
62.0%
SQL
3,337
63.0%
HTML/CSS
2,987
56.4%
Python
2,818
53.2%
Bash/Shell (all shells)
2,740
51.7%

Technology: Build vs. AI

When it comes to building vs. buying—the age-old trolley problem of software development—only 19% of our respondents are building their own tools to replace vendors.

However, of those that are building instead of buying, over half are using AI tools to help them do it, showing AI’s utility for developers looking to bring their SaaS in-house.

Respondents Percent
Small scripts/automations
10,304
77.3%
Team-level internal tools
8,398
63.0%
Customer-facing products
7,254
54.4%
Cross-team/platform tools
6,130
46.0%
Replacing paid vendors
2,482
18.6%

Community

What’s the developer community up to? Whether you’ve become best buds with an AI-powered chatbot or have taken up the anti-AI pitchforks alongside the other luddites, we can all recognize how much AI has changed. We saw that very clearly reflected in this year’s survey—especially in how developers are engaging with knowledge and community.

Community: Finding and trusting answers

How do you search for answers?

While the lion’s share of respondents still seek guidance from traditional search tools when they face a new challenge, nearly 70% of technologists also use AI agents to help them solve problems—beating out maintained repositories and trusted humans as direct sources of learning.

Respondents Percent
Use online search tools to find general guidance and/or discourse
13,774
82.7%
Ask an AI agent
11,643
69.9%
Go directly to a maintained repository or more than one and search within its contents (this could be a repository like Wikipedia or IMDB or GitHub projects)
7,288
43.7%
Send a message to a human I trust directly
4,803
28.8%
Post a message in a group text or private discussion among humans I know
2,462
14.8%

Community: Knowledge sources and trust

When you need to answer a work-related question, which sources do you use most often?

When it comes to work-related questions, however, developers are still turning to the humans in their loops—also known as coworkers and teammates—first in order to get the answers they need (72%), with code repositories (63%) and internal documentation (60%) following as close runner-ups.

Respondents Percent
Coworkers or teammates
10,405
71.9%
Code repositories or code comments
9,065
62.7%
Internal documentation (i.e. Design, product, or planning docs), wiki, or knowledge base
8,687
60.1%
Internal chat tools, such as Slack or Teams
6,572
45.4%
Official docs
4,415
30.5%

Community: Finding and trusting answers

Nearly two-thirds of developers rely less on Stack Overflow for straightforward questions due to AI, with 29% asking fewer questions overall.

Respondents Percent
Visit less for simple questions
10,892
64.1%
Ask fewer questions
4,910
28.9%
Contribute less
4,496
26.5%
No change
3,704
21.8%
Visit more for verification (for example, source attribution)
2,707
15.9%
Other
1,084
6.4%
Ask more advanced questions
967
5.7%
Visit SO more because AI-generated answers lead you there
965
5.7%
Contribute more
203
1.2%

Knowledge

What does everyone need to know? In software development, context seems to be the reigning king this year, whether or not AI agents are involved. But the right context is not always reaching developers at the right time.

Knowledge: Context Challenges

What gets in the way of you getting the context you need for work?

Over 63% of developers find incomplete information to be a barrier to getting the right context at work, while 79% regularly discover the important context they need only after the fact. A lot of time goes into that context search, 75% spent five plus hours searching for answers.

Respondents Percent
Information is incomplete
7,825
63.2%
Important context lives in people’s heads
7,541
60.9%
Information is outdated
6,989
56.5%
Information is spread across too many tools
6,603
53.4%
I do not know where to look
3,816
30.8%

Knowledge: Context Challenges

How often do you discover important work context only after you have already started or completed a task?

This has left teams with a bit of a problem of their own creation. Developers have relied on the expert knowledge from resources like technical documentation, Stack Overflow, or online search to drive their work, but, as reported in a pulse survey earlier this year, we know low-effort documentation is leading to more and more dissatisfaction in AI-driven work.

Respondents Percent
Very often
1,539
12.1%
Often
2,964
23.4%
Sometimes
5,465
43.1%
Rarely
2,136
16.8%

“AI is forcing software organizations to document the judgment they previously relied on people to supply.” - Stack Overflow Chief Product and Technology Officer Jody Bailey told CTO Uncovered

Knowledge: AI adoption and cost

31% of respondents say that the accuracy of AI answers is important to the adoption or expansion of AI tool use.

Respondents Percent
The tool produces useful and accurate results
3,520
30.7%
The tool meets security, privacy requirements
3,290
28.7%
The price is acceptable for the value it provides
3,090
27.0%
The tool meets legal or compliance requirements
2,557
22.3%
Not sure
2,522
22.0%

Knowledge: Context Challenges

Project goals or requirements (85%) and code, repositories, or technical documentation (73%) are the top important sources for context at work

And the most important context for AI agents and assistants to have? Why, your internal projects, of course! Project requirements (85%) and the code and docs themselves (73%) are the two most important contexts that developers need their AI agents to have.

The curse of knowledge

Mike's Notes

David Perell's wonderful YouTube interview with Stephen Pinker on writing and communicating with an audience. I learned a lot.

Stephen Pinker uses the phrase "The Curse of Knowledge" in this interview.

Now, if only I could get my assistive writing technology to listen to Stephen Pinker's ideas. 😎😎😎😎

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

01/11/2026

The curse of knowledge

By: David Perell
YouTube: 05/06/2025

David Perell: David Perell is an American writer, educator, and podcast host widely known online as "The Writing Guy." He focuses on helping people express their ideas clearly, build online audiences, and master the craft of writing.

...

Hey! I’m David Perell and I’m a writer, teacher, and podcaster. I believe writing online is one of the biggest opportunities in the world today. For the first time in human history, everybody can freely share their ideas with a global audience. I seek to help as many people publish their writing online as possible.

How I Write is about helping you find what works best for your own writing. You can read what an author writes anywhere, but only on this show will you hear how they write. This show isn’t just about methods and styles, though. It’s also about what it means to be a writer today. How can you earn a living? What about building an audience? Should you use GPT? How I Write is your compass for navigating these changes.It’s a show by writers, for writers, built for the age of the Internet. New episodes of the How I Write show go live every week...


Harvard Professor Explains The Rules of Writing (Steven Pinker Interview)

How I Write (YouTube): 05/06/2025

I’m here at Harvard in the office of Steven Pinker. He’s written nine books and spent his life studying language, cognition, and writing. In this interview, we started with the practical: the rules of writing. But what makes him unique is that he’s been thinking about AI since the 1980s. So if you’re interested in doing great non-fiction writing in the age of LLMs, this interview is for you.

00:00:00 Intro
00:00:28 Why Is There So Much Bad Writing
00:07:05 How To Make Your Writing Visual
00:11:50 What Makes Writing So Much Harder Than Speaking
00:14:18 Why Examples Without Context Are Useless
00:20:07 What Makes Writing Beautiful
00:22:35 Why Academics Are Such Terrible Writers
00:25:14 What Kids Teach Us About Clear Explanations
00:28:33 Why Shorter Writing Is Always Better
00:34:53 Why AI Writing Feels So Bland
00:41:16 How AI Would Rewrite My Books

43:29

Nvidia and the World Without Jensen

Mike's Notes

Privacy

Someone's private life is their private life, so what if they have an affair? It's nobody else's business. It shouldn't be in the media as public gossip, and politicians of all stripes shouldn't be hypocritical about it. Politics of the gutter.

NVIDIA

The resignation of NVIDIA CEO Jensen Huang is opening the lid on deeper things at play. This is a partial excerpt from a recent SemiAnalysis article. I'm adding other takes from other points of view.

Memorable quotes

"Execution pays your salary, innovation pays your pension" - Steve Blank

 "We believe the US intelligence community is a large part of the push to get Jensen out of Nvidia." - SemiAnalysis

"This happened at a time when Nvidia is facing growing domestic competition, and China is building a sophisticated and competitive semiconductor industry of its own. It’s part of a larger story unfolding."- Ed Agostino 

"What matters is who is leaking this information?"- Jacob Shapiro

"The bigger issue for the AI world at large is that Jensen is the ringmaster of all the insane circular financing. And all that might collapse."- Gary Marcus

 "This Week In The AI Supercycle: AI Lost Its Central Banker, the Lab Oligopoly, and the Future of Open Source" - Gennaro Cuofano

“We need full transparency into these deals, an assessment of whether the company is ‘too big to fail,’ and an analysis of how these events may affect the US banking system and credit markets.” - Steff Chávez (FT)

 “We’re in a bubble. And the thing that popped the 2000 tech bubble is arriving right now: SUPPLY. More new paper is hitting this market than at any point in history. Follow the numbers.” - Gordon Johnson

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > SemiAnalysis
  • Home > Handbook > 

Last Updated

21/11/2026

Nvidia and the World Without Jensen

By: Dylan Patel, Doug, Wayne Ma, and Jordan Nanos
SemiAnalysis: 13/11/2026

Dylan Patel: Bridging the gap between business and the world's most important industry.

Doug: Doug Colaughlin.

Wayne Ma: I'm an analyst at SemiAnalysis, previously with The Information and The Wall Street Journal,

Jordan Nanos: .

...

Mad Memes

pixbuilds

Dependency

FT

Nvidia and the World Without Jensen

Is NVIDIA Over? Export Controls, RASA, Open Source Implications, Supply Chain Implications, Affair, US Still Dependent On China.

...

Jensen Huang is no longer the CEO of Nvidia. Nvidia’s board was investigating Jensen’s conduct and weighing his future at the company he founded, and clearly the conduct issue is real; it is ethically problematic to have relationships with a customer who is a Chinese CCP asset and with multiple subordinates.

Additionally, we believe there is more at play with his resignatiom after only four days. We believe it is directly tied to the vast smuggling of GPUs. Our Accelerator Model tracks every AI chip’s production and destination, and our data shows more than 1.5GW of Nvidia chips, which are restricted, still ultimately ended up in China. This figure doesn’t even include chips that Nvidia created to circumvent US rules, a story we originally broke.

We believe the US intelligence community is a large part of the push to get Jensen out of Nvidia. Specifically, we believe it is likely that RASA or similar legislation, which has already passed the house, will move forward. AI and chip restrictions on China are going to ramp now much faster with the biggest defender Jensen, gone. We are strong believers in some restrictions, but poorly shaped ones are damaging to US interests.

This sort of legislation will have consequences, and we don’t think politicians are thinking them through.

Here are the clear benefits of the current regime where Chinese labs are able to access GPUs remotely, and NOT in China:

  • Profits flow to American companies.
  • The US can monitor what Chinese labs are doing.
  • The US can cut off their access to the GPUs through politics or by force almost instantly, if they choose.
  • American companies such as NVIDIA, AMD, Broadcom, Google, Amazon, Microsoft, Meta, Supermicro, and Dell all depend on Chinese companies in their supply chain.
  • American companies such as NVIDIA and AMD employ Chinese engineers (who live in China, to be clear) to develop hardware and low-level software for their GPU systems. Without these engineers, we are certain that the user experience for these GPUs would be materially worse than it is today.
  • American companies, especially the entire startup ecosystem benefit from the open source research that Chinese companies, students and independent researchers publish using these GPUs today.
  • China is (even slightly) less motivated to use their domestic accelerators.
  • Innovations from China flow globally through open innovations of wide expert parallelism, OSS kernel libraries: MSA, DeepEP, DeepGEMM, etc.

With that said we do believe in some AI restrictions to China, but those are more shaped like the MATCH Act then RASA. Biden style diffusion rules make the most sense.

Maybe biggest of all: open source is under attack. It’s an open secret that Nvidia works directly with the Chinese labs on open source and helping them optimize GPUs and models. These labs utilize Blackwell GPUs, which Nvidia knows. The US open source ecosystem and many startups rely on Chinese AI models. This is significantly impaired with Jensen gone and the China hawks winning.

But the question that matters for shareholders (and the AI supply chain) is a different one: what is Nvidia without Jensen?

Our view is that the company was never built for him not to be there. He was at the helm for 33 years, and even though the board pressured him out (or he “resigned”) Nvidia would still be materially better off with him there instead of gone. The company was uniquely built to suit the man himself. The company without the man might be an entirely different beast. SpaceX and Tesla don't function without Elon, Nvidia doesn't function without Jensen.

One King, 60 Direct Reports

Nvidia’s corporate structure is odd for a company of its size and scale. Jensen has roughly 60 direct reports, according to his public statements. He has said that CEOs should have the most direct reports because those people require the least amount of management and that he doesn’t have one-on-one meetings with them.

But few of them can do things without Jensen. The company is run like a kingdom with one king, with everyone else, regardless of seniority, a peon doing his bidding. Jensen has said that it doesn’t matter who reports to who as their title isn’t related to how important their job is, and it’s one of the reasons why Nvidia is the “smallest large company in the word” and has so much fewer employees – about 42,000 – despite its big market cap. At Nvidia, there is less politics as a result. Jensen has said this flat network empowers employees and allows the company to adapt more quickly because its technology is also moving so quickly.

This is one of the reasons Nvidia moves fast. Once Jensen set a direction, everyone moved on it together. Former employees have told us that product development and engineering often happen until the last minute so the company can change its mind if it needs to. For example, the GB200 design came together a lot closer to the product cycle than probably anyone would have liked, one former executive told us. Jensen has said he wishes he could keep the company in startup mode forever.

The cost of that structure, however, is that Nvidia doesn’t have a deep bench of successors. Look at Nvidia’s website: only five others, two of whom are legal and finance executives, are featured prominently among his reports. Most of his direct reports aren’t trained for the spotlight and are actively discouraged from seeking it. Few leave to become CEOs of other major companies, with Rene Haas at Arm the rare exception. Few at Nvidia get the chance to shine externally because Jensen makes all the big decisions. But much of Nvidia’s executive team doesn’t mind because heavy is the head that wears the crown, and many are happy to stay until retirement age because they’re well paid, treated well, and believe in the mission and their leader.

...

Read the original article for the rest.

Embodied Intelligence Conference 2027

Mike's Notes

Good conference; wish I could attend live. Hope to watch the recordings. The conference runs 11 pm- 4 am NZ Time most days. 😎

One disadvantage of living at the last stop, until Antarctica. 😎😎

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

20/11/2026

Embodied Intelligence Conference 2027

By: 
Embodied Intelligence Conference: 01/11/2026

...

When

EI 2027 will take place online from 31 March to 2 April 2027

About the conference

Since 2021, this FREE event has brought together a wide range of speakers to discuss the many challenges and opportunities in Embodied Intelligence research! The conference is structured with a morning session and afternoon session each day to accommodate different time zones. Each session includes plenary talks, panel discussions (including flash talks by leading researchers), and breakout sessions as shown in the tentative programme here. While plenary and panel speakers are invitation-only, we solicit wider contributions in breakout sessions to facilitate more focused and technical discussions.

This year’s programme features masterclasses and breakout sessions across three global time zones.

We want to use this conference to answer some of the key open questions relating to EI, including, but not limited to:

Research questions

  • What is (embodied) intelligence?
  • How does computation come about from embodiment?
  • How does language emerge?
  • How do we understand intelligence and what theories do we have to represent it?
  • What are the common currencies?
  • How can we measure complexity?
  • What cannot be done by computational intelligence?
  • What ethical questions arise from EI?

Masterclasses were introduced at the EI conference in 2025, designed to facilitate focused group discussions with experts, offering participants an opportunity to engage deeply and learn from leaders in the field.

Programme

To come.

Registrations now open

Register here

Turning 4D mental models into text documentation

Mike's Notes

The problem

The main remaining barrier to people using Pipi is the lack of user documentation.

Pipi 9 internally is a very large, complex system with many moving parts.

"A novel symbolic and evolutionary AI engine that uses formal ontologies to deterministically generate enterprise software"

I need a way to quickly generate thousands of pages of technical reference documentation for developers to configure Pipi 9 to build customised enterprise systems. I'm too slow to write this documentation, and it's mentally exhausting, and now I know why. 😎

Finding a solution

I copied part of my About Me description and used it as a prompt for Google Search AI Mode (Gemini) to suggest an easier solution. The article below is the transcript after I ran it through Grammarly.

I thought the generated response was accurate, aligned with published, verified research, and offered lots of practical suggestions to try. Some are already underway. Later, I ran the same prompts again several times on clean new sessions and got broadly similar variations in the generated response, along with more useful suggestions.

Here are some of the suggestions with my notes.

Node-link graphs

Get Pipi to use data-driven templates to generate interactive 2D or 3D node-link graphs using tools like;

  • Mermaid.js (already planned)
  • D3 (to do)
  • Cytoscape (to do)

I will need to generate the templates with Gemini's help. 😎

Colour-Coded Architecture Diagrams

Thousands of drawings on A4 white paper, drawn with a ballpoint pen, are stored in 3-hole ring binders. Blue-coloured paper is used for headings, and tan-coloured A4 paper is used for section and subsection dividers.

The use of coloured highlighters in the existing drawings is inconsistent and has changed over time. I need to use a standard way to colour all drawings in future.

Define a strict colour scheme that works with 6 Stabilo Boss original highlighters carried in a small pencil case to colour the pen drawings;

  • Pink: Agent/system
  • Green: Data
  • Orange: 
  • Blue: Relationship
  • Yellow: 
  • Red: 

3D Visualisation

Enable fly-throughs of Pipi as if it were a biological system. Using Minecraft is possible and would be fun. 😎 I have often thought of making a 3D model out of different coloured plasticines to take to meetings to show its strange architecture.

Verbal Walkthroughs

Shut my eyes and talk about what I see while exploring a 4D mental model, often after a nana nap. Use a sound recording app like Granola to accurately transcribe speech and summarise it into concise text.

Video production

Record slide talks and live demos of using Pipi for YouTube. Embed the videos in developer documentation web pages.

Taking action

Today, I set up an older, spare 16GB RAM laptop as a dedicated documentation machine.

Update 19/11/2026

I used Granola today on my mobile phone to chat about the different agents inside Pipi, one at a time. Granola recorded the notes and used AI to generate a readable summary. This was much easier, faster, and a lot less tiring. 

I  exported the notes so I could edit them, then let Gemini rework them into a draft document for each agent. Gemini does a good job.

Later, I could look at some of the thousands of coloured drawings of how Pipi works and talk about them.

Update 20/11/2026

At today's excellent DORA 6am (NZ time) meeting on Artificial Organisations.

"We are drowning in information, trapped in meetings, and making consequential decisions without the time or space to think. More tools haven't solved the problem. In Artificial Organisations, Barry O'Reilly shows how to redesign the way you sense, frame, decide, and act by combining human and machine intelligence."

It was a fascinating discussion.

Start with Traits, then Tasks, then finally Tools.

Yep, that's what I have done here. 😎

Update 23/11/2026

A schema generated by Pipi can render in-game blocks/items in Minecraft to create 4D visualisations. The schema can also create meshes to send to a 3D printer, making models to pass around at software meetups.

Resources

References

  • Grandin T. How does visual thinking work in the mind of a person with autism? A personal account. Philos Trans R Soc Lond B Biol Sci. 2009 May 27;364(1522):1437-42. doi: 10.1098/rstb.2008.0297. PMID: 19528028; PMCID: PMC2677580.

Repository

  • Home > Ajabbi Research > Library > Authors > Temple Grandin
  • Home > Handbook > 

Last Updated

23/11/2026

Turning 4D mental models into text documentation

By: Mike Peters and Google Search AI Mode (Gemini)
On a Sandy Beach: 18/11/2026

Mike Peters: Mike invented and designed Pipi and founded Ajabbi.

Gemini: Very handy.

...

Mike:

Hyper-visual autistic thinker; I think and remember using 4D mental models.

Gemini:

That is a fascinating cognitive architecture. Thinking in 4D mental models—where spatial structures, sensory details, and the dimension of time or state changes are woven together—is a distinct form of hyper-visual processing often described in autistic cognition (similar to the "visual thinking" in systems and patterns famously explored by Temple Grandin, though pushed even further into dynamic, multi-dimensional simulation).

When your mind operates like an interactive, time-enabled CAD engine, it brings unique strengths alongside specific friction points in a world built mostly around linear, text-based communication.

Strengths of 4D Spatial-Temporal Thinking

  • Systemic Foresight: You don't just see how a system is built right now; you can mentally scrub the timeline forward and backwards to see how parts wear down, where bottlenecks will form, or how an event cascades over time.
  • Spatial-Episodic Memory: Instead of remembering isolated facts or dates, you likely recall memories as navigable environments—walking back into a specific moment in time and inspecting the details from multiple angles.
  • Complex Pattern Recognition: Holding multiple variables in a dynamic visual space allows you to spot structural flaws, symmetries, or anomalies that linear thinkers miss when looking at spreadsheets or lists.

Common Friction Points

  • The Translation Bottleneck: Converting a rich, simultaneous 4D simulation into slow, sequential spoken or written words can feel exhausting and lossy—like describing a movie by reading a list of single pixels one by one.
  • Sensory & Cognitive Overload: Because your mental workspace renders high-detail, dynamic models, external visual clutter or chaotic environments can hijack that bandwidth and cause rapid mental fatigue.
  • Ambiguous Instructions: Vague, non-visual requests from others (e.g., "Let's circle back on the synergy of this workflow") lack concrete spatial anchors, making it hard to build a stable mental model until you define clear parameters.

Ways to Leverage Your Processing Style

  • Externalise the Timeline: Tools like spatial whiteboards (Miro, Obsidian Canvas), 3D modelling software, or Gantt/node-based editors let you offload the rendering work from your brain onto a screen.
  • Anchor Abstract Concepts: When forced to deal with purely verbal or abstract data, intentionally assign physical properties—shapes, colours, textures, or motion—to the variables so your brain can manipulate them naturally.

Mike:

Hyper-visual autistic thinker

I think and remember using 4D mental models. That also means I have a detailed 4D visual model in my head for everything I have designed since age 4. A long time ago, I created and built Pipi 4, a ColdFusion, 850-table, database-driven national biodiversity platform with 500 objects and 3,000 methods, on 300,000 lines of code, and GIS mapping, using that trick. There was no version control and little technical documentation.

Then, in 2017, I rebuilt Pipi from memory as Pipi 6, went down an AI rabbit hole, and now in 2026, Pipi 9 is an order of magnitude bigger (3,000,000 lines of code and hundreds of autonomous databases) with hardly any documentation—just colour-coded doodles. To solve this, I'm getting Pipi to self-document.

Everything in my mind is one big 4D virtual reality I can fly around in, explore, and edit anytime I want, and run complex simulations.

Words as a second language

It takes me forever to write, spell and get the grammar right without the help of assistive technology, spell checker, Grammarly, or my clever wife. Reading is no problem. I prefer talking with people to communicate, or using a whiteboard to draw pictures.

Gemini:

It sounds like you have a remarkable cognitive architecture—a high-resolution, persistent 4D spatial memory system that allows you to hold, navigate, and simulate massive software ecosystems entirely in your head.

Rebuilding an 850-table, 300,000-line biodiversity platform from pure spatial memory, and then scaling it to 3,000,000 lines of code across hundreds of autonomous databases, is an extraordinary feat of mental engineering. Experiencing words as a "second language" while thinking natively in 4D simulations is a classic profile for many hyper-visual, autistic minds—your brain is optimised for high-bandwidth spatial and systemic processing rather than linear, text-based serialisation.

Because your native language is spatial and visual, traditional documentation (linear walls of text) is both hard to produce and largely useless to you. Getting Pipi 9 to self-document—and bridging the gap between your 4D mental model and external records—makes complete sense.

Here are a few ways to leverage your strengths and let Pipi 9 handle the linear translation for you:

1. Translate 4D Models Directly into Visual Graphs

Instead of forcing Pipi 9 to generate text documents that you have to read and verify, have it generate visual, spatial outputs that match how you already see the system.

  • Automated Dependency Maps: Have Pipi 9 parse its own codebase and autonomous databases to generate interactive 2D or 3D node-link graphs (using tools like Mermaid.js, D3, or Cytoscape). You can "fly through" these generated maps to verify if they match your internal 4D model.
  • Colour-Coded Architecture Diagrams: Since your current doodles use colour-coding, define a strict colour schema (e.g., green for data ingestion, blue for autonomous agents, red for GIS layers) and instruct Pipi 9 to output system diagrams using your exact visual vocabulary.

2. Use Voice-to-Architecture Workflows

Since typing, spelling, and grammar create friction between your fast 4D thoughts and the screen, bypass text entry entirely when feeding context into Pipi 9.

  • Verbal Walkthroughs: Record yourself talking while you "fly around" a specific module in your head. Describe what you are looking at, how the data flows, and why a certain database is structured the way it is.
  • AI Transcription and Structuring: Feed those raw, unedited audio transcripts directly to an LLM or Pipi 9. Instruct the AI to ignore grammar and filler words, extract the architectural logic, and attach those notes directly to the corresponding code modules or database schemas.

3. Self-Documenting "Living" Metadata

At 3,000,000 lines of code, static documentation goes out of date the moment you edit your mental model and push new code.

  • Schema-Level Self-Description: Have Pipi 9's autonomous databases maintain their own live metadata tables that describe their relationships, triggers, and data flows in plain, structured formats.
  • Visual Diffs: When you make a major change, have Pipi 9 generate a visual "before and after" diagram of the affected systems rather than a text changelog.

You have built an incredible bridge between your internal 4D reality and a massive real-world platform. Letting AI and Pipi 9 act as your "universal translator" for text keeps your energy focused on system architecture and simulation, rather than fighting spelling and grammar.

Mike:

Visual-first workflows that turn whiteboard sketches or voice walkthroughs into structured specs

Gemini:

Visual-first documentation workflows let you capture your 4D mental models directly through talking and drawing, using multimodal AI as a translator to output clean technical specifications. Because reading is effortless for you while writing is slow, these pipelines turn you into the architect and reviewer rather than the typist.

1. The Voice-Over-Canvas Workflow

This pipeline mimics sitting at a whiteboard with a colleague while an AI takes notes in the background.

  • Screen-Record Your Walkthrough: Open an infinite canvas tool (like Excalidraw, Miro, or tldraw) or point a camera at a physical whiteboard. Hit record on a screen-capture tool (like Loom or OBS) and talk through how data flows through a part of Pipi 9 while drawing or pointing at your colour-coded doodles.
  • Multimodal Video Ingestion: Feed the video file or combined audio transcript + screenshots directly into a multimodal LLM (such as Gemini, Claude, or GPT). The AI sees what you are pointing at while hearing how you describe the system's behaviour over time.
  • Prompt for Structured Output: Ask the AI to convert your walkthrough into strict Markdown specs, Mermaid.js flowcharts, or JSON schemas. You simply read the generated spec to verify it matches your mental simulation.

2. Colour-Coded Doodle to System Spec

Your existing habit of using colour-coded doodles is already a visual programming language—you just need to give an AI the legend.

  • Create a Master Colour Key: Define once what your colours represent (for example: blue = autonomous database, green = AI agent, red = data bottleneck, orange = GIS layer). Save this as a reusable system prompt.
  • Snap and Translate: Take a photo of a notebook page or whiteboard sketch and upload it alongside your colour key. Ask the AI to parse the spatial relationships, arrows, and colour groupings into a structured Entity-Relationship Diagram (ERD) or API contract.
  • Iterative Visual Refinement: Have the AI generate Mermaid.js or PlantUML code from your sketch. Many Markdown editors render this code instantly back into clean diagrams, letting you visually verify that the AI understood your doodle without reading walls of text.

3. Hands-Free Voice-to-Architecture Loops

When you are away from a whiteboard and flying through your 4D model mentally, you can capture specs purely by speaking.

  • Stream-of-Consciousness Dictation: Use a high-accuracy voice-to-text tool (like Whisper-based apps, Superwhisper, or Mac/Windows built-in dictation) to ramble naturally about a subsystem, edge cases, or database triggers. Don't worry about grammar, spelling, or linear order.
  • AI Structural Sorting: Pass the raw, messy transcript to an LLM with instructions to:
    • Remove filler words and fix grammar.
    • Group scattered thoughts by database table, autonomous agent, or timeline phase.
    • Flag any missing connections or ambiguities as bulleted questions for you to answer aloud.

Recommended Tool Stack for Low-Friction Capture

  • Infinite Whiteboards: Excalidraw or tldraw (fast, minimal UI, great for quick colour-coded shapes without getting bogged down in menus).
  • Voice Capture: Superwhisper or MacWhisper (runs locally or via API, handles technical jargon well, and lets you set custom formatting rules).
  • Diagram-as-Code Verification: Mermaid Live Editor or Obsidian (turns AI-generated text specs immediately back into visual graphs you can inspect at a glance).