DEV Community: Cocot 💚 git reset —hard HEAD

Tu primer plan de carrera personal en desarrollo web

Cocot 💚 git reset —hard HEAD — Sat, 25 Jul 2020 23:28:19 +0000

Hace relativamente poco, di una charla introductoria sobre desarrollo Web, dirigido especialmente a quienes están empezando. A partir de ahí, recibí muchísimos mensajes de mujeres preguntando un poco más sobre mi pequeña experiencia y sobre recursos que les pudiera resultar útiles. Esto me abrió un poco la mente. Cuando recién empezaba, hace dos años atrás, tuve ayuda de muchas partes y en algún momento me encontré un poco desorientada en qué hacer primero. Es tanta la información que hay a nuestro alcance que cuando empezás a leer y a estudiar, hay más y más y sentís que nunca terminas de saberlo todo (en realidad nunca terminas de aprender). Yo creo que eso es lo que lo hace más interesante. De hecho, tomé cuál consejo me sugerían porque estaba decidida a cambiar de rumbo y había encontrado en esto un desafío súper interesante que quería emprender.

En estos años cuando me encontraba en búsqueda activa de trabajo decidí recolectar una serie de conocimientos que debería tener según mi seniority. Obviamente esto es relativo, como siempre digo no es algo estandarizado y van a encontrar que varía según la persona, la experiencia, empresa, etc etc etc. Este es mi cuadro personal que hice como mi guía cuando a veces me saturaba un poco la ansiedad de aprenderlo todo. Hoy me siento un poco más relajada al respecto porque alcancé un lugar que me costó mucho y estoy en esa instancia en la cual sigo aprendiendo pero a la vez estoy disfrutando mucho el camino y mi trabajo.

En este caso particular mi elección de siempre fue el desarrollo frontend por lo tanto mi plan de carrera está orientado a esa área. Si quieren saber más info sobre las distintas áreas en desarrollo web les dejo el link de la charla abajo o mismo también hay mucha info en internet. Les sugiero hacer cambios propios y buscar qué más les gustaría aprender en cada sección. Sino saben bien por dónde empezar creo que esto podría ser un puntapié a seguir buscando y a que lo puedan adaptar según su gusto y criterio.

Amaldonado7 / My-Career-Path

My personal Frontend career path created in Figma to use as a reference

DISCLAIMER: Este cuadro lo hice yo en Figma basado en anotaciones que hice durante dos años con un modelo que me habían pasado. Puede variar según otros criterios.

Les dejo algunos artículos relacionados con los cambios de rubro a sistemas para inspirarles:

Esta no es una historia de amor

Bel Rey ・ Jun 14 '20

#motivation #career #motherhood #startup

Cambiar de carrera post 30.

Denise Neustadt 💚💚 ・ Jun 4 '20

#career #coding #javascript

Y el link del video que les comentaba más arriba:

Happy coding!

How to be a junior pregnant developer and survive?

Cocot 💚 git reset —hard HEAD — Wed, 15 Apr 2020 19:22:32 +0000

It’s been a while since I wrote my last article. Since then, many things happened in the middle. Above all, I’m expecting my first baby, and as you could suppose (or not) these time has been revolutionary at any scale. I had the crazy idea to take a new challenge in my career and I changed job. A great way to improve your skills and to learn from the seniors could be to take it to the next level. That’s how I got an opportunity and I took it.

So here are my new list (that I’m still learning about) and I hope you like it.

1. Be confident. Believe me. Although you might be a confident person in the past, it seems that your body decided for you now so probably you’ll be through a lot of change. Don’t let this to lead you. Focus on what you need to do and keep pushing yourself as always to be better. This means that even though you’ll have some doubts and fears about everything (which is absolutely normal), don’t let this to defined you. Remember who you are (said Mufasa) and become a new version of yourself, like a combo meal.

2. Keep it together. There will be a lot of tears, more than I can even admit. If your code doesn’t compile, you cry. If you suddenly forget how a method works, you cry. If you don’t find where the bug is, you cry more. Scientists call it hormones, but I call it the unexpected. They will be with you for nine months and even after. They are part of you now. However, being sensitive is not always bad, actually makes us more empathetic to others and encourage our creativity. These are nice qualities to bring to the whole team.

