In this document I am using Sass's SCSS syntax. You can choose to use the indented syntax in sass, if you prefer it, it has no functional differences from the SCSS syntax.
For Less, I'm using the JavaScript version because this is what they suggest on the website. The ruby version may be different.
| <cfhttp url="http://blog.bittersweetryan.com/2011/02/post-some-cf-code-on-github-and-win.html" /> | |
| <cfset possibleWinners = {} /> | |
| <cfset commentsHtmlArr = rematch("<dt class='comment-author.*?</dd>", rereplace(cfhttp.filecontent, '[\r\n]+', '', 'all')) /> | |
| <cfset gistURLRegex = "https://gist\.github\.com/[0-9]+" /> | |
| <cfloop from="1" to="#arrayLen(commentsHtmlArr)#" index="arrIndex"> | |
| <cfset currHtml = commentsHtmlArr[arrIndex] /> | |
| <cfif refindNoCase(gistURLRegex, currHtml)> | |
| <cfset gistURL = reMatchNoCase(gistURLRegex, currHtml) /> | |
| <cfset gistURL = gistURL[1] /> |
#Lessons From A JavaScript Code Review
I was recently asked to review some code for a new JavaScript application and thought I might share some of the feedback I provided as it includes a mention of JavaScript fundamentals that are always useful to bear in mind. Code reviews are possibly the single biggest thing you can do to improve the overall quality of your solutions and if you're not actively taking advantage of them, you're possibly missing out on bugs you haven't noticed being found or suggestions for improvements that could make your code better.
##Challenges & Solutions
Code reviews go hand-in-hand with maintaining strong coding standards. That said, standards don't usually prevent logical errors or misunderstandings about the quirks of a programming language. Even the most experienced developers can make these kinds of mistakes and code reviews can greatly assist with catching them.
Often the most challenging part of code reviews is actually finding an experienced developer you trust to complete
| <!--- Read data from two datasource tables. ---> | |
| <cfquery | |
| name="iae1" datasource="escolar_db13"> | |
| select * from v_rc_iae_pr1 | |
| </cfquery> | |
| <cfscript> | |
| //Use an absolute path for the files. ---> | |
| theDir=GetDirectoryFromPath(GetCurrentTemplatePath()); | |
| theFile=theDir & "exportData.xls"; | |
| //Create two empty ColdFusion spreadsheet objects. ---> |
| #!/usr/bin/env bash | |
| function git_edit_files | |
| { | |
| # Init | |
| local type=$1 | |
| # Commands | |
| local ls_files='git ls-files' | |
| local diff='git diff --cached --name-only' | |
| # Messages |
| # Path to your oh-my-zsh configuration. | |
| ZSH=$HOME/.oh-my-zsh | |
| # Set name of the theme to load. | |
| # Look in ~/.oh-my-zsh/themes/ | |
| # Optionally, if you set this to "random", it'll load a random theme each | |
| # time that oh-my-zsh is loaded. | |
| ZSH_THEME="gnzh" | |
| # Texteditor and zshconfig aliases |
| [user] | |
| name = Julien Bisconti | |
| email = ****** | |
| [core] | |
| excludesfile = ~/.gitignore | |
| pager = diff-so-fancy | less --tabs=1,5 -R | |
| editor = /usr/bin/vim | |
| [alias] | |
| wow = log --all --graph --decorate --oneline --simplify-by-decoration |
| # problem: when presenting, I want to obscure | |
| # my prompt to act like it's at root of file system | |
| # and be very basic with no git info, etc. | |
| # solution: this theme lets you set a ENV to the path | |
| # of your presentation, which will help remove unneeded prompt | |
| # features while in that path | |
| # oh-my-zsh theme for presenting demos | |
| # based off the default rubbyrussell theme |
| #! /usr/bin/env ruby | |
| # NOTE: Requires Ruby 2.1 or greater. | |
| # This script can be used to parse and dump the information from | |
| # the 'html/contact_info.htm' file in a Facebook user data ZIP download. | |
| # | |
| # It prints all cell phone call + SMS message + MMS records, plus a summary of each. | |
| # | |
| # It also dumps all of the records into CSV files inside a 'CSV' folder, that is created |
