3 ms·
I've seen a number of things that relate to this: 1. a printer troubleshooting site where the only question is "What brand/model of printer do you have?" It su
by karmakaze 5y ago
I've seen a number of things that relate to this:
1. a printer troubleshooting site where the only question is "What brand/model of printer do you have?" It suggests the most common problem, and most often it's the rignt answer.
2. Sorbet is a static type checker for Ruby that will make suggestions for typo's similar to your example. It also has an autocorrect option, but use with care because sometimes it will choose the closest but completely unrelated name.
3. Error messages that are/have clickable links, which take you to a site that has entries from people who got this error and what they found caused and if known fixed it.
- gamerDude 5y agoWoah. #3 just blew my mind. What if we had a package for every language that linked the error to the top stack overflow thread or equivalent.
- vuciv1 5y agoI wanted to make this for myself in my terminal. It would read error output, search in a database I have, and then output how I fixed that error last time I received it. I am not quite sure how to intercept and inject terminal output though
- kubanczyk 5y agoI prefer we had generic search engines for the raw textual error messages. This reduces the fragility and vendor lock-in (like SO). Which is exactly the current situatuon.
- melvinroest 5y agoI prefer having both. Perhaps there's some opt-in/opt-out flag that allows you to not make clickable links. But having a database with most common errors sorted by programming experience in that particular language might be quite useful. I wouldn't be surprised if it would allow a programmer -- being a beginner in a new language -- quickly find his/her mistake most of the time.