Machiko Yasuda

The Starter Career


Machiko’s work at the UCLA Daily Bruin led her on a path well known to young journalists: school newspaper, internship at real world newspaper (the prestigious Washington Post in Machiko’s case), first job at a small town paper (Ventura County Star), and a sidestep to a bigger neighboring market (KRCC in LA). At each place, she was drawn to how things were made and was lucky enough to have colleagues willing to assume informal mentorship roles.

But Machiko’s chance for real growth came in an unlikely form: a day when two major news stories broke and neither her boss nor the senior developer were in the office. She had an idea about how to cover the story in an interesting and interactive way and the window to develop and deploy it herself (with the help of other engineers who were in the office that day). With this opportunity came what she considers the most valuable lesson she’s learned: “If you’re waiting for someone’s permission to do this, don’t. It’s not going to come. You just have to do it.”

How She Made the Leap


The early hours of Machiko’s job gave her a healthy chunk of uninterrupted time in the evening for meetups, tutorials and online courses to learn to code. She attributes a RailsGirls workshop with helping to boost her knowledge and confidence, concluding that this type of community is one of the three necessary components for making such a major career transition:

If you’re waiting for someone’s permission to do this, don’t. It’s not going to come. You just have to do it.

~ Machiko Yasuda
  1. “Just realize you can do it. You can. You just need the confidence.”
  2. “You don’t have to know everything to start because you will never know everything, even when you know what you’re doing. And you have to start somewhere.”
  3. “Surround yourself with other people doing the same things. Whether it’s meetups, peer worksessions or mentors at your job, you will need people who can share knowledge and give you support.”

When she did decide to leave her journalism job, she didn’t have another one lined up. Instead, she had a specific goal in mind: within 6 months, she needed to be skilled enough to get an internship as an engineer.

The Beginnings of a Coding Career


Machiko first worked at a Venice-based startup, where the day-to-day was driven by new product development. Like most startups, they were in a tight cycle of build, deploy, test, which Machiko says can be both fulfilling and challenging. “The problem is when you don’t have enough users or data; then you’re just constantly trying new things.” Still, she says the tight-knit culture of developers was exciting and important as she started out.

The Day-to-Day


Now, as a Junior Software Engineer at Reformation, a company determined to produce clothing with a conscience, she works among a more formal team with a CTO, a small group of engineers and a product manager. She collaborates regularly with other developers and designers, and her day-to-day is largely prioritized by the PM, a trait she says is similar to life in the newsroom.

You don’t have to know everything to start because you will never know everything, even when you know what you’re doing. And you have to start somewhere.

~ Machiko Yasuda

“Working in a newsroom, your day is filled with specific tasks that need to be addressed immediately — having a product manager is similar. It helps you to focus on what really needs to get done.”

Machiko works in RubyOnRails, HTML, Sass, a CSS pre-compiler, and React, a JavaScript framework she’s been learning on the job. Reformation uses these tools to manage their web site, as well as to explore more shopping tools in their retail spaces. On a typical day, she says she has to be “multilingual,” using many of these tools in concert to achieve a specific end, and learning on the job has its pluses and minuses. “Unlike tutorials, you have a lot of code already written to look at — but that also means that what you’re looking at is a lot more layered and complex than what you will find in a tutorial.”

Although the list of new things Machiko wants to learn is long, for now she’s focused on things related to work, specifically coding better in JavaScript and CSS for smoother user interactions on touch screens. Given her voracious curiosity, it has also piqued her interest in hardware. “I took a soldering workshop! In like 8 hours we made a GPS-enabled radiation sensor!”

The Wrap Up


Most Surprising Aspect of the Job
There’s no such thing as being finished. Whether you’re making new things or maintaining existing ones, you’re constantly in a state of change.
Most Important Thing to Consider in a New Job
Who you will be working with — mentors, managers and the broader culture of the company — are more important than the code or libraries themselves. You have to find a place that aligns with your values and interests.
Best Thing She’s Made

It’s still in progress, but I’m working on a Ruby Wrapper to pull data from Kindara, a fertility tracking app, and creating different ways of interacting with it on my laptop and phone.

*Although it’s unfinished, it highlights what Machiko feels is an important lesson for coders: behind every product, app or piece of software, there’s a human. More often than not, they’ll be excited to hear from you if you want to know how it works or how to use it for other purposes. (She’s been in touch with Kindara to access their credentials, which they gladly shared.)

Favorite Resources
I try to regularly devote an hour to learning new code, usually to further my knowledge on something relevant to my work. For resources, I like Egghead and Front End Masters, as well as free pod- and screencasts.
Advice For New Coders
Don’t discredit any of your previous experiences. Don’t say you don’t know how to do anything. You probably already know how to use a computer. You already know how to use a web site or an app. Whatever work or life experience you had before counts, and is applicable in programming, startups and technology.

Subscribe!


Want to get Erin’s awesome Day in the Life article series delivered straight to your inbox? Subscribe to our newsletter!

3 Comments on “Machiko Yasuda

  1. Hello! I don’t know how to get in touch with Erin – Erin, I just wanted to say thanks for volunteering your time to put together these interviews! I loved reading about Machiko and I’m excited to read your next interview!

    Andrea.

    • Thanks, Andrea! I’m really happy to be doing it — it gives me a chance to meet some great people and hear some inspiring stories! If you want to contact me directly, I’m on Twitter for my startup @FloorplanRugs all the time, so it’s easy to catch me there. Next post comes out tomorrow!

      • Awesome, Erin! I’ve been on the road but will be sure to find you on Twitter soon. Looking forward to reading about Valerie Woolard! At a glance, “sheer persistence through frustration” is definitely what I’m feeling right now! I’ve been learning Ruby and getting into its object-oriented side (whatever this means…) and the concepts seem so vague now. But – perseverance!

Leave a Reply

Your email address will not be published. Required fields are marked *