rally25rs

using System;
using System.Collections;
using System.Collections.Generic;
using System.Collections.ObjectModel;
using System.Data.Entity;
using System.Linq;
using System.Linq.Expressions;

namespace Rally25rs.Gist.Data
{

mortezaadi

<?xml version="1.0" encoding="UTF-8"?>

<persistence xmlns="http://java.sun.com/xml/ns/persistence"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
   http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
	version="1.0">


	<!-- derby -->

HaNdTriX

/**
 * Convert an imageURL to a
 * base64 dataURL via canvas
 *
 * @param   {String}  url
 * @param   {Object}  options
 * @param   {String}  options.outputFormat [outputFormat='image/png']
 * @param   {Float}   options.quality [quality=1.0]
 * @return  {Promise}
 * @docs    https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement#Methods

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

joshbuchea

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example