例文を組み込んだAlfred Workflowを作りました: Alfred Git Commit Message Example
以下転載:
#Database Configuration | |
spring.datasource.url=jdbc:mariadb://localhost:3306/billboard | |
spring.datasource.username=root | |
spring.datasource.password= | |
spring.datasource.driver-class-name=org.mariadb.jdbc.Driver | |
#Hibernate Configuration | |
# Show or not log for each sql query | |
spring.jpa.show-sql=true |
以下転載:
emacs --daemon
to run in the background.
emacsclient.emacs24 <filename/dirname>
to open in terminal
NOTE: "M-m and SPC can be used interchangeably".
C-/
C-?
M-c
2. Upper Case : M-u
M-l
var path = require('path'); | |
var Nightmare = require('nightmare'); | |
var should = require('chai').should(); | |
describe('Nightmare demo', function () { | |
this.timeout(15000); // Set timeout to 15 seconds, instead of the original 2 seconds | |
var url = 'http://localhost:3000'; | |
describe('Start page', function () { |
#The Problem We just described standard design issues you have when you start creating layers of services, DAOs and other components to implement an application. That blog/gist is here.
The goal is to think through some designs in order to develop something useful for an application.
#Working through Layers If you compose services and DAOs the normal way, you typically get imperative style objects. For example, imagine the following:
object DomainObjects {