they're really bad. i interviewed people that couldn't fill in a simple fizzbuzz after defining a function body and return type for them. they last because they

they're really bad. i interviewed people that couldn't fill in a simple fizzbuzz after defining a function body and return type for them. they last because they can last, a lot of these jobs really just require codemonkeys. I have seen if states literally hundreds of words long made by these kinds of people. that said i feel you. tbh, i have managed to impress anyone i worked with. most were people i met at hackathons, people that wanted to bootstrap their startups or general referals. on the other hand I failed most interviews i took(with a few noteworthy exceptions) It once took me until after the interview to figure out that the guy just wanted to find out whether i understand how variable scopes work. A lot of interview questions are questionable at best, and most code challenges are even worse. they're exactly how universities teach programming. The only problem is that universities suck at teaching programming. I know a lot of really awesome people that went to university because they thought knowing the topic they study was a good idea, but it turned out to be the opposite. But one lady once asked me is there a special command to find out where traffic goes? I said route. Is there any special flag you would use she continued. But what she wanted was to hear route -n. I'm pretty sure in those kinds of interviews they think i'm an idiot