My relationship with technology began way back in my childhood. My father was an electrical technician, and through him I discovered that every technical device had a logic that could be understood. Electric railways, a Commodore 64 with cassette tapes and floppy disks, submersible pumps, the first VHS players and recorders, and almost anything we had at home became an opportunity to explore how things worked rather than simply how to use them. Of course, at that time my father explained everything; much of it I only truly understood years later, when I started to explore software development in depth.

One of my earliest memories is typing around a hundred lines of BASIC code from a programming book to create a program that calculated the circumference and area of simple geometric shapes. At the time I wasn’t really learning BASIC yet—I was following instructions—but I wanted to understand what I was typing. Programming magazines were full of Assembly language examples that I couldn’t understand, but they gave me the feeling that there was an entire world waiting behind the screen.

When I was accepted to the Hungarian Dance Academy at the age of ten, dance naturally became my full-time focus. Days stretched from early morning until evening, leaving little room for anything else. Technology moved into the background, but my curiosity remained.

During the 1990s, electronic dance music became part of the world around me, and by the end of my school years tracker software such as Impulse Tracker was available on my 586 PC. It gave me a first glimpse into the connection between sound, rhythm and technology — a connection that would later return in different forms throughout my work.

Returning to programming as an adult in 2014 was surprisingly difficult. Learning syntax was one challenge, and that could be improved through practice; understanding the purpose of digital systems was another matter entirely. Coming from the world of theatre, I first had to understand why people collect data, organise it into sheets, search for connections between values, or use functions to automate repeated tasks.

At school, one of the first things we studied was ECDL, with a strong focus on Excel. At the time I saw it as something old-fashioned and could not understand why it mattered so much. Only later did I realise that spreadsheets are not just tables; they are tools for structuring facts, comparing information, finding relationships and supporting decisions — whether in software development, SEO, marketing, reporting or everyday administration.

For nearly a year and a half, I often felt that I was collecting disconnected pieces without seeing the complete picture. Then, gradually, the context became clear. Once I understood where software, functions and digital structures belong in real human workflows, programming stopped feeling like memorising code and started feeling like solving problems. The picture became simpler, even while the systems themselves remained complex.

That first year and a half was a real struggle. There were no conversational AI tools available to explain things step by step, so finding solutions meant reading a lot, searching carefully, and learning from sources such as Google, GitHub and Stack Overflow. Proper programming books were expensive and not always easy to access, and in my experience Hungarian translations of technical literature often arrived late, especially in areas where the technology was changing quickly. There were a few lucky exceptions, particularly with languages or concepts that developed more slowly.

After finishing the course and creating my first assessable project in C# using Visual Studio, I decided to move towards websites and web applications. Coming from C# and Visual Studio, ASP.NET felt like the natural next step, but at the time it was a difficult environment for me. I experienced much more coding than immediate visual creation, and I still needed to understand how all the pieces belonged together. At the same time, it gave me a solid foundation in backend thinking and helped me understand what happens behind the visible surface of a digital product.

Some time later I met an old friend who had already spent many years working in online marketing. He needed a developer, and we decided to join forces. For around five years, I worked with him through his company, profitonline.hu.

During this period I worked mostly on WordPress websites, webshops and SEO-focused projects. Because the clients and their needs were very diverse, I gained experience with several e-commerce platforms, including UNAS, ShopRenter, OpenCart, Shopify, WooCommerce and WordPress-based systems. My work included building websites from scratch, migrating projects from one system to another, improving SEO foundations and solving the practical technical problems that appear when online businesses grow.

In 2021 I joined Greenpeace Hungary, where I have worked ever since. This became a major turning point in my development. My technical perspective widened significantly, not only because of the complexity of the organisation, but also because I had the opportunity to work with people who approached IT systems with precision, strategic thinking and a deep understanding of organisational needs.

At Greenpeace, my work expanded beyond websites into CRM systems, digital campaigns, data, reporting, workflow automation and cross-country IT processes. I started using CRM systems on a daily basis, setting up and managing PPC campaigns in Google Ads and Meta Ads, supporting CRM developments, tailoring systems to specific organisational needs, and working with international digital infrastructures. The main tools and platforms have included HubSpot, CiviCRM, Google Ads, Meta Ads, Make — formerly Integromat — GitBook and Cloudflare.