 — maybe even created it? Not sure… google it) and he was talking about the way he had updated his keyboard layout to avoid “finger gymnastics” when typing code. 

I suddenly became very aware of the weird and wonderful contorted movements I was doing with my hands on the keyboard when I was coding.

Holding ‘shift’ whilst twisting my hands and wrist slightly to reach the ‘curly brackets’. Stretching a little more to reach the ‘normal brackets’. Hands jumping all over the keyboard just to write a small function.

I instantly realised I was using my main set of tools — 

 (yes and my brain… I get that’s the most important tool but lets not get bogged down in semantics)- in a horribly inefficient way.

Switching to Vim Motions in Cursor Completely Changed How I Navigate Code

It also makes me highly skeptical of those “Gurus “ online who tell you it’s so easy to make money on a side hustle. Maybe it is for some people but it certainly isn’t for me.

Recently though, and maybe a consequence of getting older, I am settling into a stack that I think gives me everything I need for a personal web project. That stack is:

These are the main reasons I like this stack:

The Frontend uses React which I have used for many a year. I really like React and I can be pretty productive in it. 

 gives you all that React goodness plus all the Tanstack goodness!

My New Favourite Stack — Tanstack Start, Laravel, Postgres and Mantine

I have seen AI as more of another tool to use in a developers’s toolkit.

 It can be a very useful tool in some circumstances but a tool none the less. Therefore, I like to make small incremental steps when introducing any AI into my workflow.

. I have been quite impressed so far and think it can help in my existing workflow and make my daily developer life a little better.

The README is really well documented and it was easy to get it setup in Cursor. I got it connected to our Jira board that we use at work all within a few minutes.

Using the Atlassian MCP server in Cursor

However, over the last couple of months it has been dawning on me that if you are a experienced, seasoned or senior developer (whatever you want to call yourself) you are in a beautiful position to utilise this amazing new tool that has forced itself into our everyday lives. I want to make the case that AI is not a threat to our jobs but a big boost. However, (and it’s a big HOWEVER) it all depends on how you use it.

Senior Developers Have The High Level View

 from the talented TJ DeVries and he talks about using AI to learn. Himself and (The) Primeagen were building an app with Laravel, which they both didn’t know, and found the LLM predictor to be very useful. It was providing patterns for them in a language they weren’t familiar with and they took it 

This is the massive advantage that experience Developers have right now. They know enough theory, patterns and programming fundamentals that they can quickly determine if the output from the LLM of choice is a Hit or Miss. They also know the right questions to ask or right prompts to give which I have found to be very important and not spoken about much.

It’s the Perfect Time to be a Senior Developer

The persistent inability to believe that one’s success is deserved or has been legitimately achieved as a result of one’s own efforts or skills.

Which seems to make sense in a highly cognitive environment where Software Developers find themselves.

You see people sat at their desks working fastidiously on some complicated UI on the monitor

I’m always amazed in office environments at how professional and serious everyone appears to be at first glance. When you go into an office for the first time, be it an interview or a new position, you see people sat at their desks working fastidiously on some complicated UI on the monitor. They’re dressed seriously, their expression is one of seriousness and concentration and there is that low level noise of keys being tapped and mouses (mice?) being clicked and 

It’s very easy to be convinced these people are geniuses who are operating at a super human level and that you have no right to be amongst these rarified supreme individuals

It’s even more compelling in an office full of developers. Their screens are much more elaborate and impressive. Screens filled with dark squares placed precisely into strategic compartments with rows of different coloured text flashing continuously across them. Terminal windows printing rows and rows of obscure text and different windows popping up here and there and then quickly disappearing again. It’s very easy to be convinced these people are geniuses who are operating at a super human level and that you have no right to be amongst these rarified supreme individuals.

As you peer closer the illusion starts to shrink away. That terminal window you thought they were using to hack into some top secret government server is actually being used to ssh into a AWS server to check the right docker image is running. That rows and rows of different coloured text is actually some HTML which is used to render the ‘About Us’ section on the company website. That unrecognised text editor one developer is using is actually just Neovim… wait! That guy is a genius! I jest… but my point is, if you understand what these developers are actually doing its all very logical and usually not so complicated.

I almost felt guilty for not knowing things and if anyone was to find out I didn’t know certain things then that’s it! The game is up.

I Rarely Asked Questions as a Junior Developer

