Comments by "Vitaly L" (@vitalyl1327) on "Software Engineering Careers Are Too Unstable" video.
-
13
-
6
-
2
-
1
-
1
-
1
-
@ 1) Able to solve engineering problems of any complexity efficiently. If problem can be solved at all, a competent engineer will find the solution in a reasonable time.
2) Must be able to understand and explain solutions, not just "it works, I copy-pasted it from somewhere and tested it". The implication - must not have any gaps in knowledge, including all the underlying fundamental knowledge.
3) Sort of obvious, but must use the right tool for the job. Must not be swayed by immaterial things like familiarity of a tool, as a competent developer must be able to learn any new tool in no time.
4) Related to the previous point, must always be data-driven. Solutions must be based on objective measurable criteria rather than beliefs, familiarity, popularity, etc.
5) Must be able to be productive in a team of equals, without disrupting their work and without losing productivity on impedance mismatch with the other developers.
These are the basic requirements, there are few more, but even these would cut off the vast majority.
1
-
@ A competent developer must conform to at least the following:
1) Must be able to solve engineering problems of any complexity efficiently. If problem can be solved at all, a competent engineer will find the solution in a reasonable time.
2) Must be able to understand and explain solutions, not just "it works, I copy-pasted it from somewhere and tested it". The implication - must not have any gaps in knowledge, including all the underlying fundamental knowledge.
3) Sort of obvious, but must use the right tool for the job. Must not be swayed by immaterial things like familiarity of a tool, as a competent developer must be able to learn any new tool in no time.
4) Related to the previous point, must always be data-driven. Solutions must be based on objective measurable criteria rather than beliefs, familiarity, popularity, etc.
5) Must be able to be productive in a team of equals, without disrupting their work and without losing productivity on impedance mismatch with the other developers.
1
-
@ youtube keeps deleting my answer. I'll try again:
1) Able to solve engineering problems of any complexity efficiently. If problem can be solved at all, a competent engineer will find the solution in a reasonable time.
2) Must be able to understand and explain solutions, not just "it works, I copy-pasted it from somewhere and tested it". The implication - must not have any gaps in knowledge, including all the underlying fundamental knowledge.
3) Sort of obvious, but must use the right tool for the job. Must not be swayed by immaterial things like familiarity of a tool, as a competent developer must be able to learn any new tool in no time.
4) Related to the previous point, must always be data-driven. Solutions must be based on objective measurable criteria rather than beliefs, familiarity, popularity, etc.
5) Must be able to be productive in a team of equals, without disrupting their work and without losing productivity on impedance mismatch with the other developers.
1
-
@drwhitewash youtube is very annoying, it keep deleting my answer
1) Able to solve engineering problems of any complexity efficiently. If problem can be solved at all, a competent engineer will find the solution in a reasonable time.
2) Must be able to understand and explain solutions, not just "it works, I copy-pasted it from somewhere and tested it". The implication - must not have any gaps in knowledge, including all the underlying fundamental knowledge.
3) Sort of obvious, but must use the right tool for the job. Must not be swayed by immaterial things like familiarity of a tool, as a competent developer must be able to learn any new tool in no time.
4) Related to the previous point, must always be data-driven. Solutions must be based on objective measurable criteria rather than beliefs, familiarity, popularity, etc.
5) Must be able to be productive in a team of equals, without disrupting their work and without losing productivity on impedance mismatch with the other developers.
1
-
1
-
@ I'll try to write it one more time:
1) Able to solve engineering problems of any complexity efficiently. If problem can be solved at all, a competent engineer will find the solution in a reasonable time.
2) Must be able to understand and explain solutions, not just "it works, I copy-pasted it from somewhere and tested it". The implication - must not have any gaps in knowledge, including all the underlying fundamental knowledge.
3) Sort of obvious, but must use the right tool for the job. Must not be swayed by immaterial things like familiarity of a tool, as a competent developer must be able to learn any new tool in no time.
4) Related to the previous point, must always be data-driven. Solutions must be based on objective measurable criteria rather than beliefs, familiarity, popularity, etc.
5) Must be able to be productive in a team of equals, without disrupting their work and without losing productivity on impedance mismatch with the other developers.
1