Your Power Tools for Version Control and Code Review

Simplify your development workflow
Ship higher quality code
Understand your code's history
Integrate with FogBugz and other tools
No limits on repositories

140byt.es is a tweet-sized, fork-to-play, community-curated collection of JavaScript

### How to play

1. Go to the master gist page, and click the button.
2. Modify all the files to according to the rules in the gist.
3. Save your entry and tweet it up!

Keep in mind that thanks to the awesome sensibilities of the GitHub team, gists are just repos. So feel free to clone yours and work locally for a more comfortable environment, and to allow commit messages.

see suggested repos (based on watcher relationships)

/* Checkbox Hack */

input[type=checkbox] {
position: absolute;
top: -9999px;
left: -9999px;
}
label {
-webkit-appearance: push-button;
-moz-appearance: button;
display: inline-block;
margin: 60px 0 10px 0;
cursor: pointer;
}

/* Default State */
div {
background: green;
width: 400px;
height: 100px;
line-height: 100px;
color: white;
text-align: center;
}

/* Toggled State */
input[type=checkbox]:checked ~ div {
background: red;
}

Basic
Domain Logic
Data Source
Object-Relational Behavior
Object-Relational Structure
Object-Relational Metadata
Web Presentation
Distribution patterns
Concurrency
Session State
Practical PHP Patterns: Visitor

Do want! @kuvos's text editor script for @jsprf. http://t.co/OOgWREE

A Git Repo for storing the Xcode Keyboard Shortcuts as well as being able to keep track of forks

Huffduffer extension for Google Chrome

Grapevine is a simple message aggregator. It works by feeding in messages from various sources such as Twitter and grouping them into topics. Then it will periodically send out a notification with the most popular topic. Once topics are sent out in a notification, they won't be sent out again for a specified time window.

Currently Grapevine supports:

Loading messages from Twitter.
Integration with GitHub for filtering trackbacks.
Sending notifications to Twitter accounts.

A better coding convention for lists and object literals in JavaScript

HTML emails are a great way to keep clients posted on the latest updates related to your business or product, but they’re a bit tricky. CSS support in email clients is inconsistent. As a result, we must resort to ancient techniques, such as using tables, and inline CSS. Today, I’m going to walk you through the process of creating simple HTML emails.
Intro: HTML Email
As a freelance web developer, coding HTML emails are one of the more challenging tasks that I have to deal with. Fortunately, when one of my first clients asked me to design and code his email newsletter, he was patient enough to let me go through the long and frustrating process of figuring it all out. You might not be so lucky, so prepare yourself with this tutorial.

This is a list (a very subjective list) of scripts that perform tasks you may wish were actual iTunes Menu commands. Just copy and paste 'em to your AppleScript Editor and save to your iTunes Scripts folder...then add a Shortcut.

Optionally, you can click the mini-AppleScript Editor icon link beneath each snippet to open the script in AppleScript Editor on your computer. These links use URL Protocol Messaging to safely and securely send the contents of the script to your AppleScript Editor application.

12 Second Fade/Stop and Next Track
Artist to Album Artist
Choose Playlist
Current Track to (Select Playlist)
De-Shuffle All Playlists
Delete Selected Playlists
Eject iPods
Erase Bookmark
Jump to Playlist
Just Played These
Open iTunes Scripts folder
Play Random Playlist
Play Random Track of Random Playlist
Play Selected Track Once
Remove (Album Version)
Remove SOME TEXT From Names
Reset Start and Stop Times
Search Results to New Playlist
Selected Tracks to Current Playlist
Set Skipped Count/Skipped Date
Show Get Info Window of a Track's File
Skip Ahead n Seconds
Skip and Pretend We Played This
Super Shuffle
Toggle Checkmarks of Selected
Toggle Mute
View Current Playlist
Virgin Again

