Recently, there were a few questions that kept circling in my mind.
Prompted by those questions, I decided to write this article.
I could have just let them pass, but instead, they made me reflect once again on what kind of developer I want to be at this point in time. So, this article will be a kind of organizing my thoughts, and a declaration like, 'I want to be this kind of developer'.
\nWhile talking with developer acquaintances,
What kind of developer do you want to be in the future?
It was an awkward question.
To be honest, I wondered if I had ever thought about it specifically before.
I could have given a vague answer, but that wasn't the answer I truly wanted.
Since then, \"What kind of developer do I want to be?\" I kept asking myself this question.
It's not a question with a single right answer, but after a lot of thought, this was the conclusion I came to.
I want to be a developer who makes good products. Not just focusing on frontend technology, but a developer who understands the entire process of product creation and takes full responsibility for the user's experience.
The conclusion was that I want to constantly think and strive to make good products, and through that process, increase customer value.
What does it mean to make a good product? I believe that if a service I create can be used by many people without inconvenience, and even bring them satisfaction, adding value to their daily lives, then that is truly a ‘well-made product’.
From a company's perspective, if customer value is increased and that naturally leads to profit, then that too is a well-made product.
When I first started out in development (though I'm still a beginner, of course),
“How can I implement something difficult?”
“I need to show off something technically brilliant!”
I think I had a lot of ambition like that.
Looking back now, I was someone desperate to show off how good I was at development.
But now my thoughts have completely changed.
Now, all I think about is wanting to make good products.
I believe that if I constantly strive and ponder to make good products, challenges will naturally arise, and solving those challenges will lead to an increase in user experience (value).
I think I'm looking at development a bit more from a ‘product engineer’s’ perspective.
So, this is the conclusion:
I want to be a developer who makes good products.
Do you usually hear that you're good at development? Or do you hear that you like development?
How should I answer? In the end, I spoke honestly.
I have almost never heard anyone say 'you're good at development'. Even if I heard it once or twice, I always thought, \"That's not right...\" because I've never thought that myself.
On the contrary, “You like development”,“You find development fun” I seem to have heard these kinds of things a lot.
And if I think about it carefully, that seems to have been the driving force behind my development. Development is fun.
Among them, frontend development is really fun.
As I mentioned above, the fact that the code I write is reflected on screen, and that it can directly affect the lives of users(or perhaps the people around me).
That's what's so fascinating, and it makes me want to continue doing this work.
The reason I keep holding onto this, even in a difficult job market like now, is ultimately because it's fun.
This is why I develop, and why I want to keep developing in the future.
Just like Captain America. \"I can do this all day.\"
My thought is, if I stick with it to the end, I'll eventually win!
Looking back, I still find development incredibly fun, and so I'm genuinely approaching this work.
If I keep working hard, I wonder if I'll eventually become someone who's good at it.
Even now, to some, I might seem like a good developer, while to others, I might still appear to be lacking.
But I am working to get a little better every day.
Keep calm, carry on.
Thus, I became a declarative developer.
I hope you'll watch over me, so I don't disappoint myself.
I might be small and slow, but I will keep moving forward without stopping.