/tech/ - Tech


Mode: Reply

Max message length: 8192


Max file size: 80.00 MB

Max files: 5


(used to delete files and postings)


Remember to follow the rules

The Coding Interview Comrade 07/26/2020 (Sun) 17:34:10 No. 3641
What's up with the coding interview? You would think being a competent programmer would be enough to get a job but there's a whole industry out there specialized in preparing people for code interviews. It even has a Wikipedia page of its own. No other industry has a specific Wikipedia page for their job interviews. Why? What went wrong?
I once heard of an interview for an IT position that was intentionally very exhausting so that when the negotiation time came the interviewee would be exhausted and wouldn't ask for a high wage. I don't really have any experience with interviews, however i don't think that an interview in a small-medium company would be hard enough to require any special preparation. The fact that there exists so much stuff on programming interviews might be because there are a lot of jobs in that field, and that a lot of people without adequate education look for programming jobs, so the interviewer needs to know if the person actually knows what they need to know before they hire someone.
>>3641 >Why? What went wrong? Silicon Valley startup culture that leaked into normal tech companies. This doesn't exist in other technical fields (ex: mechanical/electrical engineering) because it would bee too complex to fit into a 45 minute interview. Took off in SV because the founders were all 23 year olds who didn't have experience in real software engineering so they just ask questions out of a coding competition or data structures/algorithms book instead. That and since a bunch of people without CS degrees are in the industry now they have to test the core CS knowledge that you would learn with a degree (DS/A). They want to hire self taught hipsters but also know they aren't pseuds. I personally don't think its a good strategy i would rather have someone do real work or show a project they made or something rather than solving algo problems on a whiteboard in 45 mins. You can imagine its the sort of process a nerdy white guy CS/math major from harvard would find interesting but anyone over 30 would probably just think is bullshit and a waste of time.
>>3651 >They want to hire self taught hipsters but also know they aren't pseuds I think there's a deeper underlying problem: Software "engineers" aren't actually engineers. Real engineers in other fields are certified similarly to lawyers, doctors, pilots, etc., complete with them (AND THEIR EMPLOYERS) being subject to legal liability for failure to meet standards of their field's accrediting body. Pretty much nothing like this exists for chodemonkeys, even college-edumacated "IT majors" and holders of "certifications" from Cisco, Microsoft, Oracle, etc. have no real assurance of even minimal competence: https://blog.codinghorror.com/why-cant-programmers-program/
>>4000 So your definition of an engineer is someone who received a specific certification and has "legal liabilities"? I guess Tesla wasn't a "real" engineer since he never received a degree or certification, he's obviously some electromonkey or something. Was Steve Wozniak also just some "electromonkey" and "chodemonkey" for designing the Apple I and Apple II without a degree, certification or being bound by legal liabilities?
>>4000 Also nice job citing a blog from 2007, before leetcode, topcoder, projecteuler, khanacademy, etc. etc. were a thing, before FAANG's corporate dominance and consolidation of the internet, before the 2007 financial crisis, before the first iPhone was released, your blog is prehistoric by the rapid pace of the changing IT world.
>>4009 >>4011 >Tesla Was from the early transitional period when all this started, during an era when safety and reliability standards were far lower, and it only became universal by the post-WWII era even in the US: https://en.wikipedia.org/wiki/Regulation_and_licensure_in_engineering#History >Wozniak Cobbled together a PC design on a shoestring from spare parts, even writing the entire BASIC on paper and typing it in all at once because he didn't have regular access to a workstation. Like all PCs of the era, it was a clumsy hackjob, but the fact it worked at all was more than enough to make it amazing for the time. That's not an acceptable standard for anything even vaguely resembling the level of maturity the IT sector should've had since the '90s at the latest, not to mention today. >the changing IT world Wow, yeah, Indian webdev mills churning out script kiddies that can't "program" in anything except JS, and deploying end-user software for joke "platforms" like Electron.
>>4025 If you're really that much smarter than Tesla and Wozniak combined, why are you wasting your talents shitposting here?
>>4000 In most places of the world, "their field's accrediting body" is the university. If you have a software engineer or computer engineer diploma, you are an engineer and can call yourself one. If you work for industries where it is necessary, you will be held for the same standards as other engineers. Ask anyone working in automotive, healthcare or similar fields.
>>3641 Engineers are naturally drawn towards over-engineered solutions. Just look at Silicon Valley startups. They even invent problems where there are none just so they can create an app.


no cookies?