Diky Arga dikyarga

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

Default

Powerlevel10k

Reference: RFC 2616 - HTTP Status Code Definitions

General

400 BAD REQUEST: The request was invalid or cannot be otherwise served. An accompanying error message will explain further. For security reasons, requests without authentication are considered invalid and will yield this response.
401 UNAUTHORIZED: The authentication credentials are missing, or if supplied are not valid or not sufficient to access the resource.
403 FORBIDDEN: The request has been refused. See the accompanying message for the specific reason (most likely for exceeding rate limit).
404 NOT FOUND: The URI requested is invalid or the resource requested does not exists.
406 NOT ACCEPTABLE: The request specified an invalid format.

SIM Card Management Over GSM Modem

A small guide on how to send and receive USSD codes on Linux

I am using the built in GSM (UMTS) modem of my Thinkpad X1 extensively because I am often in places with flaky internet connections. I connect through the standard Network Manager on Ubuntu and everything works fine. There was one major annoyance though. Every time I wanted to top up the SIM balance or book a new package, I needed a phone to send and receive USSD codes. So I took some time to figure out how to do it from the shell. I wrote this down as a help for others and a reminder for myself. Without further ado...

First intsall gammu and picocom.

➜  ~  sudo apt-get install -y gammu picocom

Create a new repository, or reuse an existing one.

Generate a new SSH key:

ssh-keygen -t rsa -C "[email protected]"

Copy the contents of the file ~/.ssh/id_rsa.pub to your SSH keys in your GitHub account settings (https://github.com/settings/keys).

Test SSH key:

The Ultimate Unit Testing Cheat-sheet

Sinon Chai
Chai
Sinon

Moving to ES6 from CoffeeScript

I fell in love with CoffeeScript a couple of years ago. Javascript has always seemed something of an interesting curiosity to me and I was happy to see the meteoric rise of Node.js, but coming from a background of Python I really preferred a cleaner syntax.

In any fast moving community it is inevitable that things will change, and so today we see a big shift toward ES6, the new version of Javascript. It incorporates a handful of the nicer features from CoffeeScript and is usable today through tools like Babel. Here are some of my thoughts and issues on moving away from CoffeeScript in favor of ES6.

While reading I suggest keeping open a tab to Babel's learning ES6 page. The examples there are great.

Punctuation

Holy punctuation, Batman! Say goodbye to your whitespace and hello to parenthesis, curly braces, and semicolons again. Even with the advanced ES6 syntax you'll find yourself writing a lot more punctuatio

	/**
	* Simple node_acl example with mongoDB and expressjs
	*
	* Usage:
	* 1. Start this as server
	* 2. Play with the resoures
	*
	* Show all permissions (as JSON)
	* http://localhost:3500/info
	*

	/*

	This example shows how you can use your data structure as a basis for
	your Firebase security rules to implement role-based security. We store
	each user by their Twitter uid, and use the following simplistic approach
	for user roles:

	0 - GUEST
	10 - USER
	20 - MODERATOR

	#!/usr/bin/env sh

	# checks to see if running
	launchctl list \| grep elasticsearch

	launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.elasticsearch.plist
	launchctl remove homebrew.mxcl.elasticsearch

	pkill -f elasticsearch