Jesus Bello jesusbello

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

SUIT CSS naming conventions + SUIT CSS design principles;
PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
Flexbox is awesome. No need for grid framework;
Normalize.css, base styles and variables are solid foundation for all components;

How to setup AWS lambda function to talk to the internet and VPC

I'm going to walk you through the steps for setting up a AWS Lambda to talk to the internet and a VPC. Let's dive in.

So it might be really unintuitive at first but lambda functions have three states.

No VPC, where it can talk openly to the web, but can't talk to any of your AWS services.
VPC, the default setting where the lambda function can talk to your AWS services but can't talk to the web.
VPC with NAT, The best of both worlds, AWS services and web.

These links no longer work. Springer have pulled the free plug.

Graduate texts in mathematics

duplicates = multiple editions

A Classical Introduction to Modern Number Theory, Kenneth Ireland Michael Rosen

NVD3 (http://nvd3.org/)
- Initial evaluation: seems the most mature. Apparently, has bad documentation, and is hard to use without going to its source code.
dimple (http://dimplejs.org/)
- Initial evaluation: its main goal is to offer a simple API to create charts
C3.js (http://c3js.org/)
- Initial evaluation: highly customizable charting API.
xCharts (http://tenxer.github.io/xcharts/)
- Initial evaluation: "designed to be dynamic, fluid, and open to integrations and customization" seems to have a rather complex API though
Vega (http://trifacta.github.io/vega/)
Initial evaluation: intends to generate data visualizations from a JSON document. Charts can be generated server-side. Has an online editor http://trifacta.github.io/vega/editor/

Abstraction Suggestions

Summary: use good/established messaging patterns like Enterprise Integration Patterns. Don't make up your own. Don't expose transport implementation details to your application.

Broker

As much as possible, I prefer to hide Rabbit's implementation details from my application. In .Net we have a Broker abstraction that can communicate through a lot of different transports (rabbit just happens to be our preferred one). The broker allows us to expose a very simple API which is basically:

publish
request
start/stop subscription

303 See Other

Location: https://github.com/wsargent/docker-cheat-sheet

Hi there!

The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.

Please click on the link above to go to the cheat sheet.

	# npm publish with goodies
	# prerequisites:
	# `npm install -g trash conventional-recommended-bump conventional-changelog conventional-github-releaser conventional-commits-detector json`
	# `np` with optional argument `patch`/`minor`/`major`/`<version>`
	# defaults to conventional-recommended-bump
	# and optional argument preset `angular`/ `jquery` ...
	# defaults to conventional-commits-detector
	np() {
	travis status --no-interactive &&
	trash node_modules &>/dev/null;

	/*
	********************************************************************************
	Golang - Asterisk and Ampersand Cheatsheet
	********************************************************************************

	Also available at: https://play.golang.org/p/lNpnS9j1ma

	Allowed:
	--------
	p := Person{"Steve", 28} stores the value

	'use strict';
	/**
	* Implementing main examples from Martin Fowler article
	* on Collection Pipeline programming pattern:
	* http://martinfowler.com/articles/collection-pipeline/
	* with #javascript and underscore.js: http://underscorejs.org/
	*
	* tested with nodejs v0.10.32
	*
	* underscore.js is required:

	#!/bin/bash
	### BEGIN INIT INFO
	# Provides: kibana
	# Required-Start: $remote_fs $syslog
	# Required-Stop: $remote_fs $syslog
	# Default-Start: 2 3 4 5
	# Default-Stop: 0 1 6
	# Short-Description: Make sense of a mountain of logs.
	### END INIT INFO