I remember very distinctly the feeling I felt when starting out as a developer. I started with 4 other developers of different skill levels at exactly the same time. I was the developer with the least technical experience. In all honesty I think I was lucky to get the job from a technical perspective. I had other skills from my previous working background but my technical skills were distinctly lacking.

I knew this and I couldn’t shake the thought that I ‘

’ (I’ve later come to realise that ‘

’ is a very dangerous word to tell oneself). I almost felt guilty for not knowing things and if anyone was to find out I didn’t know certain things then that’s it! The game is up. My head will be on the chopping board and I would be sent packing with my tail between my legs. In order to avoid this potential scenario I adopted the best strategy available to me. 

I chose this strategy because I figured if I don’t say anything, then I can’t say anything stupid. 

If I were to say something stupid then my colleagues would quickly figure out I am a fraud and I will be exposed.

 If I didn’t say or ask anything then my colleagues will just assume I already know whatever they happen to be talking about. I will be the silent developer in the corner. The mysterious quiet one. Or so I thought.

This strategy however had one major downside. I couldn’t ask questions. It turns out (and this might come as a massive shock) that questions are really useful for finding out things. If you don’t know something and you’re speaking to a person who does know something, by asking questions you can find out what they know. Incredible right!

But choosing a strategy of silence makes the strategy of asking questions difficult. 

. I therefore had to resort to finding things out by other means. Reading Stackoverflow (it was a site used before ChatGPT to find answers to specific programming questions), searching through Google (it was a site used before ChatGPT to find links to specific websites that might provide insight to whatever specific problem you have) and watching tutorials (do people still watch tutorials?).

Looking back, maybe this actually had some benefits. I learnt to be self sufficient. I learnt how to be resourceful even in the face of seemingly insurmountable challenges. I learnt from other developers albeit through reading instead of talking.

Adopting this strategy meant I missed big opportunities to learn from those around me. This is one of the beautiful things about working in a team. You get to speak and learn directly from colleagues who will all have different levels of experience. Many would have toiled and suffered to learn certain things that they can then teach you in 5 mins. And vice versa, those things you have learnt the hard way might be just what your colleagues need on a certain project.

I am not sure exactly when the penny dropped for me, but it was after many years of developing. Maybe the fact I hadn’t been kicked out the team yet and had actually received a promotion started to alleviate fears that I was a complete imposter.

I had also read Jordan Peterson’s book where he speaks about ‘

. I’m paraphrasing but he basically said if you are ignorant and you ask questions, first off the person you are talking to can understand where your gaps in knowledge are so they can focus on those parts in their explanations and secondly, if you ask 1000 questions pretty soon you’re not going to be ignorant anymore.

This strategy does come with a caveat though. You can’t just constantly be asking questions and expect all the answers to come your way.

For some reason this really clicked with me so I decided to drop my pride and when I didn’t understand what someone was talking about I would ask questions. Even if I thought I ‘

’ know the answer. Turns out this is actually a better strategy than silence.

I started getting a better understanding of problems coming my way. I started learning things that I had been too afraid to ask about previously. I started to better understand different developers’ points of views.

This strategy does come with a caveat though. You can’t just constantly be asking questions and expect all the answers to come your way. Have everyone else do the hard work of finding stuff out so you don’t have to. You have to still put effort in and do some work to find answers yourself so then when you do have questions, it’s obvious to the person you’re speaking with that you have done all you can on your side.

An example of a bad question would be coming into a meeting and asking ‘What’s this meeting about?’ when the agenda has been clearly defined in the invite. This just comes across as you being lazy and unprepared which are not good traits in a professional working environment. Your colleagues will silently notice this.

Another example of a bad question is asking questions which have been answered or addressed in the recent past. Say you’re in a meeting and someone presenting is explaining what a particular section of code does. If you then ask 2 minutes later what that particular section of code does then it just looks like you weren’t listening. By all means ask questions to clarify certain aspects of what they are explaining but don’t just ask lazy questions because you weren’t listening or paying attention.

There is so much to know and learn in the world of Software Development and you will never know everything. To that end it’s OK to not know. It’s therefore ok to ask questions. In fact asking questions helps clarify to the other person what you understand about what they’re saying and what you don’t. It gives them hints as to what they should focus on elaborating in order for whatever is being discussed is understood by all.

Questions in team settings can also really help because if you don’t know something then chances are someone else in the room also doesn’t know so you’re doing you and that other person a favour by asking questions.

However, don’t be lazy with your questions and don’t ask questions about absolutely everything. This can have the opposite effect to what you may have hoped.

