From Experimental Thinking to Technical Language: The Challenge (and the Turning Point) in the Transition from Academia to Technology

I come from an academic background in music. From the very beginning of my undergraduate studies, programming was already part of my path — especially in connection with concert music, composition, performance, and sound experimentation. In academia, my thinking was shaped by context, process, experimentation, and critical reflection.

Today, however, I find myself deeply immersed in technical programming studies — and this transition has not been trivial.

For a long time, studying technology through a more objective, structured, and results-oriented logic was a major challenge. My natural reasoning gravitated toward why, what if, and in what context does this make sense? Technical study, on the other hand, demands a different approach: clarity, problem decomposition, repetition, visualization, and direct application.

Learning How to Study Differently

Over the past few months, I had to relearn how to study. I realized that an academic mindset — although extremely rich — is not always efficient when the goal is technical mastery.

The turning point came when I understood that, for programming, I needed to:

• Visualize flows before understanding abstractions

• Turn concepts into diagrams, schemas, and step-by-step notes

• Write less descriptive text and focus more on relationships

• Separate moments of exploration from moments of execution

Cognitively, my notebook stopped being a space for discursive reflection and became a functional mental map: arrows, boxes, minimal examples, inputs → processing → outputs.

From that moment on, my productivity increased significantly.

JavaScript as a Bridge Between Ideas and Implementation

I am currently studying JS Programming Essentials and Developing Backend Apps with Node.js and Express, with a clear focus on Back-end Development.

JavaScript became a central language in my process because it allowed me to take ideas off paper and turn them into real MVPs. Whether on the front end, the back end, or integrating services, JS works as a fast bridge between conception and prototyping — something essential for product-oriented thinking.

My goal is clear: deepen my expertise in back end development, move into DevOps and Cloud, and later advance toward Applied AI. This path has guided my studies in a consistent and strategic way.

Creativity, MVPs, and Applied Technology

Although it sometimes feels like I “started yesterday,” I fully committed to this transition. Today, I can clearly see myself on an upward learning curve — driven by curiosity, discipline, and a desire to build and grow exponentially.

My background in music has not been left behind. On the contrary, it has become a powerful creative engine. From it, I have developed MVPs such as:

• An e-commerce platform for music courses

• A project that began as a conference proposal and evolved into an MVP exploring how music and AI can support patients with Alzheimer’s disease

These experiences reinforced an important insight: creative ideas are not the problem. The real challenge — and also the greatest motivation — is mastering the technical language required to implement them with autonomy, quality, and scale.

Conclusion

The transition from academic language to technical language does not mean abandoning critical or experimental thinking — it means learning when and how to use it.

Today, I aim to combine technical rigor, systemic vision, and applied creativity to build real solutions.

Each line of code I write is another tool to explore ideas, prototype futures, and transform concepts into products.

And this is just the beginning.