- Concorrência
- Scheduler
- internals (semantics)
- Deadlocks, Livelocks e starvation
- O que é CSP?
const ethUtil = require('ethereumjs-util'); | |
const abi = require('ethereumjs-abi'); | |
const chai = require('chai'); | |
const typedData = { | |
types: { | |
EIP712Domain: [ | |
{ name: 'name', type: 'string' }, | |
{ name: 'version', type: 'string' }, | |
{ name: 'chainId', type: 'uint256' }, |
require 'json' | |
require 'bundler/inline' | |
gemfile do | |
source 'https://rubygems.org' | |
gem 'faraday' | |
end |
(I'm enjoying doing these raw, barely edited writeups; I hope they're useful to you too)
This is my own writeup on feature flags; for a deep dive I'd recommend something like Martin Fowler's article (https://martinfowler.com/articles/feature-toggles.html).
So. Feature flags. The basic idea that you'll store configuration/values on a database/service somewhere, and by changing those values, you can change the user experience/features for a user on the fly.
Let's say that you're building a new feature, called 'new-button' which changes the color of buttons, which is currently red, to blue. Then you'd change code that looks like this -
" Specify a directory for plugins | |
call plug#begin('~/.vim/plugged') | |
Plug 'neoclide/coc.nvim', {'branch': 'release'} | |
Plug 'scrooloose/nerdtree' | |
"Plug 'tsony-tsonev/nerdtree-git-plugin' | |
Plug 'Xuyuanp/nerdtree-git-plugin' | |
Plug 'tiagofumo/vim-nerdtree-syntax-highlight' | |
Plug 'ryanoasis/vim-devicons' | |
Plug 'airblade/vim-gitgutter' |
Some thoughts on monitoring.
Source Documents:
- https://docs.google.com/document/d/1x-frPXiGRXeJp8f-asp0LVdSoM1IAXEKSlPuYvD30fw/edit
- https://www.bigpanda.io/resource-library/monitoringscape/
- https://engineering.salesforce.com/monitoring-microservices-divide-and-conquer-acca62b209cc
- https://www.circonus.com/2018/06/comprehensive-container-based-service-monitoring-with-kubernetes-and-istio/
- https://www.vividcortex.com/blog/monitoring-and-observability-with-use-and-red
#!/bin/sh | |
# start a neo4j docker container with apoc and bloom (server variant) configured | |
# this requires to have | |
# * curl, unzip and jq being installed | |
# * having a valid bloom license file | |
# released under the WTFPL (http://www.wtfpl.net/) | |
# (c) Stefan Armbruster |
//Golang doesn't have python-Django like decorators but here is | |
//a small example of what you can do | |
package main | |
import "github.com/gin-gonic/gin" | |
func Handler(h gin.HandlerFunc, decors ...func(gin.HandlerFunc)gin.HandlerFunc) gin.HandlerFunc { | |
for i := range decors { |
For a brief user-level introduction to CMake, watch C++ Weekly, Episode 78, Intro to CMake by Jason Turner. LLVM’s CMake Primer provides a good high-level introduction to the CMake syntax. Go read it now.
After that, watch Mathieu Ropert’s CppCon 2017 talk Using Modern CMake Patterns to Enforce a Good Modular Design (slides). It provides a thorough explanation of what modern CMake is and why it is so much better than “old school” CMake. The modular design ideas in this talk are based on the book [Large-Scale C++ Software Design](https://www.amazon.de/Large-Scale-Soft
const FullHeightPage = () => ( | |
<div> | |
Hello World! | |
<style global jsx>{` | |
html, | |
body, | |
body > div:first-child, | |
div#__next, | |
div#__next > div { | |
height: 100%; |