PDE: A different take on editing code
Channel:TJ DeVries · Length:20:01 · Published:2022-06-28 · Views:88079
Summary
TJ DeVries coins the term PDE (Personalized Development Environment) to describe editors like Neovim that you shape to your own workflow. He contrasts this with out-of-the-box IDEs and discusses why customizable tools appeal to developers.
Why HN recommends it
It is the cited origin of the 'PDE' term, which HN uses when discussing vim, Neovim and Emacs as personally customized environments.
For anyone not understanding why (neo)vim exists, or why some developers prefer it to IDEs, I suggest watching — HN, 2023
Testing, debugging & developer tools
Subtitles (excerpt)
hey YouTube it's me TJ deze here to talk about a term that I hope can sort of answer this question that I often get which is basically why would you use neovim right and the answer actually doesn't necessarily revolve exclusively around neovim I think it actually revolves more broadly around this term that I want to call pde PD stands for personalized development environment today I'll explain both what I mean by that term and hopefully it sort of gives some new Clarity between text editor and IDE as well as show a few things about why neovim is a good candidate for being a PD so I hope you enjoy this talk if you have questions concerns anything like that feel leave them in the comments you know what to do thanks everybody let's get to it so let's give a little context first this term pte first occurred to me when people were asking me do I think neovim is a text editor or do I think it's an IDE and my answer was basically I don't think that it's either of them when I think of a text editor I think of something that is exclusively focused on editing text which I don't think Neo's exclusive focus is on that we ship with an LSP we have treesitter we have some things that are Beyond just the literal editing mechanics of moving
On Hacker News
> Lua is great, but one JSON file is even better I will never understand how you go back from a very customized editor setup to the one with "reasonable defaults with little to no things to configure". Great talk on this topic by TJ: Personal Development Environment: [VIDEO] — ivanjermakov, 2025-01
For anyone not understanding why (neo)vim exists, or why some developers prefer it to IDEs, I suggest watching "PDE: A different take on editing code" [1]. It reframes (neo)vim as a "Personalized Development Environment". I've been using (neo)vim for years, and don't want to use anything else. It isn't just about productivity (I would probably be as productive in an IDE). It's because its _mine_.… — ts0000, 2023-01
Well, I'd rather call it a PDE (Personal Development Environment)[0]. A term coined in the Neovim community that is pretty apt for Emacs too. Emacs can be pretty minimalist or maximalist depending on your preference, and it can be configured to have IDE-like features, though presented in a different way sometimes. Honestly, the big barrier to entry for Emacs is finding the time to configure it to… — aquariusDue, 2025-08
TJ actually has a video on this very topic [VIDEO] The tl;dw is that the term 'PDE' means the tool requires some work in order to personalise, but because neovim exposes a robust API that work is fun and rewarding. Additionally, he makes the point that because you configure it in the same language as you script it with (lua), you have much greater control over how all the pieces fit together. — petepete, 2023-11
I think it's worth it, if you are a tinkerer and if you look at that kind of software as a "Personal Development Environment" a phrase I first heard in this video[1]. So, yeah the focus is on creating software that is tailored to your requirements. If your requirements are that someone else has to be able to use it, because you do a lot of pair programming, then that's something to consider. I've… — littlelady, 2023-04
Related videos
- RailsConf 2014 - All the Little Things by Sandi Metz · Confreaks · 38:47
- "Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson · Strange Loop Conference · 40:20
- 🚀 TDD, Where Did It All Go Wrong (Ian Cooper) · DevTernity Conference · 1:03:55
- Bret Victor - Inventing on Principle · Rui Oliveira · 54:20
- Solving Problems the Clojure Way - Rafal Dittwald · Clojure/north · 1:02:26
- Debugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017 · GOTO Conferences · 52:34
- "Performance Matters" by Emery Berger · Strange Loop Conference · 42:15
- A Tour of the Acme Editor · Russ Cox · 23:16
- Tech Talk: Linus Torvalds on git · Google · 1:10:15
- "How NOT to Measure Latency" by Gil Tene · Strange Loop Conference · 42:59
- Ruby Conf 12 - Boundaries by Gary Bernhardt · Confreaks · 45:55
- Using Python to Code by Voice · Next Day Video · 28:17
- How to Do 90% of What Plugins Do (With Just Vim) · thoughtbot · 1:14:02
- Lecture 6: Version Control (git) (2020) · Missing Semester · 1:24:59
- Literate Devops with Emacs · Howard Abrams · 28:36
- Dan Abramov - Live React: Hot Reloading with Time Travel at react-europe 2015 · ReactEurope · 30:40