Thomas Junghans tjunghans

General

Unit tests: Review unit tests first. Unit tests are a fantastic way to grasp how code is meant to be used by others and to learn what the expected behavior is. Are there any test gaps that should be there?
Method arguments" Make sure arguments to methods make sense and are validated. Mentally test boundary conditions and edge cases.
Null References" (Yah yah, we know. Use F# and this goes away. We get it already.) Null references are a bitch and it’s worth looking out for them specifically.
Conventions Consistency" Make sure naming, formatting, etc. follow our conventions and are consistent. I like a codebase that’s fairly consistent so you know what to expect.
Disposables: Make sure disposable things are disposed. Look for usages of resources that should be disposed but are not.
Security: There is a whole threat and mitigation review process that falls under this bucket. In simple terms, ask yourself how this code could be exploited. The [STRIDE Threat Mo

This text now lives at https://github.com/MarcDiethelm/contributing/blob/master/README.md. I turned it into a Github repo so you can, you know, contribute to it by making pull requests.

Contributing

If you want to contribute to a project and make it better, your help is very welcome. Contributing is also a great way to learn more about social coding on Github, new technologies and and their ecosystems and how to make constructive, helpful bug reports, feature requests and the noblest of all contributions: a good, clean pull request.

alternatively use: http://geoff.greer.fm/lscolors/

LSCOLORS

The value of this variable describes what color to use for which attribute when colors are enabled with CLICOLOR. This string is a concatenation of pairs of the format fb, where f is the foreground color and b is the background color.

The color designators are as follows:

a black

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

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.

	#301 Redirects for .htaccess

	#Redirect a single page:
	Redirect 301 /pagename.php http://www.domain.com/pagename.html

	#Redirect an entire site:
	Redirect 301 / http://www.domain.com/

	#Redirect an entire site to a sub folder
	Redirect 301 / http://www.domain.com/subfolder/

	<?php

	/*
	参考自：
	http://darklaunch.com/2010/09/01/http-status-codes-in-php-http-header-response-code-function
	http://snipplr.com/view/68099/
	*/

	function HTTPStatus($num) {
	$http = array(

	<?php

	// ...
	protected function getMockedPDO()
	{
	$query = $this->getMock('\PDOStatement');
	$query->method('execute')->willReturn(true);

	$db = $this->getMockBuilder('\PDO')
	->disableOriginalConstructor()

	<!DOCTYPE html>
	<html>
	<head>
	<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/jasmine/2.3.4/jasmine.min.css">
	<script src="http://cdnjs.cloudflare.com/ajax/libs/jasmine/2.3.4/jasmine.min.js"></script>
	<script src="http://cdnjs.cloudflare.com/ajax/libs/jasmine/2.3.4/jasmine-html.min.js"></script>
	<script src="http://cdnjs.cloudflare.com/ajax/libs/jasmine/2.3.4/boot.min.js"></script>
	<meta charset="utf-8">
	<meta name="viewport" content="width=device-width">
	<title>Promise.inSequence</title>

	////Constants //////////////////////////////////////////////

	function jsonOk (body) {
	var mockResponse = new window.Response(JSON.stringify(body), { //the fetch API returns a resolved window Response object
	status: 200,
	headers: {
	'Content-type': 'application/json'
	}
	});