Once I bought a small plant to keep beside my desk. When I first brought it home, I cared for it with a very funny impatience. Water in the morning. Rotate the pot in the afternoon so it caught the sun evenly. At night, bend down to check whether any new leaf had appeared.
Three days later, it looked exactly the same.
No taller to the eye. No new leaf big enough to show off. I started feeling a little betrayed, as if the plant had received enough water, enough light, enough attention, and was still refusing to cooperate.
Then I realized: I often treat my skills the same way.
I study a new framework for a few days and already want to write it fluently. I work on a small project for a week and want it to look like something made by a person with years of experience. I have not even finished the documentation, but I am already annoyed that I cannot speak confidently like the seniors I look up to.
I plant a seed on Monday, and by Friday I am bending down asking why it has not become a tree.
Fortunately, the plant does not know how to answer.
Technology can make me addicted to speed
Working in tech makes it easy to absorb one illusion: anything can be accelerated if I am good enough. Build faster. Deploy faster. Learn faster. Ship faster. A course promises to help me "master" something in thirty days. A ten-minute video summarizes what someone else took years to understand deeply. An AI tool builds an interface in seconds.
Speed slowly becomes a kind of morality. Slow means weak. Long means wasteful. Needing time means not being optimized.
I am not against speed. Some things really do need to be fast. A production bug cannot be handled with the mood of drinking tea and watching clouds. But if I bring the same mindset into growing a long-term skill, I start hurting myself.
Some things do not grow by being pulled. Product thinking. Design taste. Debugging instincts. A feeling for users. Calm when a system breaks. Knowing when to choose a simple solution instead of one that sounds impressive.
Those things need contact, mistakes, revision, observation, and time to sink in.
I can learn syntax in a few hours. But to know why code that "works" is still hard to maintain, I need to live with the consequences for a while. I can read about UX in one evening. But to really see where a sign-up form is tiring users, I need to watch real people struggle with it.
A gardener understands what people addicted to speed often forget: not every day gives visible proof that a plant is growing. Some days everything is happening underground. Roots are looking for water. The stem is gathering strength. From the outside it looks still, but that does not mean it is useless.
I have days like that too. Reading dry documentation. Fixing a small bug no one sees. Reworking a component so it is easier to understand. Learning to name variables less carelessly. Those days do not create a moment worth posting. But they grow roots.
Patience is not sitting still
Patience is often misunderstood as passivity, as if saying "take it slowly" were an excuse to be lazy. But gardeners are not lazy. They do many small things: check the soil, water, trim leaves, protect from harsh sun, change the pot, remove pests.
They simply do not confuse care with force.
In technology, patience is similar. It does not mean opening a laptop every day, staring at a course, and believing knowledge will fall into my head. It means learning regularly, building real things, receiving feedback, repairing embarrassing parts, and accepting that results have delay.
I used to want to burn through stages because I was afraid of being left behind. Looking at other people with beautiful portfolios, large projects, and deep articles made my chest feel hot. That feeling is not entirely bad. It tells me I still want to move forward.
But if I let it drive, I will start pulling the plant out to check how long the roots are.
And anyone who has grown a plant knows: pulling it up only tears the roots.
Now I try to see learning as tending a small garden.
Some beds are green: things I can do fairly well. Some are newly planted: things I am still clumsy at and need to protect from the ego that loves to criticize. A few plants died: directions I tried and that did not fit, no need to build a dramatic memorial for them. There are rainy seasons, sunny seasons, and days when insects eat the leaves.
That is normal.
This view makes me much gentler with myself. When a project is not beautiful yet, I do not rush to conclude that I am bad. I ask: what is the soil missing? Foundational knowledge? Feedback? Time practicing? A good example to learn from? When I feel bored, I do not abandon the whole garden. I check whether I am watering the wrong place, or trying to grow too many things at once.
A good gardener does not prove skill by shouting at a plant to grow. They prove it through consistency. Water in the morning. Trim yellow leaves. Add nutrients when the soil is tired. Year after year, the garden answers with shade.
I think skills answer the same way. Slowly, but very truly.
One day, I will open old code and see that I have changed. Not because of one magical leap. Because of many days when I quietly kept watering, even when there was no new leaf large enough to show.