mala

noteとインシデントハンドリングと広報の仕事

前提

• この文章はmalaが書いています。個人の見解であり所属している企業とは関係ありません。
• noteには知り合いが何人かいるし、中の人と直接コンタクトも取っているし相談もされているが、(10月2日時点で)正規の仕事としては請け負っていない。

10月2日追記

• 正規の仕事として請け負う可能性もありますが、自身の主張や脆弱性情報の公開に制限が掛かるのであれば引き受けないつもりです。

tcnksm

• Kubernetes
  • Kubernetes: Up and Running, 2nd Edition
  • Managing Kubernetes
  • Programming Kubernetes
  • Cloud Native Infrastructure
  • Container Security
• SRE
  • Systems Performance
  • The Site Reliability Workbook
• Designing Data-Intensive Applications

tcnksm

Terraform at Mercari

2019-11-07

State of Terraform usage

All microservices-related tf codes are in one single repository

• Mercari JP and US are separated (but thinking to merge in the future)
• We have different repository for

tcnksm

• Kubernetes
  • Kubernetes: Up and Running
  • Managing Kubernetes
  • Programming Kubernetes
  • Cloud Native Infrastructure
• SRE
  • Systems Performance
  • Designing Distributed Systems
  • Site Reliability Engineering
• The Site Reliability Workbook

LouisCAD

/*
 * Copyright 2019 Louis Cognault Ayeva Derman. Use of this source code is governed by the Apache 2.0 license.
 */

import android.location.Location
import com.google.android.gms.location.LocationCallback
import com.google.android.gms.location.LocationRequest
import com.google.android.gms.location.LocationResult
import com.google.android.gms.location.LocationServices
import kotlinx.coroutines.CancellationException

hrach

import kotlinx.coroutines.experimental.*
import kotlinx.coroutines.experimental.channels.ReceiveChannel
import kotlinx.coroutines.experimental.channels.consumeEach
import kotlinx.coroutines.experimental.channels.produce
import kotlin.coroutines.experimental.CoroutineContext

fun <E> ReceiveChannel<E>.debounce(
    wait: Long = 50,
    context: CoroutineContext = DefaultDispatcher
): ReceiveChannel<E> = produce(context) {

mtei

Helix キーボードキットの製作に必要な工具メモ

目次

• 最低必要な工具
  • 温度調整機能付きハンダゴテ
  • コテ台
  • コテ先
  • ハンダ
  • 精密ピンセット
• フラックス

elizarov

import kotlinx.coroutines.experimental.DefaultDispatcher
import kotlinx.coroutines.experimental.channels.ReceiveChannel
import kotlinx.coroutines.experimental.channels.consumeEach
import kotlinx.coroutines.experimental.channels.produce
import kotlinx.coroutines.experimental.delay
import kotlinx.coroutines.experimental.runBlocking
import kotlin.coroutines.experimental.CoroutineContext

fun <T> ReceiveChannel<T>.debounce(
    wait: Long = 300,

posener

Function Failure Reporting: Error or OK

Go's "multiple return values" feature, can be used for several purposes. Among them for failure reporting to the function caller. Go has two conventions for failure reporting, but currently, no clear convention for which to use when. I've encountered different programmers that prefer different choices in different cases. In this article, we will discuss the two, and try to make the process of choosing our next function signature more conscious.

The Basics

julie-is-late

package config

import (
	"crypto/rand"
	"crypto/rsa"
	"crypto/x509"
	"encoding/pem"
	"io/ioutil"

	"github.com/CodeCollaborate/Server/utils"