Coding… What is it Good For?

Standard

This past week, I stumbled upon an article on TechCrunch entitled, “Please Don’t Learn to Code“. As you might know, I’ve been learning Web Development and Design for almost a year now. Most days I love it, some days I’m frustrated and wonder if I’m crazy. This article caught me on one of those missing confidence days. I read it, hoping that the title was misleading. I thought maybe the takeaway would be something like, “Don’t think learning to code is a process with an end date: it’s something you will continue to learn for as long as you try.” Or something along those lines. I was wrong.

I will be honest: this article didn’t deflate me as much as I would have expected. There were some legitimate and good points. For instance, the tech industry is kind of getting this “idealism bubble” placed around it. Many people seem to think that shows like Silicon Valley and rags-to-riches stories like Steve Wozniak and Mark Zuckerberg (if you can call Harvard “rags”) are the norm in tech. If you learn to code, you will make a billion dollars and maybe get fame and fortune. Coming up with the next big thing isn’t that hard. You might go through some tough times, but it will definitely be worth it in the end. Like anything else though, learning to code isn’t a one way ticket to wealth.

This article also made the point that there are people who learn to code without realizing how difficult it will be. Tech is an ever-changing field, and working as a programmer is a life of never-ending learning and growth. The languages I am currently using to build websites are not going to be the languages people will be using in 10 years. They might not even be the languages we use in 5 years. And, that’s part of what appeals to me. I love the idea of continuously learning and improving while still making a living. I can see where that would be frustrating to some. It almost sounds like it’s frustrating to the author, who spent time learning a coding language that is not only not really used today, but that new coders didn’t have to learn before moving on to the newer languages. I don’t really see that as a negative, however. People who have known how to code for a while, and know languages that new coders don’t know have an advantage in that they knowledge base that others don’t. Those new coders will one day also know what it’s like to see the language they have been using cast aside for something else. It’s just a part of the life of a programmer.

One of the more ridiculous arguments that was made in the article was that learning how to code is like learning how to be a plumber. This really isn’t the case. When you learn to be a plumber, you fix pipes. Of course, there are different kinds of pipes and different kinds of problems, but they are generally all related. When you learn to code, there are tons of different things you can do. There are people who work on the back end with servers and databases. There are people who work on the front end, making things look nice and handling the things that people see. There are people who work in big groups on big websites, there are freelancers who work on their own. Some people learn to code and never use it for anything more than enjoyment. Some people learn it to cause problems for others by finding critical mistakes in code. I think the argument is a little over simplified. I also don’t think it makes much sense because it’s kind of true for all trades and fields. I worked as a barista in coffee shops for a few years. I learned how to make coffee and other drinks. I learned quite a bit about sourcing coffee and what different kinds of beans and roasts meant in terms of flavor. That knowledge, however, isn’t really transferrable to other jobs (besides the fact that I make a mean cup of coffee and I am good at customer service).

The trick is to find skills that are easily transferrable, and I would argue that coding is one of the better fields for that. Not only is tech really broad in terms of the necessary knowledge and how someone’s skills are applied, but the problem solving and knowledge of technological language are things that can be brought to countless other positions. Besides the fact that it takes a while to learn, I personally don’t think there is any harm in learning to code. It doesn’t back you into a corner in terms of how you can use those skills and what kinds of jobs you qualify for. It opens up doors for freelancing, and being useful around an office.

So, after reading that article, it really got me thinking about why I was learning to code. Obviously, a lucrative career is something that appeals to me. And the ability to continue to learn and grow is something I’ve been searching for. Also, the balance of logic and problem solving with creativity is something I have found that I enjoy. It was good to be able to think about these things and remind myself of why I am putting time and effort into this.

The day after reading that article, another article was posted on Facebook that caught my eye: “Please Do Learn to Code“, written by Quincy Larson, the creator and teacher at Free Code Camp, one of the sources I use to learn. Quincy is a great source of encouragement and knowledge about the process of learning these skills. He is the first one to say that basically anyone can learn these skills, as long as they are willing to put in the time and effort. I have friended him on Facebook and follow him on Twitter, because having people who are a source of encouragement has been really helpful for me.

