Julian Macmang sbpipb

Faster Rails tests

Feedback loop speed in one of the biggest contributing factors to overall development time. The faster you get results, the faster you can move on to other things. A fast enough test suite is therefore critical to teams' success, and is worth investing some time at the beginning to save in the long run.

Below is a list of techniques for speeding up a Rails test suite. It is not comprehensive, but should definitely provide some quick wins. This list of techniques assumes you're using minitest, but most everything should translate over to rspec by simply replacing test/test_helper.rb with spec/spec_helper.rb.

Lead with data
bcrypt
bootsnap
Cache Time::utc calls

Restore the GRUB Bootloader on Manjaro

Chroot into your linux instalation
1. The easiest way is with mhwd-chroot
  1. Install it yaourt -S mhwd-chroot
  2. Run it sudo mhwd-chroot
  3. DONE, you have chrooted into your linux installation (open a root console of your installed linux OS, is like just open a console with root access)
Restore your GRUB
1. Install a new GRUB bootloader with grub-install /dev/sda
Recheck to ensure the that installation has completed without any errors grub-install --recheck /dev/sda

Mac OS : Show your git branch name on your bash terminal

⚠️ Does not work in zsh terminal

Add these lines in your ~/.bash_profile file

# Show current git branch name
parse_git_branch() {
     git branch 2> /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/ (\1)/'
}

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

	" Specify a directory for plugins
	call plug#begin('~/.vim/plugged')

	Plug 'neoclide/coc.nvim', {'branch': 'release'}
	Plug 'scrooloose/nerdtree'
	"Plug 'tsony-tsonev/nerdtree-git-plugin'
	Plug 'Xuyuanp/nerdtree-git-plugin'
	Plug 'tiagofumo/vim-nerdtree-syntax-highlight'
	Plug 'ryanoasis/vim-devicons'
	Plug 'airblade/vim-gitgutter'

	ActiveAdmin.register Project do

	# Don't forget to add the image attribute (here thumbnails) to permitted_params
	controller do
	def permitted_params
	params.permit project: [:title, :summary, :description, :thumbnail, :date, :url, :client_list, :technology_list, :type_list]
	end
	end

	form do \|f\|

	client = Savon::Client.new do
	# This can be a URL also
	wsdl.document = "/Path/to/your.wsdl"

	# These are optional, only if your WSDL sucks :)
	wsdl.endpoint = "https://your_endpoint"
	wsdl.namespace = "http://your_namespace"

	certs = Akami::WSSE::Certs.new :cert_file => "/path/to/cert.crt", :private_key_file => "/path/to/private/key.pem", :private_key_password => "password"
	wsse.sign_with = Akami::WSSE::Signature.new certs

	#!/bin/sh
	docker images --format '{{.Size}}\t{{.Repository}}\t{{.Tag}}\t{{.ID}}' \| sed 's/ //' \| sort -h -r \| column -t