Aza Broflovski

I managed the web team and was responsible for the architecture of the engine and the web client. My role included designing technical solutions, conducting in-depth code reviews, mentoring engineers, and setting up scalable development workflows.I managed the web team and was responsible for the architecture of the engine and the web client. My role included designing technical solutions, conducting in-depth code reviews, mentoring engineers, and setting up scalable development workflows

We built a 3D map — a fairly large and complex piece of software — along with all the tooling around it: the engine, tools for 3D artists, and a couple of additional services for working with tiles

After shipping tons of code and projects, I eventually hit my personal growth ceiling in that environment. It felt like the right moment for a context switch, so I took a career break to recharge and explore new challenges.

Before leaving, I made sure the team was set up for success: I documented the whole system, onboarded my replacement, and stayed involved until the transition was fully stable

After the lead dev left, I became responsible for all the web projects.

We built a lot of internal software and tools for clients.

One of the coolest things we delivered was online telephony for the call center. We implemented in-browser calling using WebRTC and WebSockets, with OnlinePBX under the hood, while the entire client-side part was built by us.

I also wrote a JavaScript library that unified different telephony providers (OnlinePBX wasn’t the first one we tried, but we ultimately settled on it). The idea was to have one interface and the ability to plug in custom transports. I even planned to open-source it, but it remained just an idea.

We also created a wild workaround that allowed us to render Vue components inside AngularJS. A brutal hack, but it worked. Important context: we were stuck on legacy AngularJS, and the business didn’t want a full migration because “everything works.” So we moved pages to Vue piece by piece. Eventually there were no AngularJS components left, and I swapped the whole thing to Vue — no one even noticed our heroic act.

Inside the marketplace, the backend was full of interconnected services. We improved the warehouse system too — completely our own solution. We tracked every shelf and item movement, and built a visual representation of the warehouse so managers in the admin panel could click around a fancy UI and work with physical shelves more intuitively.

And, as usual, there was absolutely no documentation. Everything lived in people's heads. We didn’t have business analysts either, so I documented everything myself whenever I had time — no one asked for it, but someone had to do it.

This is my first job in the office, I got a job as an assistant to a senior developer, I refactored existing code, implemented small features, were closing a technical debt, helped migrate from Angularjs to Vue.js.

1 year with wordpress, where we built everything imaginable except a blog xd. A ton of bullshit code that turned into a giant spaghetti sheet written by 100500 developers, and every new one just piled even more crap on top.

p.s I moved away from wp and shifted toward pure php and larave/symfony (at that time I only knew php)

It was my side project that eventually grew into a small media outlet and brought in some ad revenue. But for me it was more of a passion project than a business, and later I shifted my focus to improving my skills and shut it down.

I got into coding and eventually turned my attention to PHP. Back then it was hugely popular, and for me it was the fastest way to break into the community and start earning my first money.
I immersed myself in WordPress, Joomla, and Drupal, and later began exploring Laravel and Symfony.

I spent a lot of time reading, watching videos on YouTube. Special thanks to Sorax channel (Artem Greenberg) - he became the source of my inspiration and interest in learning new things. His methodology of teaching JavaScript laid a solid foundation for my further professional development.