The basic idea of Quincy’s article is that learning to code is beneficial, even if a person doesn’t work in the field. Programming is how humans talk to computers. Since computers are becoming increasingly intertwined in our day-to-day lives, it follows that being able to communicate with them would be useful. I completely agree. We use computers to automate work for us. The example he gives is Google searches. Without Google, it would be really tough to find the information we needed, and it would not happen as fast as it does with Google. Before being able to search the Web, some people would spend hours or days looking for the answer they needed. Some people never found the answers they were looking for. Now, we can type something into Google and have more answers than we need in only a matter of milliseconds. That wouldn’t be possible without people who know how to code, though, because computers need a clear set of instructions to be able to do tasks. Programmers are the people who give computers those instructions.

Something I found interesting about Quincy’s article is that he called coding “the new literacy”. I suppose this makes sense. Programming languages are similar to spoken languages. The words and symbols have meaning, and there are people who understand it, and people who don’t. Technology definitely isn’t going anywhere, so being able to communicate with it isn’t going to harm anything. There are people who ignore the changing trends in technology, or fail to realize that they are being left behind, and they will not be able to flourish the way that people who keep up with the changes will.

I am going to continue to learn this skill, and encourage others to do the same. Even learning a little bit and having an understanding of how technology works is a skill that is beneficial. I will not let articles dissuade me and break my confidence. I think it’s important to think about why you’re doing the things you’re doing. It’s good to challenge yourself and your reasons for doing things. It’s also important to find people who support you and help you remain confident. It’s important to find mentors and friends who are proud of you and will help you when you’re having those missing confidence days. It’s also important to be realistic and know that nothing comes easy, and those things that are truly worth it may require a lot of work.

This couldn’t have happened at a better time for me: I have an entrance interview this week for a coding school. I am scared and not sure that I have what it takes. I am not sure that I’m qualified. But, it’s something I’m passionate about, and so I have to at least try! If I get in and am able to go to the school, it will definitely help me reach my goals and I will learn so much from the experience. Humans are made to learn new things, so why stop learning?

What do you do when you need a boost in confidence? Let me know in the comments!

Advertisements

Week in Podcasts: Somethings Old, Somethings New

Standard

wipgraphic

I had a super full week of podcasts this week! Work this week was pretty quiet, so I was able to focus on some data entry tasks, and I could listen to podcasts while I was doing it! There was also a big snowstorm on Tuesday, so I listened to podcasts during my long commutes. I’m so glad that there are so many great podcasts out there! It’s the perfect thing to listen to while driving and while doing work and chores.

To start off, I have talked about Serial before, and this week was a big week for Serial. Not only was there a new episode for Season 2, there was an update to Season 1! The episode for Season 2 was good, but I am still having a tough time getting hooked to it the same way I did to Season 1. I can’t decide what it is about Bowe Bergdahl’s story that is not as interesting as Adnan Syed’s, but it is kind of cool having a podcast about a case that is currently being decided, rather than one that was decided over a decade ago. This week’s episode is about why Bowe decided to abandon his post. It covered what he was planning on telling higher ups in the military, especially about the conditions that he and his fellow soldiers were living with. It was interesting hearing him and other soldiers discussing not only what their expectations of war were and how those expectations aligned with the reality they dealt with daily. There were some issues with the conditions, and I agree that those conditions should have been better, but many people are not sure that Bowe handled the situation correctly by leaving. I am going to have to keep listening, and maybe eventually I will have an opinion about what I think happened.

The update to Serial Season 1 has been really interesting. Adnan was given a hearing to determine whether or not his case should go back to trial, so host Sarah Koenig went to report on it. She covered what they were talking about in the hearing. There was a girl who came forward to be an alibi and did not testify in the original trial. They also discussed phone records, which used cell phone tower information to determine where Adnan was the day his ex-girlfriend went missing. Apparently, the evidence based on the cell phone towers, specifically information from incoming calls, is inadmissible evidence, because it is inaccurate. That was a huge piece of evidence used to prove Adnan guilty. The hearing is still going on, so Sarah Koenig will be doing updates occasionally to discuss what happens in the trial. I am so excited for more updates!

