getting-a-gig VS guides

Guide to your first job in tech - a great read from @cassidoo. Check out Cassidy's newsletter and other resources like Getting a Gig too.

Make sure to do some practice ones, either with friends or on some sites (some options here: https://github.com/cassidoo/getting-a-gig )

- Centralized Resources like this one from my months of web-scraping https://github.com/cassidoo/getting-a-gig

https://github.com/cassidoo/getting-a-gig#your-cover-letter

Lo que yo suelo hacer es tener un template a mano donde voy cambiando el nombre de la empresa, a menos que esté aplicando a mi ✨dream job✨, en ese caso me puedo esmerar un poco más. El motivo por el cual hago esto es porque cuando estoy en búsqueda activa, mando unos 10 CVs por día (no lo recomiendo, es agotador) y no tengo el tiempo ni las ganas para dedicarme a hace eso

Write a more complicated test later. Or refactor the test later. When you're in the moment, you want a test that works. Avoid hard coded values in completed tests, but use them when you're making sure your test doesn't break the very time you write it. A failing test is the starting point of the last decision you made, not the final product. Even if the imaginary people who are going to make fun of your code and call you stupid (ignore this if you're not relating, but if you are read this or watch it) are looking at your public github repo, they're not going to your test suites first. That would be insane. So you can be clunky at first.