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

hoatle

/**
 * Calulate the personal tax following Vietnamese laws
 *
 * Let's check out the spreadsheet in action: https://docs.google.com/spreadsheets/d/1ud_yzaPAIcAICNYO_istpGApJdGSUUNkvx3vEMLrf2c/edit?pref=2&pli=1#gid=0
 *
 * <=  5m - 5%
 * <= 10m - 10%
 * <= 18m - 15%
 * <= 32m - 20%
 * <= 52m - 25%

leonardofed

A curated list of AWS resources to prepare for the AWS Certifications

A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.

---

jamiehoward

Test Driven Laravel - Adam Wathan

@adamwathan

• Write the test, then write the code to satisfy that test.
• Write the complete minimum to satisfy the test
• If the class doesn't exist, only create the class.
• Always write the tests before beginning the code.
• Start by specifying the application functions.

Rich-Harris

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.

freekmurze

sudo add-apt-repository ppa:ondrej/php

sudo apt-get install php7.0

sudo apt-get install php7.0-gd

sudo apt-get install php7.0-mysql

sudo apt-get install php-memcached

martinda

// Jenkins Pipeline DSL to demonstrate git merge before build
node {
    String path = '/tmp/jenkins/upstream-repo'
    sh "rm -rf ${path}"
    ws(path) {
        sh 'git --version'
        sh 'git init'
        sh 'touch README.md; git add README.md; git commit -m "init"'
        sh 'git checkout -b pull-requests/1/from'
        sh 'touch file.txt; git add file.txt; git commit -m "Add file"'

adamwathan

<snippet>
    <content><![CDATA[
public function ${1:relationship}()
{
    return \$this->belongsToMany(${1/^(.+)$/(?1\u$1:)/g}::class, {$2:table});
}
]]></content>
    <!-- Optional: Set a tabTrigger to define how to trigger the snippet -->
    <tabTrigger>belt</tabTrigger>
    <!-- Optional: Set a scope to limit where the snippet will trigger -->

d2s

Installing Node.js with nvm to Linux & macOS & WSL

A quick guide on how to setup Node.js development environment.

Install nvm for managing Node.js versions

nvm allows installing several versions of Node.js to the same system. Sometimes applications require a certain versions of Node.js to work. Having the flexibility of using specific versions can help.

1. Open new Terminal window.

benlinton

Multiple MySQL Versions for Development

Options included below:

• Using Docker docker-compose
• Using Homebrew brew

Using Docker (recommended)

This gist was originally created for Homebrew before the rise of Docker, yet it may be best to avoid installing mysql via brew any longer. Instead consider adding a barebones docker-compose.yml for each project and run docker-compose up to start each project's mysql service.