I interned at NASA, working on statistical modeling and machine learning projects. Now I'm at Ferguson Enterprise, working on applying UX principles to internal tooling!
it also makes the code unreadable and you start to look less and less appealing as a potential dev candidate for X company.
facts! Thanks for the advice!
This made me think of this tweet:
getify
@getify
How to answer a trick/gotcha JS question in a job interview:
JS is often thought of us as being quirky and tricky, and thus has a bad reputation. Hence your question. However, it can be written to cleanly/clearly communicate ideas without such antics. I would re-write this code.
22:47 PM - 14 Aug 2018
35161
getify
@getify
Instead of reinforcing bad practices, I'd love to discuss how I use my knowledge of JS to communicate effectively with future readers of my code.
------
If I heard this from a candidate, I'd hire on the spot.
I remember when you sent that tweet out!
facts! Thanks for the advice!
This made me think of this tweet:
That's an amazing answer, tbh. So much bad advice out there. Discerning it is key.