4 ms·
Often times, you know a proposal doesn't work, and yet you don't have chops to implement a better a solution. In that case, keeping quiet is the best solution;
by raincom 2y ago
Often times, you know a proposal doesn't work, and yet you don't have chops to implement a better a solution. In that case, keeping quiet is the best solution; otherwise, you just make enemies.
- avg_dev 2y agoone of the things i like about working at very small companies is that i don't have to immediately have a solution to everything. i can file an issue and/or mention a bug or issue that i see or foresee when we talk. i can then let it marinate until it either becomes necessary to act on it or i think of a solution and have time to work on it, whichever comes first. i often think of software as a series of problems. i don't have to worry about solutions initially. when we have polished off solutions to all of the truly immediately important problems - within some reasonable/useful level of engineering tolerances - the software can be thought of as done, for a time. just my opinion.
- omoikane 2y agoDocumenting why a proposal wouldn't work might be valuable even if a better solution is not immediately available, then at least people are aware of potential problems and perhaps temporarily workaround them. Depending on what's the worst outcome of "wouldn't work", keeping silent might be worse than making enemies.