DEV Community

Discussion on: On Technical Interviews

mohamed3on profile image
Mohamed Oun Author

Great response. But I think good programmers don't necessarily have to be great problem solvers. Some can turn requirements into well-written code very well, even if they don't have the ability to design a solution from scratch. I think that part of the job is not taken into consideration in interviews.
Also, 'passion' and 'excitement' is not a good metric for measuring quality IMO. There are a lot of great developers who only work with code in their daily job, and switch to something else entirely when they go home (Family, friends, hobbies, sports, etc).

codemouse92 profile image
Jason C. McDonald

I commented elsewhere, but I need to correct something you just said - programming is problem-solving by nature, whether it is building, rebuilding, debugging, or expanding.

You are correct that designing a solution from scratch isn't necessarily part of every job, but you need to understand that a complete inability to design from scratch (or, in the same vein, a complete inability to build on top of existing code) indicates a lack of the core skills that set mediocre programmers apart from excellent programmers.

In case you're wondering, this is coming from someone who trains programmers at all experience levels as his full time job. I've seen all sorts of programmers, and many different approaches, styles, and talents. There is a lot of diversity in programming, but among those that excel at this craft, there are common traits - problem-solving, communication, and a dedication to excellence (often misunderstood as "excitement"/"passion"). These ARE essential ingredients.