oliverdavies.uk/content/node.d2eecbf6-261e-4326-acc3-47c6e82da0cf.json

{
    "uuid": [
        {
            "value": "d2eecbf6-261e-4326-acc3-47c6e82da0cf"
        }
    ],
    "langcode": [
        {
            "value": "en"
        }
    ],
    "type": [
        {
            "target_id": "daily_email",
            "target_type": "node_type",
            "target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
        }
    ],
    "revision_timestamp": [
        {
            "value": "2025-04-16T14:13:07+00:00"
        }
    ],
    "revision_uid": [
        {
            "target_type": "user",
            "target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
        }
    ],
    "revision_log": [],
    "status": [
        {
            "value": true
        }
    ],
    "uid": [
        {
            "target_type": "user",
            "target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
        }
    ],
    "title": [
        {
            "value": "Why I work in Neovim"
        }
    ],
    "created": [
        {
            "value": "2022-08-25T00:00:00+00:00"
        }
    ],
    "changed": [
        {
            "value": "2025-04-16T14:13:07+00:00"
        }
    ],
    "promote": [
        {
            "value": false
        }
    ],
    "sticky": [
        {
            "value": false
        }
    ],
    "default_langcode": [
        {
            "value": true
        }
    ],
    "revision_translation_affected": [
        {
            "value": true
        }
    ],
    "path": [
        {
            "alias": "\/daily\/2022\/08\/25\/why-i-work-in-neovim",
            "langcode": "en"
        }
    ],
    "body": [
        {
            "value": "\n          <p>Over a year ago, I posted that I was <a href=\"http:\/\/localhost:8000\/blog\/going-full-vim\">switching to using Neovim full-time<\/a> for my development work.<\/p>\n\n<p>I'd used Vim one file at a time on remote servers, and added Vim plugins in other IDEs and editors, so I was already familiar with a lot of the key bindings and motions before I decided to use it full-time.<\/p>\n\n<p>Still, it was tough to begin with, but once I'd learned how to configure Neovim, I also learned that being able to customise and extend it as much as you need to is one of its main advantages compared to other IDEs and code editors.<\/p>\n\n<p>TJ DeVries - a Neovim core team member - has recently coined the term \"PDE\" (a personalised development environment) which, for me, describes Neovim perfectly.<\/p>\n\n<p>Currently, I have a fuzzy-finder to quickly open files (as well as many other things), an LSP client to add code intelesense, auto-completion, refactoring tools, custom snippets, and very recently, a database client and a HTTP client.<\/p>\n\n<p>Just as important to me, I've found a growing community of other Neovim users who stream on Twitch, post YouTube videos, write blog posts, or publish their dotfiles for others to see and reference.<\/p>\n\n<p>I've learned Lua. Not just for my own Neovim configuration, but I recently wrote and open-sourced my own simple plugin.<\/p>\n\n<p>Like Git, I enjoy and prefer using tools that I can configure and adapt to my workflow.<\/p>\n\n<p>Given Neovim's flexibility and configurability, its expanding feature set both in core and community plugins, and the growing community, I think that Neovim is going to be something that I continue to use and adapt for a long time.<\/p>\n\n        ",
            "format": "full_html",
            "processed": "\n          <p>Over a year ago, I posted that I was <a href=\"http:\/\/localhost:8000\/blog\/going-full-vim\">switching to using Neovim full-time<\/a> for my development work.<\/p>\n\n<p>I'd used Vim one file at a time on remote servers, and added Vim plugins in other IDEs and editors, so I was already familiar with a lot of the key bindings and motions before I decided to use it full-time.<\/p>\n\n<p>Still, it was tough to begin with, but once I'd learned how to configure Neovim, I also learned that being able to customise and extend it as much as you need to is one of its main advantages compared to other IDEs and code editors.<\/p>\n\n<p>TJ DeVries - a Neovim core team member - has recently coined the term \"PDE\" (a personalised development environment) which, for me, describes Neovim perfectly.<\/p>\n\n<p>Currently, I have a fuzzy-finder to quickly open files (as well as many other things), an LSP client to add code intelesense, auto-completion, refactoring tools, custom snippets, and very recently, a database client and a HTTP client.<\/p>\n\n<p>Just as important to me, I've found a growing community of other Neovim users who stream on Twitch, post YouTube videos, write blog posts, or publish their dotfiles for others to see and reference.<\/p>\n\n<p>I've learned Lua. Not just for my own Neovim configuration, but I recently wrote and open-sourced my own simple plugin.<\/p>\n\n<p>Like Git, I enjoy and prefer using tools that I can configure and adapt to my workflow.<\/p>\n\n<p>Given Neovim's flexibility and configurability, its expanding feature set both in core and community plugins, and the growing community, I think that Neovim is going to be something that I continue to use and adapt for a long time.<\/p>\n\n        ",
            "summary": null
        }
    ],
    "feeds_item": [
        {
            "imported": "2025-04-16T14:13:07+00:00",
            "guid": null,
            "hash": "acbf8c7860499e7d86f343897faab434",
            "target_type": "feeds_feed",
            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
        }
    ]
}