Imran Ansari imranansari

Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.

For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.

But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.

SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil

Screencapture and animated gifs

I say "animated gif" but in reality I think it's irresponsible to be serving "real" GIF files to people now. You should be serving gfy's, gifv's, webm, mp4s, whatever. They're a fraction of the filesize making it easier for you to deliver high fidelity, full color animation very quickly, especially on bad mobile connections. (But I suppose if you're just doing this for small audiences (like bug reporting), then LICEcap is a good solution).

Capturing (Easy)

Launch quicktime player
do Screen recording

Maintaining a resilient front door at massive scale, from Netflix

Netflix is responsible for about 1/3 of downstream traffic in NA
Responsible team in the company is called "edge engineering"
- Apart from resiliency/scaling, also cares about high velocity product innovation and real time health insights
Basic architecture:
- end-user devices make requests to ELBs, which delegates to zuul, which routes to origin servers serving APIs

Trello CSS Guide

“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”

You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?

This is where any fun you might have been having ends. Now it’s time to get serious and talk about rules.

Writing CSS is hard. Even if you know all the intricacies of position and float and overflow and z-index, it’s easy to end up with spaghetti code where you need inline styles, !important rules, unused cruft, and general confusion. This guide provides some architecture for writing CSS so it stays clean and ma

	/**
	* # Global logging module
	*
	* This is a global set of hooks that catch all $log messages sent out by the
	* application. Currently they are simply passed off directly to console.log
	* but this could be updated later to allow them to be stored locally, sent to
	* a server etc.
	*/

	angular.module('ngLogging', [])

	# TouchID

	http://www.andreas-kurtz.de/2014/10/ios-8-touch-id-local-authentication-caveats.html

	If Touch ID authentication is to be continued, perhaps it would be worth taking a look at the keychain access control lists (ACL),
	a new concept that was introduced in iOS 8. The attribute kSecAttrAccessControl can be used to define that keychain entries can be decrypted only if the user has again been authenticated using the device passcode or Touch ID (kSecAccessControlUserPresence).
	In such cases, the Touch ID login would be more than just a worthless view. Instead, it could actually grant access to cryptographic keys.
	As, however, the keys would still be stored on the device (although in the keychain), this is merely a compromise, albeit one which could
	actually provide added value (ACL protected items are not backed up). From a security perspective, however, entering a password is still
	recommended.

	+(BOOL)isJailbroken{

	#if !(TARGET_IPHONE_SIMULATOR)

	if ([[NSFileManager defaultManager] fileExistsAtPath:@"/Applications/Cydia.app"]){
	return YES;
	}else if([[NSFileManager defaultManager] fileExistsAtPath:@"/Library/MobileSubstrate/MobileSubstrate.dylib"]){
	return YES;
	}else if([[NSFileManager defaultManager] fileExistsAtPath:@"/bin/bash"]){
	return YES;

	BOOL isDeviceJailbroken()
	{

	#if !TARGET_IPHONE_SIMULATOR

	//Apps and System check list
	BOOL isDirectory;
	if ([[NSFileManager defaultManager] fileExistsAtPath:[NSString stringWithFormat:@"/%@%@%@%@%@%@%@", @"App", @"lic",@"ati", @"ons/", @"Cyd", @"ia.a", @"pp"]]
	\|\| [[NSFileManager defaultManager] fileExistsAtPath:[NSString stringWithFormat:@"/%@%@%@%@%@%@%@", @"App", @"lic",@"ati", @"ons/", @"bla", @"ckra1n.a", @"pp"]]
	\|\| [[NSFileManager defaultManager] fileExistsAtPath:[NSString stringWithFormat:@"/%@%@%@%@%@%@%@", @"App", @"lic",@"ati", @"ons/", @"Fake", @"Carrier.a", @"pp"]]

	// Use Gists to store code you would like to remember later on
	console.log(window); // log the "window" object to the console