First of all, thank you for bring in this topic, I believe that what you said is mostly true.
Second, I believe that our reality should not work in this way, about the blurred differences.
The big problem with our profession is that is very young the first personal computer was introduced to the market 50 years ago. Compare this with medicine for example which has been around for thousands of years. The two terms, enlisted by you, have been grown organically. I think both of them are use inappropriately. Like software engineer, there is no reason for calling engineer to someone that can follow a tutorial and create an app or a module for a system. The reason for calling Software Engineer someone should be because they are practicing software engineer not because of the kind of work they do. I know people that can make apps in C++ and they don't care about SOLID, Refactoring, TDD and of course they are all the time wasting time using wrong approaches to solve problem.
I think that any programmer doing any kind of code for any purpose can be Software Engineer as long as he is doing it professionally, which means prepare themselves continuously. I am reading a book called Software Engineering at Google in the first chapter they define software engineer as a thing which is in 3 dimensions, regular programming is in 2 dimensions, you combine knowledge and skill and you get program. However, when you do software engineer you want to consider a third dimension which is time. Once you create system to scale to resist years to pass, you are doing software engineer.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
First of all, thank you for bring in this topic, I believe that what you said is mostly true.
Second, I believe that our reality should not work in this way, about the blurred differences.
The big problem with our profession is that is very young the first personal computer was introduced to the market 50 years ago. Compare this with medicine for example which has been around for thousands of years. The two terms, enlisted by you, have been grown organically. I think both of them are use inappropriately. Like software engineer, there is no reason for calling engineer to someone that can follow a tutorial and create an app or a module for a system. The reason for calling Software Engineer someone should be because they are practicing software engineer not because of the kind of work they do. I know people that can make apps in C++ and they don't care about SOLID, Refactoring, TDD and of course they are all the time wasting time using wrong approaches to solve problem.
I think that any programmer doing any kind of code for any purpose can be Software Engineer as long as he is doing it professionally, which means prepare themselves continuously. I am reading a book called Software Engineering at Google in the first chapter they define software engineer as a thing which is in 3 dimensions, regular programming is in 2 dimensions, you combine knowledge and skill and you get program. However, when you do software engineer you want to consider a third dimension which is time. Once you create system to scale to resist years to pass, you are doing software engineer.