1. 2

    It’s kind of sad that developers have such a romance with code that we get tunnel vision as to what code should look like aesthetically, how a pattern should be implemented & what framework to use, all the while having only a naive understanding of the actual problem they are trying to solve. It seems like this is reinforced by the idea that a developer is “done” once the CI system is passing and a PR has been merged. I would like to say that the real problems are defined outside of code and therefore the only measures of a developer finishing their job are also defined outside of code. I’m always glad to see articles like this, which say things like

    The job of a software developer isn’t to write code. It’s to create solutions that create value