Selection Routines
Single Selected Track
Get a reference to a single selected track.
Each Selected Track
Get a list of references to each selected track.
Select Playing or Single Selected Track
Get a reference to the current track if player is paused or playing; otherwise, check for a single selected track.
Selected Tracks or Entire Playlist
Repeat with a reference to each of the selected tracks; or, if no tracks are selected, repeat with a reference for each track in the currently selected playlist.
Handlers
Is iTunes Running
Returns true or false.
Choose/Restore Encoder
Change encoders on-the-fly and restore Preferences-set encoder afterwards.
Nuke Track 1
Delete a track from iTunes entirely.
Nuke Track 2
Delete a track from iTunes entirely and delete its file immediately (and unrecoverably).
Nuke Track 3
Delete a track from iTunes entirely and move its file to the Trash.
text_to_list(), list_to_text(), replace_chars()
Frequently helpful text and list handlers.
Basic Idle Routine
Checks for new current track. Save as Stay-Open Application.
List Manually Managed iPods
Sets two corresponding lists to manually managed iPod names and source references
Export Artwork as File to Folder
Supply an iTunes track reference, path to folder as text, name of new file as text, and scale in pixels. NOTE: probably will not work with iTunes 9/Snow Leopard. See the slightly updated version below.
Export Artwork as File to Folder II
Supply an iTunes track reference, path to folder as text, name of new file as text, and scale in pixels.This version seems to work better in Snow Leopard with iTunes 9
Rating to Text Stars
Pass the value of a track’s rating property. Regretably, the chevrons in the Unicode do not translate into UPM so you’ll have to copy-and-paste this off the page.

am taking a test soon and I would like to know useful commands on Linux for a programmer. Some examples are string, strace, top, free, df, mount, cat, head, tail, whoami, touch. What are others?

I am a complete novice. Those are all the commands I know along with groupadd, useradd, chmod, chown, ls, rm, mkdir and echo. That is all I know.

GNU cflow analyzes a collection of C source files and prints a graph, charting control flow within the program.

GNU cflow is able to produce both direct and inverted flowgraphs for C sources. Optionally a cross-reference listing can be generated. Two output formats are implemented: POSIX and GNU (extended).

Input files can optionally be preprocessed before analyzing.

The package also provides Emacs major mode for examining the produced flowcharts in Emacs.

A sample of a direct flowchart is available online.

technoweenie (rick)

* Gists
* Message
* Follow Unfollow

GitHub Role
Captain Ruby

Name
rick

Email
technoweenie@gmail.com

Website/Blog
http://techno-weenie.net

Company
Github

Location
portland

Member Since
Jan 13, 2008

* 92 public repos
* 1,246 followers

Following 11 coders and watching 200 repositories view all →

*
*
*
*
*
*
*
*
*
*
*

What is Git?
Git is a directory content tracker (i.e. it lets you keep track of the contacts of directories as they change over time). It was developed originally by Linus Torvalds (creator of Linux) in 2005.

What do we use it for?
Until a couple of weeks ago, we were using Subversion for keeping track of our source code. We’re now about a third of the way into converting everything to git (a surprisingly straightforward process, thanks to the git-svn utility).

So git is our source code manager of preference these days. Whenever someone makes a change to one of our applications or dependencies, they check the change into the central repository via git, and the other developers can then merge those changes into their own repositories. Git makes much of this insanely easy, compared to Subversion.

Why do we like it?
Branching and merging are the features we originally fell in love with. Whenever we start development on a new feature, we create a “branch” of the code. Work done in this branch will not affect the “main” branch (called “trunk” in subversion, and “master” in git), so it is a good way to make significant changes without affecting what our users actually see.

Branching and merging in Subversion are painful. If you’ve never used it, you don’t know what I mean. If you have, you do. Branching and merging in git, though, are wonderfully, blissfully straightforward. For those two reasons alone git is worth the switch for us, though there are lots of other, more advanced, features we like about git, too (git-stash, git-bisect, etc.)

How can people learn more?
The learning curve is pretty hefty, especially if you start out thinking of it like “subversion-but-with-some-differences”. The best way to learn git is to forget everything you know about more traditional SCM’s and read through the various tutorials online. We’ve got a Backpack page where we’ve been accumulating various Git resources.

If you operate a website that features lots of code examples, you know how important it is to spend some quality time styling the <pre> element. When left unstyled, wild <pre> tags will mangle your preformatted content and destroy your site’s layout. Different browsers treat the <pre> tag quite differently, varying greatly in their default handling of font-sizing, scrollbar-rendering, and word-wrapping. Indeed, getting your preformatted code to look consistent, usable, and stylish across browsers is no easy task, but it certainly can be done. In this article, I’ll show you everything you need to create perfect <pre> tags.