We have used Storybook to document our React component library for a while, and although we love it, we’ve had to use various addon packages and do some hacky things to get components to show how we wanted. Storybook has undergone some big versioning changes recently, so I sat down to upgrade everything from 5.0 to the latest version and see what changed.
After upgrading all of the storybook npm packages, I see that the config files have completely changed. I can remove
Instead, I need:
On Monday, April 23, GumGum held our first Women Who Lunch event. This recurring event was started to bring women from the tech industry into our office to share their story and answer questions from the women in engineering here at GumGum. Our first lunch featured Tricia Lee, the SVP of Product and Development at Sony DADC New Media Solutions. Tricia shared her story and answered our questions about career advancement, balancing your career with other things going on in your life, the best part of being a woman in tech (standing out and being unique!), …
Sanja Stegerer has been working at GumGum as a Data Scientist for past two years. She has worked on various parts of our Natural Language Processing systems. In the talk below, she explains one of the most important systems in GumGum’s NLP systems — The Threat Classification System. The Threat Classification System allows us to identify whether a page is suitable for advertising or not. If a page content has violence, sexual content, illegal acts, disaster etc. Advertisers do not want to show their ads on the page. In this talk, Sanja explains how exactly we make machines identify these…
A few things came together at once for our team:
It all made sense — let’s create a shared component library!
I have 2 stand ups each day. The first is for one of our products. We have representatives from big data, computer vision, and web teams, and it is led by our VP of Product.
In a stand up meeting, everyone gives an update on what they did yesterday, what they will do today, and if they have any blockers. Ideally a stand up meeting with be very short — 1–5 minutes, so we table any discussions that arise until after the meeting. These quick meetings keep everyone on the same page and informed about what people are working on…
You’d think this would be obvious, but it was a shocking adjustment for me when I switched to the management path and realized, “hey, I have to talk to people all day now.” I went from sitting at my computer lost in code most of the day, to talking to people ALL day. Most days I finish exhausted from these interactions, but I look at my team and what we accomplish with the satisfaction of a proud parent. To avoid burn out, acknowledge the change and make sure you make time for yourself to balance it out. …
For a brand new developer, their initial contact with their very first tech job is crucial. They’re probably anxious, nervous, and unsure what to expect.
Here are some tips for new developers and their employers to help ease the transition, based on my experience with my first company which I think did a great job on-boarding and setting me up for success.
As part of my first company’s on-boarding process, we went over the company’s values, and as one of them, they stress a learning environment.