/explore
|
You are here 
|
avelino.run | ||
| | | | |
current.workingdirectory.net
|
|
| | | | | Some thoughts based on my work as a movement technologist | |
| | | | |
www.camillescott.org
|
|
| | | | | [AI summary] A tutorial explains how to use the yep Python module and Google's perftools to profile C++ extensions called from Python. | |
| | | | |
www.softdevtube.com
|
|
| | | | | Programming history is filled with bugs that turned out to be features and limitations that pushed developers to make even more interesting products. We'll journey through code that was so 'bad' it was actually good. Along the way we'll look at the important role failure plays in learning. Then we'll tame our inner perfectionists and | |
| | | | |
whatibroke.com
|
|
| | | Hey everyone, Just a quick post on something useful I came across today. In JavaScript you can access the stack trace via console using the following command (ctrl + shift + j): console.trace() In Chrome, this will let you navigate to each relevant call by clicking the line number in the console window. I've found... | ||
