Mind you, it's not like they're saying that "by-products" are a bad thing in any way. Or that the effort to make them is any less appreciable. It's about reaching a goal rather than making an exercise of style.
If, at the end of everything, you end up saying: "This codebase is majestic, but... what does the app actually do?" You know you've failed to provide value.
Blue collars hardly have any decision making chances, but there are also developers that just have to do what they're told. They don't get to see the overall picture, and won't see the value they're providing. Like bricklayers.
But fortunately not everything is black or white. The boundaries are blurred, especially for us developers, so we can at least question what we're doing. In fact, it's actually a valuable step for personal and professional growth.
So, strive to reach for the value, even if you don't take the final decisions.
For the last one, it's more or less the same thing. It's a tweet, so the context is a bit lacking, but I think the author meant that applying best practices just for the sake of it is meaningless.
Or maybe just ask him: it's a public tweet after all.
All in all, I think your post is a missed chance to ask for clarifications. You jumped to a lot of conclusions. If you deem those folks a little professional, you can ask them what made them think what they wrote, and spark a healthy debate. 👍
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.
Yes, I think you are.
Mind you, it's not like they're saying that "by-products" are a bad thing in any way. Or that the effort to make them is any less appreciable. It's about reaching a goal rather than making an exercise of style.
If, at the end of everything, you end up saying: "This codebase is majestic, but... what does the app actually do?" You know you've failed to provide value.
Blue collars hardly have any decision making chances, but there are also developers that just have to do what they're told. They don't get to see the overall picture, and won't see the value they're providing. Like bricklayers.
But fortunately not everything is black or white. The boundaries are blurred, especially for us developers, so we can at least question what we're doing. In fact, it's actually a valuable step for personal and professional growth.
So, strive to reach for the value, even if you don't take the final decisions.
For the last one, it's more or less the same thing. It's a tweet, so the context is a bit lacking, but I think the author meant that applying best practices just for the sake of it is meaningless.
Or maybe just ask him: it's a public tweet after all.
All in all, I think your post is a missed chance to ask for clarifications. You jumped to a lot of conclusions. If you deem those folks a little professional, you can ask them what made them think what they wrote, and spark a healthy debate. 👍