Adam Bender bendera

Europe

SkinFlint : Price comparison site which has some nice filtering options per switch type etc. Searches for offers in UK, Germany, Poland and Austria
mykeyboard.eu : Keyboards, keycaps and accessories. Based in Belgium.
candykeys.com : European Store selling Vortex, Leopold, KBP, Anne Pro keyboards, keycap sets and components (ISO + ANSI). Based in Germany, ships to EU.
falba.tech : custom wooden bamboo cases, and some acrylic and carbon ones. Switch packs (65 browns at 48EUR). Other parts for the GH60, Atreus, ErgoDox. Also Microcontrollers, diodes, leds etc.
42keebs.eu - Mostly PCBs, tools and accessories. Located in Czech Republic.
KEYGEM : Switches, Keycaps, lubes, cables, DIY kits and deskmats. Based in Germany, ships to the EU and worldwide.
[Eloquent Clicks - Custom Mechanical Keyboard Store](https://www.eloquen

Falsehoods programmers believe about time

This is a compiled list of falsehoods programmers tend to believe about working with time.

Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.

Falsehoods

There are always 24 hours in a day.
February is always 28 days long.
Any 24-hour period will always begin and end in the same day (or week, or month).

Keepass file format explained

I’m currently working (I’m just at the beginning, and I’m quite slow) on a personal project that will use Keepass files (kdb and kdbx).
I tried to find some documentation about .kdb and .kdbx format, but I didn’t find anything, even in the Keepass official website. I you want to know how these file formats are structured, you must read Keepass’s source code. So I wrote this article that explains how Keepass file format are structured, maybe it will help someone.

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages

Shallow

Real unit test (isolation, no children render)

Simple shallow

Calls:

constructor
render

Update package.json, set version to a prerelease version, e.g. 2.0.0-rc1, 3.1.5-rc4, ...
Run npm pack to create package
Run npm publish <package>.tgz --tag next to publish the package under the next tag
Run npm install --save package@next to install prerelease package

	"workbench.colorCustomizations": {
	// Contrast Colors - The contrast colors are typically only set for high contrast themes. If set, they add an additional border around items across the UI to increase the contrast.
	"contrastActiveBorder": "",
	"contrastBorder": "",
	// Base Colors
	"focusBorder": "",
	"foreground": "",
	"widget.shadow": "",
	"selection.background": "",
	"descriptionForeground": "",

	cd ~
	git clone git@github.com:golang/go.git gotip
	cd gotip/src
	export GOROOT_BOOTSTRAP=/usr/local/go
	env GOOS=linux GOARCH=arm GOARM=7 ./make.bash

	//install dev vesrion of google chrome form https://www.chromium.org/getting-involved/dev-channel
	//install chrome-remote-interface from npm npm install chrome-remote-interface
	const CDP = require('chrome-remote-interface');

	CDP((protocol) => {
	const {Page, Runtime} = protocol;

	// First, need to enable the domains we're going to use.
	Promise.all([
	Page.enable(),

	module.exports = (string) => {
	return string.replace(/([a-z0-9]\|(?=[A-Z]))([A-Z])/g, '$1-$2').toLowerCase();
	};