Explore >> Select a destination
|
You are here 
|
steakenthusiast.github.io | ||
| | | | |
tomasvotruba.com
|
|
| | | | | Already over 120 people bought [the Rector book](/blog/rector-the-power-of-automated-refactoring-book-released) that we released just a month ago. The continuously growing interest in abstract syntax technology makes me very happy. It leads to more developers **who can write their own custom Rector rules to improve their specific projects**. That leads to more "how-to" questions in the Rector repository. I've decided to answer one of the frequent ones today. | |
| | | | |
www.trickster.dev
|
|
| | | | | Code level discussion of web scraping, gray hat automation, growth hacking and bounty hunting | |
| | | | |
ariya.io
|
|
| | | | | A common approach to analyze JavaScript source statically is to parse the source into an abstract syntax tree (AST) and then to traverse the AST. An alternative approach that might work in a few cases is to inspect each syntax node as it is constructed. | |
| | | | |
speakerdeck.com
|
|
| | | A talk I gave at PyCon 2012 about code generation and how Jinja2 works internally. | ||