3. Breath. There will be moments when you will have to deal with tough personalities (as always) at work and you could feel not supported, not understood. Prove yourself to be better but only because you want to improve your work. The rest will need to have the responsibility and the respect to accept the context that surrounds you now.

4. Keep learning. Read documentation, do some tutorials, take classes, code for fun but never stop learning. I know we are juniors. I know the more years of experienced you have, the more skills you will get. Take your time, not everyone learn the same way, do the best you can do.

5. Be honest. If you can’t do something, you can’t. It’s not the end of the world. It’s true that in the companies the reality of time is different. They will push you as much as they can to encourage you in different ways. But there will be times when things go as certain ways that we didn’t expect it. There are seniors who doesn’t estimate well and that doesn’t define them. The valuable thing is to be committed and to keep learning when things goes wrong.

6. Don’t be block for too long. This is something that we all deal with when we develop. We want to resolve things by our own and this is great, gives you the chance to challenge yourself and to work on your independence. In the best case, you will have as much time as you want to solve an issue and if you can’t, your team will help you anytime. Another scenery (the usual one), everything will be on fire so the faster we solve things, the better.

7. Velocity. The less junior you are, the more your team will push you to improve your skills. How fast you resolve things could be one thing to improve. Don’t get frustrated. There will be cases, when there is no time, your team works fast and fluent and you will be the tiny junior trying to make things nice but not enough. This could take years of experienced. Even the best developers of the world need to improve things. “Rome wasn't built in a day”, stay humble, don’t give up and keep motivating yourself.

8. Communicate. I keep saying that communication is the base of everything. Sometimes you make a lot of effort by your own, but you don’t show off about it. So people could decide to think that you don’t do enough. It’s not easy to trust, the whole team has the responsibility to connect each other and to show humanity. Many things could change if we could communicate better.

9. Find your strength. Biology and love is an amazing thing. I'll assure you that these two will guide you and will give you the strength you need to overcome any burnout. As soon as you feel passionate about something. May the force of your baby belly be with you.

DECLAIMER:
 This is not the constitution. Everyone could have their own personal list. It's a way to share my experience in order to inspire others to do so.

Happy coding! :)
 

How to be a junior developer and survive?

Cocot 💚 git reset —hard HEAD — Wed, 08 Jan 2020 20:07:05 +0000

It’s been a little bit more than a year since I’ve become a junior developer and I’ve made a funny list of tips I learnt during this journey.

1. Patience. I know you are in the moment you want to learn everything and more, but you need to be organized and make choices. What should I learn first and why?

2. Ask to the seniors. The best way to learn is meeting with those developers who are more experienced. Ask whenever you have some doubts, it’s perfectly fine to be wrong and to make mistakes, you will learn from those mistakes so don’t be ashamed for that.

3. Respect. There would be moments when you will have to prove yourself to be a better person. In the best case you will have a great guidance from your Team and a great Project Manager, but also there would be cases where you would have to deal with some tough personalities. This is the time to find out the best version of you. Think about it in this way: what if you could have done better? Be critical of your work, even though you see that the rest is not.

4. Compete only with yourself. You will meet a lot of developers, and probably they would be more experienced than you. Don’t try to be better to catch them up, try to be better for your own experience, otherwise you will feel frustrated because people learn in different ways and times.

5. Don’t give up. I won’t lie. You will be frustrated more times than you can imagined but the best thing is you will always have another opportunity to do it better.

6. Be humble. It’s great to be confident, but also it’s better if you understand that you are a human being who can make mistakes. Learn from them and accept when they happen. Make sure to let this know to your team.

7. Be a good team partner. You will spend a lot of time with this people so it would be much better if you have a great time with them at the same time. Talk to them, connect whenever you need, offer help whenever you can.

8. Communicate. Communication is the base of everything, if you can’t communicate what you need your team won’t know what you need or how to help you. This is something that you will have to learn day by day .

DECLAIMER:
This is not the constitution. Everyone could have their own personal list. It's a way to share my experience in order to inspire others to do so.
Finally, the cover image is my cat, be careful if you look at it really closely it can take your soul, ha ha.

Happy coding! :)