Paul Tannenbaum paultannenbaum

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;

Learning Erlang / Elixir Basics

Primitives

Erlang only has a few primitives that you need to worry about. Here they are below with corresponding Elixir examples.

integer: Erlang: 123, Elixir: 123
float: Erlang: 123.5, Elixir: 123.5
atom: Erlang: hello, Elixir: :hello
binary: Erlang: <<"hello">> or <<10,20>>, Elixir: "hello" or <<10,20>>

A composable pattern for pure state machines with effects

State machines are everywhere in interactive systems, but they're rarely defined clearly and explicitly. Given some big blob of code including implicit state machines, which transitions are possible and under what conditions? What effects take place on what transitions?

There are existing design patterns for state machines, but all the patterns I've seen complect side effects with the structure of the state machine itself. Instances of these patterns are difficult to test without mocking, and they end up with more dependencies. Worse, the classic patterns compose poorly: hierarchical state machines are typically not straightforward extensions. The functional programming world has solutions, but they don't transpose neatly enough to be broadly usable in mainstream languages.

Here I present a composable pattern for pure state machiness with effects,

This write up was based on Henrik's gist

Create server

Create a droplet on digital ocean. Use my referal link for $10 credit. I also credit if you spend money, so thanks in advance ;)
1. Select "Create Droplet"
2. Under "Choose an image", click on "One-click Apps"
3. Select Dokku for your app
4. Under "Choose a size" select at least 1GB of RAM
5. Add your ssh public key
Click "Create"

React (Virtual) DOM Terminology

In React's terminology, there are five core types that are important to distinguish:

ReactElement / ReactElement Factory
ReactNode
ReactComponent / ReactComponent Class

React Elements

	///// SERVICE

	import { Injectable } from '@nestjs/common';
	import * as Sentry from '@sentry/node';
	import config from '../../config';
	import { SentryEntry } from './sentry.interceptor';

	@Injectable()
	export class SentryService {
	private isInit = false;

	import { Module } from '@nestjs/common';

	import { HttpModule } from './http/http.module';
	import { FooModule } from './foo/foo.module';

	@Module({
	imports: [
	HttpModule,
	FooModule, // <- we'll make use of the "augmented" HttpService in this module
	],

	# Step 1

	def create_subscription(email, plan_id, payment_method_id) do
	with %User{customer_id: nil, name: name} = user <-
	Repo.get_by(User, email: email),
	{:ok, %Stripe.Customer{id: customer_id}} <-
	Stripe.Customer.create(%{
	name: name,
	email: email,
	payment_method: payment_method_id,

	/*
	This example was built using standard create-react-app out of the box with no modifications or ejections
	to the underlying scripts.

	In this example, i'm using Google as a social provider configured within the Cognito User Pool.

	Each step also represents a file, so you can see how I've chosen to organize stuff...you can do it however
	you'd like so long as you follow the basic flow (which may or may not be the official way....but its what I found that works.
	The docs are pretty horrible)

	import Ember from 'ember';

	export default Ember.Component.extend({
	didInitAttrs(options) {
	console.log('didInitAttrs', options);
	},

	didUpdateAttrs(options) {
	console.log('didUpdateAttrs', options);
	},