I have always loved writing code by hand, but over the last year my workflow has shifted. I now spend more time prompting than typing, and that change has been bigger than I expected.
Most of my day-to-day work happens inside Cursor. Instead of starting with a blank file and building line by line, I start by describing the outcome. I explain the intent, the constraints, and the shape of the code I want. Then I iterate on what comes back.
That does not mean I stopped coding. It means I moved my effort up a level. I still review every file, adjust logic, and shape the final output. The difference is that I can get to a working draft faster and spend more time on the parts that actually require my judgment.
Here is what changed for me:
- I front-load context. The better my prompt, the better the result.
- I edit more than I type. I treat the output like a first draft, not the final answer.
- I move faster through boilerplate. Tests, wiring, and repeated patterns are now quick.
- I focus on decisions. The hard part is still the tradeoffs, and that is where I spend my time.
There are tradeoffs. I have to be intentional about understanding the code that is produced, and I still need to know when to slow down and reason through a problem myself. But the balance has shifted. Prompting is now the default, and hand-writing is the exception.
I did not expect this to feel as natural as it does. It is less about outsourcing the work and more about changing the interface between my intent and the code. Cursor just happens to be the tool that makes that interface fast.
If you have not tried this way of working, I recommend starting small. Use it for scaffolding, use it for refactors, and build trust in the output. Once you are comfortable, you will realize that you are spending more time on the parts that actually move the product forward.