I also listened to an episode from Stuff Mom Never Told You called “Infertility’s Global Stigma”. As the title suggests, this episode talks about infertility and how it affects women all over the world. There is definitely a stigma around infertility, and it is not something that most people are open about. Often, and especially historically, women were blamed for infertility. Even though it is something that women should be open about, since it can be a huge struggle, so often women keep the struggle to themselves. The thing I love about this podcast is that they discussed how difficult it can be for healthy couples to get pregnant. People are taught that it is extremely easy to get pregnant, generally as a deterrent for becoming sexually active before being ready. It actually isn’t always that easy. Sure, there are some couples that have a very easy time getting pregnant. There are so many couples that struggle to get pregnant, however. Sometimes, it is a short-term issue, and sometimes it becomes obvious that some people will never get pregnant. As someone who may struggle with fertility due to PCOS, this episode really hit home for me. It was good to hear about other people’s struggles, and to know that it is something that no one needs to be ashamed of. It also made me hope that I do not have problems with fertility, I would really love to be a parent someday. This episode made me sad and hopeful, I commend the hosts for discussing the topic.

Next, I listened to a podcast that I have never heard before called CodeNewbie¬†and I am so glad I found it. It’s mostly geared toward people who are new to code, it seems, but there is definitely something for everyone. The first episode includes an interview with Carlos Lazo, and talks about how he learned to code and got hired. One point made in the podcast that I am so glad they brought up is the fact that people who work in coding will always be learning, since the technology is always changing. I think that’s the thing I like about it so much. I love learning, and I love being in school, so working in an industry that is accepting of people who want to continue to learn and grow is very appealing to me. They also discussed how to interview for a job in the tech industry, which seem really scary. Not only do you have to do the standard interview where the prospective employer sees if they think you would fit in and have an idea of what you’ll be doing, but you also have to do a more technical part of the interview to show what you know. The advice that Carlos Lazo gave is to be honest in an interview about what you don’t know, but also make it clear that you’re willing to learn. This is a podcast I will definitely keep listening to, I love it!

Another new podcast I tried out this week is called The Station Wagon Podcast, which was actually recommended to me on Twitter by Marc, one of the hosts! This is a really interesting podcast, where a brother and sister duo give something up for two weeks, and talk about how it went! In the first episode, they give up sitting. That means that they stand at work, stand or squat at home, and only sit when commuting or when they had to (work meetings, etc). It was so interesting to hear how it went for them, and points where they wanted to give up. The funniest story of the podcast was a point where the other host, Julie, was at work. She had a meeting to attend, and was so excited for the rare opportunity to sit down. One of her coworkers told the person they were going to have the meeting with about Julie’s challenge. The person was super excited about her challenge, and told her she could absolutely stand through the meeting! How disappointing. I am so excited to listen to more of the episodes. I think that this podcast would be a good one for anyone to listen to. It’s not super technical, and is interesting, informative, but is also really fun!

Another podcast that was recommended to me was Developer Tea. By the title, you can see that this is also a podcast for people who work in web development. The cool thing about this podcast is that it’s a short-form podcast, which I am not very familiar with. I usually listen to podcasts that are around an hour long or more. The concept of this one is to have a podcast that someone could listen to while taking a tea or coffee break. I listened to the first two episodes. The first one was basically an introduction to the podcast and its host, Jonathan Cutrell. The second episode is about focus. This is something that I struggle with sometimes. It’s so easy to get distracted, especially at this point, when I am learning how to code. Focus is extremely important, in most of the things we do. A short discussion on focus, why it’s important, and how to increase focus was really helpful for me. I learned a little, and it made me think about my habits. This is a podcast that I am really excited to keep listening to.

I hope that you guys try out some of these podcasts, it’s awesome to support the people who make them, and learn things at the same time! Do you guys have any suggestions of podcasts I should try out? Let me know in the comments!