show me your Github profile or your learning blog, you need to build a personal brand as a developer... :)
I should not posted comment in such post, telling them what should do, and get minus points... haha
Another programming interview I blew
71–80 of 85 posts
Re: Another programming interview I blew
#72Earlier quoted context omitted.
I doubt looking into mouths is a big deal. I don't see how that's any worse or better than being a surgeon. The problem is so much of dentistry is cosmetics which is a horribly shallow thing to be dedicating your life to.
What's so shallow about giving back self-confidence to kids and adults who didn't win perfect teeth at the genetic lottery?
It's a cultural perception. Japanese girls are happy with snaggle-teeth because in Japanese culture these are cute. Some even want fake crooked teeth.
https://www.japantoday.com/category/lifestyle/view/why-japan...
So don't get too hung up about perfect teeth.
Re: Another programming interview I blew
#73I've taken a lot of shitty interviews. I have also interviewed many devs. Testing a candidate in one hour is really hard. CV's can be very deceiving. What I look for is folks who are good coders and good communicators. I don't care about culture fit. Our team is diverse from 50 year Olds, 19 year Olds, males females, black, white, brown etc. Having a github profile with interesting projects is a boon. Even better if…
Some candidates just dive into code and then get stuck. They confuse them selves.
The best candidates are the ones who ask lots of clarifications at the start, they break down the problem into little pieces without writing a single line of code. They emulate a computer and trace the steps in an abstract manner. They think like "to solve Z, I need A then do B and C and D." They then slowly write code for the little steps.
My thoughts exactly
Re: Another programming interview I blew
#74If you're looking to vent, then I'll say, "That sucks, dude. Keep in there, it's all a numbers game." Tomorrow will be a better day. But, I'm going to be bold. I'm going to out on the limb and suggest that: maybe it's not being asked "RANDOM shite," but maybe your attitude. Generally speaking, I've had to do three to five or so interviews to get an offer. Depending on the market and the timing, I've had far, far wors…
> C#/SQL are a dime-a-dozen. You're competing in a market that is dying [...] Get yourself up to speed with NodeJS/Vue/React
I think you are out of touch there. Maybe all your friends are web UI devs, but web front-end development is a minority of programming jobs - smaller than writing CRUD apps that interface via SQL, and smaller than writing the desktop applications that create all the data that the web dev guy gets to doll up and push out.
I wholly agree with your advice on constructive interviewing and seeking feedback.
Re: Another programming interview I blew
#75Feel for you. I've been in very similar positions. Just today I had an interview with a very well known company and the interviewer sounded like he couldnt really care. Ive 20+ years pro experience and over that time, if you are a good problem solver, you end up getting a whole bunch of experience in different things. Problem i've found is everyone is looking for specialists that fit into a narrow box. I really don't, and i'd guess most people with any length of experience don't either. Perhaps startups are your best bet?
Re: Another programming interview I blew
#76Bullshit interviews are part of the system now. The only way to beat it is with interview-er accountability. In interviews today, the expectation is that the candidate should be perfect, do this, that, don't forget to do this. But the interviewer has no such requirement. The interviewer can reject you because "They had a bad day".....seriously, this is what companies say. Look at some answers here: https://www.quora.…
> The interviewer can reject you because "They had a bad day"
The only answer in your Quora link that has a lot of upvotes is by the author of CTCI and she is saying just the opposite, and instead of blaming the interviewer she is putting all of the blame on the person being interviewed. I find this quite disturbing, and you are right there isn't accountability on the interviewer, here are the things the author of CTCI is saying:
> Maybe you came off as arrogant
> A number of different things could happen. But when someone asks this question -- why did I get rejected even after doing well -- the problem is nearly always in the second part: You didn't do well
> If you were interviewing with a big tech company, they have basically infinite programming spots. They don't reject someone because they found someone better; they just hire both.
> So despite what you think about your performance, you probably didn't show good algorithmic problem-solving skills
I'm all for self-introspection to assist in self-improvement but her persistence in ignoring the fact that interviewers are fallible is troubling, she is the go-to resource for probably most interviewees and interviewers and I don't like that she assumes that the thing that went wrong is "almost always" the fault of the interviewee. It's some grade-A BS.
Re: Another programming interview I blew
#77Earlier quoted context omitted.
I believe this is why Starfighters was being made; because the system is broken. Too bad it didn't work out(not the CTF or stock game; the idea). I wish there was a site where, in my own time, I can do some tasks to prove that I can actually do what I've been doing for the past 15 years. As in, "here I reversed a string and this is proof. now can we please discuss something relevant to the role or am I being hired to…
But then the interviewer trots out the old adage "but we're not testing your ability to reverse strings. I want to see how you approach solving problems." And yet, a wrong answer is an almost guaranteed no hire. I can't tell if these people believe their own bullshit or if I'm being lied to my face.
> I want to see how you approach solving problems.
Which correlates nicely to "You didn't solve it the way I would have, so you're obviously wrong."
Re: Another programming interview I blew
#78If you're looking to vent, then I'll say, "That sucks, dude. Keep in there, it's all a numbers game." Tomorrow will be a better day. But, I'm going to be bold. I'm going to out on the limb and suggest that: maybe it's not being asked "RANDOM shite," but maybe your attitude. Generally speaking, I've had to do three to five or so interviews to get an offer. Depending on the market and the timing, I've had far, far wors…
> People who have 10 years (or claim 10 years) C#/SQL are a dime-a-dozen. You're competing in a market that is dying, the same way Java developers are dying: a smaller and smaller group of employers who are stuck on the tech. I think your in a bubble. 90%+ of the jobs around here are c#, java and php. Only one local company seems to be doing anything with node (and not something node is suited for), in fact, I haven'…
I do not deny certainly that 90% of the job offers are C#, Java and PHP. Recruiters are always trying to get me to look at various offers, and I agree; however, they're pretty much all large, established companies that are desperate to hire people because the word on the street is that their projects have spun out of control, are behind schedule, etc. At least, that's the running M.O. in this city.
I also agree that NodeJS is jumping the shark. But, again, if your at where he/she is, there is where the more up-to-date Microsoft companies are hiring. NodeJS is the new hotness (five years late) in this town.
Personally, I'm already working on exiting Node. Having used it hard core for high-performance APIs, I've found all the sharp edges and failure modes. Node really falls down when you have to get fine-grain control of flow control, such as processing files and large data. Ironically, I'm seeing a resurgence of Ruby.
I've been working on tooling myself back in to Ruby (did Ruby for five years), Elixir, and Docker/Flynn/etc.
Re: Another programming interview I blew
#79If you're looking to vent, then I'll say, "That sucks, dude. Keep in there, it's all a numbers game." Tomorrow will be a better day. But, I'm going to be bold. I'm going to out on the limb and suggest that: maybe it's not being asked "RANDOM shite," but maybe your attitude. Generally speaking, I've had to do three to five or so interviews to get an offer. Depending on the market and the timing, I've had far, far wors…
> People who have 10 years (or claim 10 years) C#/SQL are a dime-a-dozen. You're competing in a market that is dying, the same way Java developers are dying: a smaller and smaller group of employers who are stuck on the tech. I think your in a bubble. 90%+ of the jobs around here are c#, java and php. Only one local company seems to be doing anything with node (and not something node is suited for), in fact, I haven'…
I do not deny certainly that 90% of the job offers are C#, Java and PHP. Recruiters are always trying to get me to look at various offers, and I agree; however, they're pretty much all large, established companies that are desperate to hire people because the word on the street is that their projects have spun out of control, are behind schedule, etc. At least, that's the running M.O. in this city.
I also agree that NodeJS is jumping the shark. But, again, if your at where he/she is, there is where the more up-to-date Microsoft companies are hiring. NodeJS is the new hotness (five years late) in this town.
Personally, I'm already working on exiting Node. Having used it hard core for high-performance APIs, I've found all the sharp edges and failure modes. Node really falls down when you have to get fine-grain control of flow control, such as processing files and large data. Ironically, I'm seeing a resurgence of Ruby.
I've been working on tooling myself back in to Ruby (did Ruby for five years), Elixir, and Docker/Flynn/etc.
Re: Another programming interview I blew
#80Bullshit interviews are part of the system now. The only way to beat it is with interview-er accountability. In interviews today, the expectation is that the candidate should be perfect, do this, that, don't forget to do this. But the interviewer has no such requirement. The interviewer can reject you because "They had a bad day".....seriously, this is what companies say. Look at some answers here: https://www.quora.…
I believe this is why Starfighters was being made; because the system is broken. Too bad it didn't work out(not the CTF or stock game; the idea). I wish there was a site where, in my own time, I can do some tasks to prove that I can actually do what I've been doing for the past 15 years. As in, "here I reversed a string and this is proof. now can we please discuss something relevant to the role or am I being hired to…
HackerRank