Author Archives: Daja Henry

Diana O. Eromosele: Developing Software that Matters for People that Matter

The year was 2016. It was a scary time for journalism. Publications were issuing out layoff after layoff. The infamous “pivot to video” loomed ahead. Diana O. Eromosele was a 26-year-old working at The Root. She had been fairly successful in journalism, having landed a CNN Editorial Fellowship prior to her job at The Root.

At 26, however, dreams are quickly overtaken by a need to survive — and pay rent. It was then that Eromosele decided to make her second career change. She had already taken an unconventional path to journalism. After completing an undergraduate degree in political science from Duke University, she worked full time in communications.

After a change of heart, she began working on a graduate degree in journalism at Georgetown University, which granted her eligibility for a CNN journalism internship. After CNN and The Root, with a couple years of journalism experience under her belt, she began to look for something more stable. She was browsing The New York Times when she noticed publications were laying off some of their best writers and editors.

“If this 20-year veteran is getting laid off because there are no jobs, what does the future look like for me?” she asked herself.

She needed a job that she could pivot into quickly and affordably, that would pay her bills and allow her to use all of her current skills. Software development checked all of those boxes, so she began her journey with a 3-month stint at Dev Bootcamp, a software engineering bootcamp designed for professionals to learn coding and be job-ready at the end of the program. Her class was dominated by people between the ages of 20 and 30, looking to change their careers.

“For me, it was do or die. It wasn’t just a hobby. I knew I wanted to transition. I knew I wanted a higher-paying career that was a bit more stable,” she said.

A few of her colleagues had already begun the transition and urged her to come along. She is now a full stack software developer at Newsela, an instructional content platform that allows users to read content at different levels. With the click of a button, educators can read an article at a second-grade reading level with their students.

Eromosele loves what she does now. “The beauty of software engineering is that whatever field you come from, every industry requires tech, requires applications they can use to make their processes faster or offer better services.”

One of the most common misconceptions, she said, is that you have to be a nerdy white male who plays video games in your mom’s basement to be a software developer, or that she sits at a computer all day staring at ones and zeroes.

While it is a white male-dominated field and being an African-American woman places her into an underrepresented group in web development, she has been able to use it to her benefit. Dev Bootcamp granted her a scholarship to attend because of her minority status.

Eromosele is dedicated to changing stereotypes and creating a space for diverse mindsets. Google’s annual diversity report reveals that about 53 percent of its workforce composition is white, with the closest minority group being Asian people at about 36 percent. Black people comprise merely 2.5 percent of its workforce and Latinx people comprise 3.6 percent.

Eromosele basks in her differences. “I’m an urban chick from New York City. I come from a liberal arts background and I love to code. I like to build things. I don’t think like anyone else,” she said. “I’m going to build things that have a social justice component.” Because of the lack of diversity, she receives emails and calls from companies heavily recruiting people like her.

She has leveraged those differences to create a tool called Categorized Tweets. It is a Rails app, running Ruby on the back end and JavaScript on the front end. The tool separates the tweets of politicians on local and national levels into nine categories, based on issues. She got the idea as a project during her bootcamp, after wanting to create a tool that would allow the average person to have an idea of what is going on in politics.

Tweets were an easy pick to build the tool around because of their brevity and the simple language that politicians have to use on the application. Combining her interest in civics and her liberal arts and journalism backgrounds, she was able to create a tool for people like herself.

Though she received pushback when she initially presented the idea, she continued with it and built the back end the next day. Upon its launch, it was so successful that she decided to launch it as its own entity. Most recently, she added a category of tweets for the polarizing Kavanaugh proceedings after seeing how active everyone was on Twitter, voicing their opinions on the matter.

She wants to continue building useful tools like Categorized Tweets and encouraging not only minority groups, but everyone to learn software development. “The tide is turning,” she said. She predicts that coding will become one of the core subjects taught in schools. She urges minorities to start building things that interest us and learning from people who look like us. With the future looming, it is imperative to have a stake in our narrative and create tools that are reflective of our entire society’s needs.

jQuery + ONA = inspiration.

jQuery was a relief for me. Last week, I struggled with JavaScript. I was, as the kids say, shook. It felt like high school math class all over again. I should’ve known that those tricky little web developers, the same guys who follow the DRY principle, wouldn’t leave it at that. Once I got out of my head and got a hang of it, I realized it wasn’t that bad, but it can still be shortened.

Enter jQuery. A fast, small and feature-rich library designed to make JavaScript easier. Also, the beginning of creating code I can see utilized in the websites I actually visit. I felt like I was doing something big once I saw all the interactive features, like sliding elements and toggles.

At the time that I finished the jQuery lessons, I had just come back from the Online News Association (ONA) Conference on the HBCU Digital Media Fellowship. At their annual Online Journalism Awards, I saw a world of new possibilities. The student category particularly surprised me. Seeing the websites for Aftermath by UNC School of Media and Journalism and Alone by Misyrlena Egkolfopoulou of UC Berkeley Graduate School of Journalism made me realize that there is more out there than just words-on-paper journalism. These pieces create experiences that put the audience in the shoes of the afflicted. This, along with the design thinking workshops and training in alternative storytelling methods by Michael Grant, made me realize the untapped potential in Howard’s journalism department, the audience’s role in the story and the possibility that we may be behind the curve.

How do we bring a comparable curriculum to our HBCU? I think this class is a step in the right direction. I think Howard needs a modern journalism curriculum that strays from the traditional.

But back to jQuery. It was easy to grasp and it was intuitive. I believe that’s also what contributes to a good story. The audience can understand and interact with it. I will say I’m inspired. I want to take my new insight back to our school’s new ONA chapter.

The jig is up.

Oh, JavaScript. The most popular programming language.

With HTML and CSS, I felt comfortable. I thought I’d be able to conquer anything. Everything was a breeze. Coding wasn’t that bad, after all.

Until it was.

I felt like I was in math class all over again. I was reliving my worst nightmare. The last two lessons almost defeated me. But just like math class, I realized that I just had to practice to prevail.

At first, I was really confused as to what JavaScript did. Why were we adding numbers and doing true/false equations? What was all the craze? Could I not do these things with my calculator? I slowly began to realize that the adding and subtracting, were just the foundation for larger functions, like creating widgets, games and apps. And just like in math class, if you mess up the basics, the whole equation will come tumbling down. Needless to say, I’ll be revisiting the lessons.

The hardest thing for me was remembering the syntax and all of the necessary elements of a function. After Tuesday’s online class, though, I was reassured in knowing that no one fully memorizes everything in JavaScript. I’ll just have to make a (or find) cheat sheet.

Another thing that baffled me in the Codecademy lessons, specifically, was that the system would sometimes return a syntax error, but I’d still get a check in the box. I found myself restarting the lessons over and over, trying to note the differences between what I typed and what Codecademy wanted.

One good thing, though, is that I fully understand what jQuery is used for. I think whoever wrote that library is brilliant. I also think that I will eventually be able to fully grasp JavaScript. It’s just a matter of time and practice. As I reflect now, I realize that I wasn’t struggling as much as I thought I was. It was a lot of material, but nothing I can’t handle.

A Lesson in Troubleshooting

This week, we got hands-on with HTML and CSS. I was eager to start linking my HTML with CSS and make a fancy website with different colors in the navigation bar and all these intricate designs. In class, everything went smoothly. I was using all the HTML I learned on Codecademy and having a blast.

During the readings, things got a little fuzzy, but it was nothing I couldn’t handle. I found the reading on responsive web design interesting. It made me realize, once again, how much of the internet we take for granted. Before the reading, I assumed that whatever you coded for a desktop website would just magically convert and appear in a mobile format. Little did I know, people type in a bajillion commands to make these things happen. It just reinforces the fact that computers are just machines that do whatever they’re told to do. They’re not evil machines that will take over the world. They’re the tools of evil people who use them to take over the world.

Anyway, all the Codecademy exercises went smoothly and I felt I had a firm grasp on the material. I did one each day, and on the final day, I created my prototype homepage. I figured it would be a piece of cake. I input all the HTML and CSS and linked them together. I made my font white, or at least I thought I did. When I loaded my prototype, none of the CSS that I had applied to my fonts was showing up. I opened a tab of Codecademy from each lesson, and I stared at the final code on each lesson for at least 20 minutes. I realized my error was in the HTML, in where I had placed the class identifiers. I got it together, uploaded the repository, and I submitted my homework. I was so proud for taking my time and submitting my homework early.

At least I thought I uploaded the repository. Since I didn’t put a summary description, my work did not upload to GitHub. I figured that out the hard way, after I had already submitted. The moral of the story is, I was wrong a couple times, but I fixed it and I learned something new. I think this class will be interesting and beneficial for me. It really forces me to think.

The world, at my fingertips

Let me just start with a confession: I spent way too much time playing around with the web inspector and changing people’s website photos to pictures of dogs. The web inspector has to be my favorite part of this week’s lesson. Aside from thinking about how useful it’d be in planning out my next pranks, I enjoyed the web inspector tool because of its potential usefulness as a learning tool.

While I was playing around with the code to make changes that I thought were funny, I also had a chance to identify the different elements making up the html code for the websites. I was able to recognize most elements from the Codecademy lessons. I noticed, though, that there were a lot more things I hadn’t yet gotten to. I feel like I have a good grasp of what I’ve learned, which is progress on an ever-changing road ahead.

I also liked how useful the features on Github were for building on a code. Though I didn’t fully understand the intro exercise when I was doing it, after further examination and meditation, I recognized how useful the branch system is to the user. GitHub is essentially a social media network for web developers. Pretty cool if you ask me.

The Codecademy exercises showed me that learning to code is not impossible. I immediately recognized that there would be a lot of information, but I was prepared this time (I already had a Codecademy account because I tried to learn before). I took notes to create a reference list of tags and what they do. Now, I know that learning to code is just like learning any other skill. When you really take the time out to learn and practice it, it’s not so bad.  I’m excited to see what I can learn how to do next. 

On Computational Thinking and The Internet

The first thing that came to mind when I delved into the readings this week was the phrase, “information overload.” It seemed fitting, since our topic is, in general terms, the Internet. I’ve always thought of it as some mysterious cloud constantly dumping information, like the YouTube video said, but now I know that it is actually simpler and, when used right, combats information overload altogether. I also thought it magically appeared somewhere around the 2000’s. I was surprised to see the many different iterations of computers and the Internet dating back decades.

After processing all the information in the readings, I think computers and the internet are designed in detail-oriented ways that answer problems with solutions. It’s kind of like Newton’s third law: To every action, there is an equal and opposite reaction. Programmers input commands, and computers just do what they’re told. When you think about it that way, they don’t seem so mysterious.

These ideas matter because they can be applied to everyday life. Lately, I’ve been doing a lot of research on Ancestry.com. It requires attention-to-detail, especially when you go further back in history. For example, my third-great grandfather, William Batiste, was a black man in Confederate Alabama. Around the same time, there was another black man by the same name and living in the same town, who fought in the Spanish-American War. At the time, I couldn’t figure out if they were the same man or two men with the same name. To differentiate between the two men, I first had to identify some qualifiers that would separate the men. I had two death records, one in 1916 in Alabama and one later in Chicago. Next, I searched for a 1920 census. I found one with my third-great grandmother listed as a widow. That confirmed that the Willie Batiste who died in 1916 was my third-great grandfather. The Spanish-American war veteran moved up to Chicago, where he was discharged after sustaining an injury. To get to this conclusion, I took a series of steps. I had to express the problem (identifying these men), express a solution (find a telling difference)  and then carry out the solution (input a specific search query and connect the dots), just as is shown in the model of computational thinking. 

Another thing that stood out to me was the entire WordPress philosophy. I think the developers of WordPress have a definite feel for their consumers. The general underlying theme is simplicity. The Internet is dominated by consumers. The vocal minority rule the post discusses is reflective of that. Only about 1% of Internet users are creators. However, I think that makes it a bit murky when choosing which features to develop and which comments to ignore. How do we tailor the Internet for billions of people with different perspectives? Is that responsibility on the user him/herself?