Configuring the tooling for React is the biggest hurdle.
create react app is the easiest entry point to getting the tooling correct for a react app. You can eject later if you want advanced configuration.
npm install -g create-react-app
import java.util.*; | |
public class MineFieldMapper { | |
public List<String> map(List<String> mineField) { | |
if (mineField.size() == 3) { | |
return Arrays.asList("1", "*", "1"); | |
} | |
String s = mineField.get(0); |
import java.util.AbstractMap.SimpleEntry; | |
import java.util.*; | |
import java.util.stream.Collectors; | |
import java.util.stream.Stream; | |
class Balance { | |
String hello = "hello"; | |
List<String> beginnings = Arrays.asList("[", "(", "{"); | |
Map<String, String> endingsToBeginnings = Collections.unmodifiableMap(Stream.of( | |
new SimpleEntry<>("]", "["), |
Configuring the tooling for React is the biggest hurdle.
create react app is the easiest entry point to getting the tooling correct for a react app. You can eject later if you want advanced configuration.
npm install -g create-react-app
#!/bin/bash | |
#Jenkins provides: | |
#GIT_COMMIT like ce9a3c1404e8c91be604088670e93434c4253f03 | |
#GIT_BRANCH like origin/master | |
#BUILD_URL like http://jenkins.test.cirrostratus.org/job/Article_View_c20n_Full_Non_Destructive_Full_Suite/1334/ | |
# per https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin | |
# The jenkins pull request builder plugin (if configured) will provide these: | |
#ghprbPullId |
We Code Review after each story, and I use them as a place to have discussions where we have the opportunity to learn from one another.
I trust the other developers on my team, especially since they will have more context on their own work, so anything I suggest is merely a suggestion, and so I always "Approve" my github review. I give them the benefit of the doubt that if I point out something, it is more than likely I misunderstood.
It is entirely reasonable for people to use their discretion to disagree with or defer my suggestions for improvement.
Browser Type | Clean | Clean | Suspect | Suspect |
---|---|---|---|---|
PerimeterX Mode | Monitor | Blocking | Monitor | Blocking |
Excelsior Restarts | 1 | 1? | 2 | 3(+?) |
PerimeterX Restarts | 0 | 0? | 1 | 0 |
Enterprise SW | Internet Companies | ||
---|---|---|---|
biggest problem: | complexity of domain | biggest problem: | volume of data |
leads to: | business logic | leads to: | complexity of data infrastructure |
solution: | Event Sourcing | solution: | Stream Processing |
From Martin Kleppman's Event Sourcing and Stream Processing at Scale from Domain-Driven Design Europe 2016 presentation
Stream Processing, Event Sourcing, Reactive, CEP... and making sense of it all
This is just a picture of this link from Feb 4, 2017
#!/usr/bin/env python | |
import boto3 | |
from datetime import datetime | |
import json | |
import sys | |
import re | |
def json_serial(obj): | |
"""JSON serializer for objects not serializable by default json code""" |