Interesting take on things! I have found that reading papers is less useful than I would like. They tend to use overly complex language and have lots of missing information. YMMV. The idea of...
Interesting take on things! I have found that reading papers is less useful than I would like. They tend to use overly complex language and have lots of missing information. YMMV.
The idea of doing a screen recording is interesting! I never thought to do that exactly. I wholeheartedly agree with this statement:
When debugging a problem, adding functionality only for the purpose debugging is often well worth the cost.
I've found myself writing a lot of specialized debugging tools lately. In particular, I'll have my app log some data, then write another app to parse and display that data in a way that highlights issues. It's enormously useful!
I don't know if it will help, but you might like The Morning Paper, a blog that provides useful summaries of CS papers that the blog author found interesting.
I don't know if it will help, but you might like The Morning Paper, a blog that provides useful summaries of CS papers that the blog author found interesting.
Interesting take on things! I have found that reading papers is less useful than I would like. They tend to use overly complex language and have lots of missing information. YMMV.
The idea of doing a screen recording is interesting! I never thought to do that exactly. I wholeheartedly agree with this statement:
I've found myself writing a lot of specialized debugging tools lately. In particular, I'll have my app log some data, then write another app to parse and display that data in a way that highlights issues. It's enormously useful!
I don't know if it will help, but you might like The Morning Paper, a blog that provides useful summaries of CS papers that the blog author found interesting.
Thanks! Looks pretty neat!