[et_pb_section bb_built=”1″ _builder_version=”3.0.47″][et_pb_row _builder_version=”3.0.47″ background_size=”initial” background_position=”top_left” background_repeat=”repeat”][et_pb_column type=”4_4″][et_pb_text _builder_version=”3.0.90″ text_font=”Work Sans||||||||” text_font_size=”16px”]
I first learned that you could become a developer without formal education in that particular field when I met a good friend who is a Swift developer.
At the time, I was struggling with the demands of society to finish my masters in English literature. I had started -and failed at- holding a normal desk job, and I was terrified of the prospect of working in an office setting (thanks to some drama and bullying I had experienced in the aforementioned desk job). I was working as an assistant teacher for children with special needs, and although it was a very fulfilling job, it was a tough job, and I felt culturally alienated from everyone I worked with. Mind you, they were nice people, and I liked most of them, but I felt as out of place as a circle in a group of triangles and squares.
[/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row _builder_version=”3.0.47″ background_size=”initial” background_position=”top_left” background_repeat=”repeat”][et_pb_column type=”2_3″][et_pb_text admin_label=”Text-2″ _builder_version=”3.0.90″ text_font=”Work Sans||||||||” text_font_size=”16px”]
My developer friends, however told me that there was a whole world out there and that it would be pretty cool if I could explore it. they said I could totally teach myself how to do this coding thing, even if it was just for myself. This was at the end of 2015.
I was not a complete computer noob, but I was pretty close to that. I had done a few Codecademy tutorials in markup language, but there were two things that happened that year that changed my life:
- I learned about the Free Code Camp.
- I learned about the Django Girls and went to my first PyConES.
The Free Code Camp is this amazing website that helps you get better at javascript and other web technologies. It’s often better to pair it up with other resources but it gave me a good curriculum to work through by myself.
The Django Girls is this one-day event where they teach a bunch of women about how web development works and all the best practices. their tutorial is one of the best Django tutorials (and one of the best tutorials-period), I have ever encountered. In my case, my acceptance to this particular Django Girls led to earning a ticket to the biggest python conference in Spain.
[/et_pb_text][/et_pb_column][et_pb_column type=”1_3″][et_pb_image admin_label=”Skip Beat ‘Box R’ reference ” src=”https://cla.udia.me/wp-content/uploads/2017/12/sb-squares.png” _builder_version=”3.0.90″]
[/et_pb_image][/et_pb_column][/et_pb_row][et_pb_row _builder_version=”3.0.47″ background_size=”initial” background_position=”top_left” background_repeat=”repeat”][et_pb_column type=”4_4″][et_pb_text admin_label=”Text-3″ _builder_version=”3.0.90″ text_font=”Work Sans||||||||” text_font_size=”16px” background_layout=”light”]
There I was, teaching myself and meeting people and feeling like everything was way over my head. People would ask things like “are you planning on learning as a hobby? Or will you make it a career?” and to be quite honest, that first year, I didn’t know. I was so close to getting that masters degree it felt like a waste of time and money not to finish. I only needed one thing: the thesis and that was it. Also, working in an office was a scary thought. It meant having to deal with my demons and that scary voice in my head that tells me “I’m not good enough!”.
Time passed and soon it was already one year after I started learning how to code, and nothing much had changed in my life. A couple of weeks ago, I went to a MeetUp and talked to a woman who was very surprised that it took me that long from the moment I started to the moment I got my first job.
What can I say? I guess it was difficult to make the decision to throw away everything I had built up until then. Some people start with computational linguistics, or mathematics or some sort of engineering. I think that kind of background makes for an easy transition. As an English literature major, I remember going to a talk from the university about employability and prospects and having a university representative say “well, if you had wanted to get a job, you wouldn’t have studied what you did”. That was it, that was all I knew. It’s hard to think you’re worth something after being the butt of the joke for so long.
So then my second year rolled around and I decided to focus on this coding thing and a second issue showed up: what language to learn? There were so many languages. I had experience enough to know most people tell you to stick to one language and go for it. Some others ask you “what do you want to accomplish? Use the language you need to get your idea working”. I have issues with both these pieces of advice:
First, if you focus on the first shiny thing that comes across, you might end up learning a lot about that one shiny thing, but then you’ll get into this annoying mentality of “I have a hammer, and I will hammer everything in sight”. You see, different computer languages have different strengths and weaknesses. I know many people who have that one thing they know, and they know it very well, but can’t really understand anything else. I don’t particularly think it’s wrong to be a specialist per se, but I think it’s a bit shortsighted to ignore everything else in favor of the one thing you know. Sometimes you need one type of app, sometimes you need a different type. Learning about languages and how they can work together gives you a bigger toolbox than just a single hammer.
Second, if you already have a product in mind, I think it’s great to think about a language that will help you accomplish that. However, if you just want to learn how to code and don’t have any idea of where to start, it’s a bit scary to think about a project. I mean, you could potentially want to build the next facebook for cats, but somehow get stuck at the part where you’re supposed to add the meow-recognition login page. How much is too much to tackle? Are you good enough at assessing how good your skills are? Are you confident you can find all the information you want online? And once you find your answers in Stack Overflow, will you even be able to understand it? But hey, if you have the idea and the drive, I think it’s okay to go for it. My one advice would be to start small, with the stuff you know how to do, and then go deeper into small aspects you can tackle and so on.
What did I do instead of those two things? I allowed myself to have some time to go over everything I could get my hands on: Python, Ruby, JS, PHP, Java, HTML, CSS, Bash. I did a course on Linux administration, then Python, then JS and if you ask me if it was messy, yes, it was. I didn’t learn very deeply about any of those technologies but I started seeing patterns and learning about things I liked in languages, and things I didn’t like in languages. All the while, I kept going to MeetUps and helping out with events until I finally understood some of the lingoes a bit better. I discovered I liked Python as a language. I like how readable it is. I like learning about accessibility and clean code. My code might still leave a lot to be desired, but I could work in that direction.
Some people decide what language they want to learn based on which language is more in demand or what will give you a job. I’m an English major. Any developer language would give me more job opportunities than my whole life of academic endeavor. So I picked something I loved: Python and I started learning.
What happens next is not exactly what you are imagining right now. First, six months after I had started taking this coding thing seriously, I met some people who had set up a coding bootcamp for refugees. It’s called Re/start, and you should check it out. They’re lovely people. I am glad that I decided to participate with them. I learned a lot there. Personal circumstances made me unable to finish the whole curriculum, but those three months were a good investment.
After a month of code-induced burnout (studying 80 hours a week is not for the faint of heart), I decided to reach out and jump back on that horse. I also decided to start seriously applying for jobs. It just so happens that a friend of mine recommended me to do an internship type of thing at the company where he works and that’s where I am right now.
It took me two years. Most people will think it’s too long. I think that -without counting the time I was unsure about whether I should do this for real- I could say it took me half a year, that would sound better in this world where faster is always the way to go. But that would be discrediting all the personal growth I’ve done in between. I still have a long way to go, but at least I know where I’m standing.
[/et_pb_text][/et_pb_column][/et_pb_row][/et_pb_section]
One reply on “Is two years too long to become a web developer?”
[…] Because I want you to succeed, here’s a couple more tips: I’m not sure about what language you want to learn. You can test out a bunch of them or you may already have one language in mind. There are books for every language you can imagine and online courses about a bunch more. It would be impossible for me to list all that there is out there, so I’ll point you in the direction of codecademy and tell you there’s plenty of free online courses online, so go find them (there might even be a few hints in my previous post). […]