A developer should definitely know his business area. Not as deep as an SME, of course.
If you just "solve problems through code" you miss out on the incredible value that you can provide.
You should definitely be able to answer a lot of questions, just not all the questions.
Also, CEO should not know all the bits and bytes of their business. This is not their job.
Regarding your second point, you have a very problematic sentence there: "They are not your typical help-desk or infrastructure IT worker."
This was never true and it is even less true these days.
You think that tracking down a semicolon is hard? Try doing it across systems, networks and applications. Both of them do it.
You can write the same article you just wrote about and just replace the profession.
I'm sorry but this is exactly why you feel the need to write this piece. Compared to architects for example, you're just a "typical developer".
I do not wish to take anything from your article and I know this was not your intent. 🙏
25+ years as a Software Developer. I'm passionate about process improvement using technology. Let's all work smarter not harder and do more with less.
MY THOUGHTS ARE MY OWN
"A developer should definitely know his business area. Not as deep as an SME, of course.
If you just "solve problems through code" you miss out on the incredible value that you can provide."
We agree for the most part. My point was your team should have a SME and it should not be the developer. You might disagree but I also believe that a developer should not be evaluated on knowing the business area.
The developer should not be evaluated on knowing the business area.
If knowing it turns him into a more valuable developer through his code then and only then should there be a distinction.
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.
I see your point. I disagree slightly.
A developer should definitely know his business area. Not as deep as an SME, of course.
If you just "solve problems through code" you miss out on the incredible value that you can provide.
You should definitely be able to answer a lot of questions, just not all the questions.
Also, CEO should not know all the bits and bytes of their business. This is not their job.
Regarding your second point, you have a very problematic sentence there: "They are not your typical help-desk or infrastructure IT worker."
This was never true and it is even less true these days.
You think that tracking down a semicolon is hard? Try doing it across systems, networks and applications. Both of them do it.
You can write the same article you just wrote about and just replace the profession.
I'm sorry but this is exactly why you feel the need to write this piece. Compared to architects for example, you're just a "typical developer".
I do not wish to take anything from your article and I know this was not your intent. 🙏
somehow your reply doesn't make sense to me. it reads like it's incomplete and unclear.
What makes it unclear and incomplete?
My reply was taking out 2 and a bit points out and commenting on them.
It is not meant to be a complete article in and of itself.
"A developer should definitely know his business area. Not as deep as an SME, of course.
If you just "solve problems through code" you miss out on the incredible value that you can provide."
We agree for the most part. My point was your team should have a SME and it should not be the developer. You might disagree but I also believe that a developer should not be evaluated on knowing the business area.
Agree completely actually.
The developer should not be evaluated on knowing the business area.
If knowing it turns him into a more valuable developer through his code then and only then should there be a distinction.