This gist is part of a blog post. Check it out at:
http://jasonrudolph.com/blog/2011/08/09/programming-achievements-how-to-level-up-as-a-developer
This gist is part of a blog post. Check it out at:
http://jasonrudolph.com/blog/2011/08/09/programming-achievements-how-to-level-up-as-a-developer
#!/usr/bin/env ruby | |
if ARGV[0].nil? || ARGV[0].match(/-h/) | |
puts "Usage : #{$0} github_username dash_sqlite_db char_appended_to_keyword [no_comments]" | |
exit | |
end | |
require 'net/http' | |
require 'open-uri' | |
#require 'awesome_print' |
Let's have some command-line fun with curl, [jq][1], and the [new GitHub Search API][2].
Today we're looking for:
By @foldleft.bsky.social, see also Unfollow everyone on bsky.app.
https://twitter.com/YOUR_USER_NAME/following
// Unfollow everyone on twitter.com, by Jamie Mason (https://twitter.com/fold_left)
As a new developer some potential employers are going to review your Github profile as part of the interview process. This doc covers some tips that should help you make a good impression. What this doc won't do is polish a turd.
Think of your experiences reviewing a Gem or other JS library on Github. Where do you look first? The README of course. What makes for a frustrating repo? One that doesn't:
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.