Great article, concise and hitting the points that really make a difference. I would stress that the first step in communication is to listen, observe and learn. Things work much smoother if developers can learn the business and then see how technology can improve the process.
I think we tend to get wrapped up too much in technology and think of systems as their implemented tech and not the problems they solve. We talk of a system with a React frontend, backed by Node microservices with MySQL persistence, not as sales prospect process that is needed to keep the revenue flowing to sustain the business.
Some of the best systems that I "developed" were one's that I never wrote. Often what is needed is a function that is already present, just not done where or how it was expected. Changing expectations or slight modifications to meet expectations are what's needed, not more code.
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.
Great article, concise and hitting the points that really make a difference. I would stress that the first step in communication is to listen, observe and learn. Things work much smoother if developers can learn the business and then see how technology can improve the process.
I think we tend to get wrapped up too much in technology and think of systems as their implemented tech and not the problems they solve. We talk of a system with a React frontend, backed by Node microservices with MySQL persistence, not as sales prospect process that is needed to keep the revenue flowing to sustain the business.
Some of the best systems that I "developed" were one's that I never wrote. Often what is needed is a function that is already present, just not done where or how it was expected. Changing expectations or slight modifications to meet expectations are what's needed, not more code.