DEV Community

Discussion on: Why do developers have the toughest interviews in the world?

Collapse
 
gabek profile image
Gabe Kangas

Software doesn't exist in a vacuum. It runs on an operating system, that sits on hardware, that utilizes a network and each piece of the puzzle inserts variables that will impact the software you wrote.

The classic interview question "what happens when you type google.com in your browser?" I think is a fantastic question, and everybody should be able to answer it at some level.

Without understanding where and how your software runs then the only answer to "It's not working in prod" will be "well... it works on my machine".

Collapse
 
robencom profile image
robencom

You know, I was watching a video(youtube.com/watch?v=Wx3WlQLFa3w&t=...) about Security the other day, and one thing that really caught my attention was the speaker saying:
"thinking you can create a secure platform to host your application when you are not a security expert is like thinking you can represent yourself in court when you are not a lawyer."

Security should be one of the biggest concerns for any developer, but yet we are all "wannabe security experts" as developers.

OS? Do we even dare to claim that we understand how the OS handle things?

Network? Who is a CISCO certified engineer? I know few, but they aren't developers.

WE might know a thing or two or three. Some of us are more hardcore, they really dive into one of those topics. But you guys cannot hold it against other developers who don't know how the DNS works or so on, because you didn't know as well at some point, you only learned about it when you NEEDED to, and you probably forgot about it by now. And there is a TON of things you don't know about OS or Networks or or or... Maybe, there's a ton of things you don't even know about that one language that you think you already mastered.

Developers want to believe they know everything. Let's face it, we don't have the brainpower to memorize it all. You learn a new thing today, you forget something you learned 100 days ago. Knowledge comes and goes, your essence as a problem solver evolves with time. That's the real you. That's your identity as a human and as a developer.