This is positively false. In my anecdotal experience, I have produced code that was brutal to write, but then it was easy to read afterward.

Just like a piece of music being easy to listen to after sweating out the composition.

Sone coding is like solving the puzzle. Once it is written and debugged, you're looking at the solution. The code will readily spoon-feed you the solution again when you revisit it months or years after forgetting everything, possibly even its existence.

Wen code is easy to write but hard to read, you must be writing fluff. Maybe try to steer your career a bit away from that. But do improve your ability to make fluff readable.