variable :FORCE_SSL, :boolean, default: '1'

Ruby's keyword args work a little differently than similar implementations (selectors in Objective C, for instance). The value on the right-hand side of the colon is the default, not the local name.

t.datetime :seen_at, default: { expr: 'NOW()' }

Default Values

hash :with_defaults, default: {} do boolean :likes_cookies, default: true end

const debounceFunc = debounce(1000, false, (num) => {    console.log('num:', num);}); // Can also be used like this, because atBegin is false by defaultconst debounceFunc = debounce(1000, (num) => {    console.log('num:', num);});

Looks like the problem is that debounce defaults to waiting for 0 ms ... which is completely useless!

However, in function components there really isn't much need for this pattern since you can just use JS default arguments

But recently I started to think about default values as some sort of a technical debt ... which is not a straight bad thing but something that could provide some "short term financing" get us to survive the project

Right, and if most uses of an FTP service use new FtpService() the one that sets an alternate port will stand out (service.SetPort(12345))

General rules of thumb

The question about default values in general - default return function values, default parameter values, default logic for when something is missing, default logic for handling exceptions, default logic for handling the edge conditions etc.

For a long time I considered default values to be a "pure evil" thing, something that "cloaks the catastrophe" and results in a very hard do find bugs.