I can relate to and sympathize with time constraints and convenience arguments, but I think it’s more accurate in both the landscaping and app examples to say it wouldn’t exist if you hadn’t _asked/paid_ for it.
And you could have made it and then you could have been proud of it. And at least some of time, that’s more valuable than an unspecified “product”. I’m more attached to things I made than things I bought.
No. We have one team at our company doing this. Management loves them, but no one in engineering trusts them and they literally just write MCPs that have no users and still experience daily incidents.
Harness Engineering is a marketing term. In reality it’s just the practice of leveraging what has always defined a good stable codebase: good docs and high test coverage.
And you could have made it and then you could have been proud of it. And at least some of time, that’s more valuable than an unspecified “product”. I’m more attached to things I made than things I bought.