@Macro_T
#JSDev. Coffee :3 @taverasmisael anywhere else.
Love coding for work and personal projects; occasionally play the piano; can take a cup of coffee at any hour of the day, is that a superpower?
Nothing here yet.
No blogs yet.
The last one is comes very handy when you're working in a project with a backend in PHP, which you have no idea, but you can read and understand simple logic errors and help your teammate to deliver faster, so you can also ship the frontend understanding the underlayings of what are you doing
Before switching to mac (only one month from now) I used windows my entire life. I tried a lot of terminals and emulators and settle with PowerShell, but then I met Hyper . In the end, I was using Hyper and the Ubuntu bash with some plugins and zsh in the Linux terminal, it was insane, funny, beautiful, powerful... and laggy. Sometimes the terminal just didn't close, so I rolled back to my PowerShell and it felt right.
It is a very descriptive picture of what to face once you are on the Hackathon, and it is what I was looking for to get a better idea of the ambience. The format for the one I'll attend next week requires to have a team and develop a solution, focused on national issues. The team has to register before, and its only 2-4 persons (we are 3 in my case). I want to win, make something fresh and smash the hackathon with my teammate but also I want to share, meet extraordinary people, see what are they building and how do they see the near future. Is the first national event like this, and I'm pretty excited. So thank you very much for giving me this extraordinary piece of advice, I know it will really help me there. Now, I have to prepare myself for what is coming ;)
I prefer to use the event.preventDefault() most of the time because is more descriptive, and sometimes you have to show your code to your project manager or someone who doesn't understand these abbreviations that are so common between us. In the end, most of the code go through Uglify, and the length of the variable name is not an inconvenient in production. Same goes for the index vs i . Let's say I just want to use the index as key for my React components, I use it as i , but if I have to do any other operation with it, I will go for a more descriptive name. Remember that you read as much code as you write, and it has to be as friendly for you as it is for the machine ;)
I prefer Jest with Enzyme over any other. The main reason for this choice is that I had never done a test to any of my applications because it seemed complicated to me install a bunch of dependencies to set a test environment, and only then write my first test. Then CRA was released, and it came with Jest build in, and I decided to give it a try; I've never looked back since then. It comes completely configured and easy to write tests with it, no need for assertions libraries and such things Jest has all this covered. Maybe then you will want to have extra help for testing your components and the DOM interaction; there's where Enzyme comes to play. It makes easier to assert, manipulate, and traverse your React Components' output . But as I said before, I haven't made tests before Jest. I tried mocha a couple of times but I haven't been able to get my head around to it. Therefore my judgment may be biased for the sake of the simplicity offered by Jest