Should you ask questions as a Software developer? What are the benefits of asking questions?

As a Senior Developer I Ask More Questions

Create, edit, manage and load complex Tmux session, window and pane configurations with ease.

This basically means if you have one Tmux window open where is your terminal, another Tmux window open which are you tests and another Tmux window which is your editor and all of these are for a specific project you can create a Tmuxifier 

 With one command in the terminal you can be up and running and get cracking on your work.

This might be clearer with an actual example…

You also need Tmux. (If you don’t know what Tmux is then check out my other 

, there are pretty clear instructions about how to install it and get it up and running. Make sure you follow all the instructions as it’s not just a case of 

 and thats it. You also have to update your 

In Tmuxifier you can basically create and edit 

 here are the same as the Tmux definitions.

 for my blog that I develop locally on my computer. I was feeling particularly creative that day so I called it blog. To create this 

This created a bash file blog.session.sh in which you can write the script for setting up your session. What I have set up is very basic for my blog as it’s a simple application but hopefully it will give you an idea and inspiration to get started:

seesion_root — This sets the root directory for your session.

if initialize_session "blog"; then — This is part of the boiler plate code when you create a new 

 but it’s basically initialising the session with the given name.

new_window — This creates a new tmux window in this session and gives it the name provided in the double quotes.

select_window — Selects the window provided in the double quotes. If the name in the quotes doesn’t exist it throws an error.

run_cmd — Runs the command provided in the quotes.

Honestly, it’s all pretty straightforward and easy to get going with this. In this particular instance I am just opening two windows in Tmux and getting my frontend and backend code bases running for my blog.

I’ve been using Tmuxifier for a few weeks now and these are the most common commands I am using:

This command allows you to actually load the 

Is this tool going to totally change your life? Probably not. But it will help you get up and running on projects that you are consistently working on. Half the battle sometimes can just be getting up and running so by running one command to be able to get going is a win.

Plus I have found I now keep my desktop more tidy. I used to leave my terminal windows open at the end of the day so I didn’t have to set up everything the next day. Now I can quite happily close everything when I have finished working on a project knowing I can come back the next day and get my setup up and running quickly.

I am a Frontend Developer working mainly with React and Typescript in my day-to-day professional life. I love exploring new tools and libraries and love the Javascript Ecosystem.

Discovering Tmuxifier and how it can improve your development environment.

Tmuxifier — One Up Your Tmux Game

As soon as the world realised the potential of ChatGPT there has been a 

 about “This is the end of programmers”. Apparently it’s only a matter of time before AI improves to the point where it can take over everything that a software developer does. Recently the latest and greatest AI implementation to replace developers was introduced — Devin — and of course the internet was flooded with 

So I thought why not try and visualise what a world without developers would actually look like. To see if it’s possible to imagine this world and how it would function. To actually look at some practical day-to-day examples to see how AI could work in this potential future.

The situation I want to imagine is for a small to medium company, let’s say 50–200 people. They have some sort of hardware products, some internal web tools and some web presence too. They work with dynamic applications, not just static websites and they have customers that they produce and sell things too.

We can start with a custom application that internal users use. It’s a custom built web based application that interacts with a backend API that acts as a interface to some business logic.

 of this application wants to add another field to one of the views to capture some kind of data that currently isn’t being captured (

let’s assume this person has been deemed the responsible one to make changes on the existing application

Even if all developers disappear and are replaced by AI and the whole thing is just working seamlessly, who is controlling the AI?

My immediate thought is there is some AI interface they can talk to and they bring it up and say something like:

“I want to add a field here to capture the manufacturer of this particular part in our product”

What happens next? I guess there are a whole host of choices:

The AI produces a few mockups almost instantly allowing the user to decide which best aligns with what they requested.

The AI just implements the field straight away on the live application for the user to try out and iterates from that directly in the live code.

There is some staging application the AI implements the field on for the user to test out.

And what about under the hood? Well I guess I am making 

a massive assumption that AI produced applications will use the same tech stacks as we use now

They update the relevant schemas and models on the backend.

They implement the Frontend from the design that was accepted by the user

They deploy all this to the production servers

I mean it’s not beyond the realms of possibility but I have a few questions:

If iterating on the live app, are they updating all the backend and frontend code simultaneously?

How is the code base structured? Would it be separated into modules and nice and readable to a human like it is now or will it just be raw machine code?

What happens if the AI just doesn’t understand what the user wants and every iteration is just not close to what the user is asking for? How to rectify this situation?

How is the design produced and made realistic? AI images from DALL-E and Midjourney are fantastical looking but 

I’ve noticed that “Iteration” doesn’t seem a familiar concept to AI. You ask it to tweak something on an image and it comes back with something quite different.

7 — Definitely some questions around this but not beyond the realms of possibility.

Let’s take a little leap now and imagine the user of this internal application wants to add a whole new complex feature. They have a vague idea of what they want but they would find it very difficult to articulate their idea out loud.

Would the AI be able to utilise all it’s datasets and piece together something novel?

With an AI application that relies on voice instructions this would prove tricky to say the least. The user could certainly have a go and maybe it would just be a case of 

I am not sure what would happen if this new feature was truly something novel. Would the AI be able to utilise all it’s datasets and piece together something novel? Who knows… but I can imagine that building out this feature could be very frustrating for the user.

In a current setup, very often the user will come with a vague idea to the software team who will in turn interpret what they heard and there would be a 

back and fourth dialogue in which the idea gets flushed out and the details slowly start getting filled in

. There is also inspiration in these group chats as ideas are bounced off of each other.

AI does everything off of data. Basically everything is produced off of the past, off something else that already exists.

Maybe in this imagined future with AI, it would require a group of people flushing out the idea first and then interacting with the AI? I can’t help but think someone of technical knowledge would be very useful in this situation (i.e. a Software Developer) to give an idea of whats feasible and to translate and interpret to the AI.

4 — I suppose it could happen in the right situation but I would imagine in reality the bigger the feature request, the more chance AI just won’t be able to interpret what is needed.

What about the building of a completely new application? How would this work in a world without developers? In most companies I have worked in when there is an idea about a new application, a 

 is usually built. This is done for a number of reasons:

It’s a way to get something up quickly that resembles the initial idea.

It’s cheaper than building out an app of production quality.

It allows the opportunity to actually try something out to see if it will actually work if implemented properly. With a new app it’s often not obvious if the whole thing will actually do what is expected in reality.

It focuses attention on what are the essential aspects of the app and only include those in the initial version.

With AI cheapness and quickness could potentially be taken out of the equation. AI theoretically can build things very quickly compared to a human developer. It also doesn’t require wages so it is relatively cheap. Plus it doesn’t sleep so can work around the clock. (You can see why investors and business people are getting so excited about the prospects of AI).

I think one thing that has been grossly underestimated is the amount of effort it will require to build a production quality application with the help of AI

The big question here for me is would a human be able to articulate well enough what they want in order for an AI interface to be able to build out an accurate representation

? I think in time they would be able to. I would imagine it would be similar to carving a statue with a stone. First start off with the main large pieces and gradually over time start redefining all the details.

However, I think one thing that has been grossly underestimated is the amount of effort it will require to build a production quality application with the help of AI. Even if the AI models have evolved from what we currently have it’s still going to be working from a human’s instruction. The initial idea will come from humans and the reality is that 

a real life application has so many details in it that are so far away from the initial idea of that application that AI or not, it still takes many iterations to get there

3 — Depends totally on what app is being built. For a generic blog or dashboard app I’m sure AI will manage quite well. For anything custom I think it would be a disaster.

One thing is to consider is that the whole paradigm of:

This may well change. The only reason we have mockups these days is it’s a quick and easy way for the developers to understand what is actually being requested and for the users to get a realistic example of what they are requesting. It’s an interface that brings a whole load of clarity to something that words just aren’t able to provide.

With AI, it can almost instantly code the solution which is being requested. Therefore it can iterate in code just as quick (if not quicker) than a human could in a tool such as Figma or Photoshop.

Therefore, you can realistically see the removal of a couple of steps from this current process. Obviously this ignores the whole part of “design” which is so under appreciated by businesses it’s not even funny. 

It’s easy to see a few DALL-E images and believe AI is creative. I guess in some way it is, but is it innovative? Is it coming up with completely fresh, original ideas and perspectives on how to look at things?

I would argue it isn’t. At the moment it’s quite easy to spot an AI generated image. Some are blatant whilst others rely on paying attention to little details. However, you can recognise them.

The questions still remain though. Can AI push the boundaries of design? Can it introduce new styles and fashion into the App world? Can it truly innovate and move our App world forward?

What about third party packages and libraries?

Almost all major programming languages have a package management system these days — Javascript has npm, Python has pip, Rust has Cargo etc. What about all the libraries that come along with any ecosystem. All that innovation and development coming from human developers that other developers are able to utilise to build out products faster and of much higher quality. Is AI going to replace all that?

What about the Companies that are providing the AI?

One final thing that I think requires mentioning. Whatever AI exists in the future it’s going to be managed and run by a company or group of companies. 

A company like OpenAI or whoever that impose their rules and their ideals on the AI which in turn influences everything it produces.

Even if all developers disappear and are replaced by AI and the whole thing is just working seamlessly, who is controlling the AI? If this is adopted globally then a small change by this company can trickle down to have massive implications. Who will oversee what it is producing?

The more I go down this rabbit hole the more I get scared by the places we could end up as humans. And all so we can get more quicker?

One thing that has also become apparent in the writing of this article is the meaning of the word “Developer”. It seems to me that some of the tasks a developer does these days will be easy to replicate with AI. Others however, will not be.

If you are a Software Developer at the moment I think you have to aspire to become a 

. Engineers have been around as long as civilisations and they will continue to be. Throughout the ages, depending on the technology, engineers have worked in different domains but they have always been needed. To build, to innovate, to create and to push things forward.

I have realised in life that things change but also they don’t.

Even if all developers are removed from a company, it seems you still need some person to act as an interface between the business side of the company and the software being produced. It seem’s to be we aren’t going to get rid of developers, rather the developer’s specific roles are going to evolve.

Who’s overseeing the AI work to make sure AI is not adding complete rubbish?

 What about data? For many companies these days, data is their product. How much trust can you put into AI to make sure it doesn’t jeopardise the data integrity? In a current software team you have Pull Requests and Retrospectives and hierarchies within a team to address quality. This is all in place to try and maintain a standard and quality of the codebase and data for the company.

Innovation and novelty also leave a big question mark for me. AI is currently LLMs built on top of lots and lots of existing data. But if there are no developers surely it won’t take long for the whole development ecosystem to become stagnant. 

AI has no agency or intent. How and why would it try to innovate?

A world without Developers seems to me like a pretty sad affair. Sure, efficiency and productivity will soar and the fat cats sitting on the board will be content counting their coppers but what about all those positive human qualities that developers currently bring to the table. 

Innovation. Novelty. Quality. The spirit to improve.

 Without human developers the whole development lifecycle would just plateau because the spark of change would have gone. The world of technology would become dull and lifeless.

Apparently it’s only a matter of time before AI improves to the point where it can take over everything that a software developer does.

A World Without Software Developers

They will practice parts of a piece over and over again until it is completely engrained into their muscle memory

One thing that struck me was how they go about their practice. These young virtuosos will practice parts of a piece over and over again until it is completely engrained into their muscle memory. They can play it without thinking which is the level one needs to get to in order for the “soul” of the pianist to come through in the music.

I related this back to the profession of Software Development and specifically coding. We’re not working at a concert pianist level and we don’t need to perform but we do work with a keyboard and there are repetitive actions we do day in day out.

The more we know about the language the more diverse our options of implementation are and the quicker we can implement one of these options.

The whole idea of a text editor is to allow us as developers to capture our thoughts in a specific coding language. 

We think first what we want to do and translate that into whichever language we happen to be writing and type that into a keyboard so it appears in our text editor.

 The more we know about the language the more diverse our options of implementation are and the quicker we can implement one of these options.

There is much to learn to become a skilled Software Developer, the same as there is much to learn to become a great pianist. But how much purposeful dedicated time do we spend on the skill of becoming very proficient at using our text editor and how important is it really?

As a software developer I would classify the skills required (I am sure I will miss some) into the following groups:

Good knowledge of language/s regularly worked in

Knowledge of systems regularly used — Git, Jira, CI CD Pipelines, Operating Systems

You notice I didn’t include the Text Editor in the group of “Systems regularly used”. This is because as a developer you spend so much of your time in your editor. It’s easy to justify dedicating some deliberate time to learning the ins and outs of it. 

Regardless of which text editor you use, you should know it top to bottom.

I just learnt as I went along. Some things naturally got quicker and occasionally I would stumble across a new keyboard shortcut and realised I had been doing something very inefficiently for the last 6 months.

However, I don’t know any developer who actively sets aside time to work on their “Text Editor skills”. It’s almost once you pick an editor (usually based on some popular opinion on the internet at that time) it’s relatively easy to get up and running and then you make do with learning as you go.

This is what I did for many a year. I picked up VSCode as all my colleagues were using it. It was easy to install and easy to click around with a mouse and get things done. But I didn’t have any lessons. I didn’t dedicate any time to practising or learning keyboard shortcuts to improve my ability and efficiencies in the tool. I just learnt as I went along. Some things naturally got quicker and occasionally I would stumble across a new keyboard shortcut and realised I had been doing something very inefficiently for the last 6 months.

Let’s say hypothetically, that you did dedicate some time everyday to learning your text editors inside out. Like a pianist who practices their scales, you would learn and practice your keyboard shortcuts. You would build up your muscle memory and discover different ways to work quicker and faster in your editor. Would it be worth it and what would be the actual benefits gained?

I would make the argument that if you intend to be a software developer for at least the next 10 years then it probably is worth dedicating some time to really learning and understanding the full capabilities of your text editor. Also, it would be worth your time at getting really proficient at the common use cases you run into in a normal working day. Things like:

Opening different panes to run tests quickly

Changing a variable name throughout your codebase

Getting to a specific line in a file quickly

When you really concentrate on what you do, there are a whole host of things you do each day that if you became proficient in these specific actions you would ultimately change the way you work.

I mean it’s one thing to be quick and efficient but if you’re writing out absolute garbage then it really doesn’t matter how quick you are.

Having said all this, there are other skills that are equally, if not more important than pure speed and efficiency. I mean it’s one thing to be quick and efficient but if you’re writing out absolute garbage then it really doesn’t matter how quick you are. Dedicating time to learning the language you are working in is obviously more critical, especially if you are at the beginning of your career.

There are enough Senior developers out there advising you to learn common algorithms and data-structures that this should be taken seriously.

Soft skills are also a completely underrated skill as a Software Developer. You need to know how to do technical implementations and to build and improve applications but if you can’t speak or communicate with people then you’re going to have a difficult career.

Considering all the other skills needed in order to be a well rounded Software Developer does it really matter if you implement some code in 45 mins instead of 40 mins? Ultimately if you implement a solid solution that will stand the test of time this is the most important thing.

I think we can take some inspiration from pianists and the way they approach their profession. However, there are some fundamental differences with the main one being pianists are training for that special one-off “performance”. Software developers however have no equivalent, they “perform” everyday but obviously not under the same conditions or scrutiny.

I do still feel developers should spend some deliberate time just playing around with their text editor. Practicing some common keyboard shortcuts, exploring all the nocks and crannies.

 Spend time discovering other potentially useful shortcuts and evolving the keyboard mappings. This will all aid in improving the process of getting their thoughts from inside their heads onto the file inside the code editor in a more timely and efficient manner.

Understanding the importance of how fast you can type code when you are a Software Developer

How Important is Coding Speed?

(Going off on a tangent… this 5 months of basically not researching to find a better solution is an interesting human condition. It’s when you have something that works but you just know it’s not optimal but there is something within you preventing you from taking the time and effort required to find that “better solution”. Is it a fear that this “better solution” doesn’t exist? Is it a fear that it could require a tremendous amount of effort which will lead you down a horrendously long rabbit hole from which you may never escape? Is it just pure laziness? What is at the root of this pervasive procrastination that invades all aspects of our lives? I wonder…)

Neovim, like Vim, uses the concept of registers to store text.

If you want to copy and paste something within Neovim then you have many possibilities.

yy This is known as “Yanking”. If you have a cursor on a specific line and you are in NORMAL mode, then pressing yywill “Yank” (essentially copy) the current contents from that line. The first y indicates the start of the yank operation and the second y specifies that the scope of the yank operation is the whole of the current line. Then pressing P or p will paste it. P — Line above. p — Line below

dd This is similar to “Yanking” but this will delete the current contents of the line also. It’s essentially “cut and paste” in a traditional editor.

You can also use y or d in VISUAL mode on selected characters. If you select a bunch of characters and press one of these buttons, again it will copy the content and you can use P or p again to paste it somewhere else within Neovim.

What is actually going on in Neovim when you press y or d? Neovim, like Vim, uses the concept of registers to store text. When the yank operation is run it takes the copied text and stores it in the default register. 

Registers are storage spaces that can hold text

When the p paste command is run it then retrieves the content from the register and inserts it into the document in the specified location.

Copying and pasting in Neovim and things you should know

Hi, I'm Adam Drake

Featured Articles on Medium

It’s the Perfect Time to be a Senior Developer

Using the Atlassian MCP server in Cursor

My New Favourite Stack — Tanstack Start, Laravel, Postgres and Mantine

Technical Skills & Tools