Okay, yes, I agree with that completely!
> If you want to produce good results and don't care about making yourself or (more likely) your boss rich, you should absolutely adopt this philosophy.
"Think long term" and "always learn things" and "aim for high quality" seem like platitudes, not a methodology or a serious philosophy. What, specifically is the problem being solved here? Where is the evidence that what is said here has actually worked? What does this document say that will actually help me achieve high quality? What is it suggesting we engineers do that we aren't already doing?
I've never known an engineer in my life that didn't already think he or she was solving the longer term problems that others couldn't see or appreciate. One of the biggest problems we have in software is over-engineering.
Interesting argument that if I don't buy into this "manifesto", then I must not care about good outcomes or personal gain. I don't buy that, I don't believe Longflow provides me with the formula for either good outcomes or achieving personal gain or satisfaction. It claims to, but it delivers something else.
Purely from an engineering perspective, I don't believe that this Longflow essay offers me any practical steps to achieving high quality, and I do believe that it contains some very bad advice; avoiding regular communication with management and avoiding budget discussions will both result in poor quality software and a failure to achieve either personal satisfaction or career growth as an engineer, in my experience.