5 ms·
This is a really interesting peek into the developers mind. Right away I notice I google things differently than the author. I try and hit up phrases that match
by dev_dull 7y ago
This is a really interesting peek into the developers mind. Right away I notice I google things differently than the author. I try and hit up phrases that match a question (which is why I probably over index on stack overflow). The author seems to hit up ideas that remind me of something that might be the title of a blog post or something. Also, my search is definitely more full of stack trace keywords. Probably 80% stack trace keywords by weight.
- saagarjha 7y agoI almost never search for stack traces: I pick out class names or error codes and search for that instead. How's your success rate with finding useful information?
- Diederich 7y agoI've had a fair bit of luck searching on quickly chosen fragments of stack traces.
- aloknnikhil 7y agoStack traces have been great at fingerprinting the issue, especially to find something on a Github issues page. And the success rate is inversely proportional to how long you have spent working on a project using that dependency. The more time you've had, the more creative ways you find to screw it up.
- simplify 7y agoCompletely agree. If you're interested in giving insight into your own developer mind, I'm working on a social network to do just that[0]. The goal is to be the sweet spot between Twitter and a blog – short enough to jot down (as blogs take too much effort), and long enough to go beyond Twitter's character limit. And you get markdown! It's very barebones MVP at the moment, but you can expect more features very soon. Open to feedback! [0] https://devlog.at https://devlog.at