Taulbee Survey depicts female computer science bachelor's degrees to be ~12% in 2010-2011
Bachelor's earned by women relative to other STEM fields. (Note decline unique to CS)
Black computer science professors near 0.25% *
// paste in your console | |
speechSynthesis.onvoiceschanged = function() { | |
var msg = new SpeechSynthesisUtterance(); | |
msg.voice = this.getVoices().filter(v => v.name == 'Cellos')[0]; | |
msg.text = Object.keys(window).join(' '); | |
this.speak(msg); | |
}; |
## | |
## Ferris | |
## | |
$the_cow = <<EOC; | |
$thoughts _ /\\ _ | |
$thoughts _ | \\ / \\ / | _ | |
$thoughts | `\\ | \\/ \\/ |_/` | | |
$thoughts _____| |______ | |
$thoughts | / | |
_____| /______ /| |
Taulbee Survey depicts female computer science bachelor's degrees to be ~12% in 2010-2011
Bachelor's earned by women relative to other STEM fields. (Note decline unique to CS)
Black computer science professors near 0.25% *
1st November, 2012
Luckily we have got a beta access to Travis CI pro which allows you to build your private repos on github. I did some research for my work and we have decided to replace our Jenkins to Travis CI pro. I leave some notes here.
We have bunch of private repositories, mainly Ruby (rails and gems), on github that we want to continuously test. We currently maintain two CI servers: Buildbot for legacy project and Jenkins for recent projects. On this research, I simply ignored the legacy one and evaluated Travis CI pro as an alternative for Jenkins.
ul | |
- for keyword in keywords | |
li | |
a rel='item' href=url("/#{keyword.id}", false) = keyword.name | |
nav | |
ul | |
- if keywords.next_page | |
li | |
a rel='next' href=url("/?page=#{keywords.next_page}", false) Next Page |
source :rubygems | |
gem 'webmachine' | |
gem 'rack' |
class LintTest < ActiveSupport::TestCase | |
include ActiveModel::Lint::Tests | |
class Model | |
# model.to_model | |
include ActiveModel::Conversion | |
# Implements Model.model_name | |
extend ActiveModel::Naming |
With Rails 3.0 released a few weeks ago I've migrated a few apps and I'm constantly finding useful new improvements. One such improvement is the ability to log anything in the same way that Rails internally logs ActiveRecord and ActionView. By default Rails 3 logs look slightly spiffier than those produced by Rails 2.3: (notice the second line has been cleaned up)
Started GET "/" for 127.0.0.1 at Mon Sep 06 01:07:11 -0400 2010
Processing by HomeController#index as HTML
User Load (0.2ms) SELECT `users`.* FROM `users` WHERE (`users`.`id` = 3) LIMIT 1
CACHE (0.0ms) SELECT `users`.* FROM `users` WHERE (`users`.`id` = 3) LIMIT 1
Rendered layouts/_nav.html.erb (363.4ms)
In response to all the responses to: | |
http://twitter.com/rtomayko/status/1155906157 | |
You should never do this in a source file included with your library, | |
app, or tests: | |
require 'rubygems' | |
The system I use to manage my $LOAD_PATH is not your library/app/tests |