start new:
tmux
start new with session name:
tmux new -s myname
// Using the Jenkins Groovy Post build plugin to execute the following after every build | |
// https://wiki.jenkins-ci.org/display/JENKINS/Groovy+Postbuild+Plugin | |
// It would be nice not to have to specify these here... the repo name should be available within the hudson | |
// api somehow, but I didn't know how to get it. The access token should maybe be saved in a config file, and | |
// read in at runtime? | |
GITHUB_REPO_NAME = 'myusername/myreponame' | |
GITHUB_ACCESS_TOKEN = 'my_github_api_v3_access_token' |
import time | |
def highlight(element): | |
"""Highlights (blinks) a Selenium Webdriver element""" | |
driver = element._parent | |
def apply_style(s): | |
driver.execute_script("arguments[0].setAttribute('style', arguments[1]);", | |
element, s) | |
original_style = element.get_attribute('style') | |
apply_style("background: yellow; border: 2px solid red;") |
The list would not be updated for now. Don't write comments.
The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Wed, 21 Sep 2022 till Thu, 21 Sep 2023.
Because of GitHub search limitations, only 1000 first users according to amount of followers are included. If you are not in the list you don't have enough followers. See raw data and source code. Algorithm in pseudocode:
githubUsers
The following is excerpted from Software Testing Techniques, 2d. Ed. by Boris Beizer.
First Law: The Pesticide Paradox -- Every method you use to prevent or find bugs leaves a residue of subtler bugs against which those methods are ineffectual.
That's no too bad, you say, because at least the software gets better and better. Not quite!
Second Law: The Complexity Barrier -- Software complexity (and therefore that of bugs) grows to the limits of our ability to manage that complexity.
...
[ | |
{ | |
"category":"Administrative", | |
"category_id":"10100100", | |
"type":"Region", | |
"subcategory":"Consolidated City" | |
}, | |
{ | |
"category":"Administrative", | |
"category_id":"10100101", |
Sete Atitudes para Hackear a Indústria de Software | |
By Klaus Wuestefeld | |
1) Torne-se excelente. | |
Seja realmente bom em alguma coisa. Não fique só choramingando ou | |
querendo progredir às custas dos outros. Não pense q pq vc sentou 4 | |
anos numa faculdade ouvindo um professor falar sobre software q vc | |
sabe alguma coisa. Jogador de futebol não aprende a jogar bola tendo |