DEV Community

Cover image for Developer diary #17. How does it work?
Kiolk
Kiolk

Posted on

Developer diary #17. How does it work?

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.

Image of Docusign

Bring your solution into Docusign. Reach over 1.6M customers.

Docusign is now extensible. Overcome challenges with disconnected products and inaccessible data by bringing your solutions into Docusign and publishing to 1.6M customers in the App Center.

Learn more

Top comments (0)

Sentry mobile image

Improving mobile performance, from slow screens to app start time

Based on our experience working with thousands of mobile developer teams, we developed a mobile monitoring maturity curve.

Read more