Skip to content

Instantly share code, notes, and snippets.

Falsehoods programmers believe about prices

  1. You can store a price in a floating point variable.
  2. All currencies are subdivided in 1/100th units (like US dollar/cents, euro/eurocents etc.).
  3. All currencies are subdivided in decimal units (like dinar/fils)
  4. All currencies currently in circulation are subdivided in decimal units. (to exclude shillings, pennies) (counter-example: MGA)
  5. All currencies are subdivided. (counter-examples: KRW, COP, JPY... Or subdivisions can be deprecated.)
  6. Prices can't have more precision than the smaller sub-unit of the currency. (e.g. gas prices)
  7. For any currency you can have a price of 1. (ZWL)
  8. Every country has its own currency. (EUR is the best example, but also Franc CFA, etc.)
##################### mailers/welcome.rb
module MyNamespace::Mailers
class Welcome
include Hanami::Mailer
templates
from 'noreply@bookshelf.org'
to 'user@example.com'
subject 'Welcome to Bookshelf'
##################### mailers/welcome.rb
class Mailers::Welcome
include Hanami::Mailer
templates
from 'noreply@bookshelf.org'
to 'user@example.com'
subject 'Welcome to Bookshelf'
@sugarfree1
sugarfree1 / issue_estimation.sql
Last active June 1, 2016 13:50 — forked from velll/issue_estimation.sql
Issue estimation
-- estimation storage table
CREATE TABLE ISSUE_ESTIMATION(
N_ESTIMATION_ID NUMBER,
VC_PREDICTOR VARCHAR2(64) NOT NULL,
VC_ISSUE VARCHAR2(64) NOT NULL,
N_ESTIMATION NUMBER NOT NULL,
D_ESTIMATION DATE NOT NULL);
ALTER TABLE ISSUE_ESTIMATION
add constraint PK_ISSUE_ESTIMATION primary key (N_ESTIMATION_ID);