Hi, I'm Gabo

I make software, ask a lot of questions, and do most of the repairs at home.

-days as PhD candidate
4products shipped
~6tmaterials hauledcement, furniture, laminate & tiles

I like taking things apart to understand how they work. Putting them back together usually takes longer than planned, and sometimes there are spare parts left. This applies to software, home servers, and quite a few things in our apartment.

I live in Ruse, Bulgaria, with my wife. We’ve renovated our apartment three times. There always seems to be something else to fix, but I enjoy doing the work myself. The materials-hauled counter above is there for a reason.

I also run a homelab, automate things that probably don’t need automating, and tinker with cars when I get the time. My setup and now page cover some of that.

What 12 years of working on products taught me

I’ve worked in support, built products, and run my own business. Support shaped how I think about all of it. A customer can describe a problem very clearly and still ask for a solution that won’t help them. It’s easy to write down the request and miss what they needed.

I'll never forget this one hardware company where customers asked for a connector with 'more bandwidth.' The product person thought they understood but didn't want to ask for clarification. So we manufactured 250-ish units with completely wrong connectors. When we placed them on the website, customers were absolutely flabbergasted – an expensive lesson in why assumptions kill products.

Bimbala and my research

I co-founded Bimbala, a tool for collecting and organising user feedback. We later sold it to another team. Building it gave me a practical way to work on a question I kept coming back to: how do you turn what people tell you into something you can use?

My PhD research follows that question into the data: methods for automatically analysing written user feedback and extracting useful information from it. You can read the publications here.

Smaller tools, writing, and sharing what I learn

A lot of my open-source work is fairly specific: editing WooCommerce orders in bulk, improving admin search, calculating server resources, or keeping track of time without an account. I like making tools that someone can use without needing a big budget.

I write about software, AI, security, and whatever I’ve spent too much time troubleshooting. I’m also working on books and reference guides, and occasionally speak at conferences and meetups about WordPress, performance, and product.

Working with me

I care about people first, then the product, then the process. I ask for context, say “I don’t know” when I don’t know, and sometimes over-explain because I want the reasoning to be clear. I can also get impatient when something I care about moves slowly. There’s a longer guide to working with me, including the less flattering bits.

Feedback from collaborators

Shared with permission; identifying details are omitted for confidentiality.

"Gabo helped us turn a pile of conflicting customer feedback into a clear set of priorities. More importantly, he made the reasoning easy for the whole team to understand and use."
Product team leadShared confidentially
"We asked Gabo to look into our store’s performance. He found the bottlenecks we had learned to live with, explained what was causing them, and helped us make the site noticeably faster."
E-commerce operatorShared confidentially
"Gabriel combines rigorous research with a practical engineering mindset. His work on feedback analysis is designed to be useful in real decisions, not just interesting in theory."
Research collaboratorShared confidentially
"Whether he is shipping a feature, untangling a production issue, or sharing what he has learned, Gabo brings the same care, curiosity, and follow-through."
Engineering peerShared confidentially
"The onboarding work gave us a much clearer view of where new users were getting stuck. Gabo did not just suggest changes; he made sure we understood why each one mattered."
Software founderShared confidentially
"Gabo understood the code, the data, and the people using the process. He helped us build a feedback loop that led to action instead of another forgotten spreadsheet."
Product managerShared confidentially