3 ms·
> it’s a poor craftsman who blames his tools It's an even worse craftsman who persists in using the wrong tool. If the tool does a poor job or requires more ma
by notacoward 9y ago
> it’s a poor craftsman who blames his tools
It's an even worse craftsman who persists in using the wrong tool. If the tool does a poor job or requires more maintenance than the work it saves - as would be the case if your suggestions were followed - then it should be abandoned in favor of another. Which is what we did. Solutions found, nothing defeatist about it, and I notice you didn't answer the question about whether you've actually tried to do this.
- ebbv 9y agoI have contributed to open source occasionally. It’s not a part of my job most of the time so it’s rare. But it’s also not relevant at all. As I tried to spell out the situation you describe is not unique at all. It’s the same thing every software dev encounters. I’m glad you found tools that work for you, but this exchange has been unpleasant so I’m done with you.
- notacoward 9y ago> It’s the same thing every software dev encounters No, it really isn't. "Upstream first" development such as Red Hat does is fundamentally different than developing in private, even if that includes throwing the occasional scrap back over the fence. If you think this exchange has been unpleasant, consider that casually dismissing others' experience rarely leads to any other outcome. Did you do your part to make it pleasant for anyone else?