3 ms·
I'm not convinced. While I've been on the receiving end of such suggestions - and yes, it can be frustrating - a lot of times the question itself reveals proble
by kstrauser 8y ago
I'm not convinced. While I've been on the receiving end of such suggestions - and yes, it can be frustrating - a lot of times the question itself reveals problems with the intended solution.
Examples:
"Hey, our home-grown queueing service slows down when we have more than 1,000 insertions per second. How do I make its SQLite backend more scalable?" "Um, perhaps that's not a good solution to your problem." "Would you please just answer the question?"
"Our service can only process one request at a time, so we're thinking of switching from Python to Rust." "Would it make more sense to make your current system multi-threaded?" "Are you gonna help us rewrite this or not?"
Sometimes lack of experience makes suggestions seem like bazookas when they're really cork guns. If you've never used a client-server database, that might seem like a scary upgrade from SQLite. In reality, it's very straightforward and common. If someone recommends a bazooka to you, first make sure that it's actually overkill and not the standard upgrade path from your current situation.
Further reading: https://en.wikipedia.org/wiki/XY_problem https://en.wikipedia.org/wiki/XY_problem
- Doxin 8y agoWhile you have a point, some people seem to think that everything is an XY problem. Sometimes I just want to ask a question and not shoot down a hundred answers because they don't understand the actual restraints I've got.