See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope>
is optional
// Framework print grid generation (for v4.0.0-beta.2) | |
// | |
// Used only to generate the correct number of grid classes given | |
// any value of `$grid-columns`. | |
// import bootstrap prior to this mixin to set the various variables and mixins needed/used. | |
@mixin make-print-grid-columns($columns: $grid-columns, $gutter: $grid-gutter-width, $name: "pr") { | |
@media print { | |
// Common properties | |
%grid-column-print { |
I've been interested in Command Query Responsibility Segregation and event sourcing since hearing Greg Young talk on the subject in early 2010. During the past seven years I've built an open-source Ruby CQRS library (rcqrs); worked professionally on .NET applications following the pattern; and more recently built an Event Store (eventstore) and CQRS library (commanded) in Elixir.
Building applications following domain-driven design and using CQRS feels really natural with the Elixir -- and Erlang -- actor model. An aggregate root fits well within an Elixir process, which are driven by immutable messages through their own message mailboxes, allowing them to run concurrently and in isolation.
The web application I built to implement these ideas in Elixir was [Segment Challen
{ | |
"AWSEBDockerrunVersion": "1", | |
"Image": { | |
"Name": "<AWS_ACCOUNT_ID>.dkr.ecr.us-east-1.amazonaws.com/<NAME>:<TAG>", | |
"Update": "true" | |
}, | |
"Ports": [ | |
{ | |
"ContainerPort": "443" | |
} |
#!/usr/bin/env python | |
#-*- coding: utf-8 -*-# | |
import smtplib, time, urllib2 | |
from bs4 import BeautifulSoup | |
from email.mime.text import MIMEText | |
def mailme(message): | |
msg = MIMEText(message) | |
msg['Subject'] = 'German Consu Termin!' | |
msg['From'] = '[email protected]' |