The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
(Have the applicant persuade you that he is not an AI)
Can I punch the interviewer in the mouth?
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
I JUST ABSOLUTELY LOVE IT!!! THE BEST LANGUAGE I'VE EVER WORKED IN! My favorites:
It's a duck-typed and scripted language, so of course the code just works. After all, there's no compilation step to tell you how you screwed up. I love languages like this because you can't screw up!
The use of this and bind is also one of the most intuitive, common sense, easiest things in the world to understand!
And it is SO COOL to be able to determine variable scope by keywords like var and let. Thank god we have moved away from variables scoped by braces!
Because it allows people who have no idea what they are doing to bodge some crap together that hides its total failures until they have time to bugger off and leave it to some other poor sod to sort out later. And call themselves "expert consultants".
It's harder to do that in a strongly typed, compiled language ... and why the heck we put up with it and HTML in the modern world, I have no idea.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
Yeah, one must think differently before appreciate the positive aspects of it. It's not an OO language, it is async (event driven) where process level or micro-service load balancing is one's friend. But when one try to bend it to a monolithic, OO and threading view, one find difficulties. It sucks indeed ...
The freedom it gives to a programmer can be a curse or a bless, it really depends on how it is used ... E.g., some of our libs are generated by programs written in strong typed languages ...
My problem with JS is having too many "solutions" available to pick from, in the form of libraries/frameworks. Too many choices can be a curse.
I've been coding as a profession for well over 20 years now (C/C++/C#, front-end, back-end, MFC, WinForms, etc), and while I've managed to put together what pretty much amounts to basic static HTML-based sites in decades past, I've just recently started to try to learn how to go about web development "the right way".