chrismo

git clone https://gist.github.com/b35434593e06fe4a2ea6eca13e4786da.git
cd b35434593e06fe4a2ea6eca13e4786da
./install-superdb.sh
./configure-claude.sh

thesuhu

How to Build and Install Latest cURL Version on Ubuntu

# Written by The Suhu (2021).

# Tested on Ubuntu 20.04 LTS

The default cURL installed on the operating system may not be the latest version. if you want the latest version, then you need to build from the source. Let's check the cURL version installed with the following command.

tuannvm

#### first class expresssion
variable "ami" {}
resource "aws_instance" "example" {
  ami           = var.ami
}

#### list & map
resource "aws_instance" "example" {
  vpc_security_group_ids = var.security_group_id != "" ? [var.security_group_id] : []
}

olih

Processing JSON using jq

jq is useful to slice, filter, map and transform structured json data.

Installing jq

On Mac OS

brew install jq

chrismo

Greg Vaughn posted this cool alias the other day:

copr = "!f() { git fetch -fu origin refs/pull/$1/head:pr-$1; git checkout pr-$1; } ; f"

Preferring to be a stock-tools person, I wanted to deconstruct this to see how I'd use it off-the-shelf without the alias.

git fetch     -- I'm already familiar with this command
-fu           -- these two flags I'm not sure are necessary, esp. -u since the help says, 
 "unless you are implementing your own Porcelain you are not supposed to use 

chrismo

As the domain logic gets more complicated and you begin moving toward a
rich Domain Model (116), the simple approach of an Active Record (160)
starts to break down. The one-to-one match of domain classes to tables
starts to fail as you factor domain logic into smaller classes.
Relational databases don't handle inheritance, so it becomes difficult
to use strategies [Gang of Four] and other neat OO patterns. As the
domain logic gets feisty, you want to be able to test it without having
to talk to the database all the time.

Fowler, Martin (2002-11-05). Patterns of Enterprise Application

glv

Trouble-Free Bundler

Every couple of weeks, I hear someone complaining about some difficulties with Bundler. Yesterday, it happened twice. But somehow I just never have those difficulties. I'm not saying Bundler is perfect; certainly in its early days it wasn't even close. But for the past two years it's been incredibly solid and trouble-free for me, and I think a large part of the reason is the way I use it. Bundler arguably does too much, and just as with Git, a big part of it is knowing what not to do, and configuring things to avoid the trouble spots.

JEG2

How Should We Use Struct?

The Choice

It's common in Ruby to see some code setup a Struct like this:

class Specialized < Struct.new(:whatever)
  # ... define custom methods here...
end

protocool

/*
  As of version 1.1.2, Propane will load and execute the contents of
  ~Library/Application Support/Propane/unsupported/caveatPatchor.js
  immediately following the execution of its own enhancer.js file.

  You can use this mechanism to add your own customizations to Campfire
  in Propane.

  Below you'll find two customization examples.

netzpirat

Continuous CoffeeScript testing with Guard and Jasmine

This Gist shows how to set up a Rails project to practice BDD with CoffeeScript, Guard and Jasmine. You can see this setup in action on Vimeo

• Install Gems with Bundler with bundle install
• Define your guards with mate Guardfile
• Initialize Jasmine with bundle exec jasmine init
• Configure Jasmine with mate spec/support/yasmine.ym
• Start Guard with bundle exec guard