This content originally appeared on DEV Community and was authored by Kiolk
How does it work? How often do we ask this question when trying something new? In most of the cases, based on my developer experience, I didn't answer this question, I just used. Why don't I answer this question? Because, it requires so much energy, time, and resources. And the result of that study is not visible immediately. Often, we start diving in some technology, only when we faced with some problem or bug that forces us to do it.
So, what are my thoughts? What is wrong with this strategy? I think there is no mistake here. It is only a different level of our expertise. When we only start a career, we should move quickly and try as many technologies as we can. With growth, we start to see common elements, patterns and structures, and the quality of code and how it works moves to first place. And now, the question "how does it work" is more relevant for us.
You can find me in X, GitHub or LinkedIn. Thanks for your time and see you in next post.
This content originally appeared on DEV Community and was authored by Kiolk
Kiolk | Sciencx (2024-08-31T09:20:00+00:00) Developer diary #17. How does it work?. Retrieved from https://www.scien.cx/2024/08/31/developer-diary-17-how-does-it-work/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.