Última actualización: 3 marzo, 2021
Nobody likes their job. That's what I used to tell myself when I got my first job and I felt such a puzzling sleepiness, together with a need to run away. I accepted it, saying that’s life, thinking that later a better job would come. What a big fat lie. And how lucky was I for reconsidering my work life.
This is not only the story about how I did it, but also a roadmap about how I would do it, if I had the chance to start over, knowing what I know now. If you also want to change your career path and reorient it towards web development, I sincerely hope this guide helps you out and spares you some troubles. But I also hope it won’t spare you from all of them, because
I believe that facing and beating the adversity is something to be proud of.
News for your "future self"
If you are or have been through an “I don’t know what to do with my life” period, you know it's an uneasy feeling. First-world problems, yeah, but you are doing yourself no favor by ignoring them or thinking that your future self will take care of them.
I have bad news for you. Neither you are going to find out what to do with your life by cotemplating the void, nor you are going to fix anything by covering the problem with a distraction. Because the deepness of the hole you make in the sand doesn’t matter, and neither if you cover your body with sand. At the end of the day you will always have to clean up the sand to be able to come back home and face your reality.
Why don’t you do a favor to your “future self” and start facing your problem today, instead of tomorrow?
That’s what I told myself in 2017, after spending months wasting time, not knowing if I should change career path or if so, where to start. Then, I imagined myself in a year from that moment. I saw myself having the same dull work life. And I panicked. But that’s not the only thing that happened. I also realized that the moment to change was NOW. And I got down to work.
The amazing side of being a developer
When you are learning web development, there is no bigger boost than the first time you achieve to code something that really does what you intended. In a way, it’s like you finally managed to train a machine and from now on it will always work for you . Once you learn that, you understand that,
in programming, the only limit is your imagination.
Programming is an art. Quite structured and logical, but still an art. But it is also a language: the language of machines. And as a language that it is, anyone that really wants to can learn it. But, like any "human" language, it is neither easy nor quick to learn. There will be people more naturally gifted for it, no doubt, but that doesn't mean that a person who is good at "human" languages wants to learn 5 languages, nor that a person who is bad at it cannot learn them.
Because in programming, as in life in general,
what matters is the will to learn and your attitude towards challenges, not your starting point.
I believe that anything can be learned, if you have the right attitude and reasons strong enough to push you forward every time you think about quitting.
Why I became a developer (and why you may wanna become one too)
I had powerful reasons, and I still have them. I learned programming because:
- I wanted to work in a creative sector
- I had always liked everything related to technology. Computer science was one of my favorite subjects in high school
- the information technology sector (IT) is a crisis-proof industry
- it is feasible to learn programming and get a job as a junior developer in less than a year
- programmers have a salary, at least, decent, and those who don’t is because they are not ambitious enough, since there is a lot of demand for developers
- It's the job that one day could give me one of my life goals: to be location independent, become a digital nomad and be able to work remotely from wherever I choose, which would give me the chance to spend more time with my loved ones.
This was one of the mindmaps I pictured:
A simplified concept of what the Japanese have discovered much earlier than me, called Ikigai.
When I did this mental analysis, a big question automatically came to my mind: was all this really possible? And if it was, why so many people around me that were sick of their jobs hadn’t already discovered it and started working on that? Very simple, because:
a) Most people complain, but then do nothing to change, because changing usually means work and pain.
b) Few people are interested in programming. Partially, because everybody likes different things, but I also believe that it due to a set of clichés that still surround the IT world.
Let's talk about programming stereotypes
No, we don't know why your printer isn't working, sorry
People tend to lump together everything that has to do with "computers". That's as absurd as saying that everyone who works in the health sector is a doctor. In healthcare there are doctors, nurses, ambulance drivers and so on. No one thinks about asking an ophthalmologist how many pills to take for the back pain, or a receptionist if he can change your knee replacement.
Similarly, in IT there is also a wide range of professionals. One of the classifications could be:
1. computer engineers
- frontend developers
- backend developers
- full stack developers
2. technicians (those who know how to fix things like the printer, tv, etc)
This article is about category 1.
Let’s do a simple analogy with a clothing store. The frontend developers would be in charge of creating the look and feel and the assembly of the store, while the backend developers would be in charge of the back room, where orders are processed and the stock is stored.
The confusion could come from the fact that the term "computer engineer" is somehow worn-out, since every computer engineer can be a developer, but not every developer needs a university degree in computer science. It’s my case. My degree is in Law, and here I am, happily turned into a frontend web developer .
This is one of the wonders of the IT sector. There are so many IT companies that will give you an opportunity to prove your skills regardless of your college degree (if any). In the end, the one who will get the position will be the one who shows technical skills and proves his eagerness to learn and solve problems.
Neither the fashion industry is our enemy nor sedentarism is our best friend
No, combining colors properly is not a mission impossible for us. I love clothes and looking stylish . Years ago, my mom and I had a business idea to create "The Digital Closet", an app to scan and classify all your clothes and automate the selection and combination process to help you save time. Ey, I’m not saying it was good, just saying that it was an idea…
On the other hand, I am a super healthy person, I care about eating well and I'm also a sports freak .
A geeky touch
Yes, it's possible that many of us are a bit geeky and we even know the name of the swords of The Lord of the Rings ... But that's not incompatible with being friendly and social. Besides... when you look closely enough, no one is normal.
No physics, no math: logic
Frontend development, my area of “expertise” , doesn't require you to know how to do complex calculations. It’s not about that. What matters is that you have a structured and curious mind, that you like to analyze everything and that you don't feel too uncomfortable about things you don't know, because the IT sector is huge and it's important to accept that you will never know everything about everything.
Welcome to a world of uncertainty…and make yourself at home .
I think I have already given you many reasons to jump in and learn to code. As I said above, I opted for frontend development, because it's much more visual, you can see the results of your code instantly on a screen.
But things were not always so clear to me. During my learning phase (I’m still on that), I fell into pitfall after pitfall. I will detail them, so that you can identify them and avoid them.
How I learned to code (common pitfalls)
- waste time on not important stuff
- not doing enough research to select good courses
- be impatient
- not knowing exactly what to study
- take notes the traditional way
I admit it, I am an impatient person. Programming has helped me to smooth that flaw, but that caused me some problems at the beginning. I did enough research to know that I could learn to code without getting a computer engineering degree, yes. In fact, I was hooked on the idea of being able to learn to code in a relatively short time, compared to the approximate 5 years it takes to obtain a college degree.
I found out that many people had learned to code on their own, self-taught. That was music to my ears, because the last thing I needed, with a full-time job, was to enroll in a course with rigid schedules impossible to balance with my circumstances.
Yes, I discovered that there were online bootcamps, but the disadvantages were more than the benefits. Specifically, there was only one drawback that beat all the benefits: the price. I had already decided that I should study online, but the prices of bootcamps seemed too high to me.
In contrast, I discovered sites like Udemy, where courses had two zeros less than a bootcamp. And it won me over. I discovered Udemy in November of 2017, and when I first saw it, they had many courses on sale due to Black Friday. So, I fell for it and bought like 5 courses. It was not a large amount, for less than € 50 I had them.
Then I realized that Udemy launches several offers a year (like this one), so, there was no need to buy those 5 courses at once , I just bought them for the "urgency" that the offer ran out. Nice little marketing trick, but hey, for the price I paid, it didn't hurt. I bought all kind of courses, not just about code, because, you know "just in case". Just in case what? I don't know, they were very cheap and consumerism won the battle .
So here is one of my mistakes: buying too many courses at once. And for what? Realistically, you will only be able to do one course at a time, because
multi-coursing is not a good idea for your productivity.
But, by far, my biggest mistake was not researching what was the best web development course out there. My first idea was to take a course in Spanish, because, being such a new topic for me, the language could be a barrier. Huge mistake, since that prevented me from selecting good quality courses simply because they were not in my mother tongue.
I was afraid of not understanding the teacher and therefore not understanding his explanations. Which could have been solved by taking the time to see the first lessons of each course, since Udemy gives you that possibility before buying it. But I didn't even try. I went straight to looking for Spanish web development courses .
I filtered by bestselling courses and bought one. I wanted to get down to work as soon as possible and start learning, so I didn't go any further in my research. If I had, I would have discovered that there are two reasons why a course can be the best seller of any platform:
- because it’s the best
- because it was the first of its niche
It took me months to realize that my first web development course fell into the second category . I held on as long as I could, until the course got so bad that I stopped beating myself up, I left it halfway and I started looking for another. This time, with no language filter. And the quality leap was massive.
I prefer not to mention the crappy course in Spanish that I did, but I will give names below of the courses that were (and still are) tremendously useful to me.
Fortunately, with the abandonment of my first crappy-course, I also ditched a habit that I still had from my university times: taking notes. Taking notes has nothing wrong. My mistake was the format. I took them by hand because I thought I was absorbing the concepts better. Not only is this reasoning useless for studying programming, but it is also very time-consuming.
I wasted hours and hours taking notes that I never really used. Every time I wanted to refresh a concept, I would search for it directly in Google. The only purpose of my notes was to gather dust.
Another of my pitfalls was that I was not very sure about what exactly I had to learn to become a frontend developer or about the content that a course should have to be considered acceptable and useful.
In my experience, it was a mistake to buy a course that contained, in about 35 hours, and according to its promotional message, enough material to become, not only frontend developer, but a full stack developer. They supposedly taught you:
- A JS framework (React)
and even more things. At a certain point in the course, they started teaching React. That's when I realized that I still had the JS level of a minion, so I got frustrated, and again, I left the course halfway.
But that was the last time I did something like that. By then, I had already spent a couple of months learning, so, things were a little clearer than before. At least I finally knew what I didn't know, what I should learn and how to learn it. So, I decided that I would do one course (at least) for each topic, namely:
- HTML and CSS
- a JS framework
And from that on, things started to go smoothly. Therefore, if today I had to start over, I would know much better which path to choose and what stops to make along the way.
Your map to success: The Frontender Challenge
This is how I would do it today if I had to start learning frontend web development. Let me summarize it in an infographic:
Find out what a developer's workday is like
No need to do that, I'll tell you about it .
I’m a big fan of the Phoneless religion, a joke (with tons of reality underneath) invented by Joan Boluda. When I started working as a developer, I noticed that I didn't even have a phone on my desk. For what? In general, developers don't have direct contact with clients, that is up to the Project managers.
To stay in touch with my team, nothing better than a chat platform, like Slack. Don’t get me wrong, I’m all in for a call when needed, but to stay in touch with my colleagues, a chat is less intrusive than a call, allowing you to focus better on your work.
Talking about distractions, being a developer also involves a high possibility to work from home. This is a tricky issue, because there are people who have more distractions at home than at the office. In my opinion, unless you have special circumstances where you must take care of someone, I think that staying focused is simply a matter of discipline (and maybe having the fridge far away).
In my company we have been working remotely since the COVID-19 outbreak and I, as most of my colleagues, couldn’t be happier. I have never been so productive and had so good work/life balance.
Another topic is the female/male ratio. At the moment things are very unbalanced, I really don't quite understand why. I would love to hear your opinion about it in the comments .
In my company the ratio is approximately ... 10 to 1. In fact, during my first year there I was the only IT girl. That being said, I never had any issue with that, because my co-workers are simply awesome. But numbers don’t lie.
I could go on talking about a developer’s worklife, but I think this is a good summary. If you are interested, in this Andrei Neagoie course there is a very interesting section about it. For more details on the courses I recommend, read on .
Do the frontend / backend test
In other words, make sure what you like the most, the frontend or the backend. You can check out YouTube videos, like this one from Max, one of my teachers on Udemy. Don't spend too much time on this, and keep in mind that choosing one does not mean discarding the other. You can always learn it later. Choosing one simply means picking your starting point.
Design your study plan
I admit it: I am a planning freak. I love planning everything. Always knowing what my next step is helps me achieve my goals. Therefore, I recommend that you design a learning plan.
Because feeling lost when learning to code is a natural part of the journey, but sticking to a plan will help you not walk blindly.
In my case, the plan consisted of:
- ️ study at least 1 hour a day, 6 days a week
- eliminate distractions (when I study I leave my phone in another room)
- reduce my working hours
- have a study buddy
- divide the study into small tasks
In fact, I studied many more hours a day, but that was the minimum. I talk about it in detail in my Geek Challenge 365. I didn't study alone either, and that's something that helped me enormously. When I decided to study programming, my boyfriend hopped in and started studying too.
Although our subjects had little to do with each other (he studied data science and machine learning), I felt very accompanied and supported. It would have been very difficult to study if every time I came home I had found him watching TV or so.
Instead, we teamed-up. When it was study time, we studied. When it was time to go out and rest, we relaxed. When one of us was stuck, we encouraged each other to keep going.
Whenever we overcame a challenge, we shared the joy, because shared happiness tastes better.
So if you have the opportunity to drag your partner or another innocent victim into studying like I did, don't hesitate. A fellow companion will be of a lot of help .
In case it is not easy for you to find that friend in your close environment, there is a very millennial alternative: find a programming buddy within a platform specialized in that, such as the Zero to Mastery Academy.
As for the study itself, I have several learning techniques. In my previous job in the Administrative/Financial legal sector, I asked to work 80% instead of full time. With that I got to work 4 days a week instead of 5. So, here's one: steal as much time as you can to study .
Another thing I always do when I study is to get my phone away from me and silence it. This way I remove the source of most of my distractions, leaving only space for study, which I usually organize by blocks. Nothing fancy, I just watch each lesson (on video) twice. The first, without pausing it, and the second, pausing it and writing the code the teacher explains, always trying to understand the why of everything.
To understand that why, practice everything the teacher proposes, and go much further. When you take online courses, it is very easy to get carried away and watch lesson after lesson like a movie. It is not.
If you value your time, take it seriously.
Learn HTML and CSS
And finally, the moment to choose a course has arrived. As I said, I chose the wrong course several times. Until I discovered Jonas Schmedtmann and his HTML and CSS course.
This course has thousands of students, so if you get stuck, open the Q&A section, because it’s very likely that your question has already been asked and solved before.
As I said above, I usually watch each video twice. This is the only negative point about Jonas's courses, who sometimes makes very long videos, and the longer a video is, the more difficult it is for you to stay focused. But don’t give up!
After your first contact with HTML and CSS, I recommend that you continue learning CSS, because you will still have a lot to learn. For that, nothing better than this advanced CSS course, also by Jonas.
Another thing that I love about Jonas is his newsletter, where every month he sends out super interesting articles about the world of web development. It saves you from having to go find the latest news yourself, keeping you up to date with the industry. A true bargain!
While doing these courses, you can start getting into the world of frontend via books. The truth is that I have few books to recommend about HTML and CSS. In fact, only one: John Duckett's. It's a wonder to look at, full of beautiful explanatory graphics.
Especially when you are taking the advanced CSS course, practice a lot. Keep in mind that there you will learn complex topics like compilation and proper file management when a project reaches a large size. This will help you, among other things, to understand the folder structure that a project should have in real life.
This will also be a good time to start learning Git and GitHub. I didn't need to buy a course on this, you can learn it with YouTube videos, or check the complete section that this course of the Zero to Mastery Academy has about it.
The moment of truth. This is when you will truly learn a programming language, because HTML and CSS are not. JS is an increasingly popular language, arousing both passions and hatred. I am very fond of it, because it’s the first programming language I learned and the one that opened the doors for me to work as a junior frontend developer.
But my start was very frustrating. I would spend weeks stuck on one topic, shedding tears of frustration on more than one occasion. I started many courses that I left halfway through, because I simply didn't understand what the hell they were talking about. Until I found The Net Ninja and his JS course. His British accent is the clearest I've ever heard, and his explanations are clean and super engaging.
It was not the only course I did, but it was the first with which I truly began to understand JS. The truth is that, although most courses claim that "this is the ONLY course you need to learn JS", in my experience, it will be convenient for you to do more than one. For many reasons:
- ️ they will explain the same concept to you from different perspectives, as they are different teachers
- you will reinforce your knowledge about JS, since they will explain concepts that you presumably already know, because you will have already done a course that explains it.
Therefore, my recommendation is that you take more courses, like this JS course that I took, from Jonas.
All courses I take (at least the ones I take now, since I learned how to select courses) are kept up-to-date by their creators. That is a key point when purchasing them, and Jonas is no exception. If so, I would stop recommending his courses or those of any instructor who doesn’t care about his students. So, no worries, I've got you covered.
Finally, I’d like to talk about what I call "transversal courses." They are courses that have everything, covering both frontend and backend topics. Be careful with these courses. I started with one of those and ended up quitting it, because it was overwhelming. But after doing Jonas's JS and The Net Ninja courses, I went back to it, and I found it remarkably good. I'm talking about Colt Steele's web development course.
Colt is a web development master. He is a teacher of in-person bootcamps in the US and you can tell that teaching is his thing. This course will help you consolidate all your JS concepts, learn some new ones, and start exploring new technologies.
I use it as an index on the world of web development in general, as well as the last transversal course that I am going to recommend you: The complete web developer - Zero to mastery, by Andrei Neagoie. Again, this will help you brush up on everything you've learned from JS (trust me, you'll need it). Also, Andrei includes two very interesting sections in his course.
One about a usual developer's work environment, and another, an introduction to React. Just for that first part it's totally worth it. If you are also sure that you want to learn React, then do not hesitate, this is your course (after having done the other courses dedicated exclusively to JS, remember).
One last thing I love about Andrei's course is that, like Jonas, he has a newsletter about web development. And, forgive me Jonas, but Andrei's is much more elaborated. It’s also true that Andrei has a bigger team behind. Also, there is no reason to not subscribe to both .
As you continue with your JS courses, it’s a good time to start listening to podcasts. I think that if you start before learning JS you will be super lost (it happened to me) and therefore, you will only waste time. I have one specific recommendation: Syntax.
If you prefer to rely on books to learn JS, you will love the You don't know JS saga.
Look for a job
The (other) moment of truth arrived. There is no going back, you feel totally un-ready to look for a job . I know. But you must start now. Because the sooner you start, the sooner you will get your first rejection, and also, the sooner you will get your first interview.
Believe it or not, when I was in the legal sector, I sent more than 300 resumes to get a job. Whereas, when I started looking for a frontend developer job I sent only around 10 resumes. They answered me from two companies.
With one, I only exchanged a couple of emails. The other offered me an interview, then another more technical interview, and at the end, an opportunity. I've been there for two years and there are days when I still don't know how I got here, although I have a slight idea.
You need to have courage to make such a change and bear the surprise (and sometimes skepticism) of people close to you.
A worthwhile company will notice that, appreciate it and give you a chance. Why? First, because they have nothing to lose (my first contract was of limited duration - 3 months - and part-time). Second, because they have a lot to gain, since a grateful and motivated employee is not so common.
Although your main research channel should be Linkedin, don't underestimate the power of your contacts. Yes, those friends who work in something related to IT. Write them, invite them to a coffee and ask them if they know if their company is looking for a junior developer. You will be surprised what can come out of those conversations.
In fact, I got my job like that, through a friend who had a friend who worked in a FinTech company. He got me in contact with them. No Linkedin needed.
By the way! If you are already in this phase, let me tell you that my company is hiring. You can contact me for more details.
I believe this is a step you should take in parallel while you are searching for a job, but don't jump right into it if you don't have a solid JS foundation. I tell you from experience. I started learning Angular too early while I still had doubts about JS, as it’s the framework that we use in my company.
That was the only reason I started studying Angular, and I honestly think you shouldn't think about it more than necessary. To have a bit of context, you can watch videos like this one in which Max explains the differences between the current 3 most popular frameworks.
If you still don't have a favorite after watching the video, just check out which framework is the most popular when you are looking for a job. I already tell you that in 2020 is React, although I personally like Angular more. That’s why I am going to recommend you my favorite Angular courses.
Finally, I’m happy to being able to recommend a course in Spanish: The Angular course by Fernando Herrera. Fernando is a very good teacher and explains things very calmly. This was the first time I heard certain programming terms in Spanish that until now I had only heard in English, and it was a bit weird at the beginning. But it doesn’t hurt to know them as well.
In any case, and in order not to get confused, I always try to use the terms in English, because is the human language used in programming languages. For that reason (although it’s not the most important) I am also going to recommend that you take the Angular course by Max Schwarzmüller.
In my opinion, Max is one of the best instructors on Udemy. He also has a course exclusively on JS, and the only reason I can't recommend it to you is because honestly, I haven't taken it. He published it in 2020 and by then I was already taking Angular courses. But if he had published it earlier, when I was in the middle of the JS learning, I would have bought it without any doubts.
Max's courses stand out for two things: his clear way of explaining things and his student support, which is of superb quality. Whenever you have a question, he or his teaching assistants will be there to answer it in the comments quicky. His courses are a real gem .
Find a job
Sooner or later, if you have done your part well, a company will make you a job offer. A sweet stage of your working life will begin, because it will be the end of long months of sacrifice on your part. But actually, now another equally important path begins for you.
Because you haven’t done this whole journey as if it was a mountain trip with the aim of reaching the top and then returning home. No. You are a developer now, and that changes a lot of things. You will notice that your mind starts working in a more structured, curious and logical way. For example, when I started programming, I also discovered the world of investments and personal finance, topics that until now had never caught my attention.
And it was not by accident. Learning to code boosted my curiosity and taught me to be more patient.
Face new challenges in your job with that same curiosity and patience, and you will surely do well.
Be nice to your co-workers and ask them all the questions you need, but try to write them down somewhere so you don't have to repeat them. For that, I use Evernote and can't live without it .
The downside of programming
No one is surprised about doctors always learning new medicine topics. They go to conferences, do seminars, and many of them often write articles for medical magazines. The web development industry has that in common with healthcare.
Like in healthcare, the IT sector has no end. There are hundreds of programming languages. Yes, hundreds. But that should never be a cause for stress. Because just as a doctor has a field of expertise, so will you. There is not enough time in a person's life to learn absolutely all the programming languages that exist. Nor you will need to.
The only real downside about programming is that, if you are like me, the more you learn about IT, the more it will fascinate you, and the more you will want to keep learning .
But aside from my geeky side, the only thing you should worry about if you are a developer is to keep up to date with the industry. With newsletters of Jonas and Andrei you will have the whole spectrum more than covered .
My developer setup
Having good co-workers is just as important as having a job that you like. When these two requirements are covered, you should pay attention to other (almost) equally important topic: the tools you use in your day-to-day life. Without further ado, I'll tell you about my developer work setup.
- My chair: for years, I have worked and studied with a € 50 Ikea chair, with some extra armrests. It was such a crappy fix. But since my company sent us to work from home due to the outbreak, I saw the ideal opportunity to upgrade, and I could not be happier. This chair takes special care of the neck, down back and arms. The best thing I bought in years. The armrests are the crucial part for me, because with such a short distance from the table to the wall, I cannot rest my forearms on it. Hence the importance of armrests.
- My laptop: it’s the company laptop, which I use both for work and study. My personal computer is a Toshiba that has lasted me since college, but having this powerful Lenovo, I hardly ever use mine.
- My keyboard and mouse: it’s a wireless pack, with only a USB stick to connect it to any of your laptop ports. It’s 3 years old and I have changed the batteries only once.
- My glasses: I don’t need glasses, these are simply to block the blue light. I bought them shortly after I started studying programming, as I started to get constant headaches. And when I say "constant", I mean every day. There is a “before and after” these glasses. If you already wear glasses, all you have to do is ask the optician to add a blue filter blocker.
- My monitor: I need to work with two screens (laptop + an extra screen). Three better than two, but you see that my desktop only fits my laptop + an extra screen. Being so close to it, it was not convenient for me to buy a monitor larger than 24 inches. Keep this in mind when designing your workspace, because if you have enough distance from the beginning of your table to the wall for your forearms, you may prefer a bigger one like this, of 28 inches.
- My earbuds: Since I only need earbuds for videocalls and music, I don't complicate my life. I use these simple headphones with microphone.
- My code editor is Visual Studio Code, a huge leap in quality compared to Sublime Text. It's built by Microsoft and it's free. What else can you ask for .
- My music: I usually use Accuradio and choose a classical music station. Yes, I am much more productive with classical music. Ey, every person is different...
How to beat the impostor syndrome
To be a developer you need, at the very least, to have a curious mind. But once you are a developer, programming will feed your curiosity, creating a perfect loop that will make you become a better developer each day.
Remember that, especially the frustrating days at work when nothing works for you, because your laptop is having a lazy day, or because you can't even move a simple button with CSS. Trust me, you will have those days.
Likewise, there will be days when the impostor syndrome comes to visit you, like a sinister shape with a raincoat and a shadowed face . That’s how my impostor syndrome looks like. Whatever yours looks like, you will recognize it as that uncomfortable feeling of shame that you will feel some days at work. An unpleasant sensation that has a voice, and tells you things like:
"I hope your colleagues never notice how little you know"
"You actually have no idea what you're doing, do you?"
"Any day they will call you at the boss office to tell you that they are firing you, because they need a real developer."
Shut up that little voice from hell as soon as possible. Look at your contract. What does it say? Frontend Web Developer.
Still having doubts about whether you are a real developer? Learn something new every day, even if it's just a keyboard shortcut.
Ask questions to your team and never isolate yourself. Find a balance between "trying to solve a problem on your own, without asking others," and "asking absolutely everything without stopping to think first." The middle ground is to assume that you have already spent enough time looking for a solution, and perhaps a colleague can guide you on how to continue.
Don't be ashamed to ask questions. There is something magical about it. In my experience, many times I have squeezed my brains trying to find a solution to a problem, and I ended up finding the solution myself, just by explaining the problem to a colleague.
Above all, be honest with yourself and do what you can to improve every day, because
who does his best everyday is not obliged to do more.
(Thanks dad for always remind me that).
Remember where you were a year ago and where you are now. Imagine what you will know in a year. But start small. Because a great journey begins with a single step. It’s all about getting started.
Sobre la autora de este post
Soy Rocío, una abogada reconvertida en programadora. Soy una apasionada de aprender cosas nuevas y ferviente defensora de que la única manera de ser feliz es alcanzando un equilibrio entre lo que te encanta hacer y lo que te saque de pobre. Mi historia completa, aquí.
Otros artículos que pueden interesarte