3 ms·

The problem is how you define a junior developer. A guy with 30 years of experience that has only exposure to imperative programming, and never really learned

The problem is how you define a junior developer. A guy with 30 years of experience that has only exposure to imperative programming, and never really learned OOP, networking, functional programming (it's not new: lisp, scheme, haskell, etc. have been around for decades), never really learned about operating systems, never really cared about automation, testing... unless you work on implementing software at a low level, which is very rare these days... guess what, that guy has a lot to learn from a fresher engineer, or engineers that actually cared about learning.

kozikow 10y ago
My point was not against new technologies. It was against religiously applying them everywhere without reasonable judgement. Since you brought up functional programming, it actually fits the same framework. In that case P includes problems with a "pure" domain (e.g. compilers) or problems that require lots of multi-threading. It does not work well for problems that are fundamentally state-full or sequential. It also does not work in "messy" domains - e.g. data mungling.
- partycoder 10y ago
  Reasonable judgment is fine. But reasonable judgment can be applied to everything, including who is better suited for making decisions about technological adoption. Someone who is biased towards "getting job done" and seeing technology adoption as a mere distraction, is simply too biased to be of any help during decision making. When evaluating technology adoption, you need to see the pros and cons (including adoption costs), and evaluate things seriously.
reinar 10y ago
lol what I think it's junior ones who lack understanding of how is OS and networks are operating, as they don't needed most of the time in more popular industries (mobile development, web, etc). source: by the chance I conducted few interviews for software engineers and devops in web industry - and instead of fizzbuzz I started with asking what's the difference between TCP and UDP. Results will surprise you (also too many people want to exploit current hiring system by just cramming algorithms).

kozikow 10y ago

My point was not against new technologies. It was against religiously applying them everywhere without reasonable judgement. Since you brought up functional programming, it actually fits the same framework. In that case P includes problems with a "pure" domain (e.g. compilers) or problems that require lots of multi-threading. It does not work well for problems that are fundamentally state-full or sequential. It also does not work in "messy" domains - e.g. data mungling.

partycoder 10y ago
Reasonable judgment is fine. But reasonable judgment can be applied to everything, including who is better suited for making decisions about technological adoption. Someone who is biased towards "getting job done" and seeing technology adoption as a mere distraction, is simply too biased to be of any help during decision making. When evaluating technology adoption, you need to see the pros and cons (including adoption costs), and evaluate things seriously.

reinar 10y ago

lol what I think it's junior ones who lack understanding of how is OS and networks are operating, as they don't needed most of the time in more popular industries (mobile development, web, etc). source: by the chance I conducted few interviews for software engineers and devops in web industry - and instead of fizzbuzz I started with asking what's the difference between TCP and UDP. Results will surprise you (also too many people want to exploit current hiring system by just cramming algorithms).