Dale Bustad divmain

OverEncrypt

This is a guide that I wrote to improve the default security of my website https://fortran.io , which has a certificate from LetsEncrypt. I'm choosing to improve HTTPS security and transparency without consideration for legacy browser support.

WARNING: if you mess up settings, lose your certificates, or decide to no longer maintain HTTPS certs, these steps can and will make your domain inaccessible.

I would recommend these steps only if you have a specific need for information security, privacy, and trust with your users, and/or maintain a separate secure.example.com domain which won't mess up your main site. If you've been thinking about hosting a site on Tor, then this might be a good option, too.

The best resources that I've found for explaining these steps are https://https.cio.gov , https://certificate-transparency.org , and https://twitter.com/konklone

Tuning Windows 10 for Slow Machines

This guide is for those who dares to install Windows 10 on slow netbooks (1GB of RAM).
Though Windows update program is over, you still may use old Windows product keys from license stickers to install Windows 10 on old machines.

UPD Jan 2019
This article is quite old, some instructions may be obsolete.

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;

Git/Bash/Node/npm on Windows

Update: there's an easier way to do this. Check out my new gist instead.

How I set up my Windows 10 machine for Node development. Time to complete: about 2 hours on a fast connection.

Requirements

Bash, not Windows shell

	'use strict';

	const { createStore, applyMiddleware } = require('./redux');
	const { addActionTakersToStore, addLoggingToStore } = require('./middleware');
	const { EventEmitter } = require('events');

	const {
	isPromise,
	isFunction,
	isObject,

	'use strict';

	/**
	* Dependencies
	*/
	const expect = require('expect');

	/**
	* Factory for creating an effects handling "runtime"
	* that stores a retrievable effects log

	use std::sync::mpsc;
	use std::sync::mpsc::{Receiver, Sender};
	use std::sync::{Arc, Mutex};
	use std::thread;

	fn main() {
	let pool = Arc::new(Pool::new());

	let mut handles = Vec::new();

	# It might work in 4, but I'm not testing there. Lower you'll have to tweak code
	#requires -Version 5.0
	param(
	# Your Live ID for MSDN login
	[Parameter(Mandatory)]
	[PSCredential]
	[System.Management.Automation.CredentialAttribute()]
	$Credential,

	# Pick a browser to use. Defaults to Firefox (which doesn't seem to require an external Driver file)

	#!/bin/bash
	#TODO: you will need to manually get an OS X SDK.

	set -e

	# Install the proper Rust nightly with rustup, and add the OSX target.
	rustup install nightly-`cat rust-nightly-date`
	rustup override add nightly-`cat rust-nightly-date`
	rustup target install x86_64-apple-darwin

	int doubler(int x) {
	return 2 * x;
	}