twalker

Getting Started

Enclosed is your custom built Lily58 keyboard.

1. Connect the halves together with the TRRS cable.
2. Connect a USB-C cable between the left half and your computer.
3. Type.

twalker

Getting Started

Enclosed is your custom built wireless Lily58 keyboard.

1. Turn on ("Right on, Left off.") each of the two halves using the small toggle under the USB-C port.
2. The keyboard should appear in bluetooth settings as "Lily58". Connect to it to pair your computer with the keyboard. Alternatively, connect a USB-C cable between the left half and your computer.
3. Type and turn knobs!

The default Lily58 keymap has been flashed onto the keyboard.

twalker

EJC adjusted                                                                                              
,-----------------------------------------.                    ,-----------------------------------------.
| ESC  |   1  |   2  |   3  |   4  |   5  |                    |   6  |   7  |   8  |   9  |   0  |  -   |
|------+------+------+------+------+------|                    |------+------+------+------+------+------|
| Tab  |   Q  |   W  |   E  |   R  |   T  |                    |   Y  |   U  |   I  |   O  |   P  |  '   |
|------+------+------+------+------+------|                    |------+------+------+------+------+------|
|LCTRL |   A  |   S  |   D  |   F  |   G  |-------.    ,-------|   H  |   J  |   K  |   L  |   ;  | Enter|
|------+------+------+------+------+------|   [   |    |    ]  |------+------+------+------+------+------|
|LShift|   Z  |   X  |   C  |   V  |   B  |-------|    |-------|   N  |   M  |   ,  |   .  |   /  |RShift|

twalker

tw2k's base keymap

legend

abbreviation	definition
CDH	base layer
MAC	Macros one-shot layer
#	numbers layer
ESC$	escape on tap, symbols layer on hold

twalker

{"version":1,"resource":"file:///Users/timwalker/projects/zmk-crkbd/.github/workflows/build.yml","entries":[{"id":"KEcD.yml","timestamp":1649020939184}]}

twalker

Choose your ergonomic keyboard

I plan to build a custom ergonomic mechanical keyboard for you. We want it to fit you so well it becomes a joy to type.

Choose your board

Name	# of keys**	Number row	Column stagger	Notes

twalker

Favorite Metal Bands

1. Slayer
2. Gojira
3. Megadeth
4. Voivod
5. King Diamond
6. Sepultura
7. Nevermore
8. Prong

twalker

#cloud-config
package_upgrade: true
write_files:
  - path: /etc/systemd/system/docker.service.d/docker.conf
    content: |
      [Service]
        ExecStart=
        ExecStart=/usr/bin/dockerd
  - path: /etc/docker/daemon.json
    content: |

twalker

Problem

A hard dependency on redis servers being available, with no way to implement a fallback if they're not.

The refresh token requests are dependent on our redis servers being available to store tokens (#3237) . If the redis server is down, refresh token requests will not complete. PR: https://scm.starbucks.com/starbucks-web/core/pull/3469

Solution

Inform consumers of the redis being in a faulted state (cannot connect, redis crashed, redis out of memory, servers not available, etc.), so they can implement a fallback strategy. e.g. If redis is down, go directly to the api for data that was expected to be in cache.

Demo

twalker

                        dispatch(action)                     (state, action)
+-------------+ data +------------+      +------------+ +--> +------------+
| gql/bff api | +--> | Action     | +--> | Store      |      | Reducers   |
+------^------+      | Creators   |      +-----+------+ <--+ +------------+
       |             +------------+ <-+        |             (newState)
       +--------+ fetch(url, query)   |        |
                                      |     connect
                                      |        |
                                      |        |
                                      |  +-----v------+