top of page

OUR SPEAKERS

speaker_badge_banner_red.png
Share on:
Asset 14icon.png
Asset 39icon.png
Asset 12icon.png

Evelyn Moadi is a software engineer at Wix specialized in Data Structures and Algorithms. She's formerly a software support & QA engineer with 6 years of experience in several international tech and startup companies.

In the past, Evelyn studied Physics in the Technion hoping to progress to PhD in Astrophysics but for personal reasons that journey was cut short and she was back in the tech world. As a fluent speaker in 3 languages, her communication skills helped her advance fast into the world of software engineering.

Her unique background and path in support & QA contributed greatly in shaping the kind of developer that she is today, starting from basic coding tasks and all the way to impacting major cross company features and projects.

Evelyn Moadi

Software Engineer
Asset 12icon.png
Asset 1TWITTER.png
Asset 39icon.png
Asset 17icon.png
linkedin.png
twitter.png
facebook.png
github.png
English, Hebrew
Languages:
Asset 7TWITTER.png
Location:
Tel Aviv, Israel
Asset 7TWITTER.png
Can also give an online talk/webinar
Paid only. Contact speaker for pricing!

MY TALKS

Keep Your Users Close and Your Bugs Closer

Inspirational, Professional Development, Software Engineering

Asset 12SLIDES.png
Asset 21talk.png
Asset 11SLIDES.png

Before I became the one who's fixing the bugs (or the one who's creating them to begin with), I used to be the one in charge of reporting them. Back then, I was operating as a support QA engineer at Wix and as a matter of fact, I couldn’t have asked for a better role than this one to prepare and to make me the developer I am today.

Users can tell you a lot about your bugs, and your bugs can tell you a lot about your system. Thanks to them both, by the time I became a developer, I had already gained so much knowledge of the system and the products, both legacy parts and the latest additions.

In this talk, I will dive into the wide variety of investigating and debugging methods I’ve developed over the years, which derived from a simple and basic action - talking to users about the bugs they encountered. This includes, for example, asking them questions which later are translated into tools that, more often than not, will deliver you the precise faulty flow that caused the bug.

Asset 1icon.png

Keep Your Users Close and Your Bugs Closer

Completed

true

Visible

true

Order

3

Go to lecture page

bottom of page