Following up from a recent post I saw, I asked a #ai #chatbot to make up 3 personas based on #emacs, #vim and #vscode. The outcome was rather predictable:

```
**Richard (Emacs User)**

* **Core Drive:** Ultimate control and extensibility. Richard sees Emacs not just as an editor, but as an operating system for his programming life.
* **Cognitive Style:** Deeply analytical and enjoys understanding underlying mechanisms. He thrives on dissecting problems and building intricate, interconnected solutions.
* **Workflow:** Highly customizable and ritualistic. Richard has spent years tuning his environment, developing bespoke functions and keybindings that automate complex tasks. He likely uses Emacs for everything from writing code to managing email and reading RSS feeds.
* **Temperament:** Patient, persistent, and deeply intellectual. He's not afraid of a steep learning curve and finds satisfaction in mastering complex systems. He may be perceived as a purist or a bit of a Luddite by some, but he values depth over breadth.
* **Social Interaction:** Might be more reserved, comfortable in his well-crafted digital space. He enjoys engaging in deep technical discussions but might find casual chat less stimulating.

**Eric (Vim User)**

* **Core Drive:** Peak editing efficiency and modal mastery. Eric views editing as a craft where speed, precision, and fluidity are paramount.
* **Cognitive Style:** Tactical and focused on immediate, high-impact actions. He excels at identifying patterns and applying sequences of commands to achieve results rapidly.
* **Workflow:** Optimized for speed and minimal hand movement. Eric's muscle memory is his primary tool. His environment is likely lean, with essential plugins, designed for quick context switching and fluid navigation through code.
* **Temperament:** Pragmatic, results-oriented, and often confident. He appreciates elegant solutions that are immediately effective. He might be seen as sharp and direct, valuing brevity in communication as much as in editing.
* **Social Interaction:** Likely enjoys banter and competitive coding challenges. He's often passionate about his tools and enjoys sharing tips and tricks, but can also be fiercely opinionated about the superiority of his chosen method.

**Steve (VS Code User)**

* **Core Drive:** Broad functionality and seamless integration. Steve wants a powerful, all-in-one tool that "just works" and connects easily with other development services.
* **Cognitive Style:** Pragmatic and solution-oriented, valuing immediate utility and a low barrier to entry. He's adept at leveraging existing tools and readily adopts new features that enhance productivity.
* **Workflow:** Highly curated but less "built from scratch." Steve likely utilizes a rich ecosystem of extensions to add specific functionalities (linters, debuggers, Git integration, etc.). His environment is productive with minimal initial configuration, and he enjoys the visual feedback VS Code provides.
* **Temperament:** Sociable, adaptable, and generally enthusiastic. He enjoys collaboration and is quick to adopt popular trends and tools that streamline team workflows. He might prioritize getting the job done with the most accessible, well-supported tools.
* **Social Interaction:** Very team-oriented and collaborative. He's likely to be involved in code reviews, pair programming, and actively seeking out the best tools to facilitate team success. He's often an early adopter of new technologies.
```