or subscribe via RSS...

Interview with Marianne Monteiro

Twitter: @hereismari  |  Slack: @Marianne Monteiro  |  Github: @mari-linhares


Where are you based?

"Brazil, Campina Grande."

What do you do?

"I've recently received a bachelor degree in Computer Science at the Federal University of Campina Grande."

What are your specialties?

"I have experience with Python development, TensorFlow and teaching. I didn't know Pytorch before starting to contribute to PySyft."

How and when did you originally come across OpenMined?

"I got to know OpenMined and PySyft at Twitter, Andrew tweeted about new PySyft tutorials at the time. I never had heard about a lot of the concepts of private deep/machine learning and I thought the idea and possible applications very interesting and highly impactful."

What was the first thing you started working on within OpenMined?

"I've started by following the tutorials. During the process, I started making PRs for fixing some typos, doing some small improvements on the tutorials and fixing good start issues. With these contributions, I could learn how to configure a developer environment and how the revision process works for PySyft. After this, I worked mostly on supporting Plans and implementing TrainConfig."

And what are you working on now?

"I'm currently more involved with the PyGrid project, a Peer-to-peer Platform for Secure, Privacy-preserving, Decentralized Data Science. I've recently helped to support hosting and querying models (encrypted or not) at the platform."

What would you say to someone who wants to start contributing?

"I would say to start by following the tutorials and examples: PySyft,  PyGrid. These will give you an overview of how the frameworks work and the possible use cases. After following the tutorials, you'll be familiar with the main concepts and how they work on a high level. Then I would search for easy fixes or low hanging fruit issues that could be done. A great place to start is adding documentation or unit tests. These are always helpful adds and you'll be more familiar with the codebase after this. Finally, search for a feature or issue that seems interesting to you, this could be an already proposed issue or something that you think could be an interesting feature. A bit of final advice would be: don't worry about not knowing some concepts, focus on what seems valuable to you and what you want to learn instead."