Jon Wicks jwicks

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

I heard from GitHub Two-Factor Authentication](https://github.com/blog/1614-two-factor-authentication) nearly a couple of days ago when I was reading my RSS feed. I enabled it and couldn' push to any of my repositories anymore. Learn in this blog post how to fix it.

Two-Factor Authentication

"Is a process involving two stages to verify the identity of an entity trying to access services in a computer or in a network". Github solves this authentication with sending an SMS to a device which wants to push to their platform.

Enabling Two-Factor Authentication

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;

We have a process that spawns lots of lambdas that we were worried might hit a concurrency limit. We wanted to know what a step function would do in that situation because the AWS documentation says that poll-based services have a built-in retry mechanism if lambdas are throttled and we were hoping that the subsequent steps would simply wait until there was enough capacity.

So I built a step function with three steps that had a sleep in them, and then set the reserve concurrency to 1 for the middle step. Then I kicked off three step functions at the same time.

The result was the second intance of the step function failed on the throttled lamda with the error message: "Lambda.TooManyRequestsException"

There are retry options in step functions, but it is interesting to know that they don't wait for a lambda slot to be available.

	application: you-app-name-here
	version: 1
	runtime: python
	api_version: 1

	default_expiration: "30d"

	handlers:
	- url: /(.*\.(appcache\|manifest))
	mime_type: text/cache-manifest

	'''
	Taken from: https://code.djangoproject.com/ticket/17561#comment:7
	'''

	from django.db import models


	class EmailField(models.EmailField):
	def get_prep_value(self, value):
	value = super(EmailField, self).get_prep_value(value)

	## MIT License
	##
	## Copyright (c) 2017 Carl Gieringer
	##
	## Permission is hereby granted, free of charge, to any person obtaining a copy
	## of this software and associated documentation files (the "Software"), to deal
	## in the Software without restriction, including without limitation the rights
	## to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
	## copies of the Software, and to permit persons to whom the Software is
	## furnished to do so, subject to the following conditions: