5 ms·

Your work doesn't depend on operating systems, databases, network communications and data structures? I can go on.

busterarm 6y ago
Not as much as it depends on human communications, organization, self-management, etc. Most technical challenges in my experience end up being reduced to word problems. All of the stuff you mentioned is probably 10% of it. You can be bad at the 10% if you're great at the 90%.
- tmotwu 6y ago
  Formalizing word problems and effectively transforming it to a program is inherently a complexity theory exercise.
- stevofolife 6y ago
  Word problem? That's not a technical challenge. That has to do with writing and communications, which are ubiquitous to all types of work. I think you're misunderstanding the premise here.
  - busterarm 6y ago
    I think you're mistaking work for being puzzle-solving. Work is always about people. If it's not about people, it's probably research, which is different from work.
    - stevofolife 6y ago
      Work is a function of people and problem solving. A balance between the two provides an effective and productive environment for producing good work. I wouldn't praise or idolize the notion that work is always about people.
    - username90 6y ago
      Someone needs to solve the technical puzzles, software engineers are people who can do that, being good at managing things is a plus but it isn't what defines the role. There are plenty of roles at companies for people who can manage everything else but not technical things, like product manager or people manager.
- minkzilla 6y ago
  Well good thing you learned to read, write, be disciplined and be organized in school along side CS.
  - busterarm 6y ago
    I didn't learn CS in school. I'm self taught. I'm 20 years into my career. That doesn't mean I don't respect a CS education, but I don't think this kind of testing is a good measure of potential.
    - tmotwu 6y ago
      But you did teach yourself the fundamentals to do your job. So this isn't a good argument against the practicalities of applying CS knowledge in software engineering? Everything you've listed - communication, organization, and self-management - are qualities of a strong student. These are skills from college that last. I don't know a single successful student who got by on his own or did so without being extremely disciplined. Outside of the homework/exam grind, college was far more social than work life ever was.
- kmkemp 6y ago
  The reduction of a technical problem to a word problem is the application of years of accumulated knowledge, including, in many cases, Computer Science concepts.
- 0x008 6y ago
  My experience is that if everybody who took part in the development of software at enterprises would have studied CS, 90% of the word problems would be gone. Most problems arise from the fact that actors underestimate or not understand the complexities that lie in software systems.
oscargrouch 6y ago
Lets just pretend that this is working to filter good candidates.. even then good software have a lot to do with team work. Its better to have people who are experts in things that the product need to be good at, but also less expert in a certain field but that will do other parts of the product, than you have to manage the group work properly.. My point being, you need people with a myriad of skill sets, and some of them don't even have to do with expert knowledge needed in some areas. Also you might have an expert in storage for instance that do poorly in certain tests giving he never needed to work with those kind of algorithms. So in the end the company ends with the same type, the same kind of person, and how can you make a great team that needs people with different skills doing distinct stuff, if you optimized your hiring to filter for one particular type?

Not as much as it depends on human communications, organization, self-management, etc. Most technical challenges in my experience end up being reduced to word problems. All of the stuff you mentioned is probably 10% of it. You can be bad at the 10% if you're great at the 90%.

tmotwu 6y ago
Formalizing word problems and effectively transforming it to a program is inherently a complexity theory exercise.
stevofolife 6y ago
Word problem? That's not a technical challenge. That has to do with writing and communications, which are ubiquitous to all types of work. I think you're misunderstanding the premise here.
- busterarm 6y ago
  I think you're mistaking work for being puzzle-solving. Work is always about people. If it's not about people, it's probably research, which is different from work.
  - stevofolife 6y ago
    Work is a function of people and problem solving. A balance between the two provides an effective and productive environment for producing good work. I wouldn't praise or idolize the notion that work is always about people.
  - username90 6y ago
    Someone needs to solve the technical puzzles, software engineers are people who can do that, being good at managing things is a plus but it isn't what defines the role. There are plenty of roles at companies for people who can manage everything else but not technical things, like product manager or people manager.
minkzilla 6y ago
Well good thing you learned to read, write, be disciplined and be organized in school along side CS.
- busterarm 6y ago
  I didn't learn CS in school. I'm self taught. I'm 20 years into my career. That doesn't mean I don't respect a CS education, but I don't think this kind of testing is a good measure of potential.
  - tmotwu 6y ago
    But you did teach yourself the fundamentals to do your job. So this isn't a good argument against the practicalities of applying CS knowledge in software engineering? Everything you've listed - communication, organization, and self-management - are qualities of a strong student. These are skills from college that last. I don't know a single successful student who got by on his own or did so without being extremely disciplined. Outside of the homework/exam grind, college was far more social than work life ever was.
kmkemp 6y ago
The reduction of a technical problem to a word problem is the application of years of accumulated knowledge, including, in many cases, Computer Science concepts.
0x008 6y ago
My experience is that if everybody who took part in the development of software at enterprises would have studied CS, 90% of the word problems would be gone. Most problems arise from the fact that actors underestimate or not understand the complexities that lie in software systems.

oscargrouch 6y ago

Lets just pretend that this is working to filter good candidates.. even then good software have a lot to do with team work. Its better to have people who are experts in things that the product need to be good at, but also less expert in a certain field but that will do other parts of the product, than you have to manage the group work properly.. My point being, you need people with a myriad of skill sets, and some of them don't even have to do with expert knowledge needed in some areas. Also you might have an expert in storage for instance that do poorly in certain tests giving he never needed to work with those kind of algorithms. So in the end the company ends with the same type, the same kind of person, and how can you make a great team that needs people with different skills doing distinct stuff, if you optimized your hiring to filter for one particular type?