Explore >> Select a destination
|
You are here 
|
codereview.chromium.org | ||
| | | | |
arveknudsen.com
|
|
| | | | | Chromium/Google Chrome is my hands-down favourite browser for developing Web sites in, owing toits incredibly sleek developer tools. I feel right at home in its JavaScript console, for evaluating JavaScript interactively or to inspect logs from arunning JavaScript application. However, the latter scenario is somewhat let down by the console's limited search functionality. At the time of writing, the console only lets you search for plain text on a line-by-line basis. If I want to search for regular expressions, which I tend todo, maybe spanning multiple lines, I'll have to paste the console contents into a text editor (Sublime, anyone?) and search in there. | |
| | | | |
darekkay.com
|
|
| | | | | How to inspect JavaScript DOM tree modifications. | |
| | | | |
www.trickster.dev
|
|
| | | | | Code level discussion of web scraping, gray hat automation, growth hacking and bounty hunting | |
| | | | |
www.blog.montgomerie.net
|
|
| | | By all means, learn enough programming to put together a prototype and have a better perspective on hiring and managing engineers. Just don't mistake a foothold in the world of coding for true engineering expertise.Buzz Andersen, commenting on Jeff Atwood's Please Don't Learn to CodeThis "Don't Learn to Code" vs. "Everyone Should Learn to Code" meme fascinates me. I pretty much agree with everything Buzz says. | ||
