| ▲ | ctoth an hour ago | |
> but withhold from others, even though the code change itself is likely small. Prediction: programming is going to change massively not only because the cost of creating code will go down, but because people are so tired of this sort of gatekeeping "we know better" from programmers. | ||
| ▲ | ljm 7 minutes ago | parent | next [-] | |
This describes a product with no vision or purpose. People have to take 'no' for an answer sometimes, even if they don't accept it. You can't really 'gatekeep' your own product. | ||
| ▲ | eterm an hour ago | parent | prev | next [-] | |
What you're describing as "gatekeeping" is actually Product Ownership and should be applauded, because the alternative is a product owner who abdicates responsibility to the customer. | ||
| ▲ | datadrivenangel an hour ago | parent | prev | next [-] | |
And the software without gatekeepers will be regarded as confusing and complicated or buggy. The work to go from software to usable software system is vast. | ||
| ▲ | mjr00 an hour ago | parent | prev [-] | |
> Prediction: programming is going to change massively not only because the cost of creating code will go down, but because people are so tired of this sort of gatekeeping "we know better" from programmers. I assume the "gatekeeping" decision to not implement a feature request is coming from someone responsible for the product, not from a developer. | ||