4 Things You Should Never Say In a Job Interview

4 Things You Should Never Say In a Job Interview We’re all familiar with that sinking feeling of dread that sometimes hits after you’ve shaken your last hand and hit the lobby button in the elevator- is it possible you said something that contributed to the warm interview fizzling like an off-brand sparkler? You thought you have answered everything perfectly, even some of those hardest interview questions. The editors at MedReps.com have compiled a list of â€Å"must-avoid† statements  for anyone about to embark on an important interview.1. â€Å"I’m a fast learner.†This goes alongside â€Å"I’m enthusiastic† or â€Å"I’m a people person† as a hollow expression that, on reflection, doesn’t make you look like a better candidate. Instead of saying you’re a fast learner, have an anecdote or two ready to illustrate a time when you learned something quickly- bonus points if you learned something easily relatable to the job for which you’re interviewing .Your demeanor in the interview should tell the interviewer that you’ve got enthusiasm and people skills, too. If someone in HR can’t sense it, a client won’t either.2. â€Å"I’m a perfectionist.†This one was probably original and compelling in early 1993, a younger and simpler time, but by now everyone knows it’s what you say when you want to offer up a socially acceptable humblebrag. If you think about it a little more, what you’re actually saying is that you need everything to be a certain way- and if something goes off-plan, you won’t have the skills to adapt and recover.3. â€Å"No, I don’t have any questions.†Do you want to have no questions because you don’t care about the company, haven’t thought about your role there, or because you think the specifics are immaterial? Or did you want the interviewer to think you don’t even have enough professional experience to know you’re supp osed to have questions? Bottom line- have questions.4. â€Å"What does your company do?†Ugh. Why would you interview without doing even a cursory Googling?! It’s even better if you have a recent (positive) news article to bring up- show your interviewer you have a brain, the ability to think critically, and those aforementioned people skills and enthusiasm.It’s what a perfectionist would do.

How and Why to Comment in Your PHP Code

How and Why to Comment in Your PHP Code A comment in PHP code is a line that is not read as part of the program. Its only purpose is to be read by someone who is editing the code. So why use comments? To let others know what youre doing. If you are working with a group of people or plan on anyone else ever using your script, the comments tell the other programmers what you were doing in each step. This makes it much easier for them to work with and to edit your code if needed.To remind yourself what you did. Although you may just be writing a quick script for yourself and dont see the need for comments, go ahead and add them in anyway. Most programmers have experienced coming back to edit their own work a year or two later and having to figure out what they did. Comments can remind you of your thoughts when you wrote the code. There are several ways to add a comment in PHP code. The first is by using // to comment out a line. This one-line comment style only comments to the end of the line or the current code block, whichever comes first. Here is an example: ?php echo hello; //this is a comment echo there; ? If you have a single line comment, another option is to use a # sign. Here is an example of this method: ?php echo hello; #this is a comment echo there; ? If you have a longer, multi-line comment, the best way to comment is with /* and  */ before and after a lengthy comment. You can contain several lines of commenting inside a block. Here is an example: ?php echo hello; /* Using this method you can create a larger block of text and it will all be commented out */ echo there; ? Dont Mix Comments Although you can nest comments within comments in PHP, do so carefully. Not all of them nest equally well. PHP supports C, C and Unix shell-style comments. C style comments end at the first */ they encounter, so dont nest C style comments.   If you are working with PHP and HTML, be aware that HTML comments mean nothing to the PHP parser. They wont work as intended and are likely to execute some function. So, stay away from:   